Re: [VOTE] Apache Cloudstack 4.9.0 RC2

[Abhinandan Prateek]

+1

Did manual testing with a cluster of Xen 6.5 in advanced zone.
Vm life cycle
VM Snapshot, volume snapshots
Volume and Template from snapshots
Migration
Change Password
Change service offering
VPC, multiple tiers, VMs, ACLs

Regards,
-abhi





On 29/07/16, 1:43 AM, "John Burwell"  wrote:

>All,
>
>I vote +1 (binding).  We have tested 4.9.0 RC2 in the following environments:
>
>   • CentOS 6.8 management server + CentOS 6.8 KVM Hosts using NFS primary 
> and secondary storage (would allow us to verify/fix the documented 
> libvirt/qemu versions)
>   • CentOS 6.8 management server + vCenter 5.5u3d + ESXi 5.5u3b using NFS 
> primary and secondary storage
>   • CentOS 6.8 management server + vCenter 6.0u2 + ESXi Express Patch 6 
> using NFS primary and secondary storage
>   • CentOS 6.8 management server + XenServer 6.2 SP1 using NFS primary 
> and secondary storage
>   • CentOS 6.8 management server + XenServer 6.5 SP1 using NFS primary 
> and secondary storage
>
>For each environment, we have run the following tests:
>
>   • All smoke tests
>   • test_accounts.py
>   • test_acl_*.py
>   • test_sharednetwork*.py
>   • test_add_remove_network.py
>   • test_advancedsg_networks.py
>   • test_affinity_groups*.py
>   • test_cpu_domain_limits.py
>   • test_cpu_limits.py
>   • test_cpu_max_limits.py
>   • test_host_maintenance.py
>   • test_memory_limits.py
>   • test_network_offering.py
>   • test_overcommit.py
>   • test_persistent_networks.py
>   • test_ps_domain_limits.py
>   • test_ps_limits.py
>   • test_ps_max_limits.py
>   • test_ps_resize_volume.py
>   • test_ps_resource_limits_volume.py
>   • test_resource_limits.py
>   • test_routers.py
>   • test_security_groups.py
>   • test_shared_networks.py
>   • test_snapshots.py
>   • test_ss_domain_limits.py
>   • test_ss_limits.py
>   • test_ss_max_limits.py
>   • test_templates.py
>   • test_update_vm.py
>   • test_volumes.py
>   • test_vpc.py
>
>During our tests, we found the following issues, but do not see any of them as 
>blockers:
>
>   • As Paul and Boris noted, the 
> test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL in 
> test_vpc_redundant.py fails.  We are uncertain as to whether this failure is 
> caused by a defect, a problem with the test case, or our test environment.
>   • We have seen NPEs in the log every 10 minutes attempting to garbage 
> collect a non-existent XenServer volume previously attached to a VR.  While 
> ugly, it is not leaving unused volumes to consume disk space.
>
>Thanks,
>-John
>
>> 
>john.burw...@shapeblue.com 
>www.shapeblue.com
>53 Chandos Place, Covent Garden, London VA WC2N 4HSUK
>@shapeblue
>  
> 
>
>On Jul 28, 2016, at 12:55 PM, Paul Angus  wrote:
>> 
>> I'm getting a pass on KVM for 
>> /marvin/test/integration/smoke/test_vpc_redundant.py
>> And a FAIL on VMware for the same test, with the same error.
>> 
>> 2016-07-28 04:00:52,133 - CRITICAL - FAILED: 
>> test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL: ['Traceback (most 
>> recent call last):\n', '  File "/usr/lib64/python2.7/unittest/case.py", line 
>> 369, in run\ntestMethod()\n', '  File 
>> "/marvin/test/integration/smoke/test_vpc_redundant.py", line 537, in 
>> test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL\n
>> self.check_routers_state(1)\n', '  File 
>> "/marvin/test/integration/smoke/test_vpc_redundant.py", line 304, in 
>> check_routers_state\nself.query_routers(count, showall)\n', '  File 
>> "/marvin/test/integration/smoke/test_vpc_redundant.py", line 297, in 
>> query_routers\n"Check that %s routers were indeed created" % count)\n', 
>> '  File "/usr/lib64/python2.7/unittest/case.py", line 553, in assertEqual\n  
>>   assertion_func(first, second, msg=msg)\n', '  File 
>> "/usr/lib64/python2.7/unittest/case.py", line 546, in _baseAssertEqual\n
>> raise self.failureException(msg)\n', 'AssertionError: Check that 1 routers 
>> were indeed created\n']
>> 
>> Kind regards,
>> 
>> Paul Angus
>> 
>> paul.an...@shapeblue.com 
>> www.shapeblue.com
>> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
>> @shapeblue
>> 
>> 
>> 
>> 
>> -Original Message-
>> From: williamstev...@gmail.com [mailto:williamstev...@gmail.com] On Behalf 
>> Of Will Stevens
>> Sent: 28 July 2016 17:24
>> To: dev@cloudstack.apache.org
>> Subject: Re: [VOTE] Apache Cloudstack 4.9.0 RC2
>> 
>> The teardown issue looks to be environmental.  Apparently the network did 
>> not get cleaned up before the network service offering using it was 
>> attempted to be deleted.
>> 
>> I am not sure about the test_vpc_redundent test failure.  I run that test 
>> all the time on KVM and have not been getting that problem.  Do you get the 
>> same thing if you run it again in your environment?
>> 
>> *Will STEVENS*
>> Lead Developer
>> 
>> *CloudOps* *| *Cloud Solutions Experts
>> 420 rue Guy *|* Montreal *

[GitHub] cloudstack pull request #1492: [CLOUDSTACK-9003] Resource Naming Policies

[ProjectMoon]

GitHub user ProjectMoon reopened a pull request:

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

[CLOUDSTACK-9003] Resource Naming Policies

Pull request #988, completed and reinvented.

This is an initial submission, a request for commentary.

This started with attempting to make the VirtualMachineName class 
non-static, and turned into a complete overhaul of how resources in CloudStack 
are named. Each supported resource has a naming policy that can be overridden 
to change the way UUIDs and names are generated for them. The primary use case 
for this is so CloudStack can emulate the naming schemes of other clouds. The 
default naming policies are in cloud-plugin-naming-policies, cloud-server has 
the server-naming module which contains the registry lifecycle, and the 
registered policies are injected into the core managers context.

The supported resources are:

* User virtual machines
* All kinds of system VMs
* Security groups
* Volumes
* Snapshots

There is one issue we have before we consider this ready for submission. 
The server-naming module has an ordering dependency. It must be loaded first in 
cloud-server in order for everything to work. Currently in this PR is a class 
called `ModuleLoadingComparator` which adds a comparator that forces the 
server-naming module to the top of the list when loading modules. We obviously 
want to get rid of this and are looking for suggestions on how to do this.

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

$ git pull https://github.com/greenqloud/cloudstack pr-naming-policies

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

https://github.com/apache/cloudstack/pull/1492.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 #1492


commit 6be87da0d98400ecb7254c200cf9fe7821181e4c
Author: nnesic 
Date:   2015-12-28T10:52:54Z

Implement the naming policy feature.

The naming policies feature is a large refactoring of how CloudStack
generates names and UUIDs for the following resources: virtual
machines (user instances and system VMs), security groups, templates,
volumes, and snapshots. Previously, most of these resources were
generated in a non-uniform way, making use of static classes or simple
UUID generation.

With the naming policies feature, each type of supported resource has
a specific naming policy to go along with it that generates UUIDs and
resource names. This allows CloudStack to emulate different kinds of
naming schemes (such as those found in other clouds).




---
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 #1492: [CLOUDSTACK-9003] Resource Naming Policies

[ProjectMoon]

Github user ProjectMoon closed the pull request at:

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


---
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 #1617: Changed UsageEventUtils to UsageEventEmitter and mad...

[ProjectMoon]

Github user ProjectMoon commented on the issue:

https://github.com/apache/cloudstack/pull/1617
  
Travis is failing due to some connection error, it seems. Any ideas?

```
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
nc: connect to localhost port 8096 (tcp) failed: Connection refused
nc: connect to localhost port 8096 (tcp) failed: Connection refused
nc: connect to localhost port 8096 (tcp) failed: Network is unreachable



---
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 #1492: [CLOUDSTACK-9003] Resource Naming Policies

[ProjectMoon]

Github user ProjectMoon commented on the issue:

https://github.com/apache/cloudstack/pull/1492
  
Travis is failing due to some connection error, it seems. Any ideas?

```
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
nc: connect to localhost port 8096 (tcp) failed: Connection refused
nc: connect to localhost port 8096 (tcp) failed: Connection refused
nc: connect to localhost port 8096 (tcp) failed: Network is unreachable



---
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 #1617: Changed UsageEventUtils to UsageEventEmitter and mad...

[ProjectMoon]

Github user ProjectMoon commented on the issue:

https://github.com/apache/cloudstack/pull/1617
  
Latest CI run does not happen to me locally. I can compile and start the 
simulator fine. Anyone have any insights?


---
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: [VOTE] Apache Cloudstack 4.9.0 RC2

[Will Stevens]

The vote is closed.  The RC passed with the following votes.

+1 : 8 (including 6 binding)
+0 : 0
-1 : 0

Thanks everyone, I will get this pushed out today...

*Will STEVENS*
Lead Developer

*CloudOps* *| *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_

On Fri, Jul 29, 2016 at 5:24 AM, Abhinandan Prateek <
abhinandan.prat...@shapeblue.com> wrote:

> +1
>
> Did manual testing with a cluster of Xen 6.5 in advanced zone.
> Vm life cycle
> VM Snapshot, volume snapshots
> Volume and Template from snapshots
> Migration
> Change Password
> Change service offering
> VPC, multiple tiers, VMs, ACLs
>
> Regards,
> -abhi
>
>
>
>
>
> On 29/07/16, 1:43 AM, "John Burwell"  wrote:
>
> >All,
> >
> >I vote +1 (binding).  We have tested 4.9.0 RC2 in the following
> environments:
> >
> >   • CentOS 6.8 management server + CentOS 6.8 KVM Hosts using NFS
> primary and secondary storage (would allow us to verify/fix the documented
> libvirt/qemu versions)
> >   • CentOS 6.8 management server + vCenter 5.5u3d + ESXi 5.5u3b
> using NFS primary and secondary storage
> >   • CentOS 6.8 management server + vCenter 6.0u2 + ESXi Express
> Patch 6 using NFS primary and secondary storage
> >   • CentOS 6.8 management server + XenServer 6.2 SP1 using NFS
> primary and secondary storage
> >   • CentOS 6.8 management server + XenServer 6.5 SP1 using NFS
> primary and secondary storage
> >
> >For each environment, we have run the following tests:
> >
> >   • All smoke tests
> >   • test_accounts.py
> >   • test_acl_*.py
> >   • test_sharednetwork*.py
> >   • test_add_remove_network.py
> >   • test_advancedsg_networks.py
> >   • test_affinity_groups*.py
> >   • test_cpu_domain_limits.py
> >   • test_cpu_limits.py
> >   • test_cpu_max_limits.py
> >   • test_host_maintenance.py
> >   • test_memory_limits.py
> >   • test_network_offering.py
> >   • test_overcommit.py
> >   • test_persistent_networks.py
> >   • test_ps_domain_limits.py
> >   • test_ps_limits.py
> >   • test_ps_max_limits.py
> >   • test_ps_resize_volume.py
> >   • test_ps_resource_limits_volume.py
> >   • test_resource_limits.py
> >   • test_routers.py
> >   • test_security_groups.py
> >   • test_shared_networks.py
> >   • test_snapshots.py
> >   • test_ss_domain_limits.py
> >   • test_ss_limits.py
> >   • test_ss_max_limits.py
> >   • test_templates.py
> >   • test_update_vm.py
> >   • test_volumes.py
> >   • test_vpc.py
> >
> >During our tests, we found the following issues, but do not see any of
> them as blockers:
> >
> >   • As Paul and Boris noted, the
> test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL in
> test_vpc_redundant.py fails.  We are uncertain as to whether this failure
> is caused by a defect, a problem with the test case, or our test
> environment.
> >   • We have seen NPEs in the log every 10 minutes attempting to
> garbage collect a non-existent XenServer volume previously attached to a
> VR.  While ugly, it is not leaving unused volumes to consume disk space.
> >
> >Thanks,
> >-John
> >
> >>
> >john.burw...@shapeblue.com
> >www.shapeblue.com
> >53 Chandos Place, Covent Garden, London VA WC2N 4HSUK
> >@shapeblue
> >
> >
> >
> >On Jul 28, 2016, at 12:55 PM, Paul Angus 
> wrote:
> >>
> >> I'm getting a pass on KVM for
> /marvin/test/integration/smoke/test_vpc_redundant.py
> >> And a FAIL on VMware for the same test, with the same error.
> >>
> >> 2016-07-28 04:00:52,133 - CRITICAL - FAILED:
> test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL: ['Traceback (most
> recent call last):\n', '  File "/usr/lib64/python2.7/unittest/case.py",
> line 369, in run\ntestMethod()\n', '  File
> "/marvin/test/integration/smoke/test_vpc_redundant.py", line 537, in
> test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL\n
> self.check_routers_state(1)\n', '  File
> "/marvin/test/integration/smoke/test_vpc_redundant.py", line 304, in
> check_routers_state\nself.query_routers(count, showall)\n', '  File
> "/marvin/test/integration/smoke/test_vpc_redundant.py", line 297, in
> query_routers\n"Check that %s routers were indeed created" % count)\n',
> '  File "/usr/lib64/python2.7/unittest/case.py", line 553, in
> assertEqual\nassertion_func(first, second, msg=msg)\n', '  File
> "/usr/lib64/python2.7/unittest/case.py", line 546, in _baseAssertEqual\n
> raise self.failureException(msg)\n', 'AssertionError: Check that 1 routers
> were indeed created\n']
> >>
> >> Kind regards,
> >>
> >> Paul Angus
> >>
> >> paul.an...@shapeblue.com
> >> www.shapeblue.com
> >> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> >> @shapeblue
> >>
> >>
> >>
> >>
> >> -Original Message-
> >> From: williamstev...@gmail.com [mailto:williamstev...@gmail.com] On
> Behalf Of Will Stevens
> >> Sent: 28 July 2016 17:24
> >> To: dev@cloudstack.apache.org
> >> Subject: Re:

Re: [VOTE] Apache Cloudstack 4.9.0 RC2

[Will Stevens]

Sorry, I did not follow the correct format.  :P

After 72 hours, the vote for CloudStack 4.9.0 *passes* with 6 PMC + 2
non-PMC votes.

+1 (PMC / binding)
* Rohit Yadav
* Mike Tutkowski
* Wido den Hollander
* Milamber
* Nux!
* John Burwell

+1 (non binding)
* Paul Angus
* Abhinandan Prateek

0
none

-1
none

Thanks to everyone participating.

*Will STEVENS*
Lead Developer

*CloudOps* *| *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_

On Fri, Jul 29, 2016 at 9:44 AM, Will Stevens  wrote:

> The vote is closed.  The RC passed with the following votes.
>
> +1 : 8 (including 6 binding)
> +0 : 0
> -1 : 0
>
> Thanks everyone, I will get this pushed out today...
>
> *Will STEVENS*
> Lead Developer
>
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
>
> On Fri, Jul 29, 2016 at 5:24 AM, Abhinandan Prateek <
> abhinandan.prat...@shapeblue.com> wrote:
>
>> +1
>>
>> Did manual testing with a cluster of Xen 6.5 in advanced zone.
>> Vm life cycle
>> VM Snapshot, volume snapshots
>> Volume and Template from snapshots
>> Migration
>> Change Password
>> Change service offering
>> VPC, multiple tiers, VMs, ACLs
>>
>> Regards,
>> -abhi
>>
>>
>>
>>
>>
>> On 29/07/16, 1:43 AM, "John Burwell"  wrote:
>>
>> >All,
>> >
>> >I vote +1 (binding).  We have tested 4.9.0 RC2 in the following
>> environments:
>> >
>> >   • CentOS 6.8 management server + CentOS 6.8 KVM Hosts using NFS
>> primary and secondary storage (would allow us to verify/fix the documented
>> libvirt/qemu versions)
>> >   • CentOS 6.8 management server + vCenter 5.5u3d + ESXi 5.5u3b
>> using NFS primary and secondary storage
>> >   • CentOS 6.8 management server + vCenter 6.0u2 + ESXi Express
>> Patch 6 using NFS primary and secondary storage
>> >   • CentOS 6.8 management server + XenServer 6.2 SP1 using NFS
>> primary and secondary storage
>> >   • CentOS 6.8 management server + XenServer 6.5 SP1 using NFS
>> primary and secondary storage
>> >
>> >For each environment, we have run the following tests:
>> >
>> >   • All smoke tests
>> >   • test_accounts.py
>> >   • test_acl_*.py
>> >   • test_sharednetwork*.py
>> >   • test_add_remove_network.py
>> >   • test_advancedsg_networks.py
>> >   • test_affinity_groups*.py
>> >   • test_cpu_domain_limits.py
>> >   • test_cpu_limits.py
>> >   • test_cpu_max_limits.py
>> >   • test_host_maintenance.py
>> >   • test_memory_limits.py
>> >   • test_network_offering.py
>> >   • test_overcommit.py
>> >   • test_persistent_networks.py
>> >   • test_ps_domain_limits.py
>> >   • test_ps_limits.py
>> >   • test_ps_max_limits.py
>> >   • test_ps_resize_volume.py
>> >   • test_ps_resource_limits_volume.py
>> >   • test_resource_limits.py
>> >   • test_routers.py
>> >   • test_security_groups.py
>> >   • test_shared_networks.py
>> >   • test_snapshots.py
>> >   • test_ss_domain_limits.py
>> >   • test_ss_limits.py
>> >   • test_ss_max_limits.py
>> >   • test_templates.py
>> >   • test_update_vm.py
>> >   • test_volumes.py
>> >   • test_vpc.py
>> >
>> >During our tests, we found the following issues, but do not see any of
>> them as blockers:
>> >
>> >   • As Paul and Boris noted, the
>> test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL in
>> test_vpc_redundant.py fails.  We are uncertain as to whether this failure
>> is caused by a defect, a problem with the test case, or our test
>> environment.
>> >   • We have seen NPEs in the log every 10 minutes attempting to
>> garbage collect a non-existent XenServer volume previously attached to a
>> VR.  While ugly, it is not leaving unused volumes to consume disk space.
>> >
>> >Thanks,
>> >-John
>> >
>> >>
>> >john.burw...@shapeblue.com
>> >www.shapeblue.com
>> >53 Chandos Place, Covent Garden, London VA WC2N 4HSUK
>> >@shapeblue
>> >
>> >
>> >
>> >On Jul 28, 2016, at 12:55 PM, Paul Angus 
>> wrote:
>> >>
>> >> I'm getting a pass on KVM for
>> /marvin/test/integration/smoke/test_vpc_redundant.py
>> >> And a FAIL on VMware for the same test, with the same error.
>> >>
>> >> 2016-07-28 04:00:52,133 - CRITICAL - FAILED:
>> test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL: ['Traceback (most
>> recent call last):\n', '  File "/usr/lib64/python2.7/unittest/case.py",
>> line 369, in run\ntestMethod()\n', '  File
>> "/marvin/test/integration/smoke/test_vpc_redundant.py", line 537, in
>> test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL\n
>> self.check_routers_state(1)\n', '  File
>> "/marvin/test/integration/smoke/test_vpc_redundant.py", line 304, in
>> check_routers_state\nself.query_routers(count, showall)\n', '  File
>> "/marvin/test/integration/smoke/test_vpc_redundant.py", line 297, in
>> query_routers\n"Check that %s routers were indeed created" % count)\n',
>> '  File "/usr/lib64/pyt

[GitHub] cloudstack pull request #1618: GQSS-2277 Now returning os info with the list...

[ProjectMoon]

GitHub user ProjectMoon opened a pull request:

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

GQSS-2277 Now returning os info with the list snapshot response

This commit adds the ID and display name of the OS on the volume. 

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

$ git pull https://github.com/greenqloud/cloudstack 
pr-return-os-info-snapshots

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

https://github.com/apache/cloudstack/pull/1618.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 #1618


commit 6e78d8e9da5a465feff76d85e2666236d6a7d002
Author: Pall Helgason 
Date:   2016-03-02T13:11:30Z

GQSS-2277 Now returning os info with the list snapshot response




---
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: [VOTE] Apache Cloudstack 4.9.0 RC2

[Rohit Yadav]

Thank you Will. Please cut the 4.9 branch so it can be picked for LTS release 
work.

I'll publish the rpm/deb packages in the sb hosted upstream repo shortly.

Regards.




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

On Fri, Jul 29, 2016 at 7:27 PM +0530, "Will Stevens" 
mailto:wstev...@cloudops.com>> wrote:

Sorry, I did not follow the correct format.  :P

After 72 hours, the vote for CloudStack 4.9.0 *passes* with 6 PMC + 2
non-PMC votes.

+1 (PMC / binding)
* Rohit Yadav
* Mike Tutkowski
* Wido den Hollander
* Milamber
* Nux!
* John Burwell

+1 (non binding)
* Paul Angus
* Abhinandan Prateek

0
none

-1
none

Thanks to everyone participating.

*Will STEVENS*
Lead Developer

*CloudOps* *| *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_

On Fri, Jul 29, 2016 at 9:44 AM, Will Stevens  wrote:

> The vote is closed.  The RC passed with the following votes.
>
> +1 : 8 (including 6 binding)
> +0 : 0
> -1 : 0
>
> Thanks everyone, I will get this pushed out today...
>
> *Will STEVENS*
> Lead Developer
>
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
>
> On Fri, Jul 29, 2016 at 5:24 AM, Abhinandan Prateek <
> abhinandan.prat...@shapeblue.com> wrote:
>
>> +1
>>
>> Did manual testing with a cluster of Xen 6.5 in advanced zone.
>> Vm life cycle
>> VM Snapshot, volume snapshots
>> Volume and Template from snapshots
>> Migration
>> Change Password
>> Change service offering
>> VPC, multiple tiers, VMs, ACLs
>>
>> Regards,
>> -abhi
>>
>>
>>
>>
>>
>> On 29/07/16, 1:43 AM, "John Burwell"  wrote:
>>
>> >All,
>> >
>> >I vote +1 (binding).  We have tested 4.9.0 RC2 in the following
>> environments:
>> >
>> >   • CentOS 6.8 management server + CentOS 6.8 KVM Hosts using NFS
>> primary and secondary storage (would allow us to verify/fix the documented
>> libvirt/qemu versions)
>> >   • CentOS 6.8 management server + vCenter 5.5u3d + ESXi 5.5u3b
>> using NFS primary and secondary storage
>> >   • CentOS 6.8 management server + vCenter 6.0u2 + ESXi Express
>> Patch 6 using NFS primary and secondary storage
>> >   • CentOS 6.8 management server + XenServer 6.2 SP1 using NFS
>> primary and secondary storage
>> >   • CentOS 6.8 management server + XenServer 6.5 SP1 using NFS
>> primary and secondary storage
>> >
>> >For each environment, we have run the following tests:
>> >
>> >   • All smoke tests
>> >   • test_accounts.py
>> >   • test_acl_*.py
>> >   • test_sharednetwork*.py
>> >   • test_add_remove_network.py
>> >   • test_advancedsg_networks.py
>> >   • test_affinity_groups*.py
>> >   • test_cpu_domain_limits.py
>> >   • test_cpu_limits.py
>> >   • test_cpu_max_limits.py
>> >   • test_host_maintenance.py
>> >   • test_memory_limits.py
>> >   • test_network_offering.py
>> >   • test_overcommit.py
>> >   • test_persistent_networks.py
>> >   • test_ps_domain_limits.py
>> >   • test_ps_limits.py
>> >   • test_ps_max_limits.py
>> >   • test_ps_resize_volume.py
>> >   • test_ps_resource_limits_volume.py
>> >   • test_resource_limits.py
>> >   • test_routers.py
>> >   • test_security_groups.py
>> >   • test_shared_networks.py
>> >   • test_snapshots.py
>> >   • test_ss_domain_limits.py
>> >   • test_ss_limits.py
>> >   • test_ss_max_limits.py
>> >   • test_templates.py
>> >   • test_update_vm.py
>> >   • test_volumes.py
>> >   • test_vpc.py
>> >
>> >During our tests, we found the following issues, but do not see any of
>> them as blockers:
>> >
>> >   • As Paul and Boris noted, the
>> test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL in
>> test_vpc_redundant.py fails.  We are uncertain as to whether this failure
>> is caused by a defect, a problem with the test case, or our test
>> environment.
>> >   • We have seen NPEs in the log every 10 minutes attempting to
>> garbage collect a non-existent XenServer volume previously attached to a
>> VR.  While ugly, it is not leaving unused volumes to consume disk space.
>> >
>> >Thanks,
>> >-John
>> >
>> >>
>> >john.burw...@shapeblue.com
>> >www.shapeblue.com
>> >53 Chandos Place, Covent Garden, London VA WC2N 4HSUK
>> >@shapeblue
>> >
>> >
>> >
>> >On Jul 28, 2016, at 12:55 PM, Paul Angus 
>> wrote:
>> >>
>> >> I'm getting a pass on KVM for
>> /marvin/test/integration/smoke/test_vpc_redundant.py
>> >> And a FAIL on VMware for the same test, with the same error.
>> >>
>> >> 2016-07-28 04:00:52,133 - CRITICAL - FAILED:
>> test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL: ['Traceback (most
>> recent call last):\n', '  File "/usr/lib64/python2.7/unittest/case.py",
>> line 369, in run\ntestMethod()\n', '  File
>> "/marvin/test/integration/smoke/test_vpc_redundant.py", line 537, in
>> test_01_create_

Re: [VOTE] Apache Cloudstack 4.9.0 RC2

[Will Stevens]

Yep, in the process of getting the release cut.  Got side tracked by people
a few times, but I am almost finished...  I will keep you posted...

*Will STEVENS*
Lead Developer

*CloudOps* *| *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_

On Fri, Jul 29, 2016 at 12:10 PM, Rohit Yadav 
wrote:

> Thank you Will. Please cut the 4.9 branch so it can be picked for LTS
> release work.
>
> I'll publish the rpm/deb packages in the sb hosted upstream repo shortly.
>
> Regards.
>
>
>
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
> On Fri, Jul 29, 2016 at 7:27 PM +0530, "Will Stevens" <
> wstev...@cloudops.com> wrote:
>
> Sorry, I did not follow the correct format.  :P
>
> After 72 hours, the vote for CloudStack 4.9.0 *passes* with 6 PMC + 2
> non-PMC votes.
>
> +1 (PMC / binding)
> * Rohit Yadav
> * Mike Tutkowski
> * Wido den Hollander
> * Milamber
> * Nux!
> * John Burwell
>
> +1 (non binding)
> * Paul Angus
> * Abhinandan Prateek
>
> 0
> none
>
> -1
> none
>
> Thanks to everyone participating.
>
> *Will STEVENS*
> Lead Developer
>
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
>
> On Fri, Jul 29, 2016 at 9:44 AM, Will Stevens 
> wrote:
>
> > The vote is closed.  The RC passed with the following votes.
> >
> > +1 : 8 (including 6 binding)
> > +0 : 0
> > -1 : 0
> >
> > Thanks everyone, I will get this pushed out today...
> >
> > *Will STEVENS*
> > Lead Developer
> >
> > *CloudOps* *| *Cloud Solutions Experts
> > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> > w cloudops.com *|* tw @CloudOps_
> >
> > On Fri, Jul 29, 2016 at 5:24 AM, Abhinandan Prateek <
> > abhinandan.prat...@shapeblue.com> wrote:
> >
> >> +1
> >>
> >> Did manual testing with a cluster of Xen 6.5 in advanced zone.
> >> Vm life cycle
> >> VM Snapshot, volume snapshots
> >> Volume and Template from snapshots
> >> Migration
> >> Change Password
> >> Change service offering
> >> VPC, multiple tiers, VMs, ACLs
> >>
> >> Regards,
> >> -abhi
> >>
> >>
> >>
> >>
> >>
> >> On 29/07/16, 1:43 AM, "John Burwell" 
> wrote:
> >>
> >> >All,
> >> >
> >> >I vote +1 (binding).  We have tested 4.9.0 RC2 in the following
> >> environments:
> >> >
> >> >   • CentOS 6.8 management server + CentOS 6.8 KVM Hosts using NFS
> >> primary and secondary storage (would allow us to verify/fix the
> documented
> >> libvirt/qemu versions)
> >> >   • CentOS 6.8 management server + vCenter 5.5u3d + ESXi 5.5u3b
> >> using NFS primary and secondary storage
> >> >   • CentOS 6.8 management server + vCenter 6.0u2 + ESXi Express
> >> Patch 6 using NFS primary and secondary storage
> >> >   • CentOS 6.8 management server + XenServer 6.2 SP1 using NFS
> >> primary and secondary storage
> >> >   • CentOS 6.8 management server + XenServer 6.5 SP1 using NFS
> >> primary and secondary storage
> >> >
> >> >For each environment, we have run the following tests:
> >> >
> >> >   • All smoke tests
> >> >   • test_accounts.py
> >> >   • test_acl_*.py
> >> >   • test_sharednetwork*.py
> >> >   • test_add_remove_network.py
> >> >   • test_advancedsg_networks.py
> >> >   • test_affinity_groups*.py
> >> >   • test_cpu_domain_limits.py
> >> >   • test_cpu_limits.py
> >> >   • test_cpu_max_limits.py
> >> >   • test_host_maintenance.py
> >> >   • test_memory_limits.py
> >> >   • test_network_offering.py
> >> >   • test_overcommit.py
> >> >   • test_persistent_networks.py
> >> >   • test_ps_domain_limits.py
> >> >   • test_ps_limits.py
> >> >   • test_ps_max_limits.py
> >> >   • test_ps_resize_volume.py
> >> >   • test_ps_resource_limits_volume.py
> >> >   • test_resource_limits.py
> >> >   • test_routers.py
> >> >   • test_security_groups.py
> >> >   • test_shared_networks.py
> >> >   • test_snapshots.py
> >> >   • test_ss_domain_limits.py
> >> >   • test_ss_limits.py
> >> >   • test_ss_max_limits.py
> >> >   • test_templates.py
> >> >   • test_update_vm.py
> >> >   • test_volumes.py
> >> >   • test_vpc.py
> >> >
> >> >During our tests, we found the following issues, but do not see any of
> >> them as blockers:
> >> >
> >> >   • As Paul and Boris noted, the
> >> test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL in
> >> test_vpc_redundant.py fails.  We are uncertain as to whether this
> failure
> >> is caused by a defect, a problem with the test case, or our test
> >> environment.
> >> >   • We have seen NPEs in the log every 10 minutes attempting to
> >> garbage collect a non-existent XenServer volume previously attached to a
> >> VR.  While ugly, it is not leaving unused volumes to consume disk space.
> >> >
> >> >Thanks,
> >> >-John
> >> >
> >> >>
> >> >john.burw...@shapeblue.com
> >> >www.shapeblue.com

Re: [VOTE] Apache Cloudstack 4.9.0 RC2

[Will Stevens]

I think everything is up to date and correct now.  Please let me know if
anything seems out of place (this is the first time I have done this).

I will wait to do an official announcement until Monday in case anything
comes up.  I will also wait to update the following things until Monday:
http://cloudstack.apache.org/downloads.html and the release notes (cause I
have to finish them).

Let me know if you have questions.

Should I be cutting a 4.8.1 release as well?  Not sure how that works.
Remi said to do the 4.9.0 release first and then take care of the 4.8.1
release after.  Ideas?

*Will STEVENS*
Lead Developer

*CloudOps* *| *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_

On Fri, Jul 29, 2016 at 12:13 PM, Will Stevens 
wrote:

> Yep, in the process of getting the release cut.  Got side tracked by
> people a few times, but I am almost finished...  I will keep you posted...
>
> *Will STEVENS*
> Lead Developer
>
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
>
> On Fri, Jul 29, 2016 at 12:10 PM, Rohit Yadav 
> wrote:
>
>> Thank you Will. Please cut the 4.9 branch so it can be picked for LTS
>> release work.
>>
>> I'll publish the rpm/deb packages in the sb hosted upstream repo shortly.
>>
>> Regards.
>>
>>
>>
>>
>> rohit.ya...@shapeblue.com
>> www.shapeblue.com
>> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
>> @shapeblue
>>
>>
>>
>> On Fri, Jul 29, 2016 at 7:27 PM +0530, "Will Stevens" <
>> wstev...@cloudops.com> wrote:
>>
>> Sorry, I did not follow the correct format.  :P
>>
>> After 72 hours, the vote for CloudStack 4.9.0 *passes* with 6 PMC + 2
>> non-PMC votes.
>>
>> +1 (PMC / binding)
>> * Rohit Yadav
>> * Mike Tutkowski
>> * Wido den Hollander
>> * Milamber
>> * Nux!
>> * John Burwell
>>
>> +1 (non binding)
>> * Paul Angus
>> * Abhinandan Prateek
>>
>> 0
>> none
>>
>> -1
>> none
>>
>> Thanks to everyone participating.
>>
>> *Will STEVENS*
>> Lead Developer
>>
>> *CloudOps* *| *Cloud Solutions Experts
>> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
>> w cloudops.com *|* tw @CloudOps_
>>
>> On Fri, Jul 29, 2016 at 9:44 AM, Will Stevens 
>> wrote:
>>
>> > The vote is closed.  The RC passed with the following votes.
>> >
>> > +1 : 8 (including 6 binding)
>> > +0 : 0
>> > -1 : 0
>> >
>> > Thanks everyone, I will get this pushed out today...
>> >
>> > *Will STEVENS*
>> > Lead Developer
>> >
>> > *CloudOps* *| *Cloud Solutions Experts
>> > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
>> > w cloudops.com *|* tw @CloudOps_
>> >
>> > On Fri, Jul 29, 2016 at 5:24 AM, Abhinandan Prateek <
>> > abhinandan.prat...@shapeblue.com> wrote:
>> >
>> >> +1
>> >>
>> >> Did manual testing with a cluster of Xen 6.5 in advanced zone.
>> >> Vm life cycle
>> >> VM Snapshot, volume snapshots
>> >> Volume and Template from snapshots
>> >> Migration
>> >> Change Password
>> >> Change service offering
>> >> VPC, multiple tiers, VMs, ACLs
>> >>
>> >> Regards,
>> >> -abhi
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> On 29/07/16, 1:43 AM, "John Burwell" 
>> wrote:
>> >>
>> >> >All,
>> >> >
>> >> >I vote +1 (binding).  We have tested 4.9.0 RC2 in the following
>> >> environments:
>> >> >
>> >> >   • CentOS 6.8 management server + CentOS 6.8 KVM Hosts using NFS
>> >> primary and secondary storage (would allow us to verify/fix the
>> documented
>> >> libvirt/qemu versions)
>> >> >   • CentOS 6.8 management server + vCenter 5.5u3d + ESXi 5.5u3b
>> >> using NFS primary and secondary storage
>> >> >   • CentOS 6.8 management server + vCenter 6.0u2 + ESXi Express
>> >> Patch 6 using NFS primary and secondary storage
>> >> >   • CentOS 6.8 management server + XenServer 6.2 SP1 using NFS
>> >> primary and secondary storage
>> >> >   • CentOS 6.8 management server + XenServer 6.5 SP1 using NFS
>> >> primary and secondary storage
>> >> >
>> >> >For each environment, we have run the following tests:
>> >> >
>> >> >   • All smoke tests
>> >> >   • test_accounts.py
>> >> >   • test_acl_*.py
>> >> >   • test_sharednetwork*.py
>> >> >   • test_add_remove_network.py
>> >> >   • test_advancedsg_networks.py
>> >> >   • test_affinity_groups*.py
>> >> >   • test_cpu_domain_limits.py
>> >> >   • test_cpu_limits.py
>> >> >   • test_cpu_max_limits.py
>> >> >   • test_host_maintenance.py
>> >> >   • test_memory_limits.py
>> >> >   • test_network_offering.py
>> >> >   • test_overcommit.py
>> >> >   • test_persistent_networks.py
>> >> >   • test_ps_domain_limits.py
>> >> >   • test_ps_limits.py
>> >> >   • test_ps_max_limits.py
>> >> >   • test_ps_resize_volume.py
>> >> >   • test_ps_resource_limits_volume.py
>> >> >   • test_resource_limits.py
>> >> >   • test_routers.py
>> >> >   • test_security_groups.py
>> >> >   • test_shared_networks.py
>> >> >   • test_snapshots.py

Re: [VOTE] Apache Cloudstack 4.9.0 RC2

[ilya]

Hi Will

What Remi mentioned sounds reasonable..

I'll be spending sometime today and next week to test out the issue
reported in 4.8 with VR not starting in Basic Zone - as well latest 4.9..

i know i'm late to the party - but this is the best i could do :(

Regards,
ilya



On 7/29/16 9:19 AM, Will Stevens wrote:
> I think everything is up to date and correct now.  Please let me know if
> anything seems out of place (this is the first time I have done this).
> 
> I will wait to do an official announcement until Monday in case anything
> comes up.  I will also wait to update the following things until Monday:
> http://cloudstack.apache.org/downloads.html and the release notes (cause I
> have to finish them).
> 
> Let me know if you have questions.
> 
> Should I be cutting a 4.8.1 release as well?  Not sure how that works.
> Remi said to do the 4.9.0 release first and then take care of the 4.8.1
> release after.  Ideas?
> 
> *Will STEVENS*
> Lead Developer
> 
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
> 
> On Fri, Jul 29, 2016 at 12:13 PM, Will Stevens 
> wrote:
> 
>> Yep, in the process of getting the release cut.  Got side tracked by
>> people a few times, but I am almost finished...  I will keep you posted...
>>
>> *Will STEVENS*
>> Lead Developer
>>
>> *CloudOps* *| *Cloud Solutions Experts
>> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
>> w cloudops.com *|* tw @CloudOps_
>>
>> On Fri, Jul 29, 2016 at 12:10 PM, Rohit Yadav 
>> wrote:
>>
>>> Thank you Will. Please cut the 4.9 branch so it can be picked for LTS
>>> release work.
>>>
>>> I'll publish the rpm/deb packages in the sb hosted upstream repo shortly.
>>>
>>> Regards.
>>>
>>>
>>>
>>>
>>> rohit.ya...@shapeblue.com
>>> www.shapeblue.com
>>> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
>>> @shapeblue
>>>
>>>
>>>
>>> On Fri, Jul 29, 2016 at 7:27 PM +0530, "Will Stevens" <
>>> wstev...@cloudops.com> wrote:
>>>
>>> Sorry, I did not follow the correct format.  :P
>>>
>>> After 72 hours, the vote for CloudStack 4.9.0 *passes* with 6 PMC + 2
>>> non-PMC votes.
>>>
>>> +1 (PMC / binding)
>>> * Rohit Yadav
>>> * Mike Tutkowski
>>> * Wido den Hollander
>>> * Milamber
>>> * Nux!
>>> * John Burwell
>>>
>>> +1 (non binding)
>>> * Paul Angus
>>> * Abhinandan Prateek
>>>
>>> 0
>>> none
>>>
>>> -1
>>> none
>>>
>>> Thanks to everyone participating.
>>>
>>> *Will STEVENS*
>>> Lead Developer
>>>
>>> *CloudOps* *| *Cloud Solutions Experts
>>> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
>>> w cloudops.com *|* tw @CloudOps_
>>>
>>> On Fri, Jul 29, 2016 at 9:44 AM, Will Stevens 
>>> wrote:
>>>
 The vote is closed.  The RC passed with the following votes.

 +1 : 8 (including 6 binding)
 +0 : 0
 -1 : 0

 Thanks everyone, I will get this pushed out today...

 *Will STEVENS*
 Lead Developer

 *CloudOps* *| *Cloud Solutions Experts
 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
 w cloudops.com *|* tw @CloudOps_

 On Fri, Jul 29, 2016 at 5:24 AM, Abhinandan Prateek <
 abhinandan.prat...@shapeblue.com> wrote:

> +1
>
> Did manual testing with a cluster of Xen 6.5 in advanced zone.
> Vm life cycle
> VM Snapshot, volume snapshots
> Volume and Template from snapshots
> Migration
> Change Password
> Change service offering
> VPC, multiple tiers, VMs, ACLs
>
> Regards,
> -abhi
>
>
>
>
>
> On 29/07/16, 1:43 AM, "John Burwell" 
>>> wrote:
>
>> All,
>>
>> I vote +1 (binding).  We have tested 4.9.0 RC2 in the following
> environments:
>>
>>   • CentOS 6.8 management server + CentOS 6.8 KVM Hosts using NFS
> primary and secondary storage (would allow us to verify/fix the
>>> documented
> libvirt/qemu versions)
>>   • CentOS 6.8 management server + vCenter 5.5u3d + ESXi 5.5u3b
> using NFS primary and secondary storage
>>   • CentOS 6.8 management server + vCenter 6.0u2 + ESXi Express
> Patch 6 using NFS primary and secondary storage
>>   • CentOS 6.8 management server + XenServer 6.2 SP1 using NFS
> primary and secondary storage
>>   • CentOS 6.8 management server + XenServer 6.5 SP1 using NFS
> primary and secondary storage
>>
>> For each environment, we have run the following tests:
>>
>>   • All smoke tests
>>   • test_accounts.py
>>   • test_acl_*.py
>>   • test_sharednetwork*.py
>>   • test_add_remove_network.py
>>   • test_advancedsg_networks.py
>>   • test_affinity_groups*.py
>>   • test_cpu_domain_limits.py
>>   • test_cpu_limits.py
>>   • test_cpu_max_limits.py
>>   • test_host_maintenance.py
>>   • test_memory_limits.py
>>   • test_network_offering.py
>>   • test_overcommit.py
>>   • test_p