RE: New Committer: Sanjeev Neelarapu

[Sateesh Chodapuneedi]

Sanjeev, Hearty Congratulations, great job.

Regards,
Sateesh

> -Original Message-
> From: Du Jun [mailto:dj199...@gmail.com]
> Sent: 14 November 2013 12:27
> To: dev@cloudstack.apache.org
> Subject: Re: New Committer: Sanjeev Neelarapu
> 
> Congratulations!
> 
> --
> Best regards.
> Frank
> 
> 
> 2013/11/14 Koushik Das 
> 
> > Congrats Sanjeev
> >
> > On 14-Nov-2013, at 11:29 AM, Prasanna Santhanam  wrote:
> >
> > > The Project Management Committee (PMC) for Apache CloudStack has
> > > asked
> > Sanjeev
> > > Neelarapu to become a committer and we are pleased to announce that
> > > they
> > have
> > > accepted.
> > >
> > > Being a committer allows many contributors to contribute more
> > autonomously. For
> > > developers, it makes it easier to submit changes and eliminates the
> > > need
> > to
> > > have contributions reviewed via the patch submission process.
> > > Whether contributions are development-related or otherwise, it is a
> > > recognition
> > of a
> > > contributor's participation in the project and commitment to the
> > > project
> > and
> > > the Apache Way.
> > >
> > > Please join me in congratulating Sanjeev!
> > >
> > > --
> > > Prasanna.,
> > > on behalf of the Apache CloudStack PMC
> > >
> > > 
> > > Powered by BigRock.com
> > >
> >
> >

RE: [4.3][QA]Test Plan for Hyper-V support

[Sailaja Mada]

Hi,

> 2) VM's with Multiple guest networks
Covered under multiple physical networks - this will include multiple guest 
networks, storage in separate network, and all combinations of that.

[Sailaja]This scenario Is about deploying the VM with multiple guest networks 
(Multiple NIC's for a VM with one being default].   Multiple Physical Networks 
can accommodate different Guest traffics.  These two are different scenarios. 

Please ignore If its already in the plan to be covered.

Thanks,
Sailaja.M

-Original Message-
From: Sowmya Krishnan [mailto:sowmya.krish...@citrix.com] 
Sent: 13 November 2013 17:15
To: dev@cloudstack.apache.org
Subject: RE: [4.3][QA]Test Plan for Hyper-V support

Thanks Sailaja. Most of these will be covered under test case document. Like I 
mentioned it's in progress.. so I've highlighted only the test scenarios based 
on supported features. Watch out for the test case document when they're 
uploaded for these individual tests. 
Comments inline as well.


> -Original Message-
> From: Sailaja Mada [mailto:sailaja.m...@citrix.com]
> Sent: Wednesday, November 13, 2013 4:10 PM
> To: dev@cloudstack.apache.org
> Subject: RE: [4.3][QA]Test Plan for Hyper-V support
> 
> Hi Sowmya,
> 
> It's a nice consolidation of the areas in the Test Plan .  I just have 
> few comments or scenarios to mention.
> 
> Please ignore if you have already plans to add it or its not supported.
> 
> 1) Hot Nic Plugin - Acquiring Public IP from a new VLAN
Hot Nic Plugin isn't supported in 4.3

> 2) VM's with Multiple guest networks
Covered under multiple physical networks - this will include multiple guest 
networks, storage in separate network, and all combinations of that. 

> 3) VM Operations - Force Stop of a VM ,  Restore the VM to a base 
> template or to a new template , Reset the VM
Watch out for Test case doc. All VM operations will be tested 

> 4) Cold Migration - Migrating the volumes to a different Storage when 
> VM is down
Test case will cover this.

> 5) Windows and Linux VM's . I am  not sure if we have any separate 
> tools ISO bundled for HyperV in order to execute certain operations 
> like the way we do for VMWARE/Xen .

I am still exploring this. There are some integrated tools to be downloaded in 
the guest VMs for certain OS. While some are already available with the OS 
(like CentOS6.4) others will need to be downloaded explicitly. This will be 
documented if need be.

> 6) Verify the HyperV supported guest Operating Systems which are 
> listed @ http://technet.microsoft.com/en-GB/library/hh831531.aspx  are 
> made available while registering the templates . It has Windows 8 and 
> 8.1 also listed. We may need to cover the latest
> 
Yeah.. I looked at that. We thought it's more of hypervisor test than CS test? 
We'll be covering one Windows VM and one Linux VM at least. It's definitely not 
possible to cover the entire list of guest OS types listed there. That's 
something which would be tested by the hypervisor test team 

> 8) Console view in different browsers
Watch out for Test case doc

> 9) Migrating the VM's across clusters if it supports Storage Motion .

Nope. Not supported

> 10) We have global config parameters specific to each hypervisor( 
> KVM/Xenserver/VMWARE). I do not see anything listed for HyperV. In 
> case if they are there, we may need to have scenarios to validate them
Nothing mentioned so far.

> 11) Alerts / Events to be generated for specific operations and have a 
> check for the same
No new events. It's all the same list of operations we do, except that it's a 
new hypervisor.

> 12) Is Volatile option with Compute Offering
Watch out for test case doc

> 13) VM Statistics to be displayed correctly.
Test case doc

> 14) Hypervisor_capabilities,guest_os_hypervisor Tables are updated 
> with the required details
Test case doc

> 15) Do we support Parallel VM deployment in HyperV ? Like we have in 
> VMWARE ?  If yes please have a scenario
Will include this.

> 16) Multiple Primary Storages
Test case doc

> 17) User defined names for the Virtual machines
Test case doc

> 18) Host tagging, Storage Tagging - This may create issues during 
> Migration

Test case doc - not hypervisor specific

> 19) Common Global Parameters like - Storage Garbage Collector, Network 
> Shutdown when there are no active VM's , Storage Migration during HA 
> (Yes/No) , VM Expunge Interval

No new params or API change mentioned in the FS. 
HA not supported. Network shutdown will be covered under Network restart cases.

> 20)  HA testing Or Host Failover cases
> 
HA not supported for this release. Failover will be covered under Host/Storage 
in maintenance mode

> Thanks and Regards,
> Sailaja.M
> 
> 
> 
> 
> 
> 
> 
> 
> 
> -Original Message-
> From: Sowmya Krishnan [mailto:sowmya.krish...@citrix.com]
> Sent: 13 November 2013 15:04
> To: dev@cloudstack.apache.org
> Subject: [4.3][QA]Test Plan for Hyper-V support
> 
> I've drafted a test plan for Hyper-V support for ar

Re: Review Request 15507: CLOUDSTACK-4835: Update global configuration test cases failed in master

[Harikrishna Patnala]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15507/
---

(Updated Nov. 14, 2013, 7:36 a.m.)


Review request for cloudstack and Koushik Das.


Bugs: CLOUDSTACK-4169, CLOUDSTACK-4835 and CLOUDSTACK-5163
https://issues.apache.org/jira/browse/CLOUDSTACK-4169
https://issues.apache.org/jira/browse/CLOUDSTACK-4835
https://issues.apache.org/jira/browse/CLOUDSTACK-5163


Repository: cloudstack-git


Description
---

CLOUDSTACK-4835: Update global configuration test cases failed in master 
Changes made in update/list configuration API to use ConfigDepot

CLOUDSTACK-4169: Scoped configuraion parameters logic moved to ConfigDepot

CLOUDSTACK-5163: missing parameters in configuration table
pool.storage.capacity.disablethreshold, storage.overprovisioning.factor, 
pool.storage.allocated.capacity.disablethreshold,
cluster.cpu.allocated.capacity.disablethreshold, 
cluster.memory.allocated.capacity.disablethreshold


Diffs (updated)
-

  api/src/com/cloud/deploy/DeploymentClusterPlanner.java ca73267 
  api/src/com/cloud/deploy/DeploymentPlanner.java 88cfc74 
  framework/config/src/org/apache/cloudstack/framework/config/ConfigDepot.java 
2fd6efb 
  
framework/config/src/org/apache/cloudstack/framework/config/impl/ConfigDepotImpl.java
 254e6d2 
  server/src/com/cloud/capacity/CapacityManagerImpl.java 70491bc 
  server/src/com/cloud/configuration/Config.java bc805b7 
  server/src/com/cloud/configuration/ConfigurationManagerImpl.java 82256ca 
  server/src/com/cloud/deploy/FirstFitPlanner.java 64b1124 
  server/src/com/cloud/network/router/VirtualNetworkApplianceManagerImpl.java 
a088a4a 
  server/src/com/cloud/server/ConfigurationServerImpl.java 8459ada 
  server/test/org/apache/cloudstack/networkoffering/ChildTestConfiguration.java 
d7ac3f7 

Diff: https://reviews.apache.org/r/15507/diff/


Testing
---


Thanks,

Harikrishna Patnala

Re: access to jenkins.buildacloud.org

[Srikanteswararao Talluri]

Œtalluri¹ is my committer id.

Thanks,
~Talluri

On 14/11/13 10:29 am, "Prasanna Santhanam"  wrote:

>On Wed, Nov 13, 2013 at 06:45:41PM +, Srikanteswararao Talluri
>wrote:
>> Please provide me access to jenkins.buildacloud.org. I would like to
>> explore  jenkins jobs for smoke and regression testing.
>
>Talluri,
>
>Could you give me your committerid? I'll create an account with the
>same name.
>
>@David : Any chance we could connect jenkins.bacd.org to the ASF ldap?
>
>> 
>> 
>> Thanks,
>> ~Talluri
>
>-- 
>Prasanna.,
>
>
>Powered by BigRock.com
>

[JENKINS] rpmbuilder running out of space

[Prasanna Santhanam]

Just an fyi:

The rpmbuilder* slave on jenkins.bacd is running low on space. I've
cleaned out the workspaces of old jobs (build-4.1/4.2 etc) which
haven't been running for a month to regain space. But I'm trying to
add a fresh slave similar to rpmbuilder. I'll send out a puppet
manifest so we can re-use it for creating fresh slaves.

*rpmbuilder - centos 6.3 slave that builds and packages cloudstack

-- 
Prasanna.,


Powered by BigRock.com

Re: New Committer: Sanjeev Neelarapu

[Du Jun]

Congratulations!

--
Best regards.
Frank


2013/11/14 Koushik Das 

> Congrats Sanjeev
>
> On 14-Nov-2013, at 11:29 AM, Prasanna Santhanam  wrote:
>
> > The Project Management Committee (PMC) for Apache CloudStack has asked
> Sanjeev
> > Neelarapu to become a committer and we are pleased to announce that they
> have
> > accepted.
> >
> > Being a committer allows many contributors to contribute more
> autonomously. For
> > developers, it makes it easier to submit changes and eliminates the need
> to
> > have contributions reviewed via the patch submission process. Whether
> > contributions are development-related or otherwise, it is a recognition
> of a
> > contributor's participation in the project and commitment to the project
> and
> > the Apache Way.
> >
> > Please join me in congratulating Sanjeev!
> >
> > --
> > Prasanna.,
> > on behalf of the Apache CloudStack PMC
> >
> > 
> > Powered by BigRock.com
> >
>
>

Re: New Committer: Sanjeev Neelarapu

[Koushik Das]

Congrats Sanjeev

On 14-Nov-2013, at 11:29 AM, Prasanna Santhanam  wrote:

> The Project Management Committee (PMC) for Apache CloudStack has asked Sanjeev
> Neelarapu to become a committer and we are pleased to announce that they have
> accepted.
> 
> Being a committer allows many contributors to contribute more autonomously. 
> For
> developers, it makes it easier to submit changes and eliminates the need to
> have contributions reviewed via the patch submission process. Whether
> contributions are development-related or otherwise, it is a recognition of a
> contributor's participation in the project and commitment to the project and
> the Apache Way.
> 
> Please join me in congratulating Sanjeev!
> 
> --
> Prasanna.,
> on behalf of the Apache CloudStack PMC
> 
> 
> Powered by BigRock.com
> 

Re: New Committer: Sanjeev Neelarapu

[Girish Shilamkar]

Congrats Sanjeev !!

Regards,
Girish

On 14-Nov-2013, at 12:11 PM, Suresh Sadhu  wrote:

> Congrats Sanjeev
> 
> -Original Message-
> From: Sailaja Mada [mailto:sailaja.m...@citrix.com] 
> Sent: 14 November 2013 11:38
> To: dev@cloudstack.apache.org
> Subject: RE: New Committer: Sanjeev Neelarapu
> 
> Congratulations Sanjeev.
> 
> Regards,
> Sailaja.M
> 
> -Original Message-
> From: Prasanna Santhanam [mailto:t...@apache.org] 
> Sent: 14 November 2013 11:30
> To: CloudStack Dev
> Subject: New Committer: Sanjeev Neelarapu
> 
> The Project Management Committee (PMC) for Apache CloudStack has asked 
> Sanjeev Neelarapu to become a committer and we are pleased to announce that 
> they have accepted.
> 
> Being a committer allows many contributors to contribute more autonomously. 
> For developers, it makes it easier to submit changes and eliminates the need 
> to have contributions reviewed via the patch submission process. Whether 
> contributions are development-related or otherwise, it is a recognition of a 
> contributor's participation in the project and commitment to the project and 
> the Apache Way.
> 
> Please join me in congratulating Sanjeev!
> 
> --
> Prasanna.,
> on behalf of the Apache CloudStack PMC
> 
> 
> Powered by BigRock.com
> 

Re: access to jenkins.buildacloud.org

[David Nalley]

On Wed, Nov 13, 2013 at 11:59 PM, Prasanna Santhanam  wrote:
> On Wed, Nov 13, 2013 at 06:45:41PM +, Srikanteswararao Talluri
> wrote:
>> Please provide me access to jenkins.buildacloud.org. I would like to
>> explore  jenkins jobs for smoke and regression testing.
>
> Talluri,
>
> Could you give me your committerid? I'll create an account with the
> same name.
>
> @David : Any chance we could connect jenkins.bacd.org to the ASF ldap?
>


Almost certainly no. I think there is a standing guideline that says
non-ASF services shall not auth against ASF LDAP.

--David

RE: New Committer: Sanjeev Neelarapu

[Suresh Sadhu]

Congrats Sanjeev

-Original Message-
From: Sailaja Mada [mailto:sailaja.m...@citrix.com] 
Sent: 14 November 2013 11:38
To: dev@cloudstack.apache.org
Subject: RE: New Committer: Sanjeev Neelarapu

Congratulations Sanjeev.

Regards,
Sailaja.M

-Original Message-
From: Prasanna Santhanam [mailto:t...@apache.org] 
Sent: 14 November 2013 11:30
To: CloudStack Dev
Subject: New Committer: Sanjeev Neelarapu

The Project Management Committee (PMC) for Apache CloudStack has asked Sanjeev 
Neelarapu to become a committer and we are pleased to announce that they have 
accepted.

Being a committer allows many contributors to contribute more autonomously. For 
developers, it makes it easier to submit changes and eliminates the need to 
have contributions reviewed via the patch submission process. Whether 
contributions are development-related or otherwise, it is a recognition of a 
contributor's participation in the project and commitment to the project and 
the Apache Way.

Please join me in congratulating Sanjeev!

--
Prasanna.,
on behalf of the Apache CloudStack PMC


Powered by BigRock.com

Re: New Committer: Sanjeev Neelarapu

[Wei ZHOU]

Congratulations Sanjeev!

2013/11/14 Prasanna Santhanam 

> The Project Management Committee (PMC) for Apache CloudStack has asked
> Sanjeev
> Neelarapu to become a committer and we are pleased to announce that they
> have
> accepted.
>
> Being a committer allows many contributors to contribute more
> autonomously. For
> developers, it makes it easier to submit changes and eliminates the need to
> have contributions reviewed via the patch submission process. Whether
> contributions are development-related or otherwise, it is a recognition of
> a
> contributor's participation in the project and commitment to the project
> and
> the Apache Way.
>
> Please join me in congratulating Sanjeev!
>
> --
> Prasanna.,
> on behalf of the Apache CloudStack PMC
>
> 
> Powered by BigRock.com
>
>

RE: New Committer: Sanjeev Neelarapu

[Radhika Puthiyetath]

Hearty congrats, Sanjeev

-Original Message-
From: Prasanna Santhanam [mailto:t...@apache.org] 
Sent: Thursday, November 14, 2013 11:30 AM
To: CloudStack Dev
Subject: New Committer: Sanjeev Neelarapu

The Project Management Committee (PMC) for Apache CloudStack has asked Sanjeev 
Neelarapu to become a committer and we are pleased to announce that they have 
accepted.

Being a committer allows many contributors to contribute more autonomously. For 
developers, it makes it easier to submit changes and eliminates the need to 
have contributions reviewed via the patch submission process. Whether 
contributions are development-related or otherwise, it is a recognition of a 
contributor's participation in the project and commitment to the project and 
the Apache Way.

Please join me in congratulating Sanjeev!

--
Prasanna.,
on behalf of the Apache CloudStack PMC


Powered by BigRock.com

Review Request 15507: CLOUDSTACK-4835: Update global configuration test cases failed in master

[Harikrishna Patnala]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15507/
---

Review request for cloudstack and Koushik Das.


Bugs: CLOUDSTACK-4169, CLOUDSTACK-4835 and CLOUDSTACK-5163
https://issues.apache.org/jira/browse/CLOUDSTACK-4169
https://issues.apache.org/jira/browse/CLOUDSTACK-4835
https://issues.apache.org/jira/browse/CLOUDSTACK-5163


Repository: cloudstack-git


Description
---

CLOUDSTACK-4835: Update global configuration test cases failed in master 
Changes made in update/list configuration API to use ConfigDepot

CLOUDSTACK-4169: Scoped configuraion parameters logic moved to ConfigDepot

CLOUDSTACK-5163: missing parameters in configuration table
pool.storage.capacity.disablethreshold, storage.overprovisioning.factor, 
pool.storage.allocated.capacity.disablethreshold,
cluster.cpu.allocated.capacity.disablethreshold, 
cluster.memory.allocated.capacity.disablethreshold


Diffs
-

  api/src/com/cloud/deploy/DeploymentClusterPlanner.java ca73267 
  api/src/com/cloud/deploy/DeploymentPlanner.java 88cfc74 
  framework/config/src/org/apache/cloudstack/framework/config/ConfigDepot.java 
2fd6efb 
  
framework/config/src/org/apache/cloudstack/framework/config/impl/ConfigDepotImpl.java
 254e6d2 
  server/src/com/cloud/capacity/CapacityManagerImpl.java 70491bc 
  server/src/com/cloud/configuration/Config.java bc805b7 
  server/src/com/cloud/configuration/ConfigurationManagerImpl.java 82256ca 
  server/src/com/cloud/deploy/FirstFitPlanner.java 64b1124 
  server/src/com/cloud/network/router/VirtualNetworkApplianceManagerImpl.java 
a088a4a 
  server/src/com/cloud/server/ConfigurationServerImpl.java 8459ada 

Diff: https://reviews.apache.org/r/15507/diff/


Testing
---


Thanks,

Harikrishna Patnala

Re: New Committer: Sanjeev Neelarapu

[Jayapal Reddy Uradi]

Congrats Sanjeev!

On 14-Nov-2013, at 11:42 AM, Bharat Kumar 
 wrote:

> Congratulations Sanjeev.
> 
> On 14-Nov-2013, at 11:38 am, Sailaja Mada  wrote:
> 
>> Congratulations Sanjeev.
>> 
>> Regards,
>> Sailaja.M
>> 
>> -Original Message-
>> From: Prasanna Santhanam [mailto:t...@apache.org] 
>> Sent: 14 November 2013 11:30
>> To: CloudStack Dev
>> Subject: New Committer: Sanjeev Neelarapu
>> 
>> The Project Management Committee (PMC) for Apache CloudStack has asked 
>> Sanjeev Neelarapu to become a committer and we are pleased to announce that 
>> they have accepted.
>> 
>> Being a committer allows many contributors to contribute more autonomously. 
>> For developers, it makes it easier to submit changes and eliminates the need 
>> to have contributions reviewed via the patch submission process. Whether 
>> contributions are development-related or otherwise, it is a recognition of a 
>> contributor's participation in the project and commitment to the project and 
>> the Apache Way.
>> 
>> Please join me in congratulating Sanjeev!
>> 
>> --
>> Prasanna.,
>> on behalf of the Apache CloudStack PMC
>> 
>> 
>> Powered by BigRock.com
>> 
> 

Re: New Committer: Sanjeev Neelarapu

[Bharat Kumar]

Congratulations Sanjeev.

On 14-Nov-2013, at 11:38 am, Sailaja Mada  wrote:

> Congratulations Sanjeev.
> 
> Regards,
> Sailaja.M
> 
> -Original Message-
> From: Prasanna Santhanam [mailto:t...@apache.org] 
> Sent: 14 November 2013 11:30
> To: CloudStack Dev
> Subject: New Committer: Sanjeev Neelarapu
> 
> The Project Management Committee (PMC) for Apache CloudStack has asked 
> Sanjeev Neelarapu to become a committer and we are pleased to announce that 
> they have accepted.
> 
> Being a committer allows many contributors to contribute more autonomously. 
> For developers, it makes it easier to submit changes and eliminates the need 
> to have contributions reviewed via the patch submission process. Whether 
> contributions are development-related or otherwise, it is a recognition of a 
> contributor's participation in the project and commitment to the project and 
> the Apache Way.
> 
> Please join me in congratulating Sanjeev!
> 
> --
> Prasanna.,
> on behalf of the Apache CloudStack PMC
> 
> 
> Powered by BigRock.com
> 

Re: New Committer: Sanjeev Neelarapu

[Abhinandan Prateek]

Congrats Sanjeev !

On 14/11/13 11:29 am, "Prasanna Santhanam"  wrote:

>The Project Management Committee (PMC) for Apache CloudStack has asked
>Sanjeev
>Neelarapu to become a committer and we are pleased to announce that they
>have
>accepted.
>
>Being a committer allows many contributors to contribute more
>autonomously. For
>developers, it makes it easier to submit changes and eliminates the need
>to
>have contributions reviewed via the patch submission process. Whether
>contributions are development-related or otherwise, it is a recognition
>of a
>contributor's participation in the project and commitment to the project
>and
>the Apache Way.
>
>Please join me in congratulating Sanjeev!
>
>--
>Prasanna.,
>on behalf of the Apache CloudStack PMC
>
>
>Powered by BigRock.com
>

RE: New Committer: Sanjeev Neelarapu

[Abhinav Roy]

Congrats Sanjeev!! :)

-Original Message-
From: Sailaja Mada [mailto:sailaja.m...@citrix.com] 
Sent: Thursday, November 14, 2013 11:38 AM
To: dev@cloudstack.apache.org
Subject: RE: New Committer: Sanjeev Neelarapu

Congratulations Sanjeev.

Regards,
Sailaja.M

-Original Message-
From: Prasanna Santhanam [mailto:t...@apache.org] 
Sent: 14 November 2013 11:30
To: CloudStack Dev
Subject: New Committer: Sanjeev Neelarapu

The Project Management Committee (PMC) for Apache CloudStack has asked Sanjeev 
Neelarapu to become a committer and we are pleased to announce that they have 
accepted.

Being a committer allows many contributors to contribute more autonomously. For 
developers, it makes it easier to submit changes and eliminates the need to 
have contributions reviewed via the patch submission process. Whether 
contributions are development-related or otherwise, it is a recognition of a 
contributor's participation in the project and commitment to the project and 
the Apache Way.

Please join me in congratulating Sanjeev!

--
Prasanna.,
on behalf of the Apache CloudStack PMC


Powered by BigRock.com

RE: New Committer: Sanjeev Neelarapu

[Sowmya Krishnan]

Congratulations Sanjeev! 

> -Original Message-
> From: Prasanna Santhanam [mailto:t...@apache.org]
> Sent: Thursday, November 14, 2013 11:30 AM
> To: CloudStack Dev
> Subject: New Committer: Sanjeev Neelarapu
> 
> The Project Management Committee (PMC) for Apache CloudStack has asked
> Sanjeev Neelarapu to become a committer and we are pleased to announce that
> they have accepted.
> 
> Being a committer allows many contributors to contribute more autonomously.
> For developers, it makes it easier to submit changes and eliminates the need 
> to
> have contributions reviewed via the patch submission process. Whether
> contributions are development-related or otherwise, it is a recognition of a
> contributor's participation in the project and commitment to the project and 
> the
> Apache Way.
> 
> Please join me in congratulating Sanjeev!
> 
> --
> Prasanna.,
> on behalf of the Apache CloudStack PMC
> 
> 
> Powered by BigRock.com

RE: New Committer: Sanjeev Neelarapu

[Sailaja Mada]

Congratulations Sanjeev.

Regards,
Sailaja.M

-Original Message-
From: Prasanna Santhanam [mailto:t...@apache.org] 
Sent: 14 November 2013 11:30
To: CloudStack Dev
Subject: New Committer: Sanjeev Neelarapu

The Project Management Committee (PMC) for Apache CloudStack has asked Sanjeev 
Neelarapu to become a committer and we are pleased to announce that they have 
accepted.

Being a committer allows many contributors to contribute more autonomously. For 
developers, it makes it easier to submit changes and eliminates the need to 
have contributions reviewed via the patch submission process. Whether 
contributions are development-related or otherwise, it is a recognition of a 
contributor's participation in the project and commitment to the project and 
the Apache Way.

Please join me in congratulating Sanjeev!

--
Prasanna.,
on behalf of the Apache CloudStack PMC


Powered by BigRock.com

New Committer: Sanjeev Neelarapu

[Prasanna Santhanam]

The Project Management Committee (PMC) for Apache CloudStack has asked Sanjeev
Neelarapu to become a committer and we are pleased to announce that they have
accepted.

Being a committer allows many contributors to contribute more autonomously. For
developers, it makes it easier to submit changes and eliminates the need to
have contributions reviewed via the patch submission process. Whether
contributions are development-related or otherwise, it is a recognition of a
contributor's participation in the project and commitment to the project and
the Apache Way.

Please join me in congratulating Sanjeev!

--
Prasanna.,
on behalf of the Apache CloudStack PMC


Powered by BigRock.com

Review Request 15505: Usage details are not getting populated when using dynamic offerings.

[bharat kumar]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15505/
---

Review request for cloudstack and Kishan Kavala.


Bugs: CLOUDSTACK-5162
https://issues.apache.org/jira/browse/CLOUDSTACK-5162


Repository: cloudstack-git


Description
---

Usage details are not getting populated when using dynamic offerings.
CLOUDSTACK-5162


Diffs
-

  engine/schema/src/com/cloud/service/ServiceOfferingVO.java 1e89add 
  server/src/com/cloud/vm/UserVmManagerImpl.java ca10b06 

Diff: https://reviews.apache.org/r/15505/diff/


Testing
---

tested on master.


Thanks,

bharat kumar

Re: Review Request 15344: Enabling DB HA for cloud stack data bases using mysql active-active solution

[Abhinandan Prateek]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15344/#review28861
---

Ship it!


Ship It!

- Abhinandan Prateek


On Nov. 14, 2013, 5:17 a.m., Damodar Reddy Talakanti wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/15344/
> ---
> 
> (Updated Nov. 14, 2013, 5:17 a.m.)
> 
> 
> Review request for cloudstack, Abhinandan Prateek and Darren Shepherd.
> 
> 
> Bugs: https://issues.apache.org/jira/browse/CLOUDSTACK-4916
> 
> https://issues.apache.org/jira/browse/https://issues.apache.org/jira/browse/CLOUDSTACK-4916
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> To enable Data base High Availability for cloud stack management server 
> database. We have used Mysql's connector parameters to switch between master 
> and slaves along with mysql's 2-way replication and chain way of replication 
> for more than 2 nodes
> 
> https://wikis.oracle.com/display/CommSuite/MySQL+High+Availability+and+Replication+Information+For+Calendar+Server#MySQLHighAvailabilityandReplicationInformationForCalendarServer-MySQLServerTwoWayReplicationExample
> 
> Due ot this defect http://bugs.mysql.com/bug.php?id=68141 changed 2 files to 
> have synchronized for on block of statements which were cauing Thread 
> BLOCKING..
> 
> 
> Diffs
> -
> 
>   client/tomcatconf/db.properties.in 31e0803 
>   framework/db/pom.xml 5af00a0 
>   framework/db/src/com/cloud/utils/db/StaticStrategy.java PRE-CREATION 
>   framework/db/src/com/cloud/utils/db/TransactionLegacy.java 39893bd 
> 
> Diff: https://reviews.apache.org/r/15344/diff/
> 
> 
> Testing
> ---
> 
> Basic sanity testing is done using 2 nodes. If any transaction(api request) 
> is in between and if server goes down then that api request will fail
> 
> 
> Thanks,
> 
> Damodar Reddy Talakanti
> 
>

Re: Review Request 15344: Enabling DB HA for cloud stack data bases using mysql active-active solution

[Damodar Reddy Talakanti]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15344/
---

(Updated Nov. 14, 2013, 5:17 a.m.)


Review request for cloudstack, Abhinandan Prateek and Darren Shepherd.


Changes
---

Forgot to add the licensing to the new file. Added the same and re uploading 
the new diff.


Bugs: https://issues.apache.org/jira/browse/CLOUDSTACK-4916

https://issues.apache.org/jira/browse/https://issues.apache.org/jira/browse/CLOUDSTACK-4916


Repository: cloudstack-git


Description
---

To enable Data base High Availability for cloud stack management server 
database. We have used Mysql's connector parameters to switch between master 
and slaves along with mysql's 2-way replication and chain way of replication 
for more than 2 nodes

https://wikis.oracle.com/display/CommSuite/MySQL+High+Availability+and+Replication+Information+For+Calendar+Server#MySQLHighAvailabilityandReplicationInformationForCalendarServer-MySQLServerTwoWayReplicationExample

Due ot this defect http://bugs.mysql.com/bug.php?id=68141 changed 2 files to 
have synchronized for on block of statements which were cauing Thread BLOCKING..


Diffs (updated)
-

  client/tomcatconf/db.properties.in 31e0803 
  framework/db/pom.xml 5af00a0 
  framework/db/src/com/cloud/utils/db/StaticStrategy.java PRE-CREATION 
  framework/db/src/com/cloud/utils/db/TransactionLegacy.java 39893bd 

Diff: https://reviews.apache.org/r/15344/diff/


Testing
---

Basic sanity testing is done using 2 nodes. If any transaction(api request) is 
in between and if server goes down then that api request will fail


Thanks,

Damodar Reddy Talakanti

Re: [VOTE] Release Apache CloudStack 4.2.1

[Abhinandan Prateek]

Marcus,

  Just summarising your concerns so that they can be followed upon:
1. Due to a VR script change a restart of VR is required. This should be
noted down in upgrade instructions in RN. (Radhika to note)
2. For a maintenance release we should limit the scope to only blockers. I
guess what is done is done probably for better as the main release had so
many new features that a whole lot fixes were expected in the maintenance
release. But again for further maintenance releases scope should be
restricted to important fixes.

Any other thing that has been missed ?

-abhi


On 14/11/13 12:06 am, "Marcus Sorensen"  wrote:

>I'm unable to deploy virtual machines after upgrading an existing
>4.2.0 to this release.
>
>It looks like the file savepassword.sh was added at the end of October
>as a virtual router script. This would likely mean that people
>upgrading to 4.2.1 will need to upgrade/redeploy their routers. I can
>verify that deploy works if I reboot the router.
>
>Looking over the current state of 4.2, I'm actually pretty surprised
>at how much has changed. I'm seeing lots of whitespace fixes, changes
>to interfaces, etc. My impression was that we'd only commit fixes for
>blocker bugs once a release has gone production, only touching it if
>we had to. This went pretty well with 4.1, I thought, but everything
>was going through the RM that round.
>
>2013-11-13 11:25:24,917 DEBUG
>[resource.virtualnetwork.VirtualRoutingResource]
>(agentRequest-Handler-2:null) Executing:
>/usr/share/cloudstack-common/scripts/network/domr/router_proxy.sh
>savepassword.sh 169.254.1.163 -v 10.2.4.116 -p fnirq_cnffjbeq
>
>2013-11-13 11:25:25,000 DEBUG
>[resource.virtualnetwork.VirtualRoutingResource]
>(agentRequest-Handler-2:null) Exit value is 127
>
>2013-11-13 11:25:25,001 DEBUG
>[resource.virtualnetwork.VirtualRoutingResource]
>(agentRequest-Handler-2:null) bash: /opt/cloud/bin/savepassword.sh: No
>such file or directory
>
>2013-11-13 11:25:25,002 DEBUG [cloud.agent.Agent]
>(agentRequest-Handler-2:null) Seq 21-289734823:  { Ans: , MgmtId:
>90520732090445, via: 21, Ver: v1, Flags: 110,
>[{"com.cloud.agent.api.Answer":{"result":false,"details":"Unable to
>save password to
>DomR.","wait":0}},{"com.cloud.agent.api.Answer":{"result":false,"details":
>"Stopped
>by previous failure","wait":0}}] }
>
>On Wed, Nov 13, 2013 at 10:26 AM, Chip Childers 
>wrote:
>> On Tue, Nov 12, 2013 at 10:52 AM, Abhinandan Prateek
>>  wrote:
>>>
>>>This vote is to approve the current RC build for 4.2.1 maintenance
>>>release.
>>> For this particular release various upgrade paths have been tested
>>>apart from regression tests and BVTs.
>>> Around 175 bugs have been fixed some new features added (see CHANGES).
>>>
>>> Following are the particulars for this release:
>>>
>>> 
>>>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=re
>>>fs/heads/4.2
>>> commit: 0b9eadaf14513f5c72de672963b0e2f12ee7206f
>>>
>>> List of changes:
>>> 
>>>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=
>>>CHANGES;hb=4.2.1
>>>
>>> Source release revision 3492 (checksums and signatures are available
>>>at the same location):
>>> https://dist.apache.org/repos/dist/dev/cloudstack/4.2.1/
>>>
>>> PGP release keys (signed using RSA Key ID = 42443AA1):
>>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>>
>>> Vote will be open for 72 hours (until 11/15 End of day PST).
>>>
>>> For sanity in tallying the vote, can PMC members please be sure to
>>>indicate "(binding)" with their vote?
>>>
>>> [ ] +1  approve
>>> [ ] +0  no opinion
>>> [ ] -1  disapprove (and reason why)
>>
>> +1 (binding)
>>
>> I only performed very rudimentary functional testing, but the
>> artifact's look legit.
>>
>> Thanks for doing this Abhi!

Re: access to jenkins.buildacloud.org

[Prasanna Santhanam]

On Wed, Nov 13, 2013 at 06:45:41PM +, Srikanteswararao Talluri
wrote:
> Please provide me access to jenkins.buildacloud.org. I would like to
> explore  jenkins jobs for smoke and regression testing.

Talluri,

Could you give me your committerid? I'll create an account with the
same name.

@David : Any chance we could connect jenkins.bacd.org to the ASF ldap?

> 
> 
> Thanks,
> ~Talluri

-- 
Prasanna.,


Powered by BigRock.com

Re: Review Request 15344: Enabling DB HA for cloud stack data bases using mysql active-active solution

[Abhinandan Prateek]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15344/#review28860
---


Add license header to StaticStrategy.java

- Abhinandan Prateek


On Nov. 12, 2013, 12:43 p.m., Damodar Reddy Talakanti wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/15344/
> ---
> 
> (Updated Nov. 12, 2013, 12:43 p.m.)
> 
> 
> Review request for cloudstack, Abhinandan Prateek and Darren Shepherd.
> 
> 
> Bugs: https://issues.apache.org/jira/browse/CLOUDSTACK-4916
> 
> https://issues.apache.org/jira/browse/https://issues.apache.org/jira/browse/CLOUDSTACK-4916
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> To enable Data base High Availability for cloud stack management server 
> database. We have used Mysql's connector parameters to switch between master 
> and slaves along with mysql's 2-way replication and chain way of replication 
> for more than 2 nodes
> 
> https://wikis.oracle.com/display/CommSuite/MySQL+High+Availability+and+Replication+Information+For+Calendar+Server#MySQLHighAvailabilityandReplicationInformationForCalendarServer-MySQLServerTwoWayReplicationExample
> 
> Due ot this defect http://bugs.mysql.com/bug.php?id=68141 changed 2 files to 
> have synchronized for on block of statements which were cauing Thread 
> BLOCKING..
> 
> 
> Diffs
> -
> 
>   client/tomcatconf/db.properties.in 31e0803 
>   framework/db/pom.xml 5af00a0 
>   framework/db/src/com/cloud/utils/db/StaticStrategy.java PRE-CREATION 
>   framework/db/src/com/cloud/utils/db/TransactionLegacy.java 39893bd 
> 
> Diff: https://reviews.apache.org/r/15344/diff/
> 
> 
> Testing
> ---
> 
> Basic sanity testing is done using 2 nodes. If any transaction(api request) 
> is in between and if server goes down then that api request will fail
> 
> 
> Thanks,
> 
> Damodar Reddy Talakanti
> 
>

Re: the plea to openstack

[Chiradeep Vittal]

In the same vein (things to watch out for)
http://www.openstack.org/summit/openstack-summit-hong-kong-2013/session-vid
eos/presentation/state-of-the-stack


On 11/6/13 8:34 AM, "Marcus Sorensen"  wrote:

>http://stochasticresonance.wordpress.com/2013/11/04/openstack-a-plea/
>
>I thought this was an interesting read. There might be some things
>CloudStack could learn or issues it could avoid by keeping some of his
>points in mind.

Re: CloudStack.next

[Steve Wilson]

Hi Mike,

Really interesting stuff and very differentiaing!

-Steve

On 11/13/13 12:33 PM, "Mike Tutkowski" 
wrote:

>Just as an FYI (to whom it may concern):
>
>For me, personally, my primary focus has been (and continues to be) on
>bringing true storage Quality of Service (QoS) to CloudStack (guaranteed
>IOPS on a per-CloudStack-volume basis).
>
>Prior to 4.2, CloudStack expected an admin to preallocate large amounts of
>storage (ex. a large volume on a SAN), then introduce this storage to his
>hypervisor, then create Primary Storage in CloudStack to represent that
>hypervisor-configured storage. At this point, a user could then create
>root
>and data disks that leveraged this storage (i.e. multiple root and data
>disks running on the same storage volume).
>
>That model may be efficient in terms of, say, number of iSCSI connections,
>but it is not very useful from the point of view of a storage system that
>is designed to deliver true QoS (eliminating the Noisy Neighbor effect by
>guaranteeing IOPS on a per-volume basis).
>
>In such a storage system, each volume on the SAN has independent QoS
>settings.
>
>In this world, it is ideal to map a single CloudStack volume to a single
>volume on the SAN. This means being able to create volumes on the SAN
>dynamically (ex. when a CloudStack volume is attached to a VM for the
>first
>time).
>
>Much of what Edison Su worked on for 4.2's storage-framework changes
>enabled me to take a large first step in that I could create a plug-in
>that
>could dynamically create volumes on our SAN (SolidFire SAN). However, the
>concept of preallocated storage is so embedded in CloudStack that I've
>needed to update core components of CloudStack, as well as CloudStack
>hypervisor-related code, to deal with dynamically created volumes.
>
>In 4.2 I released support for storage QoS with data disks on XenServer and
>VMware.
>
>In 4.3 I am releasing support for storage Qos with data disks on KVM.
>
>As we move forward, I plan to support storage QoS with root volumes on
>these hypervisors, as well (most likely starting with XenServer).
>
>It has been a bit tricky to support hypervisor snapshots in this model
>(where volumes are created dynamically on a SAN and the hypervisor data
>structures like SRs or datastores are created behind the scenes). This is
>another area I'm tackling for the 4.3 release (for XenServer and VMware).
>
>
>On Wed, Nov 13, 2013 at 11:50 AM, Steve Wilson
>wrote:
>
>> Hi Daan, Prasanna, Simon, David and Andrei!
>>
>> Thanks for chiming in.  Great way to kick off the discussion.
>>
>> In my thinking, we might want to look at things in three buckets:
>>
>> 1. Things that could go into a maintenance release like a 4.2.x
>> 2. Things that could go into a minor release like a 4.4
>> 3. Things that would require major architecture changes and might wind
>>up
>> in 5.0 or something like it
>>
>> From a Citrix perspective, we're definitely looking at things that fall
>> into all three of these buckets.  We've contributed a huge number of
>>fixes
>> to 4.2.1 and a number of features to 4.3.  We're also now starting to
>>plan
>> our contributions to 4.4 as well.  However, since I joined the
>>community,
>> I've seen very little discussion of what's really next.  What are the
>> major things we'd like to see done?  I don¹t have a particular timeframe
>> in mind for these things, I'm just looking to spark discussion --
>> especially as we go to Collab next week.
>>
>> Things that are interesting to me that fit in bucket three.  Here are a
>> couple:
>>
>> What level of scale should CloudStack be able to support?  I imagine
>>we'll
>> bee CloudStack clouds managing millions of VMs in the next few years.
>> What do we need to do to make that effective?
>>
>> I think people will want to manage "micro-clouds" -- very small, but
>> flexible clouds for special purpose needs.  What would CloudStack need
>>to
>> do to scale down very small and still be cost effective to run?
>>
>> Any thoughts about these, or any other ideas?
>>
>> -Steve
>>
>>
>> On 11/12/13 9:58 PM, "Daan Hoogland"  wrote:
>>
>> >I don't see any sugestions I don't like (including not breaking api)
>>but,
>> >
>> >- I like to second Simnons 'HA for VPC routers'
>> >extra. It is hurting not having that.
>> >
>> >- smaller releases is another one. monthly preferably or maybe an db
>> >upgrade model that allows for running snapshots and upgrading them
>> >regularly. The time to market for new features is now between 4 and 8
>> >months:(
>> >
>> >- related: master as a stable/always building and passing unit tests
>> >
>> >On Wed, Nov 13, 2013 at 6:39 AM, Prasanna Santhanam 
>> >wrote:
>> >> On Tue, Nov 12, 2013 at 11:41:17PM +, Steve Wilson wrote:
>> >>> Hi All,
>> >>>
>> >>> As we ramp towards freeze on 4.3 and start talking about 4.4, I
>> >>> thought it would be fun to queue up a discussion here on the list
>> >>> before Collab next week.
>> >>>
>> >>> What do you envision in the next MAJOR release of CloudStac

Re: CloudStack.next

[Mike Tutkowski]

Just as an FYI (to whom it may concern):

For me, personally, my primary focus has been (and continues to be) on
bringing true storage Quality of Service (QoS) to CloudStack (guaranteed
IOPS on a per-CloudStack-volume basis).

Prior to 4.2, CloudStack expected an admin to preallocate large amounts of
storage (ex. a large volume on a SAN), then introduce this storage to his
hypervisor, then create Primary Storage in CloudStack to represent that
hypervisor-configured storage. At this point, a user could then create root
and data disks that leveraged this storage (i.e. multiple root and data
disks running on the same storage volume).

That model may be efficient in terms of, say, number of iSCSI connections,
but it is not very useful from the point of view of a storage system that
is designed to deliver true QoS (eliminating the Noisy Neighbor effect by
guaranteeing IOPS on a per-volume basis).

In such a storage system, each volume on the SAN has independent QoS
settings.

In this world, it is ideal to map a single CloudStack volume to a single
volume on the SAN. This means being able to create volumes on the SAN
dynamically (ex. when a CloudStack volume is attached to a VM for the first
time).

Much of what Edison Su worked on for 4.2's storage-framework changes
enabled me to take a large first step in that I could create a plug-in that
could dynamically create volumes on our SAN (SolidFire SAN). However, the
concept of preallocated storage is so embedded in CloudStack that I've
needed to update core components of CloudStack, as well as CloudStack
hypervisor-related code, to deal with dynamically created volumes.

In 4.2 I released support for storage QoS with data disks on XenServer and
VMware.

In 4.3 I am releasing support for storage Qos with data disks on KVM.

As we move forward, I plan to support storage QoS with root volumes on
these hypervisors, as well (most likely starting with XenServer).

It has been a bit tricky to support hypervisor snapshots in this model
(where volumes are created dynamically on a SAN and the hypervisor data
structures like SRs or datastores are created behind the scenes). This is
another area I'm tackling for the 4.3 release (for XenServer and VMware).


On Wed, Nov 13, 2013 at 11:50 AM, Steve Wilson wrote:

> Hi Daan, Prasanna, Simon, David and Andrei!
>
> Thanks for chiming in.  Great way to kick off the discussion.
>
> In my thinking, we might want to look at things in three buckets:
>
> 1. Things that could go into a maintenance release like a 4.2.x
> 2. Things that could go into a minor release like a 4.4
> 3. Things that would require major architecture changes and might wind up
> in 5.0 or something like it
>
> From a Citrix perspective, we're definitely looking at things that fall
> into all three of these buckets.  We've contributed a huge number of fixes
> to 4.2.1 and a number of features to 4.3.  We're also now starting to plan
> our contributions to 4.4 as well.  However, since I joined the community,
> I've seen very little discussion of what's really next.  What are the
> major things we'd like to see done?  I don¹t have a particular timeframe
> in mind for these things, I'm just looking to spark discussion --
> especially as we go to Collab next week.
>
> Things that are interesting to me that fit in bucket three.  Here are a
> couple:
>
> What level of scale should CloudStack be able to support?  I imagine we'll
> bee CloudStack clouds managing millions of VMs in the next few years.
> What do we need to do to make that effective?
>
> I think people will want to manage "micro-clouds" -- very small, but
> flexible clouds for special purpose needs.  What would CloudStack need to
> do to scale down very small and still be cost effective to run?
>
> Any thoughts about these, or any other ideas?
>
> -Steve
>
>
> On 11/12/13 9:58 PM, "Daan Hoogland"  wrote:
>
> >I don't see any sugestions I don't like (including not breaking api) but,
> >
> >- I like to second Simnons 'HA for VPC routers'
> >extra. It is hurting not having that.
> >
> >- smaller releases is another one. monthly preferably or maybe an db
> >upgrade model that allows for running snapshots and upgrading them
> >regularly. The time to market for new features is now between 4 and 8
> >months:(
> >
> >- related: master as a stable/always building and passing unit tests
> >
> >On Wed, Nov 13, 2013 at 6:39 AM, Prasanna Santhanam 
> >wrote:
> >> On Tue, Nov 12, 2013 at 11:41:17PM +, Steve Wilson wrote:
> >>> Hi All,
> >>>
> >>> As we ramp towards freeze on 4.3 and start talking about 4.4, I
> >>> thought it would be fun to queue up a discussion here on the list
> >>> before Collab next week.
> >>>
> >>> What do you envision in the next MAJOR release of CloudStack?  Call
> >>> it 5.0 or whatever you like, but what would you like to see there?
> >>> What would you change?  What would you enhance?  Are there big bets
> >>> we should be placing as a community?
> >>>
> >>> Feel free to post any thoughts he

Re: New Ruby client for CloudStack API

[Sebastien Goasguen]

terrific and thanks for the detailed readme


On Nov 13, 2013, at 10:04 AM, Isaac Chiang  wrote:

> It is awesome! Thanks! :)
> 
> 
> On Wed, Nov 13, 2013 at 10:57 PM, Wei ZHOU  wrote:
> 
>> Great!
>> 
>> 2013/11/13 Mike Nicholaides 
>> 
>>> Hi folks,
>>> 
>>> Our team at PromptWorks, in conjunction with SunGard, has recently
>> released
>>> a new Ruby client for the CloudStack API called StackerBee:
>>> https://github.com/promptworks/stacker_bee
>>> 
>>> There are already a few Ruby clients out there but none of them met our
>>> needs so we made our own. Here's what makes StackerBee special:
>>> - supports all endpoints in the API
>>> - easy to use and developer friendly
>>> - let's developers write idiomatic Ruby
>>> - interactive CloudStack REPL
>>> - well tested and documented
>>> 
>>> Pull requests and bug reports welcome.
>>> 
>>> Special thanks to Chip Childers, Bill Jones, Dave Grizzanti and SunGard
>>> Availability Services.
>>> 
>>> Thanks,
>>> Mike Nicholaides
>>> 
>>> 
>>> --
>>> Mike Nicholaides
>>> Software Engineer and Co-Founder at PromptWorks
>>> promptworks.com
>>> (267) 622-4729
>>> 
>> 

Re: CloudStack.next

[Steve Wilson]

Hi Daan, Prasanna, Simon, David and Andrei!

Thanks for chiming in.  Great way to kick off the discussion.

In my thinking, we might want to look at things in three buckets:

1. Things that could go into a maintenance release like a 4.2.x
2. Things that could go into a minor release like a 4.4
3. Things that would require major architecture changes and might wind up
in 5.0 or something like it

>From a Citrix perspective, we're definitely looking at things that fall
into all three of these buckets.  We've contributed a huge number of fixes
to 4.2.1 and a number of features to 4.3.  We're also now starting to plan
our contributions to 4.4 as well.  However, since I joined the community,
I've seen very little discussion of what's really next.  What are the
major things we'd like to see done?  I don¹t have a particular timeframe
in mind for these things, I'm just looking to spark discussion --
especially as we go to Collab next week.

Things that are interesting to me that fit in bucket three.  Here are a
couple:

What level of scale should CloudStack be able to support?  I imagine we'll
bee CloudStack clouds managing millions of VMs in the next few years.
What do we need to do to make that effective?

I think people will want to manage "micro-clouds" -- very small, but
flexible clouds for special purpose needs.  What would CloudStack need to
do to scale down very small and still be cost effective to run?

Any thoughts about these, or any other ideas?

-Steve


On 11/12/13 9:58 PM, "Daan Hoogland"  wrote:

>I don't see any sugestions I don't like (including not breaking api) but,
>
>- I like to second Simnons 'HA for VPC routers'
>extra. It is hurting not having that.
>
>- smaller releases is another one. monthly preferably or maybe an db
>upgrade model that allows for running snapshots and upgrading them
>regularly. The time to market for new features is now between 4 and 8
>months:(
>
>- related: master as a stable/always building and passing unit tests
>
>On Wed, Nov 13, 2013 at 6:39 AM, Prasanna Santhanam 
>wrote:
>> On Tue, Nov 12, 2013 at 11:41:17PM +, Steve Wilson wrote:
>>> Hi All,
>>>
>>> As we ramp towards freeze on 4.3 and start talking about 4.4, I
>>> thought it would be fun to queue up a discussion here on the list
>>> before Collab next week.
>>>
>>> What do you envision in the next MAJOR release of CloudStack?  Call
>>> it 5.0 or whatever you like, but what would you like to see there?
>>> What would you change?  What would you enhance?  Are there big bets
>>> we should be placing as a community?
>>>
>>> Feel free to post any thoughts here and I'll look forward to talking
>>> to many of you in person at Collab next week.  You are coming to
>>> Collab, right?
>>>
>>
>> simplified upgradeability at all stages of development from version x
>> to version y.
>>
>> --
>> Prasanna.,
>>
>> 
>> Powered by BigRock.com
>>

access to jenkins.buildacloud.org

[Srikanteswararao Talluri]

Please provide me access to jenkins.buildacloud.org. I would like to explore  
jenkins jobs for smoke and regression testing.


Thanks,
~Talluri

Re: [VOTE] Release Apache CloudStack 4.2.1

[Marcus Sorensen]

I'm unable to deploy virtual machines after upgrading an existing
4.2.0 to this release.

It looks like the file savepassword.sh was added at the end of October
as a virtual router script. This would likely mean that people
upgrading to 4.2.1 will need to upgrade/redeploy their routers. I can
verify that deploy works if I reboot the router.

Looking over the current state of 4.2, I'm actually pretty surprised
at how much has changed. I'm seeing lots of whitespace fixes, changes
to interfaces, etc. My impression was that we'd only commit fixes for
blocker bugs once a release has gone production, only touching it if
we had to. This went pretty well with 4.1, I thought, but everything
was going through the RM that round.

2013-11-13 11:25:24,917 DEBUG
[resource.virtualnetwork.VirtualRoutingResource]
(agentRequest-Handler-2:null) Executing:
/usr/share/cloudstack-common/scripts/network/domr/router_proxy.sh
savepassword.sh 169.254.1.163 -v 10.2.4.116 -p fnirq_cnffjbeq

2013-11-13 11:25:25,000 DEBUG
[resource.virtualnetwork.VirtualRoutingResource]
(agentRequest-Handler-2:null) Exit value is 127

2013-11-13 11:25:25,001 DEBUG
[resource.virtualnetwork.VirtualRoutingResource]
(agentRequest-Handler-2:null) bash: /opt/cloud/bin/savepassword.sh: No
such file or directory

2013-11-13 11:25:25,002 DEBUG [cloud.agent.Agent]
(agentRequest-Handler-2:null) Seq 21-289734823:  { Ans: , MgmtId:
90520732090445, via: 21, Ver: v1, Flags: 110,
[{"com.cloud.agent.api.Answer":{"result":false,"details":"Unable to
save password to
DomR.","wait":0}},{"com.cloud.agent.api.Answer":{"result":false,"details":"Stopped
by previous failure","wait":0}}] }

On Wed, Nov 13, 2013 at 10:26 AM, Chip Childers  wrote:
> On Tue, Nov 12, 2013 at 10:52 AM, Abhinandan Prateek
>  wrote:
>>
>>This vote is to approve the current RC build for 4.2.1 maintenance 
>> release.
>> For this particular release various upgrade paths have been tested apart 
>> from regression tests and BVTs.
>> Around 175 bugs have been fixed some new features added (see CHANGES).
>>
>> Following are the particulars for this release:
>>
>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.2
>> commit: 0b9eadaf14513f5c72de672963b0e2f12ee7206f
>>
>> List of changes:
>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CHANGES;hb=4.2.1
>>
>> Source release revision 3492 (checksums and signatures are available at the 
>> same location):
>> https://dist.apache.org/repos/dist/dev/cloudstack/4.2.1/
>>
>> PGP release keys (signed using RSA Key ID = 42443AA1):
>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>
>> Vote will be open for 72 hours (until 11/15 End of day PST).
>>
>> For sanity in tallying the vote, can PMC members please be sure to indicate 
>> "(binding)" with their vote?
>>
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>
> +1 (binding)
>
> I only performed very rudimentary functional testing, but the
> artifact's look legit.
>
> Thanks for doing this Abhi!

Re: Retreive VM snapshot size

[Mike Tutkowski]

If delta snapshots are in use, my question would be, "What does the size of
such a snapshot really mean?"

For example, if you delete that snapshot, it doesn't mean that's the amount
of space you're going to get back.

How is this snapshot size info to be used?


On Wed, Nov 13, 2013 at 4:51 AM, Antonio Petrocelli <
a.petroce...@netsons.com> wrote:

> Hello,
>
> someone knows how to obtain the size of a VM snapshot with CLOUDSTACK 4.2
> API?
>
> with this call _http://cloudstack.apache.org/docs/api/apidocs-4.2/domain_
> admin/listVMSnapshot.html_ size is not specified.
>
> Thanks.
>
> Regards.
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*™*

Re: Review Request 15489: Adding protocol parameter to loadbalancer response

[Syed Ahmed]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15489/
---

(Updated Nov. 13, 2013, 6:08 p.m.)


Review request for cloudstack, Alena Prokharchyk and Murali Reddy.


Changes
---

Adding branch


Repository: cloudstack-git


Description
---

Adding protocol parameter to Loadbalancer Response


Diffs
-

  api/src/com/cloud/network/rules/LoadBalancer.java e6dadca 
  api/src/com/cloud/network/rules/LoadBalancerContainer.java 9d5ea59 
  api/src/org/apache/cloudstack/api/response/LoadBalancerResponse.java 0f18097 
  engine/schema/src/org/apache/cloudstack/lb/ApplicationLoadBalancerRuleVO.java 
37a747e 
  server/src/com/cloud/api/ApiResponseHelper.java 903c485 

Diff: https://reviews.apache.org/r/15489/diff/


Testing
---


Thanks,

Syed Ahmed

Review Request 15489: Adding protocol parameter to loadbalancer response

[Syed Ahmed]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15489/
---

Review request for cloudstack, Alena Prokharchyk and Murali Reddy.


Repository: cloudstack-git


Description
---

Adding protocol parameter to Loadbalancer Response


Diffs
-

  api/src/com/cloud/network/rules/LoadBalancer.java e6dadca 
  api/src/com/cloud/network/rules/LoadBalancerContainer.java 9d5ea59 
  api/src/org/apache/cloudstack/api/response/LoadBalancerResponse.java 0f18097 
  engine/schema/src/org/apache/cloudstack/lb/ApplicationLoadBalancerRuleVO.java 
37a747e 
  server/src/com/cloud/api/ApiResponseHelper.java 903c485 

Diff: https://reviews.apache.org/r/15489/diff/


Testing
---


Thanks,

Syed Ahmed

Re: Question regarding ServerApiException

[Alena Prokharchyk]

Note that regular gets generic messages appended with "…please contact your 
system administrator" when server side exception happens. Thats by design as 
regular user doesn't need to know the specifics, all he needs to do – let the 
admin know, and the admin will do the further debugging/fixing.

While admin should get the message explaining the root cause of the error. Its 
a known problem that in lots of the cases CS lacks the details, and it should 
get fixed. But again, for Root admin only.

-Alena.

From: Mike Tutkowski 
mailto:mike.tutkow...@solidfire.com>>
Date: Wednesday, November 13, 2013 9:46 AM
To: "dev@cloudstack.apache.org" 
mailto:dev@cloudstack.apache.org>>
Cc: Alena Prokharchyk 
mailto:alena.prokharc...@citrix.com>>, Edison Su 
mailto:edison...@citrix.com>>
Subject: Re: Question regarding ServerApiException

Hey Chris,

I think you've got a great point here. It would be nice if ServerApiException's 
getMessage() method were overridden to return getMessage().

I've noticed on occasion, as well, that exceptions I throw out of my plug-in 
get caught elsewhere and a more generic (somewhat useless) error message is 
displayed instead of the text I provided.

Talk to you later


On Wed, Nov 13, 2013 at 7:28 AM, SuichII, Christopher 
mailto:chris.su...@netapp.com>> wrote:
Alena & Edison (or others),

Is there a reason that ServerApiException has a getDescription() method rather 
than using getMessage() like all other exceptions? This causes problems in 
places where you’d like to treat all exceptions generically and be able to 
simply call getMessage(), but ServerApiException always returns null.

For example, I’m trying to fix an issue with StorageManagerImpl, where all 
errors provisioning a new storage pool simply return “Failed to add data store” 
without any actual meaningful error message. In general, we could do something 
like “Failed to add data store: “+e.getMessage(), however, that won’t work for 
ServerApiExceptions and so they would need to be handled separately from 
regular exceptions. One thought I had would be to override ServerApiException’s 
getMessage() and just return the description.

While were on the topic, is there a reason why we shouldn’t update error 
messages like “Failed to add data store” to include the exception’s message? It 
would be very beneficial for plugins and storage vendors to be able to return 
meaningful error messages from failed operations.

-Chris
--
Chris Suich
chris.su...@netapp.com
NetApp Software Engineer
Data Center Platforms – Cloud Solutions
Citrix, Cisco & Red Hat




--
Mike Tutkowski
Senior CloudStack Developer, SolidFire Inc.
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the 
cloud™

Re: Question regarding ServerApiException

[Mike Tutkowski]

Hey Chris,

I think you've got a great point here. It would be nice if
ServerApiException's getMessage() method were overridden to return
getMessage().

I've noticed on occasion, as well, that exceptions I throw out of my
plug-in get caught elsewhere and a more generic (somewhat useless) error
message is displayed instead of the text I provided.

Talk to you later


On Wed, Nov 13, 2013 at 7:28 AM, SuichII, Christopher <
chris.su...@netapp.com> wrote:

> Alena & Edison (or others),
>
> Is there a reason that ServerApiException has a getDescription() method
> rather than using getMessage() like all other exceptions? This causes
> problems in places where you’d like to treat all exceptions generically and
> be able to simply call getMessage(), but ServerApiException always returns
> null.
>
> For example, I’m trying to fix an issue with StorageManagerImpl, where all
> errors provisioning a new storage pool simply return “Failed to add data
> store” without any actual meaningful error message. In general, we could do
> something like “Failed to add data store: “+e.getMessage(), however, that
> won’t work for ServerApiExceptions and so they would need to be handled
> separately from regular exceptions. One thought I had would be to override
> ServerApiException’s getMessage() and just return the description.
>
> While were on the topic, is there a reason why we shouldn’t update error
> messages like “Failed to add data store” to include the exception’s
> message? It would be very beneficial for plugins and storage vendors to be
> able to return meaningful error messages from failed operations.
>
> -Chris
> --
> Chris Suich
> chris.su...@netapp.com
> NetApp Software Engineer
> Data Center Platforms – Cloud Solutions
> Citrix, Cisco & Red Hat
>
>


-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*™*

Re: A question on vm migrations when hosts are set into a maintenance mode.

[Alex Ough]

It sounds a little scary...

I looked at the history and found these.

8/9/ : file moved to engine by Alex Huang
9/16 : '_mgmtServer.getExecuteInSequence()' changed to
'getExecuteInSequence()' by Alex Huang


Hi Alex Huang,
I'm not sure if you're aware of this, but can you check this for me?

Thanks
Alex Ough



On Wed, Nov 13, 2013 at 11:18 AM, Marcus Sorensen wrote:

> I'm not sure. I know in the past when I've seen files change locations
> it has also clobbered updates to that file. Someone branched, did the
> reorganization work, and merged, while in-between the original file
> changed.
>
> On Wed, Nov 13, 2013 at 9:21 AM, Alex Ough  wrote:
> > All,
> >
> > While merging my changes to 4.3 branch, I found that the option,
> > 'execute.in.sequence.hypervisor.commands' is NOT used in Start/Stop/Copy
> > commands in 'VirtualMachineManagerImpl.java' any more as below.
> >
> >
> > *StopCommand stop = new StopCommand(vm, getExecuteInSequence());*
> >
> > *protected boolean getExecuteInSequence() {*
> > * return false;*
> > *}*
> >
> > As you see in the above, the function, 'getExecuteInSequence', just
> returns
> > false instead of getting the value from the global variable.
> >
> > And one more change is that the file has been moved to
> > 'engine/orchestration/src/com/cloud/vm' from 'server/src/com/cloud/vm'.
> >
> > Am I missing something related with this or do we stop supporting this
> > option in 4.3?
> > I'm a little confused, so please help me resolve this.
> >
> > Thanks
> > Alex Ough
> >
> >
> >
> >
> > On Tue, Nov 12, 2013 at 4:20 PM, Alex Ough 
> wrote:
> >
> >> Thanks a lot for your confirmation, Marcus.
> >> I'll create a review request unless anyone has an objection.
> >>
> >> Thanks
> >> Alex Ough
> >>
> >>
> >> On Tue, Nov 12, 2013 at 3:37 PM, Marcus Sorensen  >wrote:
> >>
> >>>  I have done parallel KVM migrations without issue, it's "supposed to
> >>> work". Really I think it's in the same boat as parallel start/stop. It
> >>> should work, but the config option is there just in case. I think we
> >>> should add it.
> >>>
> >>> On Thu, Oct 3, 2013 at 11:41 AM, Chip Childers
> >>>  wrote:
> >>> > On Thu, Oct 03, 2013 at 11:44:46AM -0500, Alex Ough wrote:
> >>> >> I'm not sure what else commands 'MigrateCommand' actually execute in
> >>> >> addition to 'Start/Stop/CopyCommand', but can we include
> >>> 'MigrateCommand'
> >>> >> if it consists of only those 3 commands?
> >>> >>
> >>> >> Thanks
> >>> >> Alex Ough
> >>> >
> >>> > In the case of VMware, the migrate command is executed via the
> >>> > MigrateVMTask that's part of the VMware SDK (see
> >>> >
> vmware-base/src/com/cloud/hypervisor/vmware/mo/VirtualMachineMO.java).
> >>> >
> >>> > For VMware, I know that vCenter will queue and process concurrent
> >>> > requests for migrations.  Specifically, it will throttle the
> migrations
> >>> > happening, based on it's internal concurrency constraints, but the
> task
> >>> > queue will still accept more connections.  Obviously the risk are the
> >>> > VMware layer tasks timing out if it takes too long for the task
> queue to
> >>> > complete.
> >>> >
> >>> > As for XenServer, it's happening in what appears to be a similar way
> >>> > (although the source host is the target for the migration API call).
> >>> >
> >>> > Check
> >>> >
> >>>
> plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/resource/CitrixResourceBase.java.
> >>> >
> >>> > I'm not familiar enough with XenServer's concurrency model for
> >>> > migrations.  Any experts know the answer to if it can handle
> concurrency
> >>> > in a stable way?
> >>> >
> >>> > With KVM, it's obviously executing via the agent.  Similarly to
> >>> > XenServer, I'm not familiar enough to know about concurrent
> operations.
> >>> >
> >>> > So do the HV experts on the list have any opinions about XenServer
> and
> >>> > KVM migration concurrency?
> >>> >
> >>> > -chip
> >>> >
> >>> >
> >>>
> >>>
> >>
>
>

Re: [VOTE] Release Apache CloudStack 4.2.1

[Chip Childers]

On Tue, Nov 12, 2013 at 10:52 AM, Abhinandan Prateek
 wrote:
>
>This vote is to approve the current RC build for 4.2.1 maintenance release.
> For this particular release various upgrade paths have been tested apart from 
> regression tests and BVTs.
> Around 175 bugs have been fixed some new features added (see CHANGES).
>
> Following are the particulars for this release:
>
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.2
> commit: 0b9eadaf14513f5c72de672963b0e2f12ee7206f
>
> List of changes:
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CHANGES;hb=4.2.1
>
> Source release revision 3492 (checksums and signatures are available at the 
> same location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.2.1/
>
> PGP release keys (signed using RSA Key ID = 42443AA1):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> Vote will be open for 72 hours (until 11/15 End of day PST).
>
> For sanity in tallying the vote, can PMC members please be sure to indicate 
> "(binding)" with their vote?
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)

+1 (binding)

I only performed very rudimentary functional testing, but the
artifact's look legit.

Thanks for doing this Abhi!

Re: A question on vm migrations when hosts are set into a maintenance mode.

[Marcus Sorensen]

I'm not sure. I know in the past when I've seen files change locations
it has also clobbered updates to that file. Someone branched, did the
reorganization work, and merged, while in-between the original file
changed.

On Wed, Nov 13, 2013 at 9:21 AM, Alex Ough  wrote:
> All,
>
> While merging my changes to 4.3 branch, I found that the option,
> 'execute.in.sequence.hypervisor.commands' is NOT used in Start/Stop/Copy
> commands in 'VirtualMachineManagerImpl.java' any more as below.
>
>
> *StopCommand stop = new StopCommand(vm, getExecuteInSequence());*
>
> *protected boolean getExecuteInSequence() {*
> * return false;*
> *}*
>
> As you see in the above, the function, 'getExecuteInSequence', just returns
> false instead of getting the value from the global variable.
>
> And one more change is that the file has been moved to
> 'engine/orchestration/src/com/cloud/vm' from 'server/src/com/cloud/vm'.
>
> Am I missing something related with this or do we stop supporting this
> option in 4.3?
> I'm a little confused, so please help me resolve this.
>
> Thanks
> Alex Ough
>
>
>
>
> On Tue, Nov 12, 2013 at 4:20 PM, Alex Ough  wrote:
>
>> Thanks a lot for your confirmation, Marcus.
>> I'll create a review request unless anyone has an objection.
>>
>> Thanks
>> Alex Ough
>>
>>
>> On Tue, Nov 12, 2013 at 3:37 PM, Marcus Sorensen wrote:
>>
>>>  I have done parallel KVM migrations without issue, it's "supposed to
>>> work". Really I think it's in the same boat as parallel start/stop. It
>>> should work, but the config option is there just in case. I think we
>>> should add it.
>>>
>>> On Thu, Oct 3, 2013 at 11:41 AM, Chip Childers
>>>  wrote:
>>> > On Thu, Oct 03, 2013 at 11:44:46AM -0500, Alex Ough wrote:
>>> >> I'm not sure what else commands 'MigrateCommand' actually execute in
>>> >> addition to 'Start/Stop/CopyCommand', but can we include
>>> 'MigrateCommand'
>>> >> if it consists of only those 3 commands?
>>> >>
>>> >> Thanks
>>> >> Alex Ough
>>> >
>>> > In the case of VMware, the migrate command is executed via the
>>> > MigrateVMTask that's part of the VMware SDK (see
>>> > vmware-base/src/com/cloud/hypervisor/vmware/mo/VirtualMachineMO.java).
>>> >
>>> > For VMware, I know that vCenter will queue and process concurrent
>>> > requests for migrations.  Specifically, it will throttle the migrations
>>> > happening, based on it's internal concurrency constraints, but the task
>>> > queue will still accept more connections.  Obviously the risk are the
>>> > VMware layer tasks timing out if it takes too long for the task queue to
>>> > complete.
>>> >
>>> > As for XenServer, it's happening in what appears to be a similar way
>>> > (although the source host is the target for the migration API call).
>>> >
>>> > Check
>>> >
>>> plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/resource/CitrixResourceBase.java.
>>> >
>>> > I'm not familiar enough with XenServer's concurrency model for
>>> > migrations.  Any experts know the answer to if it can handle concurrency
>>> > in a stable way?
>>> >
>>> > With KVM, it's obviously executing via the agent.  Similarly to
>>> > XenServer, I'm not familiar enough to know about concurrent operations.
>>> >
>>> > So do the HV experts on the list have any opinions about XenServer and
>>> > KVM migration concurrency?
>>> >
>>> > -chip
>>> >
>>> >
>>>
>>>
>>

Re: ui styling

[Marcus Sorensen]

Will take a look. I assume that the 4.3 changes are mostly in place
right now. Is it just those specific locations, or could/should the
whole ui directory be moved?

On Wed, Oct 30, 2013 at 2:07 PM, Brian Federle  wrote:
> Hi Frankie, unfortunately that would be hard to do, since they were just 
> incremental changes applied on master. I would have to cherry pick all the 
> commits I did over time, which would take a while :). What you can try is 
> copying the updated CSS files (/css), images (/images) and all scripts under 
> ui/widgets to your local build (in the same respective folders). Note that 
> this would contain some work-in-progress UI functionality for 4.3 that may or 
> may not be working.
>
> -Brian
>
> -Original Message-
> From: Frankie Onuonga [mailto:frankie.onuo...@gmail.com]
> Sent: Tuesday, October 29, 2013 10:11 PM
> To: dev@cloudstack.apache.org
> Subject: Re: ui styling
>
> I also wish this was the case.
> I am still trying to get in touch with the team to assist them with this.
> Hope someone gets back to me.
>
> I think I can commit a week to get this done.
>
> thanks
>
>
> On Wed, Oct 30, 2013 at 4:35 AM, Marcus Sorensen wrote:
>
>> I'm digging the UI styling changes!  It makes me wish they were all
>> merged in from a branch as a squashed commit so I could pull them out
>> and apply them to our local 4.2 build.
>>
>
>
>
> --
> Skype: Frankie Onuonga
> twitter: Frankie.onuonga
> irc #freenode: Frankie.onuonga

Re: [VOTE] Release Apache CloudStack 4.2.1

[Srikanteswararao Talluri]

+1 

I have deployed advanced zone with XenServer 6.2 host and system vms came
up with out any problem.
Tested following -
VM snapshot:
1. Deployed an instance and populated some data.
2. Took a snapshot.
3. Reverted the VM to the snapshot created in step2 and could see the data
that was present when the
Snapshot was taken.
PF rule:
1. Deployed an instance in isolated network
2. Created PF rule between 22 -> 
3. Added firewall rule for 
4. I could ssh to the public IP using port .

Thanks,
~Talluri






On 13/11/13 10:14 pm, "Daan Hoogland"  wrote:

>well, mine is a go, I have a symptom not a decease.
>
>On Wed, Nov 13, 2013 at 3:45 PM, Abhinandan Prateek
> wrote:
>>
>>
>> On 13/11/13 7:14 pm, "Daan Hoogland"  wrote:
>>
>>>I tested 4.2.1 with our custom vpc gateway on nvp patch basic usage in
>>>a adnvanced zone with niciranvp or with vlans work That means creating
>>>an standalone network or a vpc with a tier and in all cases with an
>>>instance being able to ping the outside world. I encountered one
>>>strange exception:
>>>
>>>WARN  [agent.manager.AgentManagerImpl] (AgentManager-Handler-6:) Caught:
>>>java.lang.NumberFormatException: For input string:
>>>"63424ecc-ee5c-49a0-b880-d1f879593822"
>>>at java.lang.NumberFormatException.forInputString(Unknown Source)
>>>at java.lang.Long.parseLong(Unknown Source)
>>>at java.lang.Long.parseLong(Unknown Source)
>>>at
>>>com.cloud.consoleproxy.AgentHookBase.onConsoleAccessAuthentication(Agent
>>>Ho
>>>okBase.java:135)
>>>at
>>>com.cloud.consoleproxy.ConsoleProxyListener.processControlCommand(Consol
>>>eP
>>>roxyListener.java:61)
>>>at
>>>com.cloud.agent.manager.AgentManagerImpl.handleControlCommand(AgentManag
>>>er
>>>Impl.java:347)
>>>at
>>>com.cloud.agent.manager.AgentManagerImpl.access$200(AgentManagerImpl.jav
>>>a:
>>>144)
>>>at
>>>com.cloud.agent.manager.AgentManagerImpl$AgentHandler.processRequest(Age
>>>nt
>>>ManagerImpl.java:1260)
>>>at
>>>com.cloud.agent.manager.AgentManagerImpl$AgentHandler.doTask(AgentManage
>>>rI
>>>mpl.java:1348)
>>>at
>>>com.cloud.agent.manager.ClusteredAgentManagerImpl$ClusteredAgentHandler.
>>>do
>>>Task(ClusteredAgentManagerImpl.java:666)
>>>at com.cloud.utils.nio.Task.run(Task.java:83)
>>>at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>>>at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
>>>Source)
>>>at java.lang.Thread.run(Unknown Source)
>>>
>>>I will now test to rule out the patch for this though it is in
>>>untouched code. I will enter a ticket or hold my peace forever after.
>>>
>>>btw, this is a pre-vote thread for these kinds of reports is it?
>>>
>> I think it is fine to highlight issues if any, I will wait for you final
>> say on this ?
>> Though I hope I do not carry the burden of this release to collab next
>> week :-)
>>
>> -abhi
>>>
>>

Re: [VOTE] Release Apache CloudStack 4.2.1

[Daan Hoogland]

well, mine is a go, I have a symptom not a decease.

On Wed, Nov 13, 2013 at 3:45 PM, Abhinandan Prateek
 wrote:
>
>
> On 13/11/13 7:14 pm, "Daan Hoogland"  wrote:
>
>>I tested 4.2.1 with our custom vpc gateway on nvp patch basic usage in
>>a adnvanced zone with niciranvp or with vlans work That means creating
>>an standalone network or a vpc with a tier and in all cases with an
>>instance being able to ping the outside world. I encountered one
>>strange exception:
>>
>>WARN  [agent.manager.AgentManagerImpl] (AgentManager-Handler-6:) Caught:
>>java.lang.NumberFormatException: For input string:
>>"63424ecc-ee5c-49a0-b880-d1f879593822"
>>at java.lang.NumberFormatException.forInputString(Unknown Source)
>>at java.lang.Long.parseLong(Unknown Source)
>>at java.lang.Long.parseLong(Unknown Source)
>>at
>>com.cloud.consoleproxy.AgentHookBase.onConsoleAccessAuthentication(AgentHo
>>okBase.java:135)
>>at
>>com.cloud.consoleproxy.ConsoleProxyListener.processControlCommand(ConsoleP
>>roxyListener.java:61)
>>at
>>com.cloud.agent.manager.AgentManagerImpl.handleControlCommand(AgentManager
>>Impl.java:347)
>>at
>>com.cloud.agent.manager.AgentManagerImpl.access$200(AgentManagerImpl.java:
>>144)
>>at
>>com.cloud.agent.manager.AgentManagerImpl$AgentHandler.processRequest(Agent
>>ManagerImpl.java:1260)
>>at
>>com.cloud.agent.manager.AgentManagerImpl$AgentHandler.doTask(AgentManagerI
>>mpl.java:1348)
>>at
>>com.cloud.agent.manager.ClusteredAgentManagerImpl$ClusteredAgentHandler.do
>>Task(ClusteredAgentManagerImpl.java:666)
>>at com.cloud.utils.nio.Task.run(Task.java:83)
>>at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>>at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>>at java.lang.Thread.run(Unknown Source)
>>
>>I will now test to rule out the patch for this though it is in
>>untouched code. I will enter a ticket or hold my peace forever after.
>>
>>btw, this is a pre-vote thread for these kinds of reports is it?
>>
> I think it is fine to highlight issues if any, I will wait for you final
> say on this ?
> Though I hope I do not carry the burden of this release to collab next
> week :-)
>
> -abhi
>>
>

Re: Review Request 14058: Including tests for VPC VM Lifecycle on Tagged hosts

[Girish Shilamkar]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/14058/#review28811
---


Committed to 4.2, 4.3 and master.

- Girish Shilamkar


On Nov. 8, 2013, 1:48 p.m., Ashutosh Kelkar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/14058/
> ---
> 
> (Updated Nov. 8, 2013, 1:48 p.m.)
> 
> 
> Review request for cloudstack, Girish Shilamkar, venkata swamy babu  
> budumuru, and Sheng Yang.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Added 10 tests for VPC VM liftcycle on tagged hosts
> 
> New class added  : TestVMLifeCycleDiffHosts
> 
> def test_01_deploy_instance_in_network(self):
> def test_02_stop_instance_in_network(self):
> def test_03_start_instance_in_network(self):
> def test_04_reboot_instance_in_network(self):
> def test_05_destroy_instance_in_network(self):
> def test_06_recover_instance_in_network(self):
> def test_07_migrate_instance_in_network(self):
> def test_08_user_data(self):
> def test_09_meta_data(self):
> def   test_10_expunge_instance_in_network(self):
> 
> This set of tests requires a multi host tagged setup (3 hosts - 2 hosts with 
> tag 'host1' and  1 host with tag 'host2')
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_vpc_vm_life_cycle.py cc65eed 
>   tools/marvin/marvin/integration/lib/base.py 10c636c 
> 
> Diff: https://reviews.apache.org/r/14058/diff/
> 
> 
> Testing
> ---
> 
> Tested locally on KVM advanced setup.
> 
> Log:
> 
> test_01_deploy_instance_in_network 
> (test_vpc_vm_life_cycle.TestVMLifeCycleDiffHosts)
> Test deploy an instance in VPC networks ... ok
> test_02_stop_instance_in_network 
> (test_vpc_vm_life_cycle.TestVMLifeCycleDiffHosts)
> Test stop an instance in VPC networks ... ok
> test_03_start_instance_in_network 
> (test_vpc_vm_life_cycle.TestVMLifeCycleDiffHosts)
> Test start an instance in VPC networks ... ok
> test_04_reboot_instance_in_network 
> (test_vpc_vm_life_cycle.TestVMLifeCycleDiffHosts)
> Test reboot an instance in VPC networks ... ok
> test_05_destroy_instance_in_network 
> (test_vpc_vm_life_cycle.TestVMLifeCycleDiffHosts)
> Test destroy an instance in VPC networks ... ok
> test_06_migrate_instance_in_network 
> (test_vpc_vm_life_cycle.TestVMLifeCycleDiffHosts)
> Test migrate an instance in VPC networks ... ok
> test_07_user_data (test_vpc_vm_life_cycle.TestVMLifeCycleDiffHosts)
> Test user data in virtual machines ... ok
> test_08_meta_data (test_vpc_vm_life_cycle.TestVMLifeCycleDiffHosts)
> Test meta data in virtual machines ... ok
> test_09_expunge_instance_in_network 
> (test_vpc_vm_life_cycle.TestVMLifeCycleDiffHosts)
> Test expunge an instance in VPC networks ... ok
> 
> 
> Thanks,
> 
> Ashutosh Kelkar
> 
>

Re: Review Request 13841: Missing tests from QA repo to ASF - 3 tests from test_vmware_drs.py

[Girish Shilamkar]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/13841/#review28810
---


Committed to 4.2, 4.3 and master

- Girish Shilamkar


On Oct. 30, 2013, 7:01 a.m., Ashutosh Kelkar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/13841/
> ---
> 
> (Updated Oct. 30, 2013, 7:01 a.m.)
> 
> 
> Review request for cloudstack, Girish Shilamkar and Harikrishna Patnala.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> New File added: test_vmware_drs.py
> Tests added   : def test_vm_creation_in_fully_automated_mode(self):
> def test_vmware_anti_affinity(self):
> def test_vmware_affinity(self):
> 
> The tests need manual setup and therefore have been marked as WIP and
> skipped for the moment
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_vmware_drs.py PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/13841/diff/
> 
> 
> Testing
> ---
> 
> Tested locally.
> 
> One test case is working, two are skipped (one due to unavailability of 
> particular setup and other die to feature not available in cloudstack yet)
> 
> Run Log:
> ==> client.log <==
> 2013-10-08 02:27:43,371 - DEBUG - test_vm_creation_in_fully_automated_mode 
> (test_vmware_drs.TestVMPlacement) - max memory: 14911
> 
> ==> result.log <==
> test_vmware_affinity (test_vmware_drs.TestAffinityRules)
> Test Set up affinity rules ... skipped 'Skip'
> test_vmware_anti_affinity (test_vmware_drs.TestAntiAffinityRules)
> Test Set up anti-affinity rules ... skipped 'Skip'
> test_vm_creation_in_fully_automated_mode (test_vmware_drs.TestVMPlacement)
> Test VM Creation in  automation mode = Fully automated ...
> ==> client.log <==
> 2013-10-08 02:28:53,855 - DEBUG - test_vm_creation_in_fully_automated_mode 
> (test_vmware_drs.TestVMPlacement) - Deploying VM in account: test-R7LY31
> 
> ==> result.log <==
> ok
> 
> --
> Ran 3 tests in 241.612s
> 
> OK (skipped=2)
> 
> 
> Thanks,
> 
> Ashutosh Kelkar
> 
>

Re: A question on vm migrations when hosts are set into a maintenance mode.

[Alex Ough]

All,

While merging my changes to 4.3 branch, I found that the option,
'execute.in.sequence.hypervisor.commands' is NOT used in Start/Stop/Copy
commands in 'VirtualMachineManagerImpl.java' any more as below.


*StopCommand stop = new StopCommand(vm, getExecuteInSequence());*

*protected boolean getExecuteInSequence() {*
* return false;*
*}*

As you see in the above, the function, 'getExecuteInSequence', just returns
false instead of getting the value from the global variable.

And one more change is that the file has been moved to
'engine/orchestration/src/com/cloud/vm' from 'server/src/com/cloud/vm'.

Am I missing something related with this or do we stop supporting this
option in 4.3?
I'm a little confused, so please help me resolve this.

Thanks
Alex Ough




On Tue, Nov 12, 2013 at 4:20 PM, Alex Ough  wrote:

> Thanks a lot for your confirmation, Marcus.
> I'll create a review request unless anyone has an objection.
>
> Thanks
> Alex Ough
>
>
> On Tue, Nov 12, 2013 at 3:37 PM, Marcus Sorensen wrote:
>
>>  I have done parallel KVM migrations without issue, it's "supposed to
>> work". Really I think it's in the same boat as parallel start/stop. It
>> should work, but the config option is there just in case. I think we
>> should add it.
>>
>> On Thu, Oct 3, 2013 at 11:41 AM, Chip Childers
>>  wrote:
>> > On Thu, Oct 03, 2013 at 11:44:46AM -0500, Alex Ough wrote:
>> >> I'm not sure what else commands 'MigrateCommand' actually execute in
>> >> addition to 'Start/Stop/CopyCommand', but can we include
>> 'MigrateCommand'
>> >> if it consists of only those 3 commands?
>> >>
>> >> Thanks
>> >> Alex Ough
>> >
>> > In the case of VMware, the migrate command is executed via the
>> > MigrateVMTask that's part of the VMware SDK (see
>> > vmware-base/src/com/cloud/hypervisor/vmware/mo/VirtualMachineMO.java).
>> >
>> > For VMware, I know that vCenter will queue and process concurrent
>> > requests for migrations.  Specifically, it will throttle the migrations
>> > happening, based on it's internal concurrency constraints, but the task
>> > queue will still accept more connections.  Obviously the risk are the
>> > VMware layer tasks timing out if it takes too long for the task queue to
>> > complete.
>> >
>> > As for XenServer, it's happening in what appears to be a similar way
>> > (although the source host is the target for the migration API call).
>> >
>> > Check
>> >
>> plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/resource/CitrixResourceBase.java.
>> >
>> > I'm not familiar enough with XenServer's concurrency model for
>> > migrations.  Any experts know the answer to if it can handle concurrency
>> > in a stable way?
>> >
>> > With KVM, it's obviously executing via the agent.  Similarly to
>> > XenServer, I'm not familiar enough to know about concurrent operations.
>> >
>> > So do the HV experts on the list have any opinions about XenServer and
>> > KVM migration concurrency?
>> >
>> > -chip
>> >
>> >
>>
>>
>

Re: Review Request 15477: CLOUDSTACK-5155: Removing basic and sg tags from test case which is invalid for basic zone

[ASF Subversion and Git Services]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15477/#review28808
---


Commit 5b5e444861f90feebf9a1f3b9ec0f05db61fb38b in branch refs/heads/4.3 from 
Gaurav Aradhye
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5b5e444 ]

CLOUDSTACK-5155: Removing basic and sg tags from test case
 which is invalid for basic zone


- ASF Subversion and Git Services


On Nov. 13, 2013, 1:43 p.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/15477/
> ---
> 
> (Updated Nov. 13, 2013, 1:43 p.m.)
> 
> 
> Review request for cloudstack, Girish Shilamkar and SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-5155
> https://issues.apache.org/jira/browse/CLOUDSTACK-5155
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> component.test_stopped_vm.TestRouterStateAfterDeploy.test_01_deploy_vm_no_startvm
> This test case assumes that each new VM deployment will create a router in 
> that account, which is invalid scenario for the basic zone.
> Removing basic and sg tags.
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_stopped_vm.py 2586c0b 
> 
> Diff: https://reviews.apache.org/r/15477/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Gaurav Aradhye
> 
>

Re: Review Request 15477: CLOUDSTACK-5155: Removing basic and sg tags from test case which is invalid for basic zone

[ASF Subversion and Git Services]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15477/#review28806
---


Commit 6c8b946f5c70a10c6869278d07ed057e153a6c99 in branch refs/heads/4.2 from 
Gaurav Aradhye
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6c8b946 ]

CLOUDSTACK-5155: Removing basic and sg tags from test case
 which is invalid for basic zone


- ASF Subversion and Git Services


On Nov. 13, 2013, 1:43 p.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/15477/
> ---
> 
> (Updated Nov. 13, 2013, 1:43 p.m.)
> 
> 
> Review request for cloudstack, Girish Shilamkar and SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-5155
> https://issues.apache.org/jira/browse/CLOUDSTACK-5155
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> component.test_stopped_vm.TestRouterStateAfterDeploy.test_01_deploy_vm_no_startvm
> This test case assumes that each new VM deployment will create a router in 
> that account, which is invalid scenario for the basic zone.
> Removing basic and sg tags.
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_stopped_vm.py 2586c0b 
> 
> Diff: https://reviews.apache.org/r/15477/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Gaurav Aradhye
> 
>

Re: Review Request 15477: CLOUDSTACK-5155: Removing basic and sg tags from test case which is invalid for basic zone

[ASF Subversion and Git Services]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15477/#review28807
---


Commit 6aff6aa601a165f00bfaad6543e4b2a33d798806 in branch refs/heads/master 
from Gaurav Aradhye
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6aff6aa ]

CLOUDSTACK-5155: Removing basic and sg tags from test case
 which is invalid for basic zone


- ASF Subversion and Git Services


On Nov. 13, 2013, 1:43 p.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/15477/
> ---
> 
> (Updated Nov. 13, 2013, 1:43 p.m.)
> 
> 
> Review request for cloudstack, Girish Shilamkar and SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-5155
> https://issues.apache.org/jira/browse/CLOUDSTACK-5155
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> component.test_stopped_vm.TestRouterStateAfterDeploy.test_01_deploy_vm_no_startvm
> This test case assumes that each new VM deployment will create a router in 
> that account, which is invalid scenario for the basic zone.
> Removing basic and sg tags.
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_stopped_vm.py 2586c0b 
> 
> Diff: https://reviews.apache.org/r/15477/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Gaurav Aradhye
> 
>

Re: Review Request 15478: CLOUDSTACK-5156: Fixed test script issue related to detach volume

[Girish Shilamkar]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15478/#review28805
---

Ship it!


Ship It!

- Girish Shilamkar


On Nov. 13, 2013, 2:06 p.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/15478/
> ---
> 
> (Updated Nov. 13, 2013, 2:06 p.m.)
> 
> 
> Review request for cloudstack, Girish Shilamkar and SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-5156
> https://issues.apache.org/jira/browse/CLOUDSTACK-5156
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> component.test_stopped_vm.TestDeployVM.test_08_deploy_attached_volume
> This test was failing during detaching volume from a virtual machine.
> But the volume which was being detached from the virtual machine was obtained 
> from listing the volumes belonging to the same account and picking up the 
> first element in the list which does not guarantee that it is the same volume 
> belonging to the VM as the same account is used in many test cases.
> 
> Passed virtualmachineid parameter to get the exact volume belonging to the 
> virtual machine and now the test case works.
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_stopped_vm.py 2586c0b 
> 
> Diff: https://reviews.apache.org/r/15478/diff/
> 
> 
> Testing
> ---
> 
> Tested locally on XenServer basic zone setup.
> 
> Log:
> 
> ==> client.log <==
> 2013-11-13 02:03:42,866 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Verify listVirtualMachines response for 
> virtual machine: 20930
> 0b9-0f42-4c73-941d-93c75b168203
> 2013-11-13 02:03:42,866 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Deploying instance in the account: 
> test-P6HACO
> 2013-11-13 02:04:08,353 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Deployed instance in account: test-P6HACO
> 2013-11-13 02:04:08,395 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Verify listVirtualMachines response for 
> virtual machine: 8f68e
> fd6-9d64-44e1-9998-ce03d0158cb8
> 2013-11-13 02:04:08,395 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Fetching DATADISK details for instance: 
> 8f68efd6-9d64-44e1-999
> 8-ce03d0158cb8
> 2013-11-13 02:04:08,418 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Detaching the disk: DATA-263
> 2013-11-13 02:04:13,537 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Datadisk DATA-263 detached!
> 2013-11-13 02:04:13,537 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Attaching volume to instance: 
> 209300b9-0f42-4c73-941d-93c75b16
> 8203
> 2013-11-13 02:04:18,668 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Cleaning up the resources
> 2013-11-13 02:04:33,825 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Cleanup complete!
> 
> ==> result.log <==
> Test Deploy Virtual Machine with no startVM parameter ... skipped 'Skip'
> test_upload_attach_volume (test_stopped_vm.TestUploadAttachVolume)
> Test Upload volume and attach to VM in stopped state ... skipped 'Skip'
> test_vm_per_account (test_stopped_vm.TestVMAccountLimit)
> Test VM limit per account ... skipped 'Skip'
> 
> --
> Ran 17 tests in 56.691s
> 
> OK (skipped=16)
> 
> 
> Thanks,
> 
> Gaurav Aradhye
> 
>

Re: Review Request 15478: CLOUDSTACK-5156: Fixed test script issue related to detach volume

[Girish Shilamkar]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15478/#review28803
---

Ship it!


Ship It!

- Girish Shilamkar


On Nov. 13, 2013, 2:06 p.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/15478/
> ---
> 
> (Updated Nov. 13, 2013, 2:06 p.m.)
> 
> 
> Review request for cloudstack, Girish Shilamkar and SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-5156
> https://issues.apache.org/jira/browse/CLOUDSTACK-5156
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> component.test_stopped_vm.TestDeployVM.test_08_deploy_attached_volume
> This test was failing during detaching volume from a virtual machine.
> But the volume which was being detached from the virtual machine was obtained 
> from listing the volumes belonging to the same account and picking up the 
> first element in the list which does not guarantee that it is the same volume 
> belonging to the VM as the same account is used in many test cases.
> 
> Passed virtualmachineid parameter to get the exact volume belonging to the 
> virtual machine and now the test case works.
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_stopped_vm.py 2586c0b 
> 
> Diff: https://reviews.apache.org/r/15478/diff/
> 
> 
> Testing
> ---
> 
> Tested locally on XenServer basic zone setup.
> 
> Log:
> 
> ==> client.log <==
> 2013-11-13 02:03:42,866 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Verify listVirtualMachines response for 
> virtual machine: 20930
> 0b9-0f42-4c73-941d-93c75b168203
> 2013-11-13 02:03:42,866 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Deploying instance in the account: 
> test-P6HACO
> 2013-11-13 02:04:08,353 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Deployed instance in account: test-P6HACO
> 2013-11-13 02:04:08,395 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Verify listVirtualMachines response for 
> virtual machine: 8f68e
> fd6-9d64-44e1-9998-ce03d0158cb8
> 2013-11-13 02:04:08,395 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Fetching DATADISK details for instance: 
> 8f68efd6-9d64-44e1-999
> 8-ce03d0158cb8
> 2013-11-13 02:04:08,418 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Detaching the disk: DATA-263
> 2013-11-13 02:04:13,537 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Datadisk DATA-263 detached!
> 2013-11-13 02:04:13,537 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Attaching volume to instance: 
> 209300b9-0f42-4c73-941d-93c75b16
> 8203
> 2013-11-13 02:04:18,668 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Cleaning up the resources
> 2013-11-13 02:04:33,825 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Cleanup complete!
> 
> ==> result.log <==
> Test Deploy Virtual Machine with no startVM parameter ... skipped 'Skip'
> test_upload_attach_volume (test_stopped_vm.TestUploadAttachVolume)
> Test Upload volume and attach to VM in stopped state ... skipped 'Skip'
> test_vm_per_account (test_stopped_vm.TestVMAccountLimit)
> Test VM limit per account ... skipped 'Skip'
> 
> --
> Ran 17 tests in 56.691s
> 
> OK (skipped=16)
> 
> 
> Thanks,
> 
> Gaurav Aradhye
> 
>

Re: Review Request 15478: CLOUDSTACK-5156: Fixed test script issue related to detach volume

[ASF Subversion and Git Services]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15478/#review28804
---


Commit 9e2b7bfa7b740b732de98eb4e138373dc920dc7e in branch refs/heads/4.2 from 
Gaurav Aradhye
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9e2b7bf ]

CLOUDSTACK-5156: Fixed test script issue related to detach volume


- ASF Subversion and Git Services


On Nov. 13, 2013, 2:06 p.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/15478/
> ---
> 
> (Updated Nov. 13, 2013, 2:06 p.m.)
> 
> 
> Review request for cloudstack, Girish Shilamkar and SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-5156
> https://issues.apache.org/jira/browse/CLOUDSTACK-5156
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> component.test_stopped_vm.TestDeployVM.test_08_deploy_attached_volume
> This test was failing during detaching volume from a virtual machine.
> But the volume which was being detached from the virtual machine was obtained 
> from listing the volumes belonging to the same account and picking up the 
> first element in the list which does not guarantee that it is the same volume 
> belonging to the VM as the same account is used in many test cases.
> 
> Passed virtualmachineid parameter to get the exact volume belonging to the 
> virtual machine and now the test case works.
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_stopped_vm.py 2586c0b 
> 
> Diff: https://reviews.apache.org/r/15478/diff/
> 
> 
> Testing
> ---
> 
> Tested locally on XenServer basic zone setup.
> 
> Log:
> 
> ==> client.log <==
> 2013-11-13 02:03:42,866 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Verify listVirtualMachines response for 
> virtual machine: 20930
> 0b9-0f42-4c73-941d-93c75b168203
> 2013-11-13 02:03:42,866 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Deploying instance in the account: 
> test-P6HACO
> 2013-11-13 02:04:08,353 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Deployed instance in account: test-P6HACO
> 2013-11-13 02:04:08,395 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Verify listVirtualMachines response for 
> virtual machine: 8f68e
> fd6-9d64-44e1-9998-ce03d0158cb8
> 2013-11-13 02:04:08,395 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Fetching DATADISK details for instance: 
> 8f68efd6-9d64-44e1-999
> 8-ce03d0158cb8
> 2013-11-13 02:04:08,418 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Detaching the disk: DATA-263
> 2013-11-13 02:04:13,537 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Datadisk DATA-263 detached!
> 2013-11-13 02:04:13,537 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Attaching volume to instance: 
> 209300b9-0f42-4c73-941d-93c75b16
> 8203
> 2013-11-13 02:04:18,668 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Cleaning up the resources
> 2013-11-13 02:04:33,825 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Cleanup complete!
> 
> ==> result.log <==
> Test Deploy Virtual Machine with no startVM parameter ... skipped 'Skip'
> test_upload_attach_volume (test_stopped_vm.TestUploadAttachVolume)
> Test Upload volume and attach to VM in stopped state ... skipped 'Skip'
> test_vm_per_account (test_stopped_vm.TestVMAccountLimit)
> Test VM limit per account ... skipped 'Skip'
> 
> --
> Ran 17 tests in 56.691s
> 
> OK (skipped=16)
> 
> 
> Thanks,
> 
> Gaurav Aradhye
> 
>

Re: Review Request 15478: CLOUDSTACK-5156: Fixed test script issue related to detach volume

[ASF Subversion and Git Services]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15478/#review28802
---


Commit 4d21591bf81af12469c913e4ccfb50e1a76dce73 in branch refs/heads/4.3 from 
Gaurav Aradhye
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4d21591 ]

CLOUDSTACK-5156: Fixed test script issue related to detach volume


- ASF Subversion and Git Services


On Nov. 13, 2013, 2:06 p.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/15478/
> ---
> 
> (Updated Nov. 13, 2013, 2:06 p.m.)
> 
> 
> Review request for cloudstack, Girish Shilamkar and SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-5156
> https://issues.apache.org/jira/browse/CLOUDSTACK-5156
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> component.test_stopped_vm.TestDeployVM.test_08_deploy_attached_volume
> This test was failing during detaching volume from a virtual machine.
> But the volume which was being detached from the virtual machine was obtained 
> from listing the volumes belonging to the same account and picking up the 
> first element in the list which does not guarantee that it is the same volume 
> belonging to the VM as the same account is used in many test cases.
> 
> Passed virtualmachineid parameter to get the exact volume belonging to the 
> virtual machine and now the test case works.
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_stopped_vm.py 2586c0b 
> 
> Diff: https://reviews.apache.org/r/15478/diff/
> 
> 
> Testing
> ---
> 
> Tested locally on XenServer basic zone setup.
> 
> Log:
> 
> ==> client.log <==
> 2013-11-13 02:03:42,866 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Verify listVirtualMachines response for 
> virtual machine: 20930
> 0b9-0f42-4c73-941d-93c75b168203
> 2013-11-13 02:03:42,866 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Deploying instance in the account: 
> test-P6HACO
> 2013-11-13 02:04:08,353 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Deployed instance in account: test-P6HACO
> 2013-11-13 02:04:08,395 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Verify listVirtualMachines response for 
> virtual machine: 8f68e
> fd6-9d64-44e1-9998-ce03d0158cb8
> 2013-11-13 02:04:08,395 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Fetching DATADISK details for instance: 
> 8f68efd6-9d64-44e1-999
> 8-ce03d0158cb8
> 2013-11-13 02:04:08,418 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Detaching the disk: DATA-263
> 2013-11-13 02:04:13,537 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Datadisk DATA-263 detached!
> 2013-11-13 02:04:13,537 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Attaching volume to instance: 
> 209300b9-0f42-4c73-941d-93c75b16
> 8203
> 2013-11-13 02:04:18,668 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Cleaning up the resources
> 2013-11-13 02:04:33,825 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Cleanup complete!
> 
> ==> result.log <==
> Test Deploy Virtual Machine with no startVM parameter ... skipped 'Skip'
> test_upload_attach_volume (test_stopped_vm.TestUploadAttachVolume)
> Test Upload volume and attach to VM in stopped state ... skipped 'Skip'
> test_vm_per_account (test_stopped_vm.TestVMAccountLimit)
> Test VM limit per account ... skipped 'Skip'
> 
> --
> Ran 17 tests in 56.691s
> 
> OK (skipped=16)
> 
> 
> Thanks,
> 
> Gaurav Aradhye
> 
>

Re: Review Request 15478: CLOUDSTACK-5156: Fixed test script issue related to detach volume

[ASF Subversion and Git Services]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15478/#review28801
---


Commit 2e373d58e0cc5843e4c59a9e6aaca64d003db785 in branch refs/heads/master 
from Gaurav Aradhye
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2e373d5 ]

CLOUDSTACK-5156: Fixed test script issue related to detach volume


- ASF Subversion and Git Services


On Nov. 13, 2013, 2:06 p.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/15478/
> ---
> 
> (Updated Nov. 13, 2013, 2:06 p.m.)
> 
> 
> Review request for cloudstack, Girish Shilamkar and SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-5156
> https://issues.apache.org/jira/browse/CLOUDSTACK-5156
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> component.test_stopped_vm.TestDeployVM.test_08_deploy_attached_volume
> This test was failing during detaching volume from a virtual machine.
> But the volume which was being detached from the virtual machine was obtained 
> from listing the volumes belonging to the same account and picking up the 
> first element in the list which does not guarantee that it is the same volume 
> belonging to the VM as the same account is used in many test cases.
> 
> Passed virtualmachineid parameter to get the exact volume belonging to the 
> virtual machine and now the test case works.
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_stopped_vm.py 2586c0b 
> 
> Diff: https://reviews.apache.org/r/15478/diff/
> 
> 
> Testing
> ---
> 
> Tested locally on XenServer basic zone setup.
> 
> Log:
> 
> ==> client.log <==
> 2013-11-13 02:03:42,866 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Verify listVirtualMachines response for 
> virtual machine: 20930
> 0b9-0f42-4c73-941d-93c75b168203
> 2013-11-13 02:03:42,866 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Deploying instance in the account: 
> test-P6HACO
> 2013-11-13 02:04:08,353 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Deployed instance in account: test-P6HACO
> 2013-11-13 02:04:08,395 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Verify listVirtualMachines response for 
> virtual machine: 8f68e
> fd6-9d64-44e1-9998-ce03d0158cb8
> 2013-11-13 02:04:08,395 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Fetching DATADISK details for instance: 
> 8f68efd6-9d64-44e1-999
> 8-ce03d0158cb8
> 2013-11-13 02:04:08,418 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Detaching the disk: DATA-263
> 2013-11-13 02:04:13,537 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Datadisk DATA-263 detached!
> 2013-11-13 02:04:13,537 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Attaching volume to instance: 
> 209300b9-0f42-4c73-941d-93c75b16
> 8203
> 2013-11-13 02:04:18,668 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Cleaning up the resources
> 2013-11-13 02:04:33,825 - DEBUG - test_08_deploy_attached_volume 
> (test_stopped_vm.TestDeployVM) - Cleanup complete!
> 
> ==> result.log <==
> Test Deploy Virtual Machine with no startVM parameter ... skipped 'Skip'
> test_upload_attach_volume (test_stopped_vm.TestUploadAttachVolume)
> Test Upload volume and attach to VM in stopped state ... skipped 'Skip'
> test_vm_per_account (test_stopped_vm.TestVMAccountLimit)
> Test VM limit per account ... skipped 'Skip'
> 
> --
> Ran 17 tests in 56.691s
> 
> OK (skipped=16)
> 
> 
> Thanks,
> 
> Gaurav Aradhye
> 
>

Re: New Ruby client for CloudStack API

[Isaac Chiang]

It is awesome! Thanks! :)


On Wed, Nov 13, 2013 at 10:57 PM, Wei ZHOU  wrote:

> Great!
>
> 2013/11/13 Mike Nicholaides 
>
> > Hi folks,
> >
> > Our team at PromptWorks, in conjunction with SunGard, has recently
> released
> > a new Ruby client for the CloudStack API called StackerBee:
> > https://github.com/promptworks/stacker_bee
> >
> > There are already a few Ruby clients out there but none of them met our
> > needs so we made our own. Here's what makes StackerBee special:
> > - supports all endpoints in the API
> > - easy to use and developer friendly
> > - let's developers write idiomatic Ruby
> > - interactive CloudStack REPL
> > - well tested and documented
> >
> > Pull requests and bug reports welcome.
> >
> > Special thanks to Chip Childers, Bill Jones, Dave Grizzanti and SunGard
> > Availability Services.
> >
> > Thanks,
> > Mike Nicholaides
> >
> >
> > --
> > Mike Nicholaides
> > Software Engineer and Co-Founder at PromptWorks
> > promptworks.com
> > (267) 622-4729
> >
>

Re: New Ruby client for CloudStack API

[Wei ZHOU]

Great!

2013/11/13 Mike Nicholaides 

> Hi folks,
>
> Our team at PromptWorks, in conjunction with SunGard, has recently released
> a new Ruby client for the CloudStack API called StackerBee:
> https://github.com/promptworks/stacker_bee
>
> There are already a few Ruby clients out there but none of them met our
> needs so we made our own. Here's what makes StackerBee special:
> - supports all endpoints in the API
> - easy to use and developer friendly
> - let's developers write idiomatic Ruby
> - interactive CloudStack REPL
> - well tested and documented
>
> Pull requests and bug reports welcome.
>
> Special thanks to Chip Childers, Bill Jones, Dave Grizzanti and SunGard
> Availability Services.
>
> Thanks,
> Mike Nicholaides
>
>
> --
> Mike Nicholaides
> Software Engineer and Co-Founder at PromptWorks
> promptworks.com
> (267) 622-4729
>

New Ruby client for CloudStack API

[Mike Nicholaides]

Hi folks,

Our team at PromptWorks, in conjunction with SunGard, has recently released
a new Ruby client for the CloudStack API called StackerBee:
https://github.com/promptworks/stacker_bee

There are already a few Ruby clients out there but none of them met our
needs so we made our own. Here's what makes StackerBee special:
- supports all endpoints in the API
- easy to use and developer friendly
- let's developers write idiomatic Ruby
- interactive CloudStack REPL
- well tested and documented

Pull requests and bug reports welcome.

Special thanks to Chip Childers, Bill Jones, Dave Grizzanti and SunGard
Availability Services.

Thanks,
Mike Nicholaides


-- 
Mike Nicholaides
Software Engineer and Co-Founder at PromptWorks
promptworks.com
(267) 622-4729

Re: [VOTE] Release Apache CloudStack 4.2.1

[Abhinandan Prateek]

On 13/11/13 7:14 pm, "Daan Hoogland"  wrote:

>I tested 4.2.1 with our custom vpc gateway on nvp patch basic usage in
>a adnvanced zone with niciranvp or with vlans work That means creating
>an standalone network or a vpc with a tier and in all cases with an
>instance being able to ping the outside world. I encountered one
>strange exception:
>
>WARN  [agent.manager.AgentManagerImpl] (AgentManager-Handler-6:) Caught:
>java.lang.NumberFormatException: For input string:
>"63424ecc-ee5c-49a0-b880-d1f879593822"
>at java.lang.NumberFormatException.forInputString(Unknown Source)
>at java.lang.Long.parseLong(Unknown Source)
>at java.lang.Long.parseLong(Unknown Source)
>at 
>com.cloud.consoleproxy.AgentHookBase.onConsoleAccessAuthentication(AgentHo
>okBase.java:135)
>at 
>com.cloud.consoleproxy.ConsoleProxyListener.processControlCommand(ConsoleP
>roxyListener.java:61)
>at 
>com.cloud.agent.manager.AgentManagerImpl.handleControlCommand(AgentManager
>Impl.java:347)
>at 
>com.cloud.agent.manager.AgentManagerImpl.access$200(AgentManagerImpl.java:
>144)
>at 
>com.cloud.agent.manager.AgentManagerImpl$AgentHandler.processRequest(Agent
>ManagerImpl.java:1260)
>at 
>com.cloud.agent.manager.AgentManagerImpl$AgentHandler.doTask(AgentManagerI
>mpl.java:1348)
>at 
>com.cloud.agent.manager.ClusteredAgentManagerImpl$ClusteredAgentHandler.do
>Task(ClusteredAgentManagerImpl.java:666)
>at com.cloud.utils.nio.Task.run(Task.java:83)
>at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>at java.lang.Thread.run(Unknown Source)
>
>I will now test to rule out the patch for this though it is in
>untouched code. I will enter a ticket or hold my peace forever after.
>
>btw, this is a pre-vote thread for these kinds of reports is it?
>
I think it is fine to highlight issues if any, I will wait for you final
say on this ?
Though I hope I do not carry the burden of this release to collab next
week :-)

-abhi
>

Question regarding ServerApiException

[SuichII, Christopher]

Alena & Edison (or others),

Is there a reason that ServerApiException has a getDescription() method rather 
than using getMessage() like all other exceptions? This causes problems in 
places where you’d like to treat all exceptions generically and be able to 
simply call getMessage(), but ServerApiException always returns null.

For example, I’m trying to fix an issue with StorageManagerImpl, where all 
errors provisioning a new storage pool simply return “Failed to add data store” 
without any actual meaningful error message. In general, we could do something 
like “Failed to add data store: “+e.getMessage(), however, that won’t work for 
ServerApiExceptions and so they would need to be handled separately from 
regular exceptions. One thought I had would be to override ServerApiException’s 
getMessage() and just return the description.

While were on the topic, is there a reason why we shouldn’t update error 
messages like “Failed to add data store” to include the exception’s message? It 
would be very beneficial for plugins and storage vendors to be able to return 
meaningful error messages from failed operations.

-Chris
-- 
Chris Suich
chris.su...@netapp.com
NetApp Software Engineer
Data Center Platforms – Cloud Solutions
Citrix, Cisco & Red Hat

Review Request 15478: CLOUDSTACK-5156: Fixed test script issue related to detach volume

[Gaurav Aradhye]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15478/
---

Review request for cloudstack, Girish Shilamkar and SrikanteswaraRao Talluri.


Bugs: CLOUDSTACK-5156
https://issues.apache.org/jira/browse/CLOUDSTACK-5156


Repository: cloudstack-git


Description
---

component.test_stopped_vm.TestDeployVM.test_08_deploy_attached_volume
This test was failing during detaching volume from a virtual machine.
But the volume which was being detached from the virtual machine was obtained 
from listing the volumes belonging to the same account and picking up the first 
element in the list which does not guarantee that it is the same volume 
belonging to the VM as the same account is used in many test cases.

Passed virtualmachineid parameter to get the exact volume belonging to the 
virtual machine and now the test case works.


Diffs
-

  test/integration/component/test_stopped_vm.py 2586c0b 

Diff: https://reviews.apache.org/r/15478/diff/


Testing
---

Tested locally on XenServer basic zone setup.

Log:

==> client.log <==
2013-11-13 02:03:42,866 - DEBUG - test_08_deploy_attached_volume 
(test_stopped_vm.TestDeployVM) - Verify listVirtualMachines response for 
virtual machine: 20930
0b9-0f42-4c73-941d-93c75b168203
2013-11-13 02:03:42,866 - DEBUG - test_08_deploy_attached_volume 
(test_stopped_vm.TestDeployVM) - Deploying instance in the account: test-P6HACO
2013-11-13 02:04:08,353 - DEBUG - test_08_deploy_attached_volume 
(test_stopped_vm.TestDeployVM) - Deployed instance in account: test-P6HACO
2013-11-13 02:04:08,395 - DEBUG - test_08_deploy_attached_volume 
(test_stopped_vm.TestDeployVM) - Verify listVirtualMachines response for 
virtual machine: 8f68e
fd6-9d64-44e1-9998-ce03d0158cb8
2013-11-13 02:04:08,395 - DEBUG - test_08_deploy_attached_volume 
(test_stopped_vm.TestDeployVM) - Fetching DATADISK details for instance: 
8f68efd6-9d64-44e1-999
8-ce03d0158cb8
2013-11-13 02:04:08,418 - DEBUG - test_08_deploy_attached_volume 
(test_stopped_vm.TestDeployVM) - Detaching the disk: DATA-263
2013-11-13 02:04:13,537 - DEBUG - test_08_deploy_attached_volume 
(test_stopped_vm.TestDeployVM) - Datadisk DATA-263 detached!
2013-11-13 02:04:13,537 - DEBUG - test_08_deploy_attached_volume 
(test_stopped_vm.TestDeployVM) - Attaching volume to instance: 
209300b9-0f42-4c73-941d-93c75b16
8203
2013-11-13 02:04:18,668 - DEBUG - test_08_deploy_attached_volume 
(test_stopped_vm.TestDeployVM) - Cleaning up the resources
2013-11-13 02:04:33,825 - DEBUG - test_08_deploy_attached_volume 
(test_stopped_vm.TestDeployVM) - Cleanup complete!

==> result.log <==
Test Deploy Virtual Machine with no startVM parameter ... skipped 'Skip'
test_upload_attach_volume (test_stopped_vm.TestUploadAttachVolume)
Test Upload volume and attach to VM in stopped state ... skipped 'Skip'
test_vm_per_account (test_stopped_vm.TestVMAccountLimit)
Test VM limit per account ... skipped 'Skip'

--
Ran 17 tests in 56.691s

OK (skipped=16)


Thanks,

Gaurav Aradhye

Re: [VOTE] Release Apache CloudStack 4.2.1

[Daan Hoogland]

I tested 4.2.1 with our custom vpc gateway on nvp patch basic usage in
a adnvanced zone with niciranvp or with vlans work That means creating
an standalone network or a vpc with a tier and in all cases with an
instance being able to ping the outside world. I encountered one
strange exception:

WARN  [agent.manager.AgentManagerImpl] (AgentManager-Handler-6:) Caught:
java.lang.NumberFormatException: For input string:
"63424ecc-ee5c-49a0-b880-d1f879593822"
at java.lang.NumberFormatException.forInputString(Unknown Source)
at java.lang.Long.parseLong(Unknown Source)
at java.lang.Long.parseLong(Unknown Source)
at 
com.cloud.consoleproxy.AgentHookBase.onConsoleAccessAuthentication(AgentHookBase.java:135)
at 
com.cloud.consoleproxy.ConsoleProxyListener.processControlCommand(ConsoleProxyListener.java:61)
at 
com.cloud.agent.manager.AgentManagerImpl.handleControlCommand(AgentManagerImpl.java:347)
at 
com.cloud.agent.manager.AgentManagerImpl.access$200(AgentManagerImpl.java:144)
at 
com.cloud.agent.manager.AgentManagerImpl$AgentHandler.processRequest(AgentManagerImpl.java:1260)
at 
com.cloud.agent.manager.AgentManagerImpl$AgentHandler.doTask(AgentManagerImpl.java:1348)
at 
com.cloud.agent.manager.ClusteredAgentManagerImpl$ClusteredAgentHandler.doTask(ClusteredAgentManagerImpl.java:666)
at com.cloud.utils.nio.Task.run(Task.java:83)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

I will now test to rule out the patch for this though it is in
untouched code. I will enter a ticket or hold my peace forever after.

btw, this is a pre-vote thread for these kinds of reports is it?

regards,
Daan

On Wed, Nov 13, 2013 at 2:57 AM, Abhinandan Prateek
 wrote:
>
> On 13/11/13 4:11 am, "Chip Childers"  wrote:
>
>>On Tue, Nov 12, 2013 at 10:31:47PM +, Animesh Chaturvedi wrote:
>>>
>>> The format of apache-cloudstack-4.2.1-src.tar.bz2.md5 doesn't match the
>>>gpg output.
>>>
>>> See this:
>>>
>>> localhost :: /tmp/cloudstack >gpg --print-md MD5
>>>apache-cloudstack-4.2.1-src.tar.bz2
>>> apache-cloudstack-4.2.1-src.tar.bz2: AE BF B5 B5 91 24 8B 6D  27 6F 9D
>>>35 C0 C3
>>>  DD D5 localhost :: /tmp/cloudstack
cat apache-cloudstack-4.2.1-src.tar.bz2.md5
>>> apache-cloudstack-4.2.1-src.tar.bz2: AE BF B5
>>>  B5 91 24
>>>  8B 6D  27
>>>  6F 9D 35
>>>  C0 C3 DD
>>>  D5
>>>
>>> There are extra line breaks in the .md5 file [1].  Although I'd
>>>actually prefer to get the process to switch to the md5sum tool's format
>>>anyway, can you correct this formatting before we continue with the
>>>release voting?
>>>
>>> -chip
>>>
>>> [1]
>>>https://dist.apache.org/repos/dist/dev/cloudstack/4.2.1/apache-cloudstack
>>>-4.2.1-src.tar.bz2.md5
>>>
>>> Animesh> Chip, Abhi is in a different time zone so will see this in
>>>morning, the SHA and MD5 are generated by build_asf.sh  script so if
>>>this is an issue, should have been for prior releases also. Are you
>>>suggesting to update the build_asf.sh to file to fix the formatting?
>>>
>>>
>>
>>This must be an issue with local gpg output formatting.  Weird.
>>
>>Let's go forward with the vote.  Manual inspection shows it as matching.
>>For 4.3, we should change the build script to use native md5sum and
>>sha256sum (with a script fix to get around the mac installations that
>>may have the commands pre-pended with a "g").
>>
>>I'll finish my testing and move forward with voting shortly.
>>
> I followed the release procedure and then did validation on signature etc
> using the Release test procedure wiki.
> Let me know if there are any further issues will be around to rectify.
>
> -abhi
>>
>

Review Request 15477: CLOUDSTACK-5155: Removing basic and sg tags from test case which is invalid for basic zone

[Gaurav Aradhye]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15477/
---

Review request for cloudstack, Girish Shilamkar and SrikanteswaraRao Talluri.


Bugs: CLOUDSTACK-5155
https://issues.apache.org/jira/browse/CLOUDSTACK-5155


Repository: cloudstack-git


Description
---

component.test_stopped_vm.TestRouterStateAfterDeploy.test_01_deploy_vm_no_startvm
This test case assumes that each new VM deployment will create a router in that 
account, which is invalid scenario for the basic zone.
Removing basic and sg tags.


Diffs
-

  test/integration/component/test_stopped_vm.py 2586c0b 

Diff: https://reviews.apache.org/r/15477/diff/


Testing
---


Thanks,

Gaurav Aradhye

Cloudstack collab conference

[Giles Sirett]

(cross posting to dev,users,marketing)

CLOUDSTACK COLLABORATION CONFERENCE, AMSTERDAM, 20-22 NOV
www.cloudstackcollab.org

I just had a chat with somebody whos active on the dev list, based in Europe 
and didn't know that the European CloudStack Collaboration Conference is 
happening next week in Amsterdam.

I know it has been discussed previously and I'm sure *nearly* everyone is aware 
 - but this email is just in case




Kind Regards
Giles

Giles Sirett
CEO

[Description: Mail Logo Bottom Align]

D: +44 20 3603 0541 | S: +44 20 3603 0540 | M: +44 796 111 2055

giles.sir...@shapeblue.com | 
www.shapeblue.com | 
Twitter:@shapeBlue

ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS

ShapeBlue are proud to be sponsoring CloudStack Collab EU 2013
[cid:image004.jpg@01CED4C8.C686BDF0]

Apache CloudStack Bootcamp training courses:
**NEW!** CloudStack 4.2 
training
13/14 November, 
London
09-13 December, GLOBAL. Instructor led, 
On-line
27/28 November, 
Bangalore
08/09 January 2014, 
London

This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error. Shape Blue Ltd is a company 
incorporated in England & Wales. ShapeBlue Services India LLP is a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: Review Request 15475: CLOUDSTACK-5154: Fixed test script issue related to failure in creating snapshot from volume

[ASF Subversion and Git Services]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15475/#review28799
---


Commit 52b0484812641ddcffef5715d97f39a1fc38c75e in branch refs/heads/master 
from Ashutosh K
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=52b0484 ]

CLOUDSTACK-5154: Fixed test script issue related to failure
 in creating snapshot from volume

Signed-off-by: Girish Shilamkar 


- ASF Subversion and Git Services


On Nov. 13, 2013, 11:48 a.m., Ashutosh Kelkar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/15475/
> ---
> 
> (Updated Nov. 13, 2013, 11:48 a.m.)
> 
> 
> Review request for cloudstack, Girish Shilamkar and SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-5154
> https://issues.apache.org/jira/browse/CLOUDSTACK-5154
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Fixed 
> component.test_project_limits.TestResourceLimitsProject.test_05_snapshots_per_project
> 
> Test was failing in creating snapshot because the volume from which the 
> snapshot is getting created is incorrect. It is obtained by listing the 
> volumes belonging to the project, which sometimes can list volumes belonging 
> to expunging vms. Passed virtualmachineid to the list_volumes method so as to 
> get the correct volume.
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_project_limits.py 04e6922 
> 
> Diff: https://reviews.apache.org/r/15475/diff/
> 
> 
> Testing
> ---
> 
> Tested locally on XenServer Basic Zone setup:
> 
> Result log:
> test_maxAccountNetworks (test_project_limits.TestMaxProjectNetworks)
> Test Limit number of guest account specific networks ... skipped 'skip'
> test_01_project_limits (test_project_limits.TestProjectLimits)
> Test project limits for domain admin ... skipped 'skip'
> test_02_project_limits_normal_user (test_project_limits.TestProjectLimits)
> Test project limits for normal user ... skipped 'skip'
> test_03_vm_per_project (test_project_limits.TestResourceLimitsProject)
> Test VM limit per project ... skipped 'skip'
> test_04_publicip_per_project (test_project_limits.TestResourceLimitsProject)
> Test Public IP limit per project ... skipped 'skip'
> test_05_snapshots_per_project (test_project_limits.TestResourceLimitsProject)
> Test Snapshot limit per project ... ok
> test_06_volumes_per_project (test_project_limits.TestResourceLimitsProject)
> Test Volumes limit per project ... skipped 'skip'
> test_07_templates_per_project (test_project_limits.TestResourceLimitsProject)
> Test Templates limit per project ... skipped 'skip'
> 
> --
> Ran 8 tests in 156.657s
> 
> OK (skipped=7)
> 
> Client Log:
> 2013-11-12 23:25:44,629 - DEBUG - test_05_snapshots_per_project 
> (test_project_limits.TestResourceLimitsProject) - Updating snapshot resource 
> limits for
> project: 540a482c-8add-4b08-9c67-1d551280eb56
> 2013-11-12 23:25:44,651 - DEBUG - test_05_snapshots_per_project 
> (test_project_limits.TestResourceLimitsProject) - Deploying VM in project: 
> 540a482c-8add-4b08-
> 9c67-1d551280eb56
> 2013-11-12 23:25:59,970 - DEBUG - test_05_snapshots_per_project 
> (test_project_limits.TestResourceLimitsProject) - 
> 6e611bc3-ebf3-4b41-9af9-3411b8093ea5
> 2013-11-12 23:25:59,989 - DEBUG - test_05_snapshots_per_project 
> (test_project_limits.TestResourceLimitsProject) - [{domain : 
> u'Domain-MW39F9', domainid :
> u'97742857-7330-4c22-994c-48471d5e26bb', projectid : 
> u'540a482c-8add-4b08-9c67-1d551280eb56', zoneid : 
> u'2c42d5dc-7377-4385-b2fa-dd6fd837380f', vmname :
> u'6e611bc3-ebf3-4b41-9af9-3411b8093ea5', id : 
> u'bc2720d9-ece4-4ce0-afc3-8243f28ccf86', size : 21474836480, storage : 
> u'primary0clus0', displayvolume : False,
> destroyed : False, state : u'Ready', serviceofferingdisplaytext : u'Tiny 
> Instance', vmdisplayname : u'TestVM', type : u'ROOT', serviceofferingid : 
> u'aac1cc50-
> 0d2e-4d47-ae0b-1e8f4f9777e7', zonename : u'test0', tags : [], isextractable : 
> True, name : u'ROOT-259', virtualmachineid : u'6e611bc3-ebf3-4b41-9af9-
> 3411b8093ea5', storagetype : u'shared', hypervisor : u'XenServer', created : 
> u'2013-11-13T02:59:13-0800', vmstate : u'Running', project : 
> u'Project-VDCYWI',
> deviceid : 0, serviceofferingname : u'Tiny Instance'}]
> 2013-11-12 23:25:59,989 - DEBUG - test_05_snapshots_per_project 
> (test_project_limits.TestResourceLimitsProject) - Creating snapshot from 
> volume: bc2720d9-ece4-
> 4ce0-afc3-8243f28ccf86
> 
> 
> Thanks,
> 
> Ashutosh Kelkar
> 
>

Re: Review Request 15475: CLOUDSTACK-5154: Fixed test script issue related to failure in creating snapshot from volume

[ASF Subversion and Git Services]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15475/#review28798
---


Commit 57c782527554028d3cf6cf51eff59914b7b1b10e in branch refs/heads/4.3 from 
Ashutosh K
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=57c7825 ]

CLOUDSTACK-5154: Fixed test script issue related to failure
 in creating snapshot from volume

Signed-off-by: Girish Shilamkar 


- ASF Subversion and Git Services


On Nov. 13, 2013, 11:48 a.m., Ashutosh Kelkar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/15475/
> ---
> 
> (Updated Nov. 13, 2013, 11:48 a.m.)
> 
> 
> Review request for cloudstack, Girish Shilamkar and SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-5154
> https://issues.apache.org/jira/browse/CLOUDSTACK-5154
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Fixed 
> component.test_project_limits.TestResourceLimitsProject.test_05_snapshots_per_project
> 
> Test was failing in creating snapshot because the volume from which the 
> snapshot is getting created is incorrect. It is obtained by listing the 
> volumes belonging to the project, which sometimes can list volumes belonging 
> to expunging vms. Passed virtualmachineid to the list_volumes method so as to 
> get the correct volume.
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_project_limits.py 04e6922 
> 
> Diff: https://reviews.apache.org/r/15475/diff/
> 
> 
> Testing
> ---
> 
> Tested locally on XenServer Basic Zone setup:
> 
> Result log:
> test_maxAccountNetworks (test_project_limits.TestMaxProjectNetworks)
> Test Limit number of guest account specific networks ... skipped 'skip'
> test_01_project_limits (test_project_limits.TestProjectLimits)
> Test project limits for domain admin ... skipped 'skip'
> test_02_project_limits_normal_user (test_project_limits.TestProjectLimits)
> Test project limits for normal user ... skipped 'skip'
> test_03_vm_per_project (test_project_limits.TestResourceLimitsProject)
> Test VM limit per project ... skipped 'skip'
> test_04_publicip_per_project (test_project_limits.TestResourceLimitsProject)
> Test Public IP limit per project ... skipped 'skip'
> test_05_snapshots_per_project (test_project_limits.TestResourceLimitsProject)
> Test Snapshot limit per project ... ok
> test_06_volumes_per_project (test_project_limits.TestResourceLimitsProject)
> Test Volumes limit per project ... skipped 'skip'
> test_07_templates_per_project (test_project_limits.TestResourceLimitsProject)
> Test Templates limit per project ... skipped 'skip'
> 
> --
> Ran 8 tests in 156.657s
> 
> OK (skipped=7)
> 
> Client Log:
> 2013-11-12 23:25:44,629 - DEBUG - test_05_snapshots_per_project 
> (test_project_limits.TestResourceLimitsProject) - Updating snapshot resource 
> limits for
> project: 540a482c-8add-4b08-9c67-1d551280eb56
> 2013-11-12 23:25:44,651 - DEBUG - test_05_snapshots_per_project 
> (test_project_limits.TestResourceLimitsProject) - Deploying VM in project: 
> 540a482c-8add-4b08-
> 9c67-1d551280eb56
> 2013-11-12 23:25:59,970 - DEBUG - test_05_snapshots_per_project 
> (test_project_limits.TestResourceLimitsProject) - 
> 6e611bc3-ebf3-4b41-9af9-3411b8093ea5
> 2013-11-12 23:25:59,989 - DEBUG - test_05_snapshots_per_project 
> (test_project_limits.TestResourceLimitsProject) - [{domain : 
> u'Domain-MW39F9', domainid :
> u'97742857-7330-4c22-994c-48471d5e26bb', projectid : 
> u'540a482c-8add-4b08-9c67-1d551280eb56', zoneid : 
> u'2c42d5dc-7377-4385-b2fa-dd6fd837380f', vmname :
> u'6e611bc3-ebf3-4b41-9af9-3411b8093ea5', id : 
> u'bc2720d9-ece4-4ce0-afc3-8243f28ccf86', size : 21474836480, storage : 
> u'primary0clus0', displayvolume : False,
> destroyed : False, state : u'Ready', serviceofferingdisplaytext : u'Tiny 
> Instance', vmdisplayname : u'TestVM', type : u'ROOT', serviceofferingid : 
> u'aac1cc50-
> 0d2e-4d47-ae0b-1e8f4f9777e7', zonename : u'test0', tags : [], isextractable : 
> True, name : u'ROOT-259', virtualmachineid : u'6e611bc3-ebf3-4b41-9af9-
> 3411b8093ea5', storagetype : u'shared', hypervisor : u'XenServer', created : 
> u'2013-11-13T02:59:13-0800', vmstate : u'Running', project : 
> u'Project-VDCYWI',
> deviceid : 0, serviceofferingname : u'Tiny Instance'}]
> 2013-11-12 23:25:59,989 - DEBUG - test_05_snapshots_per_project 
> (test_project_limits.TestResourceLimitsProject) - Creating snapshot from 
> volume: bc2720d9-ece4-
> 4ce0-afc3-8243f28ccf86
> 
> 
> Thanks,
> 
> Ashutosh Kelkar
> 
>

Re: Review Request 15475: CLOUDSTACK-5154: Fixed test script issue related to failure in creating snapshot from volume

[ASF Subversion and Git Services]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15475/#review28797
---


Commit b5d3b99307668269d74b4c2fc3c71e6650b88b03 in branch refs/heads/4.2 from 
Ashutosh K
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b5d3b99 ]

CLOUDSTACK-5154: Fixed test script issue related to failure
 in creating snapshot from volume

Signed-off-by: Girish Shilamkar 


- ASF Subversion and Git Services


On Nov. 13, 2013, 11:48 a.m., Ashutosh Kelkar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/15475/
> ---
> 
> (Updated Nov. 13, 2013, 11:48 a.m.)
> 
> 
> Review request for cloudstack, Girish Shilamkar and SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-5154
> https://issues.apache.org/jira/browse/CLOUDSTACK-5154
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Fixed 
> component.test_project_limits.TestResourceLimitsProject.test_05_snapshots_per_project
> 
> Test was failing in creating snapshot because the volume from which the 
> snapshot is getting created is incorrect. It is obtained by listing the 
> volumes belonging to the project, which sometimes can list volumes belonging 
> to expunging vms. Passed virtualmachineid to the list_volumes method so as to 
> get the correct volume.
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_project_limits.py 04e6922 
> 
> Diff: https://reviews.apache.org/r/15475/diff/
> 
> 
> Testing
> ---
> 
> Tested locally on XenServer Basic Zone setup:
> 
> Result log:
> test_maxAccountNetworks (test_project_limits.TestMaxProjectNetworks)
> Test Limit number of guest account specific networks ... skipped 'skip'
> test_01_project_limits (test_project_limits.TestProjectLimits)
> Test project limits for domain admin ... skipped 'skip'
> test_02_project_limits_normal_user (test_project_limits.TestProjectLimits)
> Test project limits for normal user ... skipped 'skip'
> test_03_vm_per_project (test_project_limits.TestResourceLimitsProject)
> Test VM limit per project ... skipped 'skip'
> test_04_publicip_per_project (test_project_limits.TestResourceLimitsProject)
> Test Public IP limit per project ... skipped 'skip'
> test_05_snapshots_per_project (test_project_limits.TestResourceLimitsProject)
> Test Snapshot limit per project ... ok
> test_06_volumes_per_project (test_project_limits.TestResourceLimitsProject)
> Test Volumes limit per project ... skipped 'skip'
> test_07_templates_per_project (test_project_limits.TestResourceLimitsProject)
> Test Templates limit per project ... skipped 'skip'
> 
> --
> Ran 8 tests in 156.657s
> 
> OK (skipped=7)
> 
> Client Log:
> 2013-11-12 23:25:44,629 - DEBUG - test_05_snapshots_per_project 
> (test_project_limits.TestResourceLimitsProject) - Updating snapshot resource 
> limits for
> project: 540a482c-8add-4b08-9c67-1d551280eb56
> 2013-11-12 23:25:44,651 - DEBUG - test_05_snapshots_per_project 
> (test_project_limits.TestResourceLimitsProject) - Deploying VM in project: 
> 540a482c-8add-4b08-
> 9c67-1d551280eb56
> 2013-11-12 23:25:59,970 - DEBUG - test_05_snapshots_per_project 
> (test_project_limits.TestResourceLimitsProject) - 
> 6e611bc3-ebf3-4b41-9af9-3411b8093ea5
> 2013-11-12 23:25:59,989 - DEBUG - test_05_snapshots_per_project 
> (test_project_limits.TestResourceLimitsProject) - [{domain : 
> u'Domain-MW39F9', domainid :
> u'97742857-7330-4c22-994c-48471d5e26bb', projectid : 
> u'540a482c-8add-4b08-9c67-1d551280eb56', zoneid : 
> u'2c42d5dc-7377-4385-b2fa-dd6fd837380f', vmname :
> u'6e611bc3-ebf3-4b41-9af9-3411b8093ea5', id : 
> u'bc2720d9-ece4-4ce0-afc3-8243f28ccf86', size : 21474836480, storage : 
> u'primary0clus0', displayvolume : False,
> destroyed : False, state : u'Ready', serviceofferingdisplaytext : u'Tiny 
> Instance', vmdisplayname : u'TestVM', type : u'ROOT', serviceofferingid : 
> u'aac1cc50-
> 0d2e-4d47-ae0b-1e8f4f9777e7', zonename : u'test0', tags : [], isextractable : 
> True, name : u'ROOT-259', virtualmachineid : u'6e611bc3-ebf3-4b41-9af9-
> 3411b8093ea5', storagetype : u'shared', hypervisor : u'XenServer', created : 
> u'2013-11-13T02:59:13-0800', vmstate : u'Running', project : 
> u'Project-VDCYWI',
> deviceid : 0, serviceofferingname : u'Tiny Instance'}]
> 2013-11-12 23:25:59,989 - DEBUG - test_05_snapshots_per_project 
> (test_project_limits.TestResourceLimitsProject) - Creating snapshot from 
> volume: bc2720d9-ece4-
> 4ce0-afc3-8243f28ccf86
> 
> 
> Thanks,
> 
> Ashutosh Kelkar
> 
>

Re: Review Request 15475: CLOUDSTACK-5154: Fixed test script issue related to failure in creating snapshot from volume

[Girish Shilamkar]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15475/#review28796
---

Ship it!


Ship It!

- Girish Shilamkar


On Nov. 13, 2013, 11:48 a.m., Ashutosh Kelkar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/15475/
> ---
> 
> (Updated Nov. 13, 2013, 11:48 a.m.)
> 
> 
> Review request for cloudstack, Girish Shilamkar and SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-5154
> https://issues.apache.org/jira/browse/CLOUDSTACK-5154
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Fixed 
> component.test_project_limits.TestResourceLimitsProject.test_05_snapshots_per_project
> 
> Test was failing in creating snapshot because the volume from which the 
> snapshot is getting created is incorrect. It is obtained by listing the 
> volumes belonging to the project, which sometimes can list volumes belonging 
> to expunging vms. Passed virtualmachineid to the list_volumes method so as to 
> get the correct volume.
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_project_limits.py 04e6922 
> 
> Diff: https://reviews.apache.org/r/15475/diff/
> 
> 
> Testing
> ---
> 
> Tested locally on XenServer Basic Zone setup:
> 
> Result log:
> test_maxAccountNetworks (test_project_limits.TestMaxProjectNetworks)
> Test Limit number of guest account specific networks ... skipped 'skip'
> test_01_project_limits (test_project_limits.TestProjectLimits)
> Test project limits for domain admin ... skipped 'skip'
> test_02_project_limits_normal_user (test_project_limits.TestProjectLimits)
> Test project limits for normal user ... skipped 'skip'
> test_03_vm_per_project (test_project_limits.TestResourceLimitsProject)
> Test VM limit per project ... skipped 'skip'
> test_04_publicip_per_project (test_project_limits.TestResourceLimitsProject)
> Test Public IP limit per project ... skipped 'skip'
> test_05_snapshots_per_project (test_project_limits.TestResourceLimitsProject)
> Test Snapshot limit per project ... ok
> test_06_volumes_per_project (test_project_limits.TestResourceLimitsProject)
> Test Volumes limit per project ... skipped 'skip'
> test_07_templates_per_project (test_project_limits.TestResourceLimitsProject)
> Test Templates limit per project ... skipped 'skip'
> 
> --
> Ran 8 tests in 156.657s
> 
> OK (skipped=7)
> 
> Client Log:
> 2013-11-12 23:25:44,629 - DEBUG - test_05_snapshots_per_project 
> (test_project_limits.TestResourceLimitsProject) - Updating snapshot resource 
> limits for
> project: 540a482c-8add-4b08-9c67-1d551280eb56
> 2013-11-12 23:25:44,651 - DEBUG - test_05_snapshots_per_project 
> (test_project_limits.TestResourceLimitsProject) - Deploying VM in project: 
> 540a482c-8add-4b08-
> 9c67-1d551280eb56
> 2013-11-12 23:25:59,970 - DEBUG - test_05_snapshots_per_project 
> (test_project_limits.TestResourceLimitsProject) - 
> 6e611bc3-ebf3-4b41-9af9-3411b8093ea5
> 2013-11-12 23:25:59,989 - DEBUG - test_05_snapshots_per_project 
> (test_project_limits.TestResourceLimitsProject) - [{domain : 
> u'Domain-MW39F9', domainid :
> u'97742857-7330-4c22-994c-48471d5e26bb', projectid : 
> u'540a482c-8add-4b08-9c67-1d551280eb56', zoneid : 
> u'2c42d5dc-7377-4385-b2fa-dd6fd837380f', vmname :
> u'6e611bc3-ebf3-4b41-9af9-3411b8093ea5', id : 
> u'bc2720d9-ece4-4ce0-afc3-8243f28ccf86', size : 21474836480, storage : 
> u'primary0clus0', displayvolume : False,
> destroyed : False, state : u'Ready', serviceofferingdisplaytext : u'Tiny 
> Instance', vmdisplayname : u'TestVM', type : u'ROOT', serviceofferingid : 
> u'aac1cc50-
> 0d2e-4d47-ae0b-1e8f4f9777e7', zonename : u'test0', tags : [], isextractable : 
> True, name : u'ROOT-259', virtualmachineid : u'6e611bc3-ebf3-4b41-9af9-
> 3411b8093ea5', storagetype : u'shared', hypervisor : u'XenServer', created : 
> u'2013-11-13T02:59:13-0800', vmstate : u'Running', project : 
> u'Project-VDCYWI',
> deviceid : 0, serviceofferingname : u'Tiny Instance'}]
> 2013-11-12 23:25:59,989 - DEBUG - test_05_snapshots_per_project 
> (test_project_limits.TestResourceLimitsProject) - Creating snapshot from 
> volume: bc2720d9-ece4-
> 4ce0-afc3-8243f28ccf86
> 
> 
> Thanks,
> 
> Ashutosh Kelkar
> 
>

Retreive VM snapshot size

[Antonio Petrocelli]

Hello,

someone knows how to obtain the size of a VM snapshot with CLOUDSTACK 
4.2 API?


with this call 
_http://cloudstack.apache.org/docs/api/apidocs-4.2/domain_admin/listVMSnapshot.html_ 
size is not specified.


Thanks.

Regards.

Review Request 15475: CLOUDSTACK-5154: Fixed test script issue related to failure in creating snapshot from volume

[Ashutosh Kelkar]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15475/
---

Review request for cloudstack, Girish Shilamkar and SrikanteswaraRao Talluri.


Bugs: CLOUDSTACK-5154
https://issues.apache.org/jira/browse/CLOUDSTACK-5154


Repository: cloudstack-git


Description
---

Fixed 
component.test_project_limits.TestResourceLimitsProject.test_05_snapshots_per_project

Test was failing in creating snapshot because the volume from which the 
snapshot is getting created is incorrect. It is obtained by listing the volumes 
belonging to the project, which sometimes can list volumes belonging to 
expunging vms. Passed virtualmachineid to the list_volumes method so as to get 
the correct volume.


Diffs
-

  test/integration/component/test_project_limits.py 04e6922 

Diff: https://reviews.apache.org/r/15475/diff/


Testing
---

Tested locally on XenServer Basic Zone setup:

Result log:
test_maxAccountNetworks (test_project_limits.TestMaxProjectNetworks)
Test Limit number of guest account specific networks ... skipped 'skip'
test_01_project_limits (test_project_limits.TestProjectLimits)
Test project limits for domain admin ... skipped 'skip'
test_02_project_limits_normal_user (test_project_limits.TestProjectLimits)
Test project limits for normal user ... skipped 'skip'
test_03_vm_per_project (test_project_limits.TestResourceLimitsProject)
Test VM limit per project ... skipped 'skip'
test_04_publicip_per_project (test_project_limits.TestResourceLimitsProject)
Test Public IP limit per project ... skipped 'skip'
test_05_snapshots_per_project (test_project_limits.TestResourceLimitsProject)
Test Snapshot limit per project ... ok
test_06_volumes_per_project (test_project_limits.TestResourceLimitsProject)
Test Volumes limit per project ... skipped 'skip'
test_07_templates_per_project (test_project_limits.TestResourceLimitsProject)
Test Templates limit per project ... skipped 'skip'

--
Ran 8 tests in 156.657s

OK (skipped=7)

Client Log:
2013-11-12 23:25:44,629 - DEBUG - test_05_snapshots_per_project 
(test_project_limits.TestResourceLimitsProject) - Updating snapshot resource 
limits for
project: 540a482c-8add-4b08-9c67-1d551280eb56
2013-11-12 23:25:44,651 - DEBUG - test_05_snapshots_per_project 
(test_project_limits.TestResourceLimitsProject) - Deploying VM in project: 
540a482c-8add-4b08-
9c67-1d551280eb56
2013-11-12 23:25:59,970 - DEBUG - test_05_snapshots_per_project 
(test_project_limits.TestResourceLimitsProject) - 
6e611bc3-ebf3-4b41-9af9-3411b8093ea5
2013-11-12 23:25:59,989 - DEBUG - test_05_snapshots_per_project 
(test_project_limits.TestResourceLimitsProject) - [{domain : u'Domain-MW39F9', 
domainid :
u'97742857-7330-4c22-994c-48471d5e26bb', projectid : 
u'540a482c-8add-4b08-9c67-1d551280eb56', zoneid : 
u'2c42d5dc-7377-4385-b2fa-dd6fd837380f', vmname :
u'6e611bc3-ebf3-4b41-9af9-3411b8093ea5', id : 
u'bc2720d9-ece4-4ce0-afc3-8243f28ccf86', size : 21474836480, storage : 
u'primary0clus0', displayvolume : False,
destroyed : False, state : u'Ready', serviceofferingdisplaytext : u'Tiny 
Instance', vmdisplayname : u'TestVM', type : u'ROOT', serviceofferingid : 
u'aac1cc50-
0d2e-4d47-ae0b-1e8f4f9777e7', zonename : u'test0', tags : [], isextractable : 
True, name : u'ROOT-259', virtualmachineid : u'6e611bc3-ebf3-4b41-9af9-
3411b8093ea5', storagetype : u'shared', hypervisor : u'XenServer', created : 
u'2013-11-13T02:59:13-0800', vmstate : u'Running', project : u'Project-VDCYWI',
deviceid : 0, serviceofferingname : u'Tiny Instance'}]
2013-11-12 23:25:59,989 - DEBUG - test_05_snapshots_per_project 
(test_project_limits.TestResourceLimitsProject) - Creating snapshot from 
volume: bc2720d9-ece4-
4ce0-afc3-8243f28ccf86


Thanks,

Ashutosh Kelkar

RE: [4.3][QA]Test Plan for Hyper-V support

[Sowmya Krishnan]

Thanks Sailaja. Most of these will be covered under test case document. Like I 
mentioned it's in progress.. so I've highlighted only the test scenarios based 
on supported features. Watch out for the test case document when they're 
uploaded for these individual tests. 
Comments inline as well.


> -Original Message-
> From: Sailaja Mada [mailto:sailaja.m...@citrix.com]
> Sent: Wednesday, November 13, 2013 4:10 PM
> To: dev@cloudstack.apache.org
> Subject: RE: [4.3][QA]Test Plan for Hyper-V support
> 
> Hi Sowmya,
> 
> It's a nice consolidation of the areas in the Test Plan .  I just have few 
> comments
> or scenarios to mention.
> 
> Please ignore if you have already plans to add it or its not supported.
> 
> 1) Hot Nic Plugin - Acquiring Public IP from a new VLAN
Hot Nic Plugin isn't supported in 4.3

> 2) VM's with Multiple guest networks
Covered under multiple physical networks - this will include multiple guest 
networks, storage in separate network, and all combinations of that. 

> 3) VM Operations - Force Stop of a VM ,  Restore the VM to a base template or
> to a new template , Reset the VM
Watch out for Test case doc. All VM operations will be tested 

> 4) Cold Migration - Migrating the volumes to a different Storage when VM is
> down
Test case will cover this.

> 5) Windows and Linux VM's . I am  not sure if we have any separate tools ISO
> bundled for HyperV in order to execute certain operations like the way we do 
> for
> VMWARE/Xen .

I am still exploring this. There are some integrated tools to be downloaded in 
the guest VMs for certain OS. While some are already available with the OS 
(like CentOS6.4) others will need to be downloaded explicitly. This will be 
documented if need be.

> 6) Verify the HyperV supported guest Operating Systems which are listed @
> http://technet.microsoft.com/en-GB/library/hh831531.aspx  are made available
> while registering the templates . It has Windows 8 and 8.1 also listed. We may
> need to cover the latest
> 
Yeah.. I looked at that. We thought it's more of hypervisor test than CS test? 
We'll be covering one Windows VM and one Linux VM at least. It's definitely not 
possible to cover the entire list of guest OS types listed there. That's 
something which would be tested by the hypervisor test team 

> 8) Console view in different browsers
Watch out for Test case doc

> 9) Migrating the VM's across clusters if it supports Storage Motion .

Nope. Not supported

> 10) We have global config parameters specific to each hypervisor(
> KVM/Xenserver/VMWARE). I do not see anything listed for HyperV. In case if
> they are there, we may need to have scenarios to validate them
Nothing mentioned so far.

> 11) Alerts / Events to be generated for specific operations and have a check 
> for
> the same
No new events. It's all the same list of operations we do, except that it's a 
new hypervisor.

> 12) Is Volatile option with Compute Offering
Watch out for test case doc

> 13) VM Statistics to be displayed correctly.
Test case doc

> 14) Hypervisor_capabilities,guest_os_hypervisor Tables are updated with the
> required details
Test case doc

> 15) Do we support Parallel VM deployment in HyperV ? Like we have in VMWARE
> ?  If yes please have a scenario
Will include this.

> 16) Multiple Primary Storages
Test case doc

> 17) User defined names for the Virtual machines
Test case doc

> 18) Host tagging, Storage Tagging - This may create issues during Migration

Test case doc - not hypervisor specific

> 19) Common Global Parameters like - Storage Garbage Collector, Network
> Shutdown when there are no active VM's , Storage Migration during HA (Yes/No)
> , VM Expunge Interval

No new params or API change mentioned in the FS. 
HA not supported. Network shutdown will be covered under Network restart cases.

> 20)  HA testing Or Host Failover cases
> 
HA not supported for this release. Failover will be covered under Host/Storage 
in maintenance mode

> Thanks and Regards,
> Sailaja.M
> 
> 
> 
> 
> 
> 
> 
> 
> 
> -Original Message-
> From: Sowmya Krishnan [mailto:sowmya.krish...@citrix.com]
> Sent: 13 November 2013 15:04
> To: dev@cloudstack.apache.org
> Subject: [4.3][QA]Test Plan for Hyper-V support
> 
> I've drafted a test plan for Hyper-V support for areas to be tested:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Hyper-
> V+Test+Plan+for+4.3 based on the FS
> (https://cwiki.apache.org/confluence/x/4hLVAQ).
> Test cases are being drafted (not many new tests really, mostly consolidating
> existing tests to be run on new hypervisor) and will be uploaded in the next 
> few
> days.
> Meanwhile, any feedback/comments are welcome!
> 
> Thanks,
> Sowmya

RE: [4.3][QA]Test Plan for Hyper-V support

[Sailaja Mada]

Hi Sowmya,

It's a nice consolidation of the areas in the Test Plan .  I just have few 
comments or scenarios to mention.  

Please ignore if you have already plans to add it or its not supported.

1) Hot Nic Plugin - Acquiring Public IP from a new VLAN 
2) VM's with Multiple guest networks 
3) VM Operations - Force Stop of a VM ,  Restore the VM to a base template or 
to a new template , Reset the VM 
4) Cold Migration - Migrating the volumes to a different Storage when VM is 
down 
5) Windows and Linux VM's . I am  not sure if we have any separate tools ISO 
bundled for HyperV in order to execute certain operations like the way we do 
for VMWARE/Xen .
6) Verify the HyperV supported guest Operating Systems which are listed @ 
http://technet.microsoft.com/en-GB/library/hh831531.aspx  are made available 
while registering the templates . It has Windows 8 and 8.1 also listed. We may 
need to cover the latest 
8) Console view in different browsers 
9) Migrating the VM's across clusters if it supports Storage Motion .
10) We have global config parameters specific to each hypervisor( 
KVM/Xenserver/VMWARE). I do not see anything listed for HyperV. In case if they 
are there, we may need to have scenarios to validate them
11) Alerts / Events to be generated for specific operations and have a check 
for the same
12) Is Volatile option with Compute Offering 
13) VM Statistics to be displayed correctly. 
14) Hypervisor_capabilities,guest_os_hypervisor Tables are updated with the 
required details
15) Do we support Parallel VM deployment in HyperV ? Like we have in VMWARE ?  
If yes please have a scenario 
16) Multiple Primary Storages 
17) User defined names for the Virtual machines 
18) Host tagging, Storage Tagging - This may create issues during Migration  
19) Common Global Parameters like - Storage Garbage Collector, Network Shutdown 
when there are no active VM's , Storage Migration during HA (Yes/No)  , VM 
Expunge Interval 
20)  HA testing Or Host Failover cases  

Thanks and Regards,
Sailaja.M









-Original Message-
From: Sowmya Krishnan [mailto:sowmya.krish...@citrix.com] 
Sent: 13 November 2013 15:04
To: dev@cloudstack.apache.org
Subject: [4.3][QA]Test Plan for Hyper-V support

I've drafted a test plan for Hyper-V support for areas to be tested: 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Hyper-V+Test+Plan+for+4.3
 based on the FS (https://cwiki.apache.org/confluence/x/4hLVAQ). 
Test cases are being drafted (not many new tests really, mostly consolidating 
existing tests to be run on new hypervisor) and will be uploaded in the next 
few days.
Meanwhile, any feedback/comments are welcome!

Thanks,
Sowmya

RE: Purpose of OS Type on templates

[Donal Lafferty]

Thanks for the example!

> -Original Message-
> From: Nux! [mailto:n...@li.nux.ro]
> Sent: 13 November 2013 10:18
> To: dev@cloudstack.apache.org
> Subject: Re: Purpose of OS Type on templates
> 
> On 13.11.2013 10:11, Donal Lafferty wrote:
> > Which hypervisors make use of OS type on a template's configuration?
> 
> Hi Donal,
> 
> KVM at least does, it exposes paravirt VirtIO devices if the OS type is known
> to support it. Xenserver also creates a PV or HVM vm based on the OS type.
> 
> HTH
> Lucian
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro

Re: Purpose of OS Type on templates

[Abhinandan Prateek]

On 13/11/13 3:41 pm, "Donal Lafferty"  wrote:

>Which hypervisors make use of OS type on a template's configuration?
All the Hypervisors. The OS type mapping exists in cloudstack that maps to
the OS type values that a particular Hypervisor use


-abhi
>

Re: Purpose of OS Type on templates

[Nux!]

On 13.11.2013 10:11, Donal Lafferty wrote:

Which hypervisors make use of OS type on a template's configuration?


Hi Donal,

KVM at least does, it exposes paravirt VirtIO devices if the OS type is 
known to support it. Xenserver also creates a PV or HVM vm based on the 
OS type.


HTH
Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

Purpose of OS Type on templates

[Donal Lafferty]

Which hypervisors make use of OS type on a template's configuration?

[4.3][QA]Test Plan for Hyper-V support

[Sowmya Krishnan]

I've drafted a test plan for Hyper-V support for areas to be tested: 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Hyper-V+Test+Plan+for+4.3
 based on the FS (https://cwiki.apache.org/confluence/x/4hLVAQ). 
Test cases are being drafted (not many new tests really, mostly consolidating 
existing tests to be run on new hypervisor) and will be uploaded in the next 
few days.
Meanwhile, any feedback/comments are welcome!

Thanks,
Sowmya