Code base evolution over time of cloudstack

[Marc-Aurèle Brothier]

Hi everyone,

I thought you might like to have a graphical view of how cloudstack code
has evolved over time. I ran the script
https://github.com/erikbern/git-of-theseus on the project on December 15th
2016.

Cheers,
Marc-Aurèle

[GitHub] cloudstack issue #1450: CLOUDSTACK-9317: Enable/disable static NAT associate...

[jayapalu]

Github user jayapalu commented on the issue:

https://github.com/apache/cloudstack/pull/1450
  
I tested this patch with below steps. It is not removing the ip addresses 
on the VR interface. Some times observed that even there is one ip with static 
nat but the interface got removed.

Steps to test this:
1. Configure additional public subnet  and acquire 4 ip addresses
2. Enabled static nat on the 4 public ip addresses.
3. Go to VR console and see the new public interface created and ips are 
configured on the interface.
4. Disable static on all 4 public addresses (disable from UI  one by one 
quickly)
 expected: inteface should get removed from the VR. But the interface 
is there in VR

In another case in step4 disable static nat on only 3 public ip addresses. 
expected: interface with one ip supposed to be there. But the interface is 
deleted


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1450: CLOUDSTACK-9317: Enable/disable static NAT associate...

[ProjectMoon]

Github user ProjectMoon commented on the issue:

https://github.com/apache/cloudstack/pull/1450
  
@jayapalu Can you post this in the new version of the fix? (And possibly 
re-test, if you were using an older version)


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

FOSDEM 2017 Open Source Conference - Brussels

[Sharan F]

Hello Everyone

This email is to tell you about ASF participation at FOSDEM. The event 
will be held in Brussels on 4^th & 5^th February 2017 and we are hoping 
that many people from our ASF projects will be there.


https://fosdem.org/2017/

Attending FOSDEM is completely free and the ASF will again be running a 
booth there. Our main focus will on talking to people about the ASF, our 
projects and communities.


*_Why Attend FOSDEM?_*
Some reasons for attending FOSDEM are:

1. Promoting your project: FOSDEM has up to 4-5000 attendees so is a
   great place to spread the word about your project
2. Learning, participating and meeting up: FOSDEM is a developers
   conference so includes presentations covering a range of
   technologies and includes lots of topic specific devrooms

_*FOSDEM Wiki *_
A page on the Community Development wiki has been created with the main 
details about our involvement at conference, so please take a look


https://cwiki.apache.org/confluence/display/COMDEV/FOSDEM+2017

If you would like to spend some time on the ASF booth promoting your 
project then please sign up on the FOSDEM wiki page. Initially we would 
like to split this into slots of 3-4 hours but this will depend on the 
number of projects that are represented.


We are also looking for volunteers to help out on the booth over the 2 
days of the conference, so if you are going to be there and are willing 
to help then please add your name to the volunteer list.


_*Project Stickers*_
If you are going to be at FOSDEM and do not have any project stickers to 
give away then we may (budget permitting) be able to help you get some 
printed. Please contact me with your requirements.


_*Social Event*_
Some people have asked about organising an ASF social event / meetup 
during the conference. This is possible but we will need know how many 
people are interested and which date works best. The FOSDEM wiki page 
also contains an 'Arrival / Departure' section so so please add your 
details if you would like to participate.


I hope this helps people see some of the advantages of attending FOSDEM 
and we are looking forward to seeing lots of people there from our ASF 
communities.


Thanks
Sharan

Apache Community Development
http://community.apache.org/

[GitHub] cloudstack pull request #1904: Use latest Nuage client.

[fmaximus]

GitHub user fmaximus opened a pull request:

https://github.com/apache/cloudstack/pull/1904

Use latest Nuage client.

CloudStack root pom change to use Amazon WS 11.1.16
caused our client to fail, as it was depending on classes,
which are not not present anymore.
Latest client version uses Gson instead.

BUG-ID: CLOUDSTACK-9729
Bugfix-for: master

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/fmaximus/cloudstack bugfix/CLOUDSTACK-9729

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1904.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1904


commit ec4216476eb274b970c5e319cae57887f68a45f8
Author: Frank Maximus 
Date:   2017-01-12T13:15:22Z

Use latest Nuage client.

CloudStack root pom change to use Amazon WS 11.1.16
caused our client to fail, as it was depending on classes,
which are not not present anymore.
Latest client version uses Gson instead.

BUG-ID: CLOUDSTACK-9729
Bugfix-for: master




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1888: CLOUDSTACK-9710: Switch to JRE1.8

[blueorangutan]

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1888
  
Trillian test result (tid-780)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 36526 seconds
Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr1888-t780-kvm-centos7.zip
Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py
Intermitten failure detected: 
/marvin/tests/smoke/test_routers_network_ops.py
Intermitten failure detected: /marvin/tests/smoke/test_volumes.py
Test completed. 47 look ok, 2 have error(s)


Test | Result | Time (s) | Test File
--- | --- | --- | ---
test_04_rvpc_privategw_static_routes | `Failure` | 308.92 | 
test_privategw_acl.py
test_01_create_volume | `Error` | 279.75 | test_volumes.py
test_01_vpc_site2site_vpn | Success | 164.76 | test_vpc_vpn.py
test_01_vpc_remote_access_vpn | Success | 80.92 | test_vpc_vpn.py
test_01_redundant_vpc_site2site_vpn | Success | 239.55 | test_vpc_vpn.py
test_02_VPC_default_routes | Success | 436.51 | test_vpc_router_nics.py
test_01_VPC_nics_after_destroy | Success | 862.15 | test_vpc_router_nics.py
test_05_rvpc_multi_tiers | Success | 511.06 | test_vpc_redundant.py
test_04_rvpc_network_garbage_collector_nics | Success | 1406.25 | 
test_vpc_redundant.py
test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | 
Success | 616.92 | test_vpc_redundant.py
test_02_redundant_VPC_default_routes | Success | 737.57 | 
test_vpc_redundant.py
test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | Success | 1320.38 | 
test_vpc_redundant.py
test_09_delete_detached_volume | Success | 151.16 | test_volumes.py
test_08_resize_volume | Success | 161.08 | test_volumes.py
test_07_resize_fail | Success | 156.06 | test_volumes.py
test_06_download_detached_volume | Success | 150.99 | test_volumes.py
test_05_detach_volume | Success | 240.99 | test_volumes.py
test_04_delete_attached_volume | Success | 145.85 | test_volumes.py
test_03_download_attached_volume | Success | 155.99 | test_volumes.py
test_02_attach_volume | Success | 179.78 | test_volumes.py
test_deploy_vm_multiple | Success | 337.28 | test_vm_life_cycle.py
test_deploy_vm | Success | 0.02 | test_vm_life_cycle.py
test_advZoneVirtualRouter | Success | 0.02 | test_vm_life_cycle.py
test_10_attachAndDetach_iso | Success | 26.48 | test_vm_life_cycle.py
test_09_expunge_vm | Success | 125.19 | test_vm_life_cycle.py
test_08_migrate_vm | Success | 35.62 | test_vm_life_cycle.py
test_07_restore_vm | Success | 0.09 | test_vm_life_cycle.py
test_06_destroy_vm | Success | 130.64 | test_vm_life_cycle.py
test_03_reboot_vm | Success | 125.66 | test_vm_life_cycle.py
test_02_start_vm | Success | 10.12 | test_vm_life_cycle.py
test_01_stop_vm | Success | 125.65 | test_vm_life_cycle.py
test_CreateTemplateWithDuplicateName | Success | 90.59 | test_templates.py
test_08_list_system_templates | Success | 0.02 | test_templates.py
test_07_list_public_templates | Success | 0.03 | test_templates.py
test_05_template_permissions | Success | 0.04 | test_templates.py
test_04_extract_template | Success | 5.10 | test_templates.py
test_03_delete_template | Success | 5.08 | test_templates.py
test_02_edit_template | Success | 90.10 | test_templates.py
test_01_create_template | Success | 45.34 | test_templates.py
test_10_destroy_cpvm | Success | 131.24 | test_ssvm.py
test_09_destroy_ssvm | Success | 163.33 | test_ssvm.py
test_08_reboot_cpvm | Success | 131.50 | test_ssvm.py
test_07_reboot_ssvm | Success | 133.05 | test_ssvm.py
test_06_stop_cpvm | Success | 131.62 | test_ssvm.py
test_05_stop_ssvm | Success | 133.19 | test_ssvm.py
test_04_cpvm_internals | Success | 1.18 | test_ssvm.py
test_03_ssvm_internals | Success | 2.93 | test_ssvm.py
test_02_list_cpvm_vm | Success | 0.09 | test_ssvm.py
test_01_list_sec_storage_vm | Success | 0.09 | test_ssvm.py
test_01_snapshot_root_disk | Success | 10.91 | test_snapshots.py
test_04_change_offering_small | Success | 209.26 | test_service_offerings.py
test_03_delete_service_offering | Success | 0.03 | test_service_offerings.py
test_02_edit_service_offering | Success | 0.04 | test_service_offerings.py
test_01_create_service_offering | Success | 0.07 | test_service_offerings.py
test_02_sys_template_ready | Success | 0.09 | test_secondary_storage.py
test_01_sys_vm_start | Success | 0.12 | test_secondary_storage.py
test_09_reboot_router | Success | 35.23 | test_routers.py
test_08_start_router | Success | 30.25 | test_routers.py
test_07_stop_router | Success | 10.12 | test_routers.py
test_06_router_advanced | Success | 0.04 | test_routers.py
test_05_router_basic | Success | 0.03 | test_routers.py
test_04_restart_network_wo_cleanup | S

[GitHub] cloudstack pull request #1901: [4.9] CLOUDSTACK-9405: add details parameter ...

[serg38]

Github user serg38 commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/1901#discussion_r95828294
  
--- Diff: 
api/src/org/apache/cloudstack/api/command/admin/domain/ListDomainsCmd.java ---
@@ -53,6 +59,12 @@
description = "If set to false, list only resources 
belonging to the command's caller; if set to true - list resources that the 
caller is authorized to see. Default value is false")
 private Boolean listAll;
 
+@Parameter(name = ApiConstants.DETAILS,
+   type = CommandType.LIST,
+   collectionType = CommandType.STRING,
+   description = "comma separated list of host details 
requested, value can be a list of [ all, resource, min]")
--- End diff --

Can you clarify what would be permitted values for details parameter? If 
they are only "min", resource", "all" then we might want to change the name and 
description of this parameter to reflect true purpose. What is the difference 
between 'resource' and 'all'?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1888: CLOUDSTACK-9710: Switch to JRE1.8

[rhtyd]

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1888
  
Thanks everyone, since we've no outstanding issues or objections and all 
regression tests across xen/vmware/kvm pass -- I'll proceed with merge this.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request #1888: CLOUDSTACK-9710: Switch to JRE1.8

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cloudstack/pull/1888


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [DISCUSS] Moving for JDK8, this time for real!

[Rohit Yadav]

Thank you all, the PR has been merged now.


As a note, developers please setup Jenv in your environment and make sure to 
install/setup both JDK7 and JDK8 to help you work on master and 4.9/previous 
branches:

http://www.jenv.be/


No additional build changes are required.


For deploying and testing CloudStack from master, a new systemvmtemplate will 
be required. Please see for urls:

http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.10/upgrade/upgrade-4.9.html#update-system-vm-templates


Regards.


From: Rohit Yadav 
Sent: 10 January 2017 12:08:24
To: dev
Subject: Re: [DISCUSS] Moving for JDK8, this time for real!

All,


Thank you for your feedback.


We've no outstanding objections to the PR, at the time of the 4.10 release 
we'll document the new requirements around JRE1.8 and new systemvmtemplate in 
our installation/upgrade notes.


I'll proceed with the merge later this week.


Regards.


From: Erik Weber 
Sent: 06 January 2017 02:50:36
To: dev
Subject: Re: [DISCUSS] Moving for JDK8, this time for real!

Yes, I understood that your proposal didn't change the debian version, I
suggested that it should do, since when we do update the debian version we
have to test everything over again anyway.

That said, I won't oppose your proposal, I'm +1 of upgrading to jdk 1.8

--
Erik


tor. 5. jan. 2017 kl. 15.46 skrev Rohit Yadav :

> Erik,
>
>
>
>
>
> The PR I've proposed does not change the base Debian distro, it's still
> Debian 7 (wheezy) and not Jessie. I would like to avoid making too many
> changes in the same PR, especially moving to Jessie which won't be straight
> forward as it would introduce several changes, major package version
> changes, systemd usage etc.
>
>
>
>
>
> What I'm proposing is simple -- moving to jdk8 for building CloudStack
> (this works flawlessly now), and using jre-8 on systemvm template.
>
>
>
>
>
> Regards.
>
>
>
> 
>
> From: Erik Weber 
>
> Sent: 05 January 2017 18:25:38
>
> To: dev
>
> Subject: Re: [DISCUSS] Moving for JDK8, this time for real!
>
>
>
>
>
> rohit.ya...@shapeblue.com
>
> www.shapeblue.com
>
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
>
> @shapeblue
>
>
>
>
>
>
>
> On Thu, Jan 5, 2017 at 1:11 PM, Rohit Yadav 
> wrote:
>
> > All,
>
> >
>
> >
>
> > I've been working on moving our codebase and runtime-environment to Java
> 8, and since this is a much needed big change I want your feedback and
> blessings on:
>
> >
>
> > https://github.com/apache/cloudstack/pull/1888
>
> >
>
> >
>
> > In order for this to work, I had to make changes in our veewee-based
> systemvmtemplate build scripts to install a third party opensource
> openjdk-8-jre distribution (xulu-8 is a openjdk-8 distribution from Azul,
> please review and advise wrt their terms of usage here:
> http://www.azul.com/products/zulu/zulu-terms-of-use/), since
>
> >
>
> > Debian 7 (wheezy) repositories don't have openjdk-8-jre and installing
> openjdk-8-jre from testing/sid updates several system packages such as libc
> that I wanted to avoid. Accepting this change on master/4.10 would require
> us to have a new systemvmtemplate for 4.10+ releases.
>
> >
>
> >
>
> > With these changes, I've ran smoke tests across KVM, VMware and
> XenServer in the following PR and all of the tests are passing (ignoring
> known intermittent failures in vpc/rvr related tests).
>
> >
>
> >
>
> > Thoughts, feedback?
>
>
>
> Wheezy has roughly 1 year left (until May 2018) before it is EOL.
>
> Since 4.10 is not LTS and the fact that both Java8 and Debian Jessie
>
> could have hard to find issues I would suggest that you update the
>
> systemvm now, and work through bugs and quirks throught the 4.10.x
>
> version.
>
> I believe there are other changes, like strongswan, as well that could
>
> make 4.10 a potentially unstable version?
>
>
>
> --
>
> Erik
>
>

rohit.ya...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue




rohit.ya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

[GitHub] cloudstack pull request #1893: Improve misleading translations

[niwo]

Github user niwo closed the pull request at:

https://github.com/apache/cloudstack/pull/1893


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request #1852: CLOUDSTACK-9695: VM snapshot is disabled if t...

[rashmidixit]

Github user rashmidixit closed the pull request at:

https://github.com/apache/cloudstack/pull/1852


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request #1852: CLOUDSTACK-9695: VM snapshot is disabled if t...

[rashmidixit]

GitHub user rashmidixit reopened a pull request:

https://github.com/apache/cloudstack/pull/1852

CLOUDSTACK-9695: VM snapshot is disabled if the VM Instance is off

Refer to 
[CLOUDSTACK-9695](https://issues.apache.org/jira/browse/CLOUDSTACK-9695) for 
more details.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Accelerite/cloudstack CLOUDSTACK-9695

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1852.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1852


commit 00a47802ce279900fef444ec7069b57418dda204
Author: Sanket Thite 
Date:   2016-07-12T09:50:47Z

VM snapshot is disabled if the VM Instance is off




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request #1901: [4.9] CLOUDSTACK-9405: add details parameter ...

[ustcweizhou]

Github user ustcweizhou commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/1901#discussion_r95948158
  
--- Diff: 
api/src/org/apache/cloudstack/api/command/admin/domain/ListDomainsCmd.java ---
@@ -53,6 +59,12 @@
description = "If set to false, list only resources 
belonging to the command's caller; if set to true - list resources that the 
caller is authorized to see. Default value is false")
 private Boolean listAll;
 
+@Parameter(name = ApiConstants.DETAILS,
+   type = CommandType.LIST,
+   collectionType = CommandType.STRING,
+   description = "comma separated list of host details 
requested, value can be a list of [ all, resource, min]")
--- End diff --

@serg38 currently no difference. However if we want to add more type of 
details, then it will be useful. for example, we add a new detail type: stats 
in our branch.

the defition is copied from listhosts API (you can see host details in the 
decription, I will change it).


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---