date:20140318

Hi All, just following up on the emails from yesterday - anyone any ideas on 
the below?

Where would I expect to see the statement to set this up on reboot within the 
code? I've looked in the cloud-useage.in file where I would expect to see 
something and can't - is this the issue?



An automatic start setup is not carried out after cloudstack-usage installation.

# yum install cloudstack-usage -y --nogpgcheck
# chkconfig --list | grep cloud
cloudstack-management 0:off 1:off 2:off 3:on 4:on 5:on 6:off
#

You have to carry out an automatic start setup manually.
# chkconfig --add cloudstack-usage

In version 4.0.x, it was set up automatically.

# chkconfig --list | grep cloud
cloud-management 0:off 1:off 2:on 3:on 4:on 5:on 6:off
cloud-usage 0:off 1:off 2:off 3:on 4:on 5:on 6:off
#


-Original Message-
From: Alex Hitchins [mailto:alex.hitch...@shapeblue.com]
Sent: 17 March 2014 10:30
To: dev@cloudstack.apache.org
Subject: CLOUDSTACK-2908

All,

I'm looking at https://issues.apache.org/jira/browse/CLOUDSTACK-2908 now. 
Again, I believe this is a simple change.

Where would I expect to see the statement to set this up on reboot within the 
code? I've looked in the cloud-useage.in file where I would expect to see 
something and can't - is this the issue?


Alex
Need Enterprise Grade Support for Apache CloudStack?
Our CloudStack Infrastructure 
Support offers the 
best 24/7 SLA for CloudStack Environments.

Apache CloudStack Bootcamp training courses

**NEW!** CloudStack 4.2.1 training
18th-19th February 2014, Brazil. 
Classroom
17th-23rd March 2014, Region A. Instructor led, 
On-line
24th-28th March 2014, Region B. Instructor led, 
On-line
16th-20th June 2014, Region A. Instructor led, 
On-line
23rd-27th June 2014, Region B. Instructor led, 
On-line

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.
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.

CLOUDSTACK-1507

All, another bump from yesterday - if someone can assist I can get this knocked 
on the head.

**

I'm going through Jira at the moment clearing up some old tickets.

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

The issue above looks like a fairly straightforward change, can I ask someone 
to review and let me know if ubuntu-12.04.2-server-i386 is still the right 
version to update to? I notice the ticket is a year old, so things may have 
moved on past this version. I can easily make the change once confirmed.

Many thanks!

Alex

Need Enterprise Grade Support for Apache CloudStack?
Our CloudStack Infrastructure 
Support offers the 
best 24/7 SLA for CloudStack Environments.

Apache CloudStack Bootcamp training courses

**NEW!** CloudStack 4.2.1 training
18th-19th February 2014, Brazil. 
Classroom
17th-23rd March 2014, Region A. Instructor led, 
On-line
24th-28th March 2014, Region B. Instructor led, 
On-line
16th-20th June 2014, Region A. Instructor led, 
On-line
23rd-27th June 2014, Region B. Instructor led, 
On-line

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: [REMINDER] Review Request 18677: CLOUDSTACK-3272

2014-03-18 Thread Sonal Ojha

Hello Nitin,

There was a requirement to control the publishing of events on the
messaging queue as opposed to how it is currently. At present, all events
by default gets published over the queue. The idea was to have control over
the types of events being published in the queue not necessarily as a
matter of performance.

Kindly refer https://issues.apache.org/jira/browse/CLOUDSTACK-3272 for more
details.

-Sonal


On Tue, Mar 18, 2014 at 11:12 AM, Nitin Mehta wrote:

> Can you please explain why would one want to restrict publishing certain
> kind of events ? Performance ?
>
> On 17/03/14 9:44 PM, "Sonal Ojha"  wrote:
>
> >Any updates?
> >
> >
> >On Mon, Mar 10, 2014 at 10:01 AM, Sonal Ojha 
> >wrote:
> >
> >> Kindly let me know your review comments.
> >>
> >> -- Forwarded message --
> >> From: Sonal Ojha 
> >> Date: Tue, Mar 4, 2014 at 11:20 AM
> >> Subject: Re: Review Request 18677: CLOUDSTACK-3272
> >> To: Sonal Ojha , cloudstack <
> >> dev@cloudstack.apache.org>
> >>
> >>
> >>This is an automatically generated e-mail. To reply, visit:
> >> https://reviews.apache.org/r/18677/
> >>
> >> - Sonal Ojha
> >>
> >> On March 3rd, 2014, 5:58 a.m. UTC, Sonal Ojha wrote:
> >>Review request for cloudstack.
> >> By Sonal Ojha.
> >>
> >> *Updated March 3, 2014, 5:58 a.m.*
> >>  *Repository: * cloudstack-git
> >> Description
> >>
> >> At present, there are multiple event types that are generated by CS,
> >>action events,usage events, resource state change events and alerts.
> >>Current problem is
> >> all the events gets published on the event bus when event bus is
> >>enabled. Intent is to introduce global setting config parameters to
> >>specify which category of events to be published or not be published on
> >>the event bus.
> >>
> >>   Testing
> >>
> >> Successfully tested publishing / not publishing of various events based
> >>on the global parameter publish.*.events.
> >>
> >>   Diffs
> >>
> >>-
> >>plugins/event-bus/rabbitmq/src/org/apache/cloudstack/mom/rabbitmq/RabbitM
> >>QEventBus.java
> >>(478c8d7)
> >>- server/src/com/cloud/configuration/Config.java (2d55f46)
> >>- server/src/com/cloud/test/DatabaseConfig.java (9370218)
> >>
> >> View Diff 
> >>
> >>
> >>
> >> --
> >>
> >> Regards,
> >>
> >> ___
> >>
> >> *Sonal Ojha* ● Senior Engineer - Product Developement ● SunGard
> >> Availability Services, India ● Mobile: +91 9922412645●  Email:
> >> sonal.o...@sungard.com ● Website: http://www.sungardas.in/
> >>
> >> 8 Times Winner – BC Service Provider of the Year – 2011, 2010, 2009,
> >>2006,
> >> 2005, 2002, 2000, 1999; Finalist – 2008, 2007, 2004, 2001 ● Excellence
> >>in
> >> Infrastructure Management – 2010 ● Outstanding Excellence in Business
> >> Continuity – 2008 ● Business Continuity Provider of the Year (BCM
> >> Service) – 2013 BCI Global Awards ● Business Continuity Provider of the
> >> Year (BCM Product) – 2013 BCI India Awards
> >>
> >> *[image: AS_yt]* *[image:
> >> AS_twitter]* *[image:
> >>AS_in]**[image:
> >> AS_gplus]* *[image:
> >> AS_fb]* *[image:
> >>AS_ss]*
> >>
> >
> >
> >
> >--
> >
> >Regards,
> >
> >___
> >
> >*Sonal Ojha* ● Senior Engineer - Product Developement ● SunGard
> >Availability Services, India ● Mobile: +91 9922412645●  Email:
> >sonal.o...@sungard.com ● Website: http://www.sungardas.in/
> >
> >8 Times Winner – BC Service Provider of the Year – 2011, 2010, 2009, 2006,
> >2005, 2002, 2000, 1999; Finalist – 2008, 2007, 2004, 2001 ● Excellence in
> >Infrastructure Management – 2010 ● Outstanding Excellence in Business
> >Continuity – 2008 ● Business Continuity Provider of the Year (BCM Service)
> >– 2013 BCI Global Awards ● Business Continuity Provider of the Year (BCM
> >Product) – 2013 BCI India Awards
> >
> >*[image: AS_yt]* *[image:
> >AS_twitter]* *[image:
> >AS_in]**[image:
> >AS_gplus]* *[image:
> >AS_fb]**[image:
> >AS_ss]* 
>
>


-- 

Regards,

___

*Sonal Ojha* ● Senior Engineer - Product Developement ● SunGard
Availability Services, India ● Mobile: +91 9922412645●  Email:
sonal.o...@sungard.com ● Website: http://www.sungardas.in/

8 Times Winner – BC Service Provider of the Year – 2011, 2010, 2009, 2006,
2005, 2002, 2000, 1999; Finalist – 2008, 2007, 2004, 2001 ● Excellence in
Infrastructure Management – 2010 ● Outstanding Excellence in Business
Con

RE: [VOTE] Apache CloudStack 4.3.0 (eighth round)


On 17.03.2014 22:39, Animesh Chaturvedi wrote:

Edison

Thanks for taking care of this issue. Nux can you try with this fix
and I will go off building RC


Works for me! Thanks!

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

[PROPOSAL] Use Liquibase to manage DB changes

2014-03-18 Thread Miguel Ferreira

All,

Following from the discussion of [1], I have written a small tool [2] to detect 
potential conflicts related to ACS DB changes.
With the input supplied by that tool, I will proceed to check every commit 
since tag 4.2 up to the head of master.
For every commit that introduces relevant changes to the DB I will create a 
Liquibase [3] change set, apply it to a running ACS DB, run automated system 
tests and possibly refine the change set until the DB is left in a consistent 
state.
(Liquibase is one of the tools proposed in [1] by Rajani to help managing the 
changes to the DB. See [1] for more details on that.)

My goal is twofold: (1) assess how suitable Liquibase is for managing changes 
to ACS DB; and (2) how frequent are "breaking" changes to the DB made.
By "breaking" changes I mean changes that otherwise would require a fresh DB to 
start with.
With the data I will collect I expect to be able to say something about how 
feasible it is to use Liquibase, and how involved would it be to ask every 
developer to make independent and incremental changes to the DB related code.

I will report back on my findings, but feel free to jump in and help out anyway 
you see possible.

Cheers,
Miguel


[1] http://markmail.org/message/7qohq2sbumthjhw6
[2] https://github.com/schubergphilis/cloudstack-db-updater
[3] http://www.liquibase.org/

Re: [VOTE] Apache CloudStack 4.3.0 (eighth round)


On Mar 17, 2014, at 10:53 PM, Prachi Damle  wrote:

> John,
> 
> I could not reproduce the build failure on my dev setup, as mentioned earlier.
> Also Jenkins seem to create awsapi 4.3 build fine without issues.

Did you remove all your cached maven repos ?

> 
> As to whether rampart maven dependencies can be safely removed, we need to 
> really test awsapi functionality after removing the jars thoroughly.
> I am afraid I do not know why these jars are needed or were added to this 
> project.
> 
> Prachi
> 
> 
> From: John Kinsella [mailto:j...@stratosec.co]
> Sent: Monday, March 17, 2014 2:48 PM
> To: dev@cloudstack.apache.org
> Cc: Likitha Shetty; Prachi Damle
> Subject: Re: [VOTE] Apache CloudStack 4.3.0 (eighth round)
> 
> Thanks Sebastien. I had been intending to mail previous committers on the 
> subdir.
> 
> Prachi/Likitha - any comments on https://reviews.apache.org/r/18392/ would be 
> appreciated.
> 
> On Mar 17, 2014, at 12:54 PM, Sebastien Goasguen 
> mailto:run...@gmail.com>> wrote:
> 
> 
> John, I am copying Likitha and Prachi who worked on awsapi, maybe they can 
> help
> 
> -sebastien
> 
> On Mar 17, 2014, at 2:25 PM, John Kinsella 
> mailto:j...@stratosec.co>> wrote:
> 
> 
> Before we go to 9th round, let's get 
> https://issues.apache.org/jira/browse/CLOUDSTACK-6156 resolved.
> 
> I'm pretty busy this week, but will see if I can come up with. Just tried 
> doing a clean awsapi build on a clean AWS instance again and it still fails.
> 
> 
> On Mar 12, 2014, at 5:26 PM, Animesh Chaturvedi 
> mailto:animesh.chaturv...@citrix.com>>
>  wrote:
> 
> Hi All,
> 
> 
> 
> I've created a 4.3.0 release, with the following artifacts up for a
> 
> vote:
> 
> 
> 
> 
> 
> Git Branch and Commit SH:
> 
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.3
> Commit: 6a6ec648099553a42f830dcd566eab2452428908
> 
> 
> 
> List of changes:
> 
> New Features in 4.3: https://issues.apache.org/jira/issues/?filter=12325248
> 
> Improvement in 4.3: https://issues.apache.org/jira/issues/?filter=12325249
> 
> Issues fixed in 4.3 https://issues.apache.org/jira/issues/?filter=12326161
> 
> Known Issues in 4.3: https://issues.apache.org/jira/issues/?filter=12326162
> 
> 
> 
> 
> 
> 
> 
> Source release (checksums and signatures are available at the same
> 
> location):
> 
> https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/
> 
> 
> 
> PGP release keys (signed using 94BE0D7C):
> 
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> 
> 
> 
> Testing instructions are here:
> 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure
> 
> 
> 
> Vote will be open for 72 hours (Monday evening PST 5:30 PM)
> 
> 
> 
> 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)
> 
> 
> 
> Thanks
> 
> Animesh
> 
> 
> Stratosec - Compliance as a Service
> o: 415.315.9385
> @johnlkinsella
> 
> 
> Stratosec - Compliance as a Service
> o: 415.315.9385
> @johnlkinsella
>

Re: [QUESTION] distributed router and VPC routers

2014-03-18 Thread Murali Reddy

On 17/03/14 8:34 PM, "Daan Hoogland"  wrote:

>H Murali,
>
>I saw you checked in a lot of things in a branch called
>distrubutedrouter. As I happen to know Karl Harris at sunguard is busy
>at VPC RVRs.
>Can you tell me how this is related?

Daan,

They are not related. Having a redundent VPC VR avoids VPC VR being single
point of failure. What I am doing is to offload the functionalities
provided by the VPC VR to vSwitch'es on the hypervisors. For 4.4 both
inter-tier routing and network ACL's in VPC can be performed directly on
the hypervisors.

Thanks,
Murali
>And if we can somehow bundle resources for this?
>
>thanks
>-- 
>Daan
>

Re: [PROPOSAL] Enhance the cloudstack events to include more information

2014-03-18 Thread Sonal Ojha

Hello Nitin,

I agree with you, to start with we can replace the event descriptions to
include the resource UUIDs of the required parameters only. For example,
DetachIsoCmd needs only virtualMachineId as the required parameter. Hence,
the event description should include the resource UUID for the virtual
machine. Likewise the required parameters resource UUIDs would be included
in the event description.

-Sonal


On Mon, Mar 17, 2014 at 10:48 PM, Nitin Mehta wrote:

> Sonal - This is a great proposal. In addition, you should also include all
> the first class entities involved in the event.
> Say its a detach iso on a vm - then I should have uuids for both the iso
> and the vm. This would definitely help giving more information and in
> debugging.
>
> Thanks,
> -Nitin
>
> On 17/03/14 9:52 AM, "Alena Prokharchyk" 
> wrote:
>
> >On #1 I would say “display UUID INSTEAD of the DB id in the events API”.
> >We should never expose the DB ids to the API caller, especially if the
> >caller is not an admin. I guess we just never revised the events after
> >UUIDs were introduced.
> >
> >On #4. We should distinguish between end user and an admin and determine
> >which errors are allowed to be shown to the end user. For example, he
> >shouldn’t see any errors related to physical resources allocation error as
> >he has no knowledge about hosts/storages/physical network topology.
> >
> >
> >-Alena.
> >
> >
> >
> >On 3/17/14, 9:40 AM, "John Kinsella"  wrote:
> >
> >>I didn’t see comments from others, but this sounds great to me. More info
> >>is always better IMHO.
> >>
> >>On Mar 11, 2014, at 2:31 AM, Sonal Ojha
> >>mailto:sonal.o...@sungard.com>> wrote:
> >>
> >>Currently the event logged in CloudStack doesn't give detailed
> >>information
> >>about the event that has occurred. The information provided in each event
> >>shown on the cloudstack ui doesn't provide specifics, particularly in
> >>case
> >>of errors. For example, the message shown on the cloudstack ui is just
> >>"Error while starting Vm. Vm Id: " in case of failure to start a vm ,
> >>which doesnt help much.
> >>
> >>I would like to propose some changes to enhance the events to be more
> >>informative. Like:
> >>
> >>1) Instead of just showing resource database id in the event details it
> >>should also display resource UUID. Since all the cloudstack apis take
> >>input
> >>as resource uuid it would be helpful to see the same on the ui as well.
> >>Like in the quickview mode introduce another field as resource UUID which
> >>would specify the UUID for the resource on which the event occurred.
> >>
> >>2) Enhance the events and listEvents API to include the resource UUID so
> >>that it can be queried by the resource UUID as well.
> >>
> >>3) Currently, the event description messages are specified in the
> >>*Cmd.java
> >>file instead, all of them should be externalize to a resource file. This
> >>would be helpful even for internationalization.
> >>
> >>4) Provide more detailed messages in case of error events. Messages such
> >>as
> >>"Error while starting VM" are generic to take any action.
> >>
> >>These changes could be taken forward in phases, some suggestion like
> >>
> >>Phase I -
> >>include 2 and 3 point mentioned above
> >>Phase II -
> >>include 1 and 4 point mentioned above
> >>
> >>Thoughts / Suggestions ?
> >>
> >>--
> >>
> >>Regards,
> >>
> >>___
> >>
> >>*Sonal Ojha* ● Senior Engineer - Product Developement ● SunGard
> >>Availability Services, India ● Mobile: +91 9922412645●  Email:
> >>sonal.o...@sungard.com ● Website:
> >>http://www.sungardas.in/
> >>
> >>8 Times Winner – BC Service Provider of the Year – 2011, 2010, 2009,
> >>2006,
> >>2005, 2002, 2000, 1999; Finalist – 2008, 2007, 2004, 2001 ● Excellence in
> >>Infrastructure Management – 2010 ● Outstanding Excellence in Business
> >>Continuity – 2008 ● Business Continuity Provider of the Year (BCM
> >>Service)
> >>– 2013 BCI Global Awards ● Business Continuity Provider of the Year (BCM
> >>Product) – 2013 BCI India Awards
> >>
> >>Stratosec - Compliance as a Service
> >>o: 415.315.9385
> >>@johnlkinsella
> >>
> >
>
>


-- 

Regards,

___

*Sonal Ojha* ● Senior Engineer - Product Developement ● SunGard
Availability Services, India ● Mobile: +91 9922412645●  Email:
sonal.o...@sungard.com ● Website: http://www.sungardas.in/

8 Times Winner – BC Service Provider of the Year – 2011, 2010, 2009, 2006,
2005, 2002, 2000, 1999; Finalist – 2008, 2007, 2004, 2001 ● Excellence in
Infrastructure Management – 2010 ● Outstanding Excellence in Business
Continuity – 2008 ● Business Continuity Provider of the Year (BCM Service)
– 2013 BCI Global Awards ● Business Continuity Provider of the Year (BCM
Product) – 2013 BCI India Awards

*[image: AS_yt]* *[image:
AS_twitter]*

Re: [PROPOSAL] Enhance the cloudstack events to include more information

2014-03-18 Thread Sonal Ojha

Shall I go ahead and open a jira item on this to add more details?


On Tue, Mar 18, 2014 at 3:59 PM, Sonal Ojha  wrote:

> Hello Nitin,
>
> I agree with you, to start with we can replace the event descriptions to
> include the resource UUIDs of the required parameters only. For example,
> DetachIsoCmd needs only virtualMachineId as the required parameter. Hence,
> the event description should include the resource UUID for the virtual
> machine. Likewise the required parameters resource UUIDs would be included
> in the event description.
>
> -Sonal
>
>
> On Mon, Mar 17, 2014 at 10:48 PM, Nitin Mehta wrote:
>
>> Sonal - This is a great proposal. In addition, you should also include all
>> the first class entities involved in the event.
>> Say its a detach iso on a vm - then I should have uuids for both the iso
>> and the vm. This would definitely help giving more information and in
>> debugging.
>>
>> Thanks,
>> -Nitin
>>
>> On 17/03/14 9:52 AM, "Alena Prokharchyk" 
>> wrote:
>>
>> >On #1 I would say “display UUID INSTEAD of the DB id in the events API”.
>> >We should never expose the DB ids to the API caller, especially if the
>> >caller is not an admin. I guess we just never revised the events after
>> >UUIDs were introduced.
>> >
>> >On #4. We should distinguish between end user and an admin and determine
>> >which errors are allowed to be shown to the end user. For example, he
>> >shouldn’t see any errors related to physical resources allocation error
>> as
>> >he has no knowledge about hosts/storages/physical network topology.
>> >
>> >
>> >-Alena.
>> >
>> >
>> >
>> >On 3/17/14, 9:40 AM, "John Kinsella"  wrote:
>> >
>> >>I didn’t see comments from others, but this sounds great to me. More
>> info
>> >>is always better IMHO.
>> >>
>> >>On Mar 11, 2014, at 2:31 AM, Sonal Ojha
>> >>mailto:sonal.o...@sungard.com>> wrote:
>> >>
>> >>Currently the event logged in CloudStack doesn't give detailed
>> >>information
>> >>about the event that has occurred. The information provided in each
>> event
>> >>shown on the cloudstack ui doesn't provide specifics, particularly in
>> >>case
>> >>of errors. For example, the message shown on the cloudstack ui is just
>> >>"Error while starting Vm. Vm Id: " in case of failure to start a vm
>> ,
>> >>which doesnt help much.
>> >>
>> >>I would like to propose some changes to enhance the events to be more
>> >>informative. Like:
>> >>
>> >>1) Instead of just showing resource database id in the event details it
>> >>should also display resource UUID. Since all the cloudstack apis take
>> >>input
>> >>as resource uuid it would be helpful to see the same on the ui as well.
>> >>Like in the quickview mode introduce another field as resource UUID
>> which
>> >>would specify the UUID for the resource on which the event occurred.
>> >>
>> >>2) Enhance the events and listEvents API to include the resource UUID so
>> >>that it can be queried by the resource UUID as well.
>> >>
>> >>3) Currently, the event description messages are specified in the
>> >>*Cmd.java
>> >>file instead, all of them should be externalize to a resource file. This
>> >>would be helpful even for internationalization.
>> >>
>> >>4) Provide more detailed messages in case of error events. Messages such
>> >>as
>> >>"Error while starting VM" are generic to take any action.
>> >>
>> >>These changes could be taken forward in phases, some suggestion like
>> >>
>> >>Phase I -
>> >>include 2 and 3 point mentioned above
>> >>Phase II -
>> >>include 1 and 4 point mentioned above
>> >>
>> >>Thoughts / Suggestions ?
>> >>
>> >>--
>> >>
>> >>Regards,
>> >>
>> >>___
>> >>
>> >>*Sonal Ojha* ● Senior Engineer - Product Developement ● SunGard
>> >>Availability Services, India ● Mobile: +91 9922412645●  Email:
>> >>sonal.o...@sungard.com ● Website:
>> >>http://www.sungardas.in/
>> >>
>> >>8 Times Winner – BC Service Provider of the Year – 2011, 2010, 2009,
>> >>2006,
>> >>2005, 2002, 2000, 1999; Finalist – 2008, 2007, 2004, 2001 ● Excellence
>> in
>> >>Infrastructure Management – 2010 ● Outstanding Excellence in Business
>> >>Continuity – 2008 ● Business Continuity Provider of the Year (BCM
>> >>Service)
>> >>– 2013 BCI Global Awards ● Business Continuity Provider of the Year (BCM
>> >>Product) – 2013 BCI India Awards
>> >>
>> >>Stratosec - Compliance as a Service
>> >>o: 415.315.9385
>> >>@johnlkinsella
>> >>
>> >
>>
>>
>
>
> --
>
> Regards,
>
> ___
>
> *Sonal Ojha* ● Senior Engineer - Product Developement ● SunGard
> Availability Services, India ● Mobile: +91 9922412645●  Email:
> sonal.o...@sungard.com ● Website: http://www.sungardas.in/
>
> 8 Times Winner – BC Service Provider of the Year – 2011, 2010, 2009, 2006,
> 2005, 2002, 2000, 1999; Finalist – 2008, 2007, 2004, 2001 ● Excellence in
> Infrastructure Management – 2010 ● Outstanding Excellence in

Re: QoS of VIF not working

2014-03-18 Thread Yitao Jiang

Sorry,guys it's my mistake.i set up two mgmt server and forget to sync
codes to another.
On Mar 18, 2014 3:44 PM, "Yitao Jiang"  wrote:

> Hi,
>
> In CirtixResourceBase.java(
> https://github.com/apache/cloudstack/blob/4.2.1/plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/resource/CitrixResourceBase.java)
> of createVif method , i see that the network rate value will be multiplied
> by 128 .
>  if (nic.getNetworkRateMbps() != null
> && nic.getNetworkRateMbps().intValue() != -1) {
>  vifr.qosAlgorithmType = "ratelimit";
> vifr.qosAlgorithmParams = new HashMap();
>  // convert mbs to kilobyte per second
> vifr.qosAlgorithmParams.put("kbps",
>  Integer.toString(nic.getNetworkRateMbps() * 128));
>  }
> and when i create a service_offering with 1Mb/s QoS, the vm's networking
> will be limited in 128Kb/s.
> All works fine.
>
> But what i wanna do is when a service_offering with 1Mb/s then the vm will
> be limited in 1Kb/s,so I change the coded like that
> vifr.qosAlgorithmParams.put("kbps",
> Integer.toString(nic.getNetworkRateMbps()));
> without multiplied by 128.
>
> But acctualy the vm still limit in 128Kb/s.
>
> Did i miss anyting?
>
> My environments is :
> CS 4.2.1
> Xenserver 6.2.0
>
> Thanks,
>
> Yitao
>

Re: [PROPOSAL] Enhance the cloudstack events to include more information

2014-03-18 Thread Jeff Hair

I just noticed this here. I'm working on a plugin that we've chosen to
implement in an event-based fashion, using the event bus. The event bus
events have basically no information on them, and the database-recorded
events have non-standard description formats which usually have useful
information. In my case, I was trying to bind to the static IP events. I
was able to do that fine, but without the ID of the IP that was enabled, it
was kind of useless for what I was trying to do.

So I'd like to also propose that event bus events either:
A) have the event's DB ID recorded, and can query that ID and get a
standard-format (e.g. JSON) event out of the database with relevant
information.
B) Just put the same standard-format event info directly into the event bus
messages.

Jeff


On Tue, Mar 18, 2014 at 10:29 AM, Sonal Ojha  wrote:

> Hello Nitin,
>
> I agree with you, to start with we can replace the event descriptions to
> include the resource UUIDs of the required parameters only. For example,
> DetachIsoCmd needs only virtualMachineId as the required parameter. Hence,
> the event description should include the resource UUID for the virtual
> machine. Likewise the required parameters resource UUIDs would be included
> in the event description.
>
> -Sonal
>
>
> On Mon, Mar 17, 2014 at 10:48 PM, Nitin Mehta  >wrote:
>
> > Sonal - This is a great proposal. In addition, you should also include
> all
> > the first class entities involved in the event.
> > Say its a detach iso on a vm - then I should have uuids for both the iso
> > and the vm. This would definitely help giving more information and in
> > debugging.
> >
> > Thanks,
> > -Nitin
> >
> > On 17/03/14 9:52 AM, "Alena Prokharchyk" 
> > wrote:
> >
> > >On #1 I would say “display UUID INSTEAD of the DB id in the events API”.
> > >We should never expose the DB ids to the API caller, especially if the
> > >caller is not an admin. I guess we just never revised the events after
> > >UUIDs were introduced.
> > >
> > >On #4. We should distinguish between end user and an admin and determine
> > >which errors are allowed to be shown to the end user. For example, he
> > >shouldn’t see any errors related to physical resources allocation error
> as
> > >he has no knowledge about hosts/storages/physical network topology.
> > >
> > >
> > >-Alena.
> > >
> > >
> > >
> > >On 3/17/14, 9:40 AM, "John Kinsella"  wrote:
> > >
> > >>I didn’t see comments from others, but this sounds great to me. More
> info
> > >>is always better IMHO.
> > >>
> > >>On Mar 11, 2014, at 2:31 AM, Sonal Ojha
> > >>mailto:sonal.o...@sungard.com>> wrote:
> > >>
> > >>Currently the event logged in CloudStack doesn't give detailed
> > >>information
> > >>about the event that has occurred. The information provided in each
> event
> > >>shown on the cloudstack ui doesn't provide specifics, particularly in
> > >>case
> > >>of errors. For example, the message shown on the cloudstack ui is just
> > >>"Error while starting Vm. Vm Id: " in case of failure to start a
> vm ,
> > >>which doesnt help much.
> > >>
> > >>I would like to propose some changes to enhance the events to be more
> > >>informative. Like:
> > >>
> > >>1) Instead of just showing resource database id in the event details it
> > >>should also display resource UUID. Since all the cloudstack apis take
> > >>input
> > >>as resource uuid it would be helpful to see the same on the ui as well.
> > >>Like in the quickview mode introduce another field as resource UUID
> which
> > >>would specify the UUID for the resource on which the event occurred.
> > >>
> > >>2) Enhance the events and listEvents API to include the resource UUID
> so
> > >>that it can be queried by the resource UUID as well.
> > >>
> > >>3) Currently, the event description messages are specified in the
> > >>*Cmd.java
> > >>file instead, all of them should be externalize to a resource file.
> This
> > >>would be helpful even for internationalization.
> > >>
> > >>4) Provide more detailed messages in case of error events. Messages
> such
> > >>as
> > >>"Error while starting VM" are generic to take any action.
> > >>
> > >>These changes could be taken forward in phases, some suggestion like
> > >>
> > >>Phase I -
> > >>include 2 and 3 point mentioned above
> > >>Phase II -
> > >>include 1 and 4 point mentioned above
> > >>
> > >>Thoughts / Suggestions ?
> > >>
> > >>--
> > >>
> > >>Regards,
> > >>
> > >>___
> > >>
> > >>*Sonal Ojha* ● Senior Engineer - Product Developement ● SunGard
> > >>Availability Services, India ● Mobile: +91 9922412645●  Email:
> > >>sonal.o...@sungard.com ● Website:
> > >>http://www.sungardas.in/
> > >>
> > >>8 Times Winner – BC Service Provider of the Year – 2011, 2010, 2009,
> > >>2006,
> > >>2005, 2002, 2000, 1999; Finalist – 2008, 2007, 2004, 2001 ● Excellence
> in
> > >>Infrastructure Management – 2010 ● Outstanding Excellence in Business
> > >>Continuity – 2008 ● Business Cont

random template from zones

2014-03-18 Thread Daan Hoogland

H Min, Edison,

As discussed in a prior mailthread [1] templates being copied from a
random zone was fixed in 4.3. The code is not present in master (or
4.4) is this solved in another way later on? The commit doesn't
cleanly cherry-pick. It is hurting us in 4.2 so let me know if it pays
cleaning it for master, please.

[1] http://markmail.org/message/4cn5pn4e7butyj2c

-- 
Daan

CloudStack implementations

2014-03-18 Thread Marcus

Do we have any general stats on how cloudstack is being used? Common
deployment sizes, largest deployments, etc? I'm curious as to how far
people have actually scaled it in real deployments, although I realize that
the info can be proprietary.

Re: CloudStack implementations

2014-03-18 Thread Wido den Hollander


On 03/18/2014 12:07 PM, Marcus wrote:

Do we have any general stats on how cloudstack is being used? Common
deployment sizes, largest deployments, etc? I'm curious as to how far
people have actually scaled it in real deployments, although I realize that
the info can be proprietary.



Recently at the Ceph project the tool "ceph-brag" was developed. It 
gathers information about your Ceph deployment and sends back the 
information to the project.


Something like this might be nice (opt-in!!) for CloudStack. It can 
anonymously report things like:

- Number of Instances
- Number of pods, cluster, hosts
- Number of Primary Storage and their type
- Basic / Advanced Networking

This could all be written into one JSON file which we can submit back to 
the project.


With this we would get more information about how CloudStack is used.

Obviously, the code will be Open Source so people can see how we gather 
the information (probably a lot of SQL selects..) and how we submit it 
to our servers.


Is that something what you would like?

Wido

Re: CloudStack implementations


On Mar 18, 2014, at 12:15 PM, Wido den Hollander  wrote:

> On 03/18/2014 12:07 PM, Marcus wrote:
>> Do we have any general stats on how cloudstack is being used? Common
>> deployment sizes, largest deployments, etc? I'm curious as to how far
>> people have actually scaled it in real deployments, although I realize that
>> the info can be proprietary.
>> 
> 
> Recently at the Ceph project the tool "ceph-brag" was developed. It gathers 
> information about your Ceph deployment and sends back the information to the 
> project.
> 
> Something like this might be nice (opt-in!!) for CloudStack. It can 
> anonymously report things like:
> - Number of Instances
> - Number of pods, cluster, hosts
> - Number of Primary Storage and their type
> - Basic / Advanced Networking
> 
> This could all be written into one JSON file which we can submit back to the 
> project.
> 
> With this we would get more information about how CloudStack is used.
> 
> Obviously, the code will be Open Source so people can see how we gather the 
> information (probably a lot of SQL selects..) and how we submit it to our 
> servers.
> 
> Is that something what you would like?

+1

> 
> Wido

Re: CloudStack implementations

2014-03-18 Thread Chip Childers



> On Mar 18, 2014, at 7:07 AM, Marcus  wrote:
> 
> Do we have any general stats on how cloudstack is being used? Common
> deployment sizes, largest deployments, etc? I'm curious as to how far
> people have actually scaled it in real deployments, although I realize that
> the info can be proprietary.

The largest deployment is 40,000 physical hosts.

Re: [PROPOSAL] Enhance the cloudstack events to include more information

2014-03-18 Thread Chip Childers

Jira for tracking progress, and a design page on the wiki for any design info. 

> On Mar 18, 2014, at 6:34 AM, Sonal Ojha  wrote:
> 
> Shall I go ahead and open a jira item on this to add more details?
> 
> 
>> On Tue, Mar 18, 2014 at 3:59 PM, Sonal Ojha  wrote:
>> 
>> Hello Nitin,
>> 
>> I agree with you, to start with we can replace the event descriptions to
>> include the resource UUIDs of the required parameters only. For example,
>> DetachIsoCmd needs only virtualMachineId as the required parameter. Hence,
>> the event description should include the resource UUID for the virtual
>> machine. Likewise the required parameters resource UUIDs would be included
>> in the event description.
>> 
>> -Sonal
>> 
>> 
>> On Mon, Mar 17, 2014 at 10:48 PM, Nitin Mehta wrote:
>> 
>>> Sonal - This is a great proposal. In addition, you should also include all
>>> the first class entities involved in the event.
>>> Say its a detach iso on a vm - then I should have uuids for both the iso
>>> and the vm. This would definitely help giving more information and in
>>> debugging.
>>> 
>>> Thanks,
>>> -Nitin
>>> 
>>> On 17/03/14 9:52 AM, "Alena Prokharchyk" 
>>> wrote:
>>> 
 On #1 I would say “display UUID INSTEAD of the DB id in the events API”.
 We should never expose the DB ids to the API caller, especially if the
 caller is not an admin. I guess we just never revised the events after
 UUIDs were introduced.
 
 On #4. We should distinguish between end user and an admin and determine
 which errors are allowed to be shown to the end user. For example, he
 shouldn’t see any errors related to physical resources allocation error
>>> as
 he has no knowledge about hosts/storages/physical network topology.
 
 
 -Alena.
 
 
 
> On 3/17/14, 9:40 AM, "John Kinsella"  wrote:
> 
> I didn’t see comments from others, but this sounds great to me. More
>>> info
> is always better IMHO.
> 
> On Mar 11, 2014, at 2:31 AM, Sonal Ojha
> mailto:sonal.o...@sungard.com>> wrote:
> 
> Currently the event logged in CloudStack doesn't give detailed
> information
> about the event that has occurred. The information provided in each
>>> event
> shown on the cloudstack ui doesn't provide specifics, particularly in
> case
> of errors. For example, the message shown on the cloudstack ui is just
> "Error while starting Vm. Vm Id: " in case of failure to start a vm
>>> ,
> which doesnt help much.
> 
> I would like to propose some changes to enhance the events to be more
> informative. Like:
> 
> 1) Instead of just showing resource database id in the event details it
> should also display resource UUID. Since all the cloudstack apis take
> input
> as resource uuid it would be helpful to see the same on the ui as well.
> Like in the quickview mode introduce another field as resource UUID
>>> which
> would specify the UUID for the resource on which the event occurred.
> 
> 2) Enhance the events and listEvents API to include the resource UUID so
> that it can be queried by the resource UUID as well.
> 
> 3) Currently, the event description messages are specified in the
> *Cmd.java
> file instead, all of them should be externalize to a resource file. This
> would be helpful even for internationalization.
> 
> 4) Provide more detailed messages in case of error events. Messages such
> as
> "Error while starting VM" are generic to take any action.
> 
> These changes could be taken forward in phases, some suggestion like
> 
> Phase I -
> include 2 and 3 point mentioned above
> Phase II -
> include 1 and 4 point mentioned above
> 
> Thoughts / Suggestions ?
> 
> --
> 
> Regards,
> 
> ___
> 
> *Sonal Ojha* ● Senior Engineer - Product Developement ● SunGard
> Availability Services, India ● Mobile: +91 9922412645●  Email:
> sonal.o...@sungard.com ● Website:
> http://www.sungardas.in/
> 
> 8 Times Winner – BC Service Provider of the Year – 2011, 2010, 2009,
> 2006,
> 2005, 2002, 2000, 1999; Finalist – 2008, 2007, 2004, 2001 ● Excellence
>>> in
> Infrastructure Management – 2010 ● Outstanding Excellence in Business
> Continuity – 2008 ● Business Continuity Provider of the Year (BCM
> Service)
> – 2013 BCI Global Awards ● Business Continuity Provider of the Year (BCM
> Product) – 2013 BCI India Awards
> 
> Stratosec - Compliance as a Service
> o: 415.315.9385
> @johnlkinsella
>> 
>> 
>> --
>> 
>> Regards,
>> 
>> ___
>> 
>> *Sonal Ojha* ● Senior Engineer - Product Developement ● SunGard
>> Availability Services, India ● Mobile: +91 9922412645●  Email:
>> son

Build failed in Jenkins: build-master #489

2014-03-18 Thread jenkins

See 

Changes:

[Daan Hoogland] CLOUDSTACK-5432: potential bugs in case of stop mgt server while

--
[...truncated 1430 lines...]
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.668 sec
Running org.apache.cloudstack.privategw.AclOnPrivateGwTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.247 sec
Running org.apache.cloudstack.service.ServiceOfferingVOTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
Running org.apache.cloudstack.affinity.AffinityApiUnitTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.15 sec
Running org.apache.cloudstack.network.lb.ApplicationLoadBalancerTest
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.308 sec
Running org.apache.cloudstack.network.lb.CertServiceTest
Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.481 sec
Running 
org.apache.cloudstack.region.gslb.GlobalLoadBalancingRulesServiceImplTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.039 sec
Running org.apache.cloudstack.region.RegionManagerTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec

Results :

Tests run: 135, Failures: 0, Errors: 0, Skipped: 1

[INFO] 
[INFO] 
[INFO] Building Apache CloudStack Usage Server 4.5.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ cloud-usage ---
[INFO] Deleting 
 (includes = 
[**/*], excludes = [])
[INFO] Deleting  
(includes = [target, dist], excludes = [])
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ 
cloud-usage ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-usage ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.7:run (generate-resource) @ cloud-usage ---
[INFO] Executing tasks

main:
 [copy] Copying 2 files to 

[INFO] Executed tasks
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
cloud-usage ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ cloud-usage 
---
[INFO] Compiling 18 source files to 

[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
cloud-usage ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 8 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ 
cloud-usage ---
[INFO] Compiling 4 source files to 

[INFO] 
[INFO] --- maven-surefire-plugin:2.12:test (default-test) @ cloud-usage ---
[INFO] Surefire report directory: 


---
 T E S T S
---
Running com.cloud.usage.UsageSanityCheckerTest
log4j:WARN No appenders could be found for logger 
(com.cloud.utils.crypt.EncryptionSecretKeyChecker).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
info.
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.676 sec

Results :

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0

[INFO] 
[INFO] 
[INFO] Building Apache XenSource XAPI 6.2.0-1-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ xapi ---
[INFO] Deleting 
 
(includes = [**/*], excludes = [])
[INFO] Deleting 
 
(includes = [target, dist], excludes = [])
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ xapi ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ xapi ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDi

Re: Review Request 18677: CLOUDSTACK-3272

2014-03-18 Thread Murali Reddy


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



plugins/event-bus/rabbitmq/src/org/apache/cloudstack/mom/rabbitmq/RabbitMQEventBus.java


Please use String.Equals method than '=='



plugins/event-bus/rabbitmq/src/org/apache/cloudstack/mom/rabbitmq/RabbitMQEventBus.java


Why not filter at the source where events gets published it self instead of 
filtering in the plug-ins?

For e.g. in ActionEventUtils.publishOnEventBus you could check the config 
value 'publish.action.events' and then decide to publish or not.


- Murali Reddy


On March 4, 2014, 5:51 a.m., Sonal Ojha wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/18677/
> ---
> 
> (Updated March 4, 2014, 5:51 a.m.)
> 
> 
> Review request for cloudstack, Chiradeep Vittal and Murali Reddy.
> 
> 
> Bugs: CLOUDSTACK-3272
> https://issues.apache.org/jira/browse/CLOUDSTACK-3272
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> At present, there are multiple event types that are generated by CS, action 
> events,usage events, resource state change events and alerts. Current problem 
> is
> all the events gets published on the event bus when event bus is enabled. 
> Intent is to introduce global setting config parameters to specify which 
> category of events to be published or not be published on the event bus.
> 
> 
> Diffs
> -
> 
>   
> plugins/event-bus/rabbitmq/src/org/apache/cloudstack/mom/rabbitmq/RabbitMQEventBus.java
>  478c8d7 
>   server/src/com/cloud/configuration/Config.java 2d55f46 
>   server/src/com/cloud/test/DatabaseConfig.java 9370218 
> 
> Diff: https://reviews.apache.org/r/18677/diff/
> 
> 
> Testing
> ---
> 
> Successfully tested publishing / not publishing of various events based on 
> the global parameter publish.*.events.
> 
> 
> Thanks,
> 
> Sonal Ojha
> 
>

Build failed in Jenkins: build-master #490

2014-03-18 Thread jenkins

See 

Changes:

[Daan Hoogland] checkstyle: trailing spaces

--
[...truncated 1527 lines...]
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
xapi ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ xapi 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12:test (default-test) @ xapi ---
[INFO] Surefire report directory: 


---
 T E S T S
---

Results :

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

[INFO] 
[INFO] 
[INFO] Building Apache CloudStack Cloud Engine Orchestration Component 
4.5.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
cloud-engine-orchestration ---
[INFO] Deleting 

 (includes = [**/*], excludes = [])
[INFO] Deleting 
 
(includes = [target, dist], excludes = [])
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ 
cloud-engine-orchestration ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloud-engine-orchestration ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
cloud-engine-orchestration ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ 
cloud-engine-orchestration ---
[INFO] Compiling 68 source files to 

[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
cloud-engine-orchestration ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ 
cloud-engine-orchestration ---
[INFO] Compiling 5 source files to 

[INFO] 
[INFO] --- maven-surefire-plugin:2.12:test (default-test) @ 
cloud-engine-orchestration ---
[INFO] Tests are skipped.
[INFO] 
[INFO] 
[INFO] Building Apache CloudStack Cloud Services 4.5.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ cloudstack-services 
---
[INFO] Deleting 
 (includes 
= [**/*], excludes = [])
[INFO] Deleting  
(includes = [target, dist], excludes = [])
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloudstack-services ---
[INFO] 
[INFO] 
[INFO] Building Apache CloudStack Secondary Storage 4.5.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
cloudstack-service-secondary-storage ---
[INFO] Deleting 

 (includes = [**/*], excludes = [])
[INFO] Deleting 
 
(includes = [target, dist], excludes = [])
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ 
cloudstack-service-secondary-storage ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloudstack-service-secondary-storage ---
[INFO]

RE: CloudStack implementations

2014-03-18 Thread Giles Sirett

Wido
+1 on that idea

I know many people get nervous about such things for a FOSS project, so we 
would need to make sure that anything is transparent, is VERY careful about 
data and gives people the option to opt-out

The simple fact is that we don't currently have any idea how many production 
deployments, their scale,etc

We did a survey last year and got c.270 responses -  but we had to promote the 
awareness of that surevey and  there were plenty of ACS sites I know of who 
just didn't respond.  There will be many others that I don't know of

What differentiates ACS from other similar techs IMO is the number of 
production deployments. If we cant quantify that, it sounds like a lot of hot 
air.

Another approach, may be to put a "showcase" area on the website where people 
can submit their own sort of case studies

Kind Regards
Giles

D: +44 20 3603 0541 | M: +44 796 111 2055
giles.sir...@shapeblue.com

-Original Message-
From: sebgoa [mailto:run...@gmail.com]
Sent: 18 March 2014 11:21
To: dev@cloudstack.apache.org
Subject: Re: CloudStack implementations

On Mar 18, 2014, at 12:15 PM, Wido den Hollander  wrote:

> On 03/18/2014 12:07 PM, Marcus wrote:
>> Do we have any general stats on how cloudstack is being used? Common
>> deployment sizes, largest deployments, etc? I'm curious as to how far
>> people have actually scaled it in real deployments, although I
>> realize that the info can be proprietary.
>>
>
> Recently at the Ceph project the tool "ceph-brag" was developed. It gathers 
> information about your Ceph deployment and sends back the information to the 
> project.
>
> Something like this might be nice (opt-in!!) for CloudStack. It can 
> anonymously report things like:
> - Number of Instances
> - Number of pods, cluster, hosts
> - Number of Primary Storage and their type
> - Basic / Advanced Networking
>
> This could all be written into one JSON file which we can submit back to the 
> project.
>
> With this we would get more information about how CloudStack is used.
>
> Obviously, the code will be Open Source so people can see how we gather the 
> information (probably a lot of SQL selects..) and how we submit it to our 
> servers.
>
> Is that something what you would like?

+1

>
> Wido

Need Enterprise Grade Support for Apache CloudStack?
Our CloudStack Infrastructure 
Support offers the 
best 24/7 SLA for CloudStack Environments.

Apache CloudStack Bootcamp training courses

**NEW!** CloudStack 4.2.1 training
18th-19th February 2014, Brazil. 
Classroom
17th-23rd March 2014, Region A. Instructor led, 
On-line
24th-28th March 2014, Region B. Instructor led, 
On-line
16th-20th June 2014, Region A. Instructor led, 
On-line
23rd-27th June 2014, Region B. Instructor led, 
On-line

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.

Jenkins build is back to normal : build-master #491

2014-03-18 Thread jenkins

See

Re: CloudStack implementations

2014-03-18 Thread Rohit Yadav

Cool idea, we can also have a monkey-brag ACS plugin which gives users an
API which can be triggered via cloudmonkey cli tool or by some gui/button
on the frontend to submit stats anonymously to our servers.

Cheers.


On Tue, Mar 18, 2014 at 4:45 PM, Wido den Hollander  wrote:

> On 03/18/2014 12:07 PM, Marcus wrote:
>
>> Do we have any general stats on how cloudstack is being used? Common
>> deployment sizes, largest deployments, etc? I'm curious as to how far
>> people have actually scaled it in real deployments, although I realize
>> that
>> the info can be proprietary.
>>
>>
> Recently at the Ceph project the tool "ceph-brag" was developed. It
> gathers information about your Ceph deployment and sends back the
> information to the project.
>
> Something like this might be nice (opt-in!!) for CloudStack. It can
> anonymously report things like:
> - Number of Instances
> - Number of pods, cluster, hosts
> - Number of Primary Storage and their type
> - Basic / Advanced Networking
>
> This could all be written into one JSON file which we can submit back to
> the project.
>
> With this we would get more information about how CloudStack is used.
>
> Obviously, the code will be Open Source so people can see how we gather
> the information (probably a lot of SQL selects..) and how we submit it to
> our servers.
>
> Is that something what you would like?
>
> Wido
>

Cloudstack documentation

2014-03-18 Thread Pierre-Luc Dion

Hi all,

I would like to know where we can get newer version of documentation for
Cloudstack. Look like the documentation site is not updated since 4.2.0. I
know that the documentation system will change, is their any information
about it somewhere?

Also, I would like to contribute as well.

Thanks,

Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_

orchestrateTakeVolumeSnapshot Call

All,

I'm looking at the following issue[0]. The reporter says in the second sentence 
the method is always returning success even when an exception occurs or 
otherwise fails. Looking at the code, if the inside call to 
orchestrateTakeVolumeSnapshot raises an exception, it should bubble up and not 
return the SUCCEEDED message surely?


private Pair 
orchestrateTakeVolumeSnapshot(VmWorkTakeVolumeSnapshot work) throws Exception {
Account account = _accountDao.findById(work.getAccountId());
orchestrateTakeVolumeSnapshot(work.getVolumeId(), work.getPolicyId(), 
work.getSnapshotId(),
account, work.isQuiesceVm());
return new Pair(JobInfo.Status.SUCCEEDED,
_jobMgr.marshallResultObject(work.getSnapshotId()));
}

[0] https://issues.apache.org/jira/browse/CLOUDSTACK-5825
Need Enterprise Grade Support for Apache CloudStack?
Our CloudStack Infrastructure 
Support offers the 
best 24/7 SLA for CloudStack Environments.

Apache CloudStack Bootcamp training courses

**NEW!** CloudStack 4.2.1 training
18th-19th February 2014, Brazil. 
Classroom
17th-23rd March 2014, Region A. Instructor led, 
On-line
24th-28th March 2014, Region B. Instructor led, 
On-line
16th-20th June 2014, Region A. Instructor led, 
On-line
23rd-27th June 2014, Region B. Instructor led, 
On-line

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.

Review Request 19351: Fixed updating ipset on acquiring vm nic secondary ip for advanced SG zone

2014-03-18 Thread Jayapal Reddy


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

Review request for cloudstack, Abhinandan Prateek and edison su.


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


Repository: cloudstack-git


Description
---

Updated adding SG rules for nic secondary ips in Advacned SG.


Diffs
-

  api/src/org/apache/cloudstack/api/command/user/vm/AddIpToVmNicCmd.java 
b5e2239 

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


Testing
---

Tested 'ipset -L' output on xenserver after acquiring secondary ip for vm nic


Thanks,

Jayapal Reddy

Re: Cloudstack documentation

2014-03-18 Thread Wido den Hollander


On 03/18/2014 02:08 PM, Pierre-Luc Dion wrote:

Hi all,

I would like to know where we can get newer version of documentation for
Cloudstack. Look like the documentation site is not updated since 4.2.0. I
know that the documentation system will change, is their any information
about it somewhere?



Yes, it moved to it's own repository: 
https://git-wip-us.apache.org/repos/asf?p=cloudstack-docs.git


$ git clone https://git-wip-us.apache.org/repos/asf/cloudstack-docs.git

From there you can probably build the docs yourself. Be aware that we 
are moving to RST.



Also, I would like to contribute as well.



Patches are always welcome!


Thanks,

Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_

CLOUDSTACK-6240 patch

2014-03-18 Thread Jayapal Reddy Uradi

Hi Animesh,

Uploaded the patch for CLOUDSTACK-6240 -ipset requires VM stop/start to get 
updated
https://reviews.apache.org/r/19351/

Also updated the bug with the patch.

Thanks,
Jayapal

RE: Java Coding Convention Errors

2014-03-18 Thread Soheil Eizadi

Here is a code fragment for serialization:

result = (T)gson.fromJson(resultString, 
TypeToken.get(newObject.getClass()).getType());

It is just generic/single handler for all generic type corresponding to the 
same raw type.

-Soheil


From: Hugo Trippaers [trip...@gmail.com]
Sent: Monday, March 17, 2014 11:30 PM
To: dev@cloudstack.apache.org
Subject: Re: Java Coding Convention Errors

Soheil,

How are these classes serialized? There are different ways to solve this like 
annotations with the serialized name or a gson policy.

Cheers,
Hugo

Sent from my iPhone

> On 18 mrt. 2014, at 03:33, Soheil Eizadi  wrote:
>
> Looks like in the new trunk we have turned on checks to enforce coding 
> conventions in Eclipse? I have errors with some classes that I need to turn 
> off:
> "Name 'is_default' must match pattern '^_?[a-zA-Z0-9]*$'."
>
> For example a declaration:
>
>private boolean is_default;
>
> These classes are part of the interface for REST communication so the strings 
> must match the corresponding JSON objects. What is the best practice to turn 
> this off in the project for a particular Class?
> -Soheil

Re: Review Request 18964: Windowsfication of CloudStack Management Server - Changes to support windows OS

2014-03-18 Thread Damodar Reddy Talakanti

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

(Updated March 18, 2014, 1:46 p.m.)

Review request for cloudstack, Abhinandan Prateek, Chiradeep Vittal, daan
Hoogland, and Donal Lafferty.

Changes
---

Added test case to verify the right scripts are returned based on OS name.

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

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

Repository: cloudstack-git

Description
---

Windowsfication of CloudStack Management Server

Diffs (updated)
-

scripts/installer/windows/acs.wxs PRE-CREATION
scripts/installer/windows/client.wxs PRE-CREATION
scripts/installer/windows/start.bat PRE-CREATION
scripts/vm/systemvm/injectkeys.py PRE-CREATION
server/src/com/cloud/server/ConfigurationServerImpl.java b8da4c8
server/test/com/cloud/server/ConfigurationServerImplTest.java 08a2097

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

Testing
---

Tested in Linux environment after changes
Also tested in Windows environment(For now tested on windows-8) to make sure it
is getting installed and management service is running.

Able to add zones, able to register templates, able to launch a VM when it is
running on windows.

Currently though it is getting added as a windows service, not able to start
the service through windows service control manager which I am looking into
currently. When run .exe file which is installed then server is getting up and
able to access cloud stack UI.

For now The following assumptions are made:
1. SSH keys are already installed
2. JAVA is already installed
3. tomcat is already installed

This patch contains the following new files related to WiX tool (To compile and
run we need this tool)
1. acs.wxs
The following command will be used to compile
"\bin\candle.exe" acs.wxs
2. client.wxs
The following command will be used to generate the above file
"\bin\heat" dir client -gg -cg Test -ke -sfrag
-template fragment -out client.wxs -var wix.SourceClient -dr WEBAPPS
The following command will be used to compile the above generated file
"\bin\candle.exe" client.wxs
3. The following command will be used to generate .msi file
"\bin\light.exe" acs.wixobj client.wixobj -out acs.msi
-ext "C:\Program Files (x86)\WiX Toolset v3.8\bin\WixUIExtension.dll"
-dSourceClient=SourceDir\client

Thanks,

Damodar Reddy Talakanti

[GitHub] cloudstack-docs pull request: add warning not to use "-Dmaven.test...

2014-03-18 Thread asfgit

Github user asfgit closed the pull request at:

https://github.com/apache/cloudstack-docs/pull/2


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

Re: Cloudstack documentation

2014-03-18 Thread Pierre-Luc Dion

Thanks Wido,

Cool, look like the rtd version is in there too.  so I guest we need a lot
of work on conversion from publican to RST?




Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
514-447-3456, 1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_


On Tue, Mar 18, 2014 at 9:15 AM, Wido den Hollander  wrote:

> On 03/18/2014 02:08 PM, Pierre-Luc Dion wrote:
>
>> Hi all,
>>
>> I would like to know where we can get newer version of documentation for
>> Cloudstack. Look like the documentation site is not updated since 4.2.0. I
>> know that the documentation system will change, is their any information
>> about it somewhere?
>>
>>
> Yes, it moved to it's own repository: https://git-wip-us.apache.org/
> repos/asf?p=cloudstack-docs.git
>
> $ git clone https://git-wip-us.apache.org/repos/asf/cloudstack-docs.git
>
> From there you can probably build the docs yourself. Be aware that we are
> moving to RST.
>
>
>  Also, I would like to contribute as well.
>>
>>
> Patches are always welcome!
>
>  Thanks,
>>
>> Pierre-Luc Dion
>> Architecte de Solution Cloud | Cloud Solutions Architect
>> - - -
>>
>> *CloudOps*420 rue Guy
>>
>> Montréal QC  H3J 1S6
>> www.cloudops.com
>> @CloudOps_
>>
>>
>

RE: [VOTE] Apache CloudStack 4.3.0 (eighth round)


On 17.03.2014 22:39, Animesh Chaturvedi wrote:

Edison

Thanks for taking care of this issue. Nux can you try with this fix
and I will go off building RC


Animesh, can you also pull in the patches Jayapal wrote to fix the 
ipset issue?


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

Thanks!
Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

Re: orchestrateTakeVolumeSnapshot Call

2014-03-18 Thread SuichII, Christopher

Ah, yes. Now seeing this snippet I can explain the issue.

So, during "orchestrateTakeVolumeSnapshot(work.getVolumeId(), 
work.getPolicyId(), work.getSnapshotId(), account, work.isQuiesceVm());” if an 
exception is thrown, it is caught and ignored by 
VolumeServiceImpl.takeSnapshot(VolumeInfo):

@Override
public SnapshotInfo takeSnapshot(VolumeInfo volume) {
SnapshotInfo snapshot = null;
try {
snapshot = snapshotMgr.takeSnapshot(volume);
} catch (Exception e) {
s_logger.debug("Take snapshot: " + volume.getId() + " failed", e);
}

return snapshot;
}

So, "return new Pair(JobInfo.Status.SUCCEEDED,  
_jobMgr.marshallResultObject(work.getSnapshotId()));” will return 
JobInfo.Status.SUCCEEDED even when an exception was thrown.

That said, I’m now getting a warning that 
VolumeApiServiceImpl.orchestrateTakeVolumeSnapshot(VmWorkTakeVolumeSnapshot) is 
never called, so I’m not sure if this method trace has changed since I reported 
the issue.

(FYI, I’ve copied this info into the ticket as well)

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

On Mar 18, 2014, at 9:11 AM, Alex Hitchins 
mailto:alex.hitch...@shapeblue.com>> wrote:

All,

I'm looking at the following issue[0]. The reporter says in the second sentence 
the method is always returning success even when an exception occurs or 
otherwise fails. Looking at the code, if the inside call to 
orchestrateTakeVolumeSnapshot raises an exception, it should bubble up and not 
return the SUCCEEDED message surely?


   private Pair 
orchestrateTakeVolumeSnapshot(VmWorkTakeVolumeSnapshot work) throws Exception {
   Account account = _accountDao.findById(work.getAccountId());
   orchestrateTakeVolumeSnapshot(work.getVolumeId(), work.getPolicyId(), 
work.getSnapshotId(),
   account, work.isQuiesceVm());
   return new Pair(JobInfo.Status.SUCCEEDED,
   _jobMgr.marshallResultObject(work.getSnapshotId()));
   }

[0] https://issues.apache.org/jira/browse/CLOUDSTACK-5825
Need Enterprise Grade Support for Apache CloudStack?
Our CloudStack Infrastructure 
Support offers the 
best 24/7 SLA for CloudStack Environments.

Apache CloudStack Bootcamp training courses

**NEW!** CloudStack 4.2.1 training
18th-19th February 2014, Brazil. 
Classroom
17th-23rd March 2014, Region A. Instructor led, 
On-line
24th-28th March 2014, Region B. Instructor led, 
On-line
16th-20th June 2014, Region A. Instructor led, 
On-line
23rd-27th June 2014, Region B. Instructor led, 
On-line

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: Cloudstack documentation

On Mar 18, 2014, at 3:02 PM, Pierre-Luc Dion  wrote:

> Thanks Wido,
> 
> Cool, look like the rtd version is in there too.  so I guest we need a lot
> of work on conversion from publican to RST?

It' already done :) I'd be mean I would tell you to search the mailing list :) 

If you search the cloudstack mirrors on github:
https://github.com/orgs/apache?query=cloudstack

you will see four documentation repo.
cloudstack-docs
cloudstack-docs-rn (release notes)
cloudstack-docs-admin (the admin guide)
cloudstack-docs-install (the installation guide)

the rn, admin and installation guide are pure rest, and are a conversion of the 
publican to .rst. there is still work to do, especially on the admin guide.

These docs are pushed automatically to readthedocs.org and provide:

http://apache-cloudstack-release-notes.readthedocs.org/en/latest/
http://cloudstack-installation.readthedocs.org/en/latest/
http://cloudstack-administration.readthedocs.org/en/latest/
http://docs.cloudstack.apache.org

I am actively working on cleaning this up and fixing the URLs/CNAMEs.

The easiest way to contribute is *really* to visit the RTD sites and click on 
the "edit on github" button, this will automatically fork the repo in your 
github account.
You can then submit a pull request. It will send a notification on dev@ list 
and we can merge it.

There is still lots of work to do, both on the formatting (the conversion was 
not perfect) and the content of course.

Have at it, I'd be delighted to merge your patches :)

-sebastien

> 
> 
> 
> 
> Pierre-Luc Dion
> Architecte de Solution Cloud | Cloud Solutions Architect
> 514-447-3456, 1101
> - - -
> 
> *CloudOps*420 rue Guy
> Montréal QC  H3J 1S6
> www.cloudops.com
> @CloudOps_
> 
> 
> On Tue, Mar 18, 2014 at 9:15 AM, Wido den Hollander  wrote:
> 
>> On 03/18/2014 02:08 PM, Pierre-Luc Dion wrote:
>> 
>>> Hi all,
>>> 
>>> I would like to know where we can get newer version of documentation for
>>> Cloudstack. Look like the documentation site is not updated since 4.2.0. I
>>> know that the documentation system will change, is their any information
>>> about it somewhere?
>>> 
>>> 
>> Yes, it moved to it's own repository: https://git-wip-us.apache.org/
>> repos/asf?p=cloudstack-docs.git
>> 
>> $ git clone https://git-wip-us.apache.org/repos/asf/cloudstack-docs.git
>> 
>> From there you can probably build the docs yourself. Be aware that we are
>> moving to RST.
>> 
>> 
>> Also, I would like to contribute as well.
>>> 
>>> 
>> Patches are always welcome!
>> 
>> Thanks,
>>> 
>>> Pierre-Luc Dion
>>> Architecte de Solution Cloud | Cloud Solutions Architect
>>> - - -
>>> 
>>> *CloudOps*420 rue Guy
>>> 
>>> Montréal QC  H3J 1S6
>>> www.cloudops.com
>>> @CloudOps_
>>> 
>>> 
>>

RE: orchestrateTakeVolumeSnapshot Call

Thanks for the information Chris,

I can check for the returned null to decide if the snapshot took place. 
Concerning that you are getting reports of it being orphaned though.


Regards

Alex Hitchins

D: +44 1892 523 587 | S: +44 2036 030 540 | M: +44 7788 423 969

alex.hitch...@shapeblue.com

-Original Message-
From: SuichII, Christopher [mailto:chris.su...@netapp.com]
Sent: 18 March 2014 14:08
To: dev
Subject: Re: orchestrateTakeVolumeSnapshot Call

Ah, yes. Now seeing this snippet I can explain the issue.

So, during "orchestrateTakeVolumeSnapshot(work.getVolumeId(), 
work.getPolicyId(), work.getSnapshotId(), account, work.isQuiesceVm());" if an 
exception is thrown, it is caught and ignored by 
VolumeServiceImpl.takeSnapshot(VolumeInfo):

@Override
public SnapshotInfo takeSnapshot(VolumeInfo volume) {
SnapshotInfo snapshot = null;
try {
snapshot = snapshotMgr.takeSnapshot(volume);
} catch (Exception e) {
s_logger.debug("Take snapshot: " + volume.getId() + " failed", e);
}

return snapshot;
}

So, "return new Pair(JobInfo.Status.SUCCEEDED,  
_jobMgr.marshallResultObject(work.getSnapshotId()));" will return 
JobInfo.Status.SUCCEEDED even when an exception was thrown.

That said, I'm now getting a warning that 
VolumeApiServiceImpl.orchestrateTakeVolumeSnapshot(VmWorkTakeVolumeSnapshot) is 
never called, so I'm not sure if this method trace has changed since I reported 
the issue.

(FYI, I've copied this info into the ticket as well)

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

On Mar 18, 2014, at 9:11 AM, Alex Hitchins 
mailto:alex.hitch...@shapeblue.com>> wrote:

All,

I'm looking at the following issue[0]. The reporter says in the second sentence 
the method is always returning success even when an exception occurs or 
otherwise fails. Looking at the code, if the inside call to 
orchestrateTakeVolumeSnapshot raises an exception, it should bubble up and not 
return the SUCCEEDED message surely?


   private Pair 
orchestrateTakeVolumeSnapshot(VmWorkTakeVolumeSnapshot work) throws Exception {
   Account account = _accountDao.findById(work.getAccountId());
   orchestrateTakeVolumeSnapshot(work.getVolumeId(), work.getPolicyId(), 
work.getSnapshotId(),
   account, work.isQuiesceVm());
   return new Pair(JobInfo.Status.SUCCEEDED,
   _jobMgr.marshallResultObject(work.getSnapshotId()));
   }

[0] https://issues.apache.org/jira/browse/CLOUDSTACK-5825
Need Enterprise Grade Support for Apache CloudStack?
Our CloudStack Infrastructure 
Support offers the 
best 24/7 SLA for CloudStack Environments.

Apache CloudStack Bootcamp training courses

**NEW!** CloudStack 4.2.1 training
18th-19th February 2014, Brazil. 
Classroom
17th-23rd March 2014, Region A. Instructor led, 
On-line
24th-28th March 2014, Region B. Instructor led, 
On-line
16th-20th June 2014, Region A. Instructor led, 
On-line
23rd-27th June 2014, Region B. Instructor led, 
On-line

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.

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 i

Re: [REMINDER] Review Request 18677: CLOUDSTACK-3272

2014-03-18 Thread Nitin Mehta

Thanks Sonal. I understand the requirement but not the use case where this
is needed, so was curious.

-Nitin

On 18/03/14 3:03 AM, "Sonal Ojha"  wrote:

>Hello Nitin,
>
>There was a requirement to control the publishing of events on the
>messaging queue as opposed to how it is currently. At present, all events
>by default gets published over the queue. The idea was to have control
>over
>the types of events being published in the queue not necessarily as a
>matter of performance.
>
>Kindly refer https://issues.apache.org/jira/browse/CLOUDSTACK-3272 for
>more
>details.
>
>-Sonal
>
>
>On Tue, Mar 18, 2014 at 11:12 AM, Nitin Mehta
>wrote:
>
>> Can you please explain why would one want to restrict publishing certain
>> kind of events ? Performance ?
>>
>> On 17/03/14 9:44 PM, "Sonal Ojha"  wrote:
>>
>> >Any updates?
>> >
>> >
>> >On Mon, Mar 10, 2014 at 10:01 AM, Sonal Ojha 
>> >wrote:
>> >
>> >> Kindly let me know your review comments.
>> >>
>> >> -- Forwarded message --
>> >> From: Sonal Ojha 
>> >> Date: Tue, Mar 4, 2014 at 11:20 AM
>> >> Subject: Re: Review Request 18677: CLOUDSTACK-3272
>> >> To: Sonal Ojha , cloudstack <
>> >> dev@cloudstack.apache.org>
>> >>
>> >>
>> >>This is an automatically generated e-mail. To reply, visit:
>> >> https://reviews.apache.org/r/18677/
>> >>
>> >> - Sonal Ojha
>> >>
>> >> On March 3rd, 2014, 5:58 a.m. UTC, Sonal Ojha wrote:
>> >>Review request for cloudstack.
>> >> By Sonal Ojha.
>> >>
>> >> *Updated March 3, 2014, 5:58 a.m.*
>> >>  *Repository: * cloudstack-git
>> >> Description
>> >>
>> >> At present, there are multiple event types that are generated by CS,
>> >>action events,usage events, resource state change events and alerts.
>> >>Current problem is
>> >> all the events gets published on the event bus when event bus is
>> >>enabled. Intent is to introduce global setting config parameters to
>> >>specify which category of events to be published or not be published
>>on
>> >>the event bus.
>> >>
>> >>   Testing
>> >>
>> >> Successfully tested publishing / not publishing of various events
>>based
>> >>on the global parameter publish.*.events.
>> >>
>> >>   Diffs
>> >>
>> >>-
>> 
plugins/event-bus/rabbitmq/src/org/apache/cloudstack/mom/rabbitmq/Rabbi
tM
>> >>QEventBus.java
>> >>(478c8d7)
>> >>- server/src/com/cloud/configuration/Config.java (2d55f46)
>> >>- server/src/com/cloud/test/DatabaseConfig.java (9370218)
>> >>
>> >> View Diff 
>> >>
>> >>
>> >>
>> >> --
>> >>
>> >> Regards,
>> >>
>> >> ___
>> >>
>> >> *Sonal Ojha* ● Senior Engineer - Product Developement ● SunGard
>> >> Availability Services, India ● Mobile: +91 9922412645●  Email:
>> >> sonal.o...@sungard.com ● Website: http://www.sungardas.in/
>> >>
>> >> 8 Times Winner – BC Service Provider of the Year – 2011, 2010, 2009,
>> >>2006,
>> >> 2005, 2002, 2000, 1999; Finalist – 2008, 2007, 2004, 2001 ●
>>Excellence
>> >>in
>> >> Infrastructure Management – 2010 ● Outstanding Excellence in Business
>> >> Continuity – 2008 ● Business Continuity Provider of the Year (BCM
>> >> Service) – 2013 BCI Global Awards ● Business Continuity Provider of
>>the
>> >> Year (BCM Product) – 2013 BCI India Awards
>> >>
>> >> *[image: AS_yt]* *[image:
>> >> AS_twitter]* *[image:
>> >>AS_in]**[image:
>> >> AS_gplus]* *[image:
>> >> AS_fb]* *[image:
>> >>AS_ss]*
>> >>
>> >
>> >
>> >
>> >--
>> >
>> >Regards,
>> >
>> >___
>> >
>> >*Sonal Ojha* ● Senior Engineer - Product Developement ● SunGard
>> >Availability Services, India ● Mobile: +91 9922412645●  Email:
>> >sonal.o...@sungard.com ● Website: http://www.sungardas.in/
>> >
>> >8 Times Winner – BC Service Provider of the Year – 2011, 2010, 2009,
>>2006,
>> >2005, 2002, 2000, 1999; Finalist – 2008, 2007, 2004, 2001 ● Excellence
>>in
>> >Infrastructure Management – 2010 ● Outstanding Excellence in Business
>> >Continuity – 2008 ● Business Continuity Provider of the Year (BCM
>>Service)
>> >– 2013 BCI Global Awards ● Business Continuity Provider of the Year
>>(BCM
>> >Product) – 2013 BCI India Awards
>> >
>> >*[image: AS_yt]* *[image:
>> >AS_twitter]* *[image:
>> >AS_in]**[image:
>> >AS_gplus]* *[image:
>> >AS_fb]**[image:
>> >AS_ss]* 
>>
>>
>
>
>-- 
>
>Regards,
>
>___
>
>*Sonal Ojha* ● Senior Engineer - Product Developement ● SunGard
>Availability Services, I

Re: IAM guidelines for CS APIs

2014-03-18 Thread David Grizzanti

Min,

Thanks for the overview.  Will take a look at this and starting reviewing with 
the team here to see where we can contribute.

What's the best way to contribute our code back for a feature like this?  So 
far for anything I've been working on, I've created reviews on Review Board 
with patches that are linked to a Jira (mostly bugs). Should we create a 
private fork, work on our changes and then raise a review for each item?

Thanks!

-- 
David Grizzanti
Software Engineer
Sungard Availability Services
e: david.grizza...@sungard.com
w: 215.446.1431
c: 570.575.0315

On March 17, 2014 at 2:18:15 PM, Min Chen (min.c...@citrix.com) wrote:

Hi David,  

Thanks a lot for your interest and willing to help on this feature. For  
the Phase I work laid out in  
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Identity+  
and+Access+Management+%28IAM%29+Plugin, we have pretty much completed most  
of implementations and merged into 4.4 branch. The major items left for  
this feature are:  
1) Add more automated marvin test cases. We have added test_vm_iam marvin  
test for VM under new IAM model, but we need more coverage on most other  
entity types to make sure that there are not much regressions.  
2) As mentioned in the FS, for this release, creating a custom  
policy/group is supported through API only. For further releases, we can  
provide either a UI or a config file + policy language mechanism to  
facilitate the custom policy/group creation. If you have enough bandwidth  
to develop a simple utility to read from JSON-like policy/group  
configuration file to ease custom policy/group creation, that would be  
very beneficial to people who are interested in this feature. UI work is  
currently planned for 4.5.  
3) Phase I work has only built the foundation for us to provide true IAM  
services for CloudStack resources. But we haven't had time to modify all  
existing CloudStack hard-coded RBAC logics to integrate with this new IAM  
model, which are planned for Phase II and include the following 3 aspects:  
- Eliminate the need for shared and isolated networks  
- Modify dedicated resource feature to use new IAM model.  
- Handle IAM control on such non ControlledEntity like Domain and Service  
Offering(Disk offering, Network Offering). In Phase I, our current  
implementation has handled all ControlledEntity. These Non controlled  
entities are still using the old logic as before.  


Thanks  
-min  

On 3/17/14 10:57 AM, "David Grizzanti"  wrote:  

>Hi Prachi,  
>  
>I've been loosely following the work you've been doing with regard to the  
>IAM enhancements. We've been having some discussions recently regarding a  
>better access control model to CloudStack at SunGard for upcoming  
>requirements we have. I didn't realize until today that the work was this  
>close to being complete!  
>  
>From looking over the documentation you provided, this feature looks  
>great.  
>I was curious if everything you set out to accomplish that is discussed  
>here  
>https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Identity  
>+and+Access+Management+%28IAM%29+Pluginwas  
>completed? Otherwise, are there any outstanding items that you think  
>you need help with? We have some developers here who are looking to start  
>contributing. If there are no major items, even something like unit tests  
>for this feature could work.  
>  
>Thanks!  
>  
>  
>On Fri, Mar 14, 2014 at 7:32 PM, Prachi Damle  
>wrote:  
>  
>> Hi there,  
>>  
>> With the introduction of the IAM feature, there are some new  
>> annotations/mechanisms to implement access control at CS API and Service  
>> layer.  
>>  
>> Min and I have documented guidelines to follow while adding APIs to  
>> CloudStack:  
>>  
>>  
>>https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+IAM+gui  
>>delines+for+API+and+Service+Layer  
>>  
>>  
>> If you are adding a new API or modifying an existing one, please refer  
>> this document to know:  
>>  
>> - How to set API permissions  
>>  
>> - How to use annotations for specifying correct entity  
>> permissions in CUD APIs  
>>  
>> - How to write list API's  
>>  
>> - How to support Response View Separation for API Commands  
>>  
>>  
>> Thank you,  
>> Prachi  
>>  
>  
>  
>  
>--  
>David Grizzanti  
>Software Engineer  
>Sungard Availability Services  
>  
>e: david.grizza...@sungard.com  
>w: 215.446.1431  
>c: 570.575.0315

Re: Cloudstack documentation

2014-03-18 Thread Pierre-Luc Dion

Thanks Sebastien,


Seams quite complete! Is there a reason why doc url on
http://cloudstack.apache.org/ still point to the old doc ?



Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
514-447-3456, 1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_


On Tue, Mar 18, 2014 at 10:16 AM, sebgoa  wrote:

>
> On Mar 18, 2014, at 3:02 PM, Pierre-Luc Dion  wrote:
>
> > Thanks Wido,
> >
> > Cool, look like the rtd version is in there too.  so I guest we need a
> lot
> > of work on conversion from publican to RST?
>
> It' already done :) I'd be mean I would tell you to search the mailing
> list :)
>
> If you search the cloudstack mirrors on github:
> https://github.com/orgs/apache?query=cloudstack
>
> you will see four documentation repo.
> cloudstack-docs
> cloudstack-docs-rn (release notes)
> cloudstack-docs-admin (the admin guide)
> cloudstack-docs-install (the installation guide)
>
> the rn, admin and installation guide are pure rest, and are a conversion
> of the publican to .rst. there is still work to do, especially on the admin
> guide.
>
> These docs are pushed automatically to readthedocs.org and provide:
>
> http://apache-cloudstack-release-notes.readthedocs.org/en/latest/
> http://cloudstack-installation.readthedocs.org/en/latest/
> http://cloudstack-administration.readthedocs.org/en/latest/
> http://docs.cloudstack.apache.org
>
> I am actively working on cleaning this up and fixing the URLs/CNAMEs.
>
> The easiest way to contribute is *really* to visit the RTD sites and click
> on the "edit on github" button, this will automatically fork the repo in
> your github account.
> You can then submit a pull request. It will send a notification on dev@list 
> and we can merge it.
>
> There is still lots of work to do, both on the formatting (the conversion
> was not perfect) and the content of course.
>
> Have at it, I'd be delighted to merge your patches :)
>
> -sebastien
>
> >
> >
> >
> >
> > Pierre-Luc Dion
> > Architecte de Solution Cloud | Cloud Solutions Architect
> > 514-447-3456, 1101
> > - - -
> >
> > *CloudOps*420 rue Guy
> > Montréal QC  H3J 1S6
> > www.cloudops.com
> > @CloudOps_
> >
> >
> > On Tue, Mar 18, 2014 at 9:15 AM, Wido den Hollander 
> wrote:
> >
> >> On 03/18/2014 02:08 PM, Pierre-Luc Dion wrote:
> >>
> >>> Hi all,
> >>>
> >>> I would like to know where we can get newer version of documentation
> for
> >>> Cloudstack. Look like the documentation site is not updated since
> 4.2.0. I
> >>> know that the documentation system will change, is their any
> information
> >>> about it somewhere?
> >>>
> >>>
> >> Yes, it moved to it's own repository: https://git-wip-us.apache.org/
> >> repos/asf?p=cloudstack-docs.git
> >>
> >> $ git clone https://git-wip-us.apache.org/repos/asf/cloudstack-docs.git
> >>
> >> From there you can probably build the docs yourself. Be aware that we
> are
> >> moving to RST.
> >>
> >>
> >> Also, I would like to contribute as well.
> >>>
> >>>
> >> Patches are always welcome!
> >>
> >> Thanks,
> >>>
> >>> Pierre-Luc Dion
> >>> Architecte de Solution Cloud | Cloud Solutions Architect
> >>> - - -
> >>>
> >>> *CloudOps*420 rue Guy
> >>>
> >>> Montréal QC  H3J 1S6
> >>> www.cloudops.com
> >>> @CloudOps_
> >>>
> >>>
> >>
>
>

Re: Cloudstack documentation


On Mar 18, 2014, at 3:50 PM, Pierre-Luc Dion  wrote:

> Thanks Sebastien,
> 
> 
> Seams quite complete! Is there a reason why doc url on
> http://cloudstack.apache.org/ still point to the old doc ?

My plan is to make the switch once 4.3 is out.

There is still some cleaning up to do on the .rst/RTD stuff which would be nice 
to fix before making it official.

Also, we might have to vote on docs releases…haven't touched that one yet :)

-sebastien

> 
> 
> 
> Pierre-Luc Dion
> Architecte de Solution Cloud | Cloud Solutions Architect
> 514-447-3456, 1101
> - - -
> 
> *CloudOps*420 rue Guy
> Montréal QC  H3J 1S6
> www.cloudops.com
> @CloudOps_
> 
> 
> On Tue, Mar 18, 2014 at 10:16 AM, sebgoa  wrote:
> 
>> 
>> On Mar 18, 2014, at 3:02 PM, Pierre-Luc Dion  wrote:
>> 
>>> Thanks Wido,
>>> 
>>> Cool, look like the rtd version is in there too.  so I guest we need a
>> lot
>>> of work on conversion from publican to RST?
>> 
>> It' already done :) I'd be mean I would tell you to search the mailing
>> list :)
>> 
>> If you search the cloudstack mirrors on github:
>> https://github.com/orgs/apache?query=cloudstack
>> 
>> you will see four documentation repo.
>> cloudstack-docs
>> cloudstack-docs-rn (release notes)
>> cloudstack-docs-admin (the admin guide)
>> cloudstack-docs-install (the installation guide)
>> 
>> the rn, admin and installation guide are pure rest, and are a conversion
>> of the publican to .rst. there is still work to do, especially on the admin
>> guide.
>> 
>> These docs are pushed automatically to readthedocs.org and provide:
>> 
>> http://apache-cloudstack-release-notes.readthedocs.org/en/latest/
>> http://cloudstack-installation.readthedocs.org/en/latest/
>> http://cloudstack-administration.readthedocs.org/en/latest/
>> http://docs.cloudstack.apache.org
>> 
>> I am actively working on cleaning this up and fixing the URLs/CNAMEs.
>> 
>> The easiest way to contribute is *really* to visit the RTD sites and click
>> on the "edit on github" button, this will automatically fork the repo in
>> your github account.
>> You can then submit a pull request. It will send a notification on dev@list 
>> and we can merge it.
>> 
>> There is still lots of work to do, both on the formatting (the conversion
>> was not perfect) and the content of course.
>> 
>> Have at it, I'd be delighted to merge your patches :)
>> 
>> -sebastien
>> 
>>> 
>>> 
>>> 
>>> 
>>> Pierre-Luc Dion
>>> Architecte de Solution Cloud | Cloud Solutions Architect
>>> 514-447-3456, 1101
>>> - - -
>>> 
>>> *CloudOps*420 rue Guy
>>> Montréal QC  H3J 1S6
>>> www.cloudops.com
>>> @CloudOps_
>>> 
>>> 
>>> On Tue, Mar 18, 2014 at 9:15 AM, Wido den Hollander 
>> wrote:
>>> 
 On 03/18/2014 02:08 PM, Pierre-Luc Dion wrote:
 
> Hi all,
> 
> I would like to know where we can get newer version of documentation
>> for
> Cloudstack. Look like the documentation site is not updated since
>> 4.2.0. I
> know that the documentation system will change, is their any
>> information
> about it somewhere?
> 
> 
 Yes, it moved to it's own repository: https://git-wip-us.apache.org/
 repos/asf?p=cloudstack-docs.git
 
 $ git clone https://git-wip-us.apache.org/repos/asf/cloudstack-docs.git
 
 From there you can probably build the docs yourself. Be aware that we
>> are
 moving to RST.
 
 
 Also, I would like to contribute as well.
> 
> 
 Patches are always welcome!
 
 Thanks,
> 
> Pierre-Luc Dion
> Architecte de Solution Cloud | Cloud Solutions Architect
> - - -
> 
> *CloudOps*420 rue Guy
> 
> Montréal QC  H3J 1S6
> www.cloudops.com
> @CloudOps_
> 
> 
 
>> 
>>

[PROPOSAL] Support pure Xen as a hypervisor

2014-03-18 Thread Tim Mackey

Historically CloudStack has used Xen and XenServer interchangeably to refer
to any XenAPI based implementation.  With the recent release of Xen Project
4.4 (http://blog.xen.org/index.php/2014/03/10/xen-4-4-released/), and
interest in alternate architectures like ARM, the loose definition of our
Xen support could be confusing.  In this two part effort I propose that
CloudStack 4.4 be cleansed to ensure that all Xen references become
XenServer references, and second that an alternate hypervisor type of
"XenProject" be introduced for pure Xen which could either support libvirt
or  libxl (preference for libvirt given the 4.4 work to improve the
interface and broader support for libvirt in general).

Cross posted to users to for broader comment.

-tim

RE: orchestrateTakeVolumeSnapshot Call

Just a note to say I've got the fix in testing. Even if it's not used, if it's 
still in the code it should at least work. Dangerous to have something saying 
it's worked when it hasn't.


Regards

Alex Hitchins

D: +44 1892 523 587 | S: +44 2036 030 540 | M: +44 7788 423 969

alex.hitch...@shapeblue.com

-Original Message-
From: Alex Hitchins [mailto:alex.hitch...@shapeblue.com]
Sent: 18 March 2014 14:21
To: dev@cloudstack.apache.org
Subject: RE: orchestrateTakeVolumeSnapshot Call

Thanks for the information Chris,

I can check for the returned null to decide if the snapshot took place. 
Concerning that you are getting reports of it being orphaned though.


Regards

Alex Hitchins

D: +44 1892 523 587 | S: +44 2036 030 540 | M: +44 7788 423 969

alex.hitch...@shapeblue.com

-Original Message-
From: SuichII, Christopher [mailto:chris.su...@netapp.com]
Sent: 18 March 2014 14:08
To: dev
Subject: Re: orchestrateTakeVolumeSnapshot Call

Ah, yes. Now seeing this snippet I can explain the issue.

So, during "orchestrateTakeVolumeSnapshot(work.getVolumeId(), 
work.getPolicyId(), work.getSnapshotId(), account, work.isQuiesceVm());" if an 
exception is thrown, it is caught and ignored by 
VolumeServiceImpl.takeSnapshot(VolumeInfo):

@Override
public SnapshotInfo takeSnapshot(VolumeInfo volume) {
SnapshotInfo snapshot = null;
try {
snapshot = snapshotMgr.takeSnapshot(volume);
} catch (Exception e) {
s_logger.debug("Take snapshot: " + volume.getId() + " failed", e);
}

return snapshot;
}

So, "return new Pair(JobInfo.Status.SUCCEEDED,  
_jobMgr.marshallResultObject(work.getSnapshotId()));" will return 
JobInfo.Status.SUCCEEDED even when an exception was thrown.

That said, I'm now getting a warning that 
VolumeApiServiceImpl.orchestrateTakeVolumeSnapshot(VmWorkTakeVolumeSnapshot) is 
never called, so I'm not sure if this method trace has changed since I reported 
the issue.

(FYI, I've copied this info into the ticket as well)

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

On Mar 18, 2014, at 9:11 AM, Alex Hitchins 
mailto:alex.hitch...@shapeblue.com>> wrote:

All,

I'm looking at the following issue[0]. The reporter says in the second sentence 
the method is always returning success even when an exception occurs or 
otherwise fails. Looking at the code, if the inside call to 
orchestrateTakeVolumeSnapshot raises an exception, it should bubble up and not 
return the SUCCEEDED message surely?


   private Pair 
orchestrateTakeVolumeSnapshot(VmWorkTakeVolumeSnapshot work) throws Exception {
   Account account = _accountDao.findById(work.getAccountId());
   orchestrateTakeVolumeSnapshot(work.getVolumeId(), work.getPolicyId(), 
work.getSnapshotId(),
   account, work.isQuiesceVm());
   return new Pair(JobInfo.Status.SUCCEEDED,
   _jobMgr.marshallResultObject(work.getSnapshotId()));
   }

[0] https://issues.apache.org/jira/browse/CLOUDSTACK-5825
Need Enterprise Grade Support for Apache CloudStack?
Our CloudStack Infrastructure 
Support offers the 
best 24/7 SLA for CloudStack Environments.

Apache CloudStack Bootcamp training courses

**NEW!** CloudStack 4.2.1 training
18th-19th February 2014, Brazil. 
Classroom
17th-23rd March 2014, Region A. Instructor led, 
On-line
24th-28th March 2014, Region B. Instructor led, 
On-line
16th-20th June 2014, Region A. Instructor led, 
On-line
23rd-27th June 2014, Region B. Instructor led, 
On-line

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.

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 B

Re: CloudStack implementations

2014-03-18 Thread Marcus

I think its critical. It's difficult for me to pitch CloudStack as a
solution if I have no stats to show what's possible or how much of a
userbase it has. It would have been nice to have that yesterday. I
think in the past year things have gone backward in this regard, as
there used to at least be a list of contributing vendors somewhere
that I can no longer find. I wonder perhaps if that's due in part to
migration to the ASF. I think it will be hard to stay relevant if it's
difficult for the average IT person to get a sense of how active the
community is by visiting the site.

On Tue, Mar 18, 2014 at 7:06 AM, Rohit Yadav  wrote:
> Cool idea, we can also have a monkey-brag ACS plugin which gives users an
> API which can be triggered via cloudmonkey cli tool or by some gui/button
> on the frontend to submit stats anonymously to our servers.
>
> Cheers.
>
>
> On Tue, Mar 18, 2014 at 4:45 PM, Wido den Hollander  wrote:
>
>> On 03/18/2014 12:07 PM, Marcus wrote:
>>
>>> Do we have any general stats on how cloudstack is being used? Common
>>> deployment sizes, largest deployments, etc? I'm curious as to how far
>>> people have actually scaled it in real deployments, although I realize
>>> that
>>> the info can be proprietary.
>>>
>>>
>> Recently at the Ceph project the tool "ceph-brag" was developed. It
>> gathers information about your Ceph deployment and sends back the
>> information to the project.
>>
>> Something like this might be nice (opt-in!!) for CloudStack. It can
>> anonymously report things like:
>> - Number of Instances
>> - Number of pods, cluster, hosts
>> - Number of Primary Storage and their type
>> - Basic / Advanced Networking
>>
>> This could all be written into one JSON file which we can submit back to
>> the project.
>>
>> With this we would get more information about how CloudStack is used.
>>
>> Obviously, the code will be Open Source so people can see how we gather
>> the information (probably a lot of SQL selects..) and how we submit it to
>> our servers.
>>
>> Is that something what you would like?
>>
>> Wido
>>

Re: CloudStack implementations

2014-03-18 Thread SuichII, Christopher

I was thinking something along the same lines. The current API & UI plugin 
frameworks would allow for an optional plugin which can be added to any 
deployment post-install. It could allow for configurable reporting so that 
users can decide what information is acceptable to report. If we can get the 
infrastructure set up, it could even allow for reporting of actions in real 
time, such as when new hosts are added, how many instances are brought up per 
week, etc.

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

On Mar 18, 2014, at 9:06 AM, Rohit Yadav  wrote:

> Cool idea, we can also have a monkey-brag ACS plugin which gives users an
> API which can be triggered via cloudmonkey cli tool or by some gui/button
> on the frontend to submit stats anonymously to our servers.
> 
> Cheers.
> 
> 
> On Tue, Mar 18, 2014 at 4:45 PM, Wido den Hollander  wrote:
> 
>> On 03/18/2014 12:07 PM, Marcus wrote:
>> 
>>> Do we have any general stats on how cloudstack is being used? Common
>>> deployment sizes, largest deployments, etc? I'm curious as to how far
>>> people have actually scaled it in real deployments, although I realize
>>> that
>>> the info can be proprietary.
>>> 
>>> 
>> Recently at the Ceph project the tool "ceph-brag" was developed. It
>> gathers information about your Ceph deployment and sends back the
>> information to the project.
>> 
>> Something like this might be nice (opt-in!!) for CloudStack. It can
>> anonymously report things like:
>> - Number of Instances
>> - Number of pods, cluster, hosts
>> - Number of Primary Storage and their type
>> - Basic / Advanced Networking
>> 
>> This could all be written into one JSON file which we can submit back to
>> the project.
>> 
>> With this we would get more information about how CloudStack is used.
>> 
>> Obviously, the code will be Open Source so people can see how we gather
>> the information (probably a lot of SQL selects..) and how we submit it to
>> our servers.
>> 
>> Is that something what you would like?
>> 
>> Wido
>>

Re: [MERGE] resize-root branch

Thanks
-min

On 3/17/14 10:39 PM, "Marcus"  wrote:

>This commit in 4.4 should fix it (cherry picked to master as well):
>
>commit 8eed3c5113d1141be820077e121db802566faec6
>Author: Marcus Sorensen 
>Date:   Fri Mar 14 07:13:34 2014 -0600
>
>Change newly added details map for deployVirtualMachine to an empty
>map, instead of passing all possible keys as empty values
>
>diff --git a/tools/marvin/marvin/integration/lib/base.py
>b/tools/marvin/marvin/integration/lib/base.py
>index ca9f2b4..38e8568 100755
>--- a/tools/marvin/marvin/integration/lib/base.py
>+++ b/tools/marvin/marvin/integration/lib/base.py
>@@ -413,7 +413,7 @@ class VirtualMachine:
> if "userdata" in services:
> cmd.userdata = base64.urlsafe_b64encode(services["userdata"])
>
>-cmd.details = [{"cpuNumber":
>"","cpuSpeed":"","memory":"","rootdisksize":""}]
>+cmd.details = [{}]
>
> if customcpunumber:
> cmd.details[0]["cpuNumber"] = customcpunumber
>
>On Mon, Mar 17, 2014 at 11:26 PM, Marcus  wrote:
>> Looks like all of the items in 'details' are getting added to the API
>> call as empty params:
>>
>> GET 
>>/client/api?domainid=7193957c-ab53-11e3-a79c-000c29d82947&zoneid=bfc93d0d
>>-9531-4648-9d04-ca1f47fcd5a6&apiKey=8d6jxAVly_B6asBBjuL5S5bxXzNhx3CyiPLCJ
>>Q7Qa4hti3HLlQQkP-x-ayenmO6t8vfZt5nDRHixsJc7XKdIGA&details%5B0%5D.rootdisk
>>size=&serviceofferingid=80bc069b-8283-4357-a995-e429d34b65d6&displayname=
>>Test+VM&signature=fHopjtezyTNYP2zPU4rHySxt%2FnM%3D&details%5B0%5D.cpuNumb
>>er=&templateid=719528ec-ab53-11e3-a79c-000c29d82947&response=json&details
>>%5B0%5D.memory=&account=test-TestDeployVM-test_deploy_vm_multiple-QTF0VD&
>>name=testvm&details%5B0%5D.cpuSpeed=&command=deployVirtualMachine&hypervi
>>sor=kvm
>> HTTP/1.1
>>
>> I've changed the default details map to be empty, instead of defining
>> all possible details as having empty strings as the original commit
>> did. Testing now and will commit if it works. I hope it doesn't break
>> *their* tests...
>>
>> commit 3f7b628c707cd9c30542efd670416be5fbb473f0
>> Author: Gaurav Aradhye 
>> Date:   Fri Feb 28 01:46:24 2014 -0500
>>
>> CLOUDSTACK-6147: Adding first set of test caess for Dynamic
>> Compute Offering feature
>>
>> Signed-off-by: SrikanteswaraRao Talluri 
>>
>>
>> On Mon, Mar 17, 2014 at 11:01 PM, Marcus  wrote:
>>> I'll take a look. I wasn't the one who added the details map to
>>> base.py, although I did add to it and can probably figure out what's
>>> wrong. The original commit didn't change any deployVirtualMachine
>>> calls. Can you give me an example of a test that is faling? Is it
>>> test_deploy_vm.py?
>>>
>>> On Mon, Mar 17, 2014 at 5:43 PM, Min Chen  wrote:
 Hi Marcus,

 I found an issue with this merge, my previous marvin test is
broken in
 deployVirtualMachine if no rootdisksize is passed. All previous marvin
 tests are written without passing this parameter. Can you take a look
at
 base.py to make sure that old marvin tests without passing those
custom
 parameters are still working fine?

 Thanks
 -min

 On 3/11/14 1:17 PM, "Marcus"  wrote:

>I'd like to merge the resize-root branch for the requested feature of
>being able to resize root volumes. I have pulled from master and
>tested.
>
>I should note that this feature is affected by an existing bug in
>master that was introduced recently, breaking the existing data disk
>resize feature on Ubuntu 12.04 + stock libvirt, but has otherwise been
>tested to work with Ubuntu 12.04 + recent libvirt and CentOS 6.4,6.5.
>We are discussing how to proceed with that separate issue on-list.
>
>Integration tests were added for deploy in a new file
>"test_deploy_vm_root_resize.py" and existing resize tests were
>extended to root volumes in the existing test_volumes.py.
>
>Findbugs indicates there are no new issues introduced (220/220), as
>reported by running the following on both master and resize-root. This
>was just my stab in the dark at trying to make sense of the output in
>absence of familiarity with findbugs:
>
># mvn -P enablefindbugs verify
># find . -name findbugs.xml -exec xmllint --format {} \; | grep -c
>BugInstance
>
>FS:
>https://cwiki.apache.org/confluence/display/CLOUDSTACK/Root+Resize+Sup
>port
>JIRA: https://issues.apache.org/jira/browse/CLOUDSTACK-6181

Re: [MERGE] resize-root branch

Yes, that is the root cause for the failure.

Thanks
-min

On 3/17/14 10:26 PM, "Marcus"  wrote:

>Looks like all of the items in 'details' are getting added to the API
>call as empty params:
>
>GET 
>/client/api?domainid=7193957c-ab53-11e3-a79c-000c29d82947&zoneid=bfc93d0d-
>9531-4648-9d04-ca1f47fcd5a6&apiKey=8d6jxAVly_B6asBBjuL5S5bxXzNhx3CyiPLCJQ7
>Qa4hti3HLlQQkP-x-ayenmO6t8vfZt5nDRHixsJc7XKdIGA&details%5B0%5D.rootdisksiz
>e=&serviceofferingid=80bc069b-8283-4357-a995-e429d34b65d6&displayname=Test
>+VM&signature=fHopjtezyTNYP2zPU4rHySxt%2FnM%3D&details%5B0%5D.cpuNumber=&t
>emplateid=719528ec-ab53-11e3-a79c-000c29d82947&response=json&details%5B0%5
>D.memory=&account=test-TestDeployVM-test_deploy_vm_multiple-QTF0VD&name=te
>stvm&details%5B0%5D.cpuSpeed=&command=deployVirtualMachine&hypervisor=kvm
>HTTP/1.1
>
>I've changed the default details map to be empty, instead of defining
>all possible details as having empty strings as the original commit
>did. Testing now and will commit if it works. I hope it doesn't break
>*their* tests...
>
>commit 3f7b628c707cd9c30542efd670416be5fbb473f0
>Author: Gaurav Aradhye 
>Date:   Fri Feb 28 01:46:24 2014 -0500
>
>CLOUDSTACK-6147: Adding first set of test caess for Dynamic
>Compute Offering feature
>
>Signed-off-by: SrikanteswaraRao Talluri 
>
>
>On Mon, Mar 17, 2014 at 11:01 PM, Marcus  wrote:
>> I'll take a look. I wasn't the one who added the details map to
>> base.py, although I did add to it and can probably figure out what's
>> wrong. The original commit didn't change any deployVirtualMachine
>> calls. Can you give me an example of a test that is faling? Is it
>> test_deploy_vm.py?
>>
>> On Mon, Mar 17, 2014 at 5:43 PM, Min Chen  wrote:
>>> Hi Marcus,
>>>
>>> I found an issue with this merge, my previous marvin test is
>>>broken in
>>> deployVirtualMachine if no rootdisksize is passed. All previous marvin
>>> tests are written without passing this parameter. Can you take a look
>>>at
>>> base.py to make sure that old marvin tests without passing those custom
>>> parameters are still working fine?
>>>
>>> Thanks
>>> -min
>>>
>>> On 3/11/14 1:17 PM, "Marcus"  wrote:
>>>
I'd like to merge the resize-root branch for the requested feature of
being able to resize root volumes. I have pulled from master and
tested.

I should note that this feature is affected by an existing bug in
master that was introduced recently, breaking the existing data disk
resize feature on Ubuntu 12.04 + stock libvirt, but has otherwise been
tested to work with Ubuntu 12.04 + recent libvirt and CentOS 6.4,6.5.
We are discussing how to proceed with that separate issue on-list.

Integration tests were added for deploy in a new file
"test_deploy_vm_root_resize.py" and existing resize tests were
extended to root volumes in the existing test_volumes.py.

Findbugs indicates there are no new issues introduced (220/220), as
reported by running the following on both master and resize-root. This
was just my stab in the dark at trying to make sense of the output in
absence of familiarity with findbugs:

# mvn -P enablefindbugs verify
# find . -name findbugs.xml -exec xmllint --format {} \; | grep -c
BugInstance

FS:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Root+Resize+Supp
ort
JIRA: https://issues.apache.org/jira/browse/CLOUDSTACK-6181
>>>

Re: IAM guidelines for CS APIs

Review board with patches that are linked to JIRA  should be the right way to 
go. Do let us know what you are going to work on to avoid overlapping.

Thanks
-min

From: David Grizzanti 
mailto:david.grizza...@sungard.com>>
Date: Tuesday, March 18, 2014 7:46 AM
To: Min Chen mailto:min.c...@citrix.com>>, 
"dev@cloudstack.apache.org" 
mailto:dev@cloudstack.apache.org>>, Prachi Damle 
mailto:prachi.da...@citrix.com>>
Subject: Re: IAM guidelines for CS APIs

Min,

Thanks for the overview.  Will take a look at this and starting reviewing with 
the team here to see where we can contribute.

What's the best way to contribute our code back for a feature like this?  So 
far for anything I've been working on, I've created reviews on Review Board 
with patches that are linked to a Jira (mostly bugs). Should we create a 
private fork, work on our changes and then raise a review for each item?

Thanks!

--
David Grizzanti
Software Engineer
Sungard Availability Services
e: david.grizza...@sungard.com
w: 215.446.1431
c: 570.575.0315


On March 17, 2014 at 2:18:15 PM, Min Chen 
(min.c...@citrix.com) wrote:

Hi David,

Thanks a lot for your interest and willing to help on this feature. For
the Phase I work laid out in
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Identity+
and+Access+Management+%28IAM%29+Plugin, we have pretty much completed most
of implementations and merged into 4.4 branch. The major items left for
this feature are:
1) Add more automated marvin test cases. We have added test_vm_iam marvin
test for VM under new IAM model, but we need more coverage on most other
entity types to make sure that there are not much regressions.
2) As mentioned in the FS, for this release, creating a custom
policy/group is supported through API only. For further releases, we can
provide either a UI or a config file + policy language mechanism to
facilitate the custom policy/group creation. If you have enough bandwidth
to develop a simple utility to read from JSON-like policy/group
configuration file to ease custom policy/group creation, that would be
very beneficial to people who are interested in this feature. UI work is
currently planned for 4.5.
3) Phase I work has only built the foundation for us to provide true IAM
services for CloudStack resources. But we haven't had time to modify all
existing CloudStack hard-coded RBAC logics to integrate with this new IAM
model, which are planned for Phase II and include the following 3 aspects:
- Eliminate the need for shared and isolated networks
- Modify dedicated resource feature to use new IAM model.
- Handle IAM control on such non ControlledEntity like Domain and Service
Offering(Disk offering, Network Offering). In Phase I, our current
implementation has handled all ControlledEntity. These Non controlled
entities are still using the old logic as before.


Thanks
-min

On 3/17/14 10:57 AM, "David Grizzanti" 
mailto:david.grizza...@sungard.com>> wrote:

>Hi Prachi,
>
>I've been loosely following the work you've been doing with regard to the
>IAM enhancements. We've been having some discussions recently regarding a
>better access control model to CloudStack at SunGard for upcoming
>requirements we have. I didn't realize until today that the work was this
>close to being complete!
>
>From looking over the documentation you provided, this feature looks
>great.
>I was curious if everything you set out to accomplish that is discussed
>here
>https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Identity
>+and+Access+Management+%28IAM%29+Pluginwas
>completed? Otherwise, are there any outstanding items that you think
>you need help with? We have some developers here who are looking to start
>contributing. If there are no major items, even something like unit tests
>for this feature could work.
>
>Thanks!
>
>
>On Fri, Mar 14, 2014 at 7:32 PM, Prachi Damle
>mailto:prachi.da...@citrix.com>>wrote:
>
>> Hi there,
>>
>> With the introduction of the IAM feature, there are some new
>> annotations/mechanisms to implement access control at CS API and Service
>> layer.
>>
>> Min and I have documented guidelines to follow while adding APIs to
>> CloudStack:
>>
>>
>>https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+IAM+gui
>>delines+for+API+and+Service+Layer
>>
>>
>> If you are adding a new API or modifying an existing one, please refer
>> this document to know:
>>
>> - How to set API permissions
>>
>> - How to use annotations for specifying correct entity
>> permissions in CUD APIs
>>
>> - How to write list API's
>>
>> - How to support Response View Separation for API Commands
>>
>>
>> Thank you,
>> Prachi
>>
>
>
>
>--
>David Grizzanti
>Software Engineer
>Sungard Availability Services
>
>e: david.grizza...@sungard.com
>w: 215.446.1431
>c: 570.575.0315

RE: [PROPOSAL] Support pure Xen as a hypervisor

2014-03-18 Thread Stephen Turner

+1. I find it confusing that "Xen" is used for XenServer rather than 
XenProject, and I think it would be good to be explicit about which we mean in 
each case.

-- 
Stephen Turner


-Original Message-
From: Tim Mackey [mailto:tmac...@gmail.com] 
Sent: 18 March 2014 15:40
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: [PROPOSAL] Support pure Xen as a hypervisor

Historically CloudStack has used Xen and XenServer interchangeably to refer to 
any XenAPI based implementation.  With the recent release of Xen Project
4.4 (http://blog.xen.org/index.php/2014/03/10/xen-4-4-released/), and interest 
in alternate architectures like ARM, the loose definition of our Xen support 
could be confusing.  In this two part effort I propose that CloudStack 4.4 be 
cleansed to ensure that all Xen references become XenServer references, and 
second that an alternate hypervisor type of "XenProject" be introduced for pure 
Xen which could either support libvirt or  libxl (preference for libvirt given 
the 4.4 work to improve the interface and broader support for libvirt in 
general).

Cross posted to users to for broader comment.

-tim

Re: [PROPOSAL] Support pure Xen as a hypervisor


On Mar 18, 2014, at 4:40 PM, Tim Mackey  wrote:

> Historically CloudStack has used Xen and XenServer interchangeably to refer
> to any XenAPI based implementation.  With the recent release of Xen Project
> 4.4 (http://blog.xen.org/index.php/2014/03/10/xen-4-4-released/), and
> interest in alternate architectures like ARM, the loose definition of our
> Xen support could be confusing.  In this two part effort I propose that
> CloudStack 4.4 be cleansed to ensure that all Xen references become
> XenServer references, and second that an alternate hypervisor type of
> "XenProject" be introduced for pure Xen which could either support libvirt
> or  libxl (preference for libvirt given the 4.4 work to improve the
> interface and broader support for libvirt in general).
> 

+1 in general, I am not sure what would be best between libvirt and libxl 
though.

but as you know there might be a quick path to reuse the KVM agent and use 
libvirt to interact with xenproject

> Cross posted to users to for broader comment.
> 
> -tim

Re: Review Request 18964: Windowsfication of CloudStack Management Server - Changes to support windows OS

2014-03-18 Thread Damodar Reddy Talakanti



> On March 14, 2014, 12:14 p.m., Damodar Reddy Talakanti wrote:
> > Hi Daan
> > 
> > I have updated the FS in wiki regarding how to build and install using this 
> > code. The link to FS is
> > 
> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Cloudstack+Windowsfication#CloudstackWindowsfication-Installer
> >
> 
> Donal Lafferty wrote:
> Hi Damodar,
> 
> Other reviews may differ in opinion, but IMHO manual setup steps have to 
> be documented precisely and in a form that other contributors can improve.  
> An excellent example is at 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Setting+up+a+CloudStack+dev+environment+on+Windows
>   An example of where this level of detail is required is the "Seed 
> SystemTemplate".  
> 
> WRT testing, if would be highly unusual to claim Windows 2k12 R2 support 
> without having tried it in that environment.  Have you tried reaching to the 
> community for help verify your install steps on a Win2K12 R2?
> 
> WRT accepting the code in this review, why not narrow the scope of the 
> submission.  The code above seems only to relate to Windows install for the 
> management server, but the title implies that all details of Windows support 
> will be covered.  Rather than commit a half-finished feature, why not break 
> windowsfication into a series of narrowly defined features.  You can then 
> make incremental submissions.
> 
> DL
>

Hi Donal,

 We planned to do this in 2 phases. In the first phase we put changes to be 
able to start and use management server on windows. We will pick up seed 
template part and VMware related stuff in the second phase.

I had tested on windows 2008 server. I will put a mail in the community to get 
tested on the 2012 server. Till that time I will change the FS probably.

Definitely I will try to improve the FS to cover as much as possible in detail.


- Damodar Reddy


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


On March 18, 2014, 1:46 p.m., Damodar Reddy Talakanti wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/18964/
> ---
> 
> (Updated March 18, 2014, 1:46 p.m.)
> 
> 
> Review request for cloudstack, Abhinandan Prateek, Chiradeep Vittal, daan 
> Hoogland, and Donal Lafferty.
> 
> 
> Bugs: https://issues.apache.org/jira/browse/CLOUDSTACK-6105
> 
> https://issues.apache.org/jira/browse/https://issues.apache.org/jira/browse/CLOUDSTACK-6105
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Windowsfication of CloudStack Management Server
> 
> 
> Diffs
> -
> 
>   scripts/installer/windows/acs.wxs PRE-CREATION 
>   scripts/installer/windows/client.wxs PRE-CREATION 
>   scripts/installer/windows/start.bat PRE-CREATION 
>   scripts/vm/systemvm/injectkeys.py PRE-CREATION 
>   server/src/com/cloud/server/ConfigurationServerImpl.java b8da4c8 
>   server/test/com/cloud/server/ConfigurationServerImplTest.java 08a2097 
> 
> Diff: https://reviews.apache.org/r/18964/diff/
> 
> 
> Testing
> ---
> 
> Tested in Linux environment after changes 
> Also tested in Windows environment(For now tested on windows-8) to make sure 
> it is getting installed and management service is running.
> 
> Able to add zones, able to register templates, able to launch a VM when it is 
> running on windows.
> 
> Currently though it is getting added as a windows service, not able to start 
> the service through windows service control manager which I am looking into 
> currently. When run .exe file which is installed then server is getting up 
> and able to access cloud stack UI. 
> 
> For now The following assumptions are made:
> 1. SSH keys are already installed
> 2. JAVA is already installed
> 3. tomcat is already installed
> 
> This patch contains the following new files related to WiX tool (To compile 
> and run we need this tool)
> 1. acs.wxs
> The following command will be used to compile
>   "\bin\candle.exe" acs.wxs
> 2. client.wxs
> The following command will be used to generate the above file
>   "\bin\heat" dir client -gg -cg Test  -ke -sfrag 
> -template fragment -out client.wxs  -var wix.SourceClient -dr WEBAPPS
> The following command will be used to compile the above generated file
>   "\bin\candle.exe" client.wxs
> 3. The following command will be used to generate .msi file
>   "\bin\light.exe" acs.wixobj client.wixobj -out 
> acs.msi  -ext "C:\Program Files (x86)\WiX Toolset 
> v3.8\bin\WixUIExtension.dll" -dSourceClient=SourceDir\client
> 
> 
> Thanks,
> 
> Damodar Reddy Talakanti
> 
>

Re: [PROPOSAL] Support pure Xen as a hypervisor


On 18.03.2014 16:48, sebgoa wrote:

+1 in general, I am not sure what would be best between libvirt and
libxl though.

but as you know there might be a quick path to reuse the KVM agent
and use libvirt to interact with xenproject


+1 XenProject
+1 Reuse KVM/libvirt agent

Good ideas! :)

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

RE: CloudStack implementations

+1 on this tool.

Regards

Alex Hitchins

D: +44 1892 523 587 | S: +44 2036 030 540 | M: +44 7788 423 969

alex.hitch...@shapeblue.com

-Original Message-
From: Wido den Hollander [mailto:w...@widodh.nl]
Sent: 18 March 2014 11:16
To: dev@cloudstack.apache.org
Subject: Re: CloudStack implementations

On 03/18/2014 12:07 PM, Marcus wrote:
> Do we have any general stats on how cloudstack is being used? Common
> deployment sizes, largest deployments, etc? I'm curious as to how far
> people have actually scaled it in real deployments, although I realize
> that the info can be proprietary.
>

Recently at the Ceph project the tool "ceph-brag" was developed. It gathers 
information about your Ceph deployment and sends back the information to the 
project.

Something like this might be nice (opt-in!!) for CloudStack. It can anonymously 
report things like:
- Number of Instances
- Number of pods, cluster, hosts
- Number of Primary Storage and their type
- Basic / Advanced Networking

This could all be written into one JSON file which we can submit back to the 
project.

With this we would get more information about how CloudStack is used.

Obviously, the code will be Open Source so people can see how we gather the 
information (probably a lot of SQL selects..) and how we submit it to our 
servers.

Is that something what you would like?

Wido
Need Enterprise Grade Support for Apache CloudStack?
Our CloudStack Infrastructure 
Support offers the 
best 24/7 SLA for CloudStack Environments.

Apache CloudStack Bootcamp training courses

**NEW!** CloudStack 4.2.1 training
18th-19th February 2014, Brazil. 
Classroom
17th-23rd March 2014, Region A. Instructor led, 
On-line
24th-28th March 2014, Region B. Instructor led, 
On-line
16th-20th June 2014, Region A. Instructor led, 
On-line
23rd-27th June 2014, Region B. Instructor led, 
On-line

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: CloudStack implementations


On 18.03.2014 11:07, Marcus wrote:

Do we have any general stats on how cloudstack is being used? Common
deployment sizes, largest deployments, etc? I'm curious as to how far
people have actually scaled it in real deployments, although I realize 
that

the info can be proprietary.


(copying same message from users@)

That's a very good question. A good indicator might be similar stats 
from Openstack:

https://twitter.com/cdaffara/status/438700618975154176/photo/1

I realise there are some large deployments out there, but I suspect 
most installations are quite "modest", i.e. "VPS" level.


Lucian


--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

RE: [VOTE] Apache CloudStack 4.3.0 (eighth round)

2014-03-18 Thread Florin Dumitrascu

Hi,

I am trying to create an advanced zone using RC8, but I am blocked even from 
the first steps.
As seen in the attached image, I cannot select the Hypervisor type from the 
drop down box.
Has anyone else seen this behaviour ?

Thanks,
Florin





-Original Message-
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
Sent: Thursday, March 13, 2014 12:27 AM
To: dev@cloudstack.apache.org
Subject: [VOTE] Apache CloudStack 4.3.0 (eighth round)

Hi All,



I've created a 4.3.0 release, with the following artifacts up for a

vote:





Git Branch and Commit SH:

https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.3
Commit: 6a6ec648099553a42f830dcd566eab2452428908



List of changes:

New Features in 4.3: https://issues.apache.org/jira/issues/?filter=12325248

Improvement in 4.3: https://issues.apache.org/jira/issues/?filter=12325249

Issues fixed in 4.3 https://issues.apache.org/jira/issues/?filter=12326161

Known Issues in 4.3: https://issues.apache.org/jira/issues/?filter=12326162







Source release (checksums and signatures are available at the same

location):

https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/



PGP release keys (signed using 94BE0D7C):

https://dist.apache.org/repos/dist/release/cloudstack/KEYS



Testing instructions are here:

https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure



Vote will be open for 72 hours (Monday evening PST 5:30 PM)



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)



Thanks

Animesh



IMPORTANT NOTE: The information in this e-mail (and any attachments) is 
confidential. The contents may not be disclosed or used by anyone other than 
the addressee. If you are not the intended recipient, please notify the sender 
immediately or telephone: +353 (0)1 6204700. We cannot accept any 
responsibility for the accuracy or completeness of this message as it has been 
transmitted over a public network. If you suspect that the message may have 
been intercepted or amended, please call the sender.

RE: [VOTE] Apache CloudStack 4.3.0 (eighth round)

2014-03-18 Thread Florin Dumitrascu

Apologies for the missing link. Screenshot of the GUI bug is here:

http://imgur.com/FL9OnY0

Thanks,
Florin


-Original Message-
From: Florin Dumitrascu [mailto:florin.dumitra...@intunenetworks.com]
Sent: Tuesday, March 18, 2014 5:11 PM
To: dev@cloudstack.apache.org
Subject: RE: [VOTE] Apache CloudStack 4.3.0 (eighth round)

Hi,

I am trying to create an advanced zone using RC8, but I am blocked even from 
the first steps.
As seen in the attached image, I cannot select the Hypervisor type from the 
drop down box.
Has anyone else seen this behaviour ?

Thanks,
Florin





-Original Message-
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
Sent: Thursday, March 13, 2014 12:27 AM
To: dev@cloudstack.apache.org
Subject: [VOTE] Apache CloudStack 4.3.0 (eighth round)

Hi All,



I've created a 4.3.0 release, with the following artifacts up for a

vote:





Git Branch and Commit SH:

https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.3
Commit: 6a6ec648099553a42f830dcd566eab2452428908



List of changes:

New Features in 4.3: https://issues.apache.org/jira/issues/?filter=12325248

Improvement in 4.3: https://issues.apache.org/jira/issues/?filter=12325249

Issues fixed in 4.3 https://issues.apache.org/jira/issues/?filter=12326161

Known Issues in 4.3: https://issues.apache.org/jira/issues/?filter=12326162







Source release (checksums and signatures are available at the same

location):

https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/



PGP release keys (signed using 94BE0D7C):

https://dist.apache.org/repos/dist/release/cloudstack/KEYS



Testing instructions are here:

https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure



Vote will be open for 72 hours (Monday evening PST 5:30 PM)



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)



Thanks

Animesh



IMPORTANT NOTE: The information in this e-mail (and any attachments) is 
confidential. The contents may not be disclosed or used by anyone other than 
the addressee. If you are not the intended recipient, please notify the sender 
immediately or telephone: +353 (0)1 6204700. We cannot accept any 
responsibility for the accuracy or completeness of this message as it has been 
transmitted over a public network. If you suspect that the message may have 
been intercepted or amended, please call the sender.


IMPORTANT NOTE: The information in this e-mail (and any attachments) is 
confidential. The contents may not be disclosed or used by anyone other than 
the addressee. If you are not the intended recipient, please notify the sender 
immediately or telephone: +353 (0)1 6204700. We cannot accept any 
responsibility for the accuracy or completeness of this message as it has been 
transmitted over a public network. If you suspect that the message may have 
been intercepted or amended, please call the sender.

Re: [VOTE] Apache CloudStack 4.3.0 (eighth round)

Florin, can you check the output of the following DB query:

Select * from configuration where name="hypervisor.list"



On 3/18/14, 10:17 AM, "Florin Dumitrascu"
 wrote:

>Apologies for the missing link. Screenshot of the GUI bug is here:
>
>http://imgur.com/FL9OnY0
>
>Thanks,
>Florin
>
>
>-Original Message-
>From: Florin Dumitrascu [mailto:florin.dumitra...@intunenetworks.com]
>Sent: Tuesday, March 18, 2014 5:11 PM
>To: dev@cloudstack.apache.org
>Subject: RE: [VOTE] Apache CloudStack 4.3.0 (eighth round)
>
>Hi,
>
>I am trying to create an advanced zone using RC8, but I am blocked even
>from the first steps.
>As seen in the attached image, I cannot select the Hypervisor type from
>the drop down box.
>Has anyone else seen this behaviour ?
>
>Thanks,
>Florin
>
>
>
>
>
>-Original Message-
>From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
>Sent: Thursday, March 13, 2014 12:27 AM
>To: dev@cloudstack.apache.org
>Subject: [VOTE] Apache CloudStack 4.3.0 (eighth round)
>
>Hi All,
>
>
>
>I've created a 4.3.0 release, with the following artifacts up for a
>
>vote:
>
>
>
>
>
>Git Branch and Commit SH:
>
>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs
>/heads/4.3
>Commit: 6a6ec648099553a42f830dcd566eab2452428908
>
>
>
>List of changes:
>
>New Features in 4.3:
>https://issues.apache.org/jira/issues/?filter=12325248
>
>Improvement in 4.3: https://issues.apache.org/jira/issues/?filter=12325249
>
>Issues fixed in 4.3 https://issues.apache.org/jira/issues/?filter=12326161
>
>Known Issues in 4.3:
>https://issues.apache.org/jira/issues/?filter=12326162
>
>
>
>
>
>
>
>Source release (checksums and signatures are available at the same
>
>location):
>
>https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/
>
>
>
>PGP release keys (signed using 94BE0D7C):
>
>https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
>
>
>Testing instructions are here:
>
>https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+proced
>ure
>
>
>
>Vote will be open for 72 hours (Monday evening PST 5:30 PM)
>
>
>
>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)
>
>
>
>Thanks
>
>Animesh
>
>
>
>IMPORTANT NOTE: The information in this e-mail (and any attachments) is
>confidential. The contents may not be disclosed or used by anyone other
>than the addressee. If you are not the intended recipient, please notify
>the sender immediately or telephone: +353 (0)1 6204700. We cannot accept
>any responsibility for the accuracy or completeness of this message as it
>has been transmitted over a public network. If you suspect that the
>message may have been intercepted or amended, please call the sender.
>
>
>IMPORTANT NOTE: The information in this e-mail (and any attachments) is
>confidential. The contents may not be disclosed or used by anyone other
>than the addressee. If you are not the intended recipient, please notify
>the sender immediately or telephone: +353 (0)1 6204700. We cannot accept
>any responsibility for the accuracy or completeness of this message as it
>has been transmitted over a public network. If you suspect that the
>message may have been intercepted or amended, please call the sender.

RE: [VOTE] Apache CloudStack 4.3.0 (eighth round)

2014-03-18 Thread Florin Dumitrascu

Hi Alena,

Actually I just had a quick look at the management server logs and I see this 
error. MySQL server is running, so not sure what is causing it:

2014-03-18 17:37:12,453 ERROR [c.c.u.d.Merovingian2] (main:null) Unable to get 
a new db connection
com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Could not 
create connection to database server. Attempted reconnect 3 times. Giving up.



-Original Message-
From: Alena Prokharchyk [mailto:alena.prokharc...@citrix.com]
Sent: Tuesday, March 18, 2014 5:40 PM
To: dev@cloudstack.apache.org; Florin Dumitrascu
Subject: Re: [VOTE] Apache CloudStack 4.3.0 (eighth round)

Florin, can you check the output of the following DB query:

Select * from configuration where name="hypervisor.list"



On 3/18/14, 10:17 AM, "Florin Dumitrascu"
 wrote:

>Apologies for the missing link. Screenshot of the GUI bug is here:
>
>http://imgur.com/FL9OnY0
>
>Thanks,
>Florin
>
>
>-Original Message-
>From: Florin Dumitrascu [mailto:florin.dumitra...@intunenetworks.com]
>Sent: Tuesday, March 18, 2014 5:11 PM
>To: dev@cloudstack.apache.org
>Subject: RE: [VOTE] Apache CloudStack 4.3.0 (eighth round)
>
>Hi,
>
>I am trying to create an advanced zone using RC8, but I am blocked even
>from the first steps.
>As seen in the attached image, I cannot select the Hypervisor type from
>the drop down box.
>Has anyone else seen this behaviour ?
>
>Thanks,
>Florin
>
>
>
>
>
>-Original Message-
>From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
>Sent: Thursday, March 13, 2014 12:27 AM
>To: dev@cloudstack.apache.org
>Subject: [VOTE] Apache CloudStack 4.3.0 (eighth round)
>
>Hi All,
>
>
>
>I've created a 4.3.0 release, with the following artifacts up for a
>
>vote:
>
>
>
>
>
>Git Branch and Commit SH:
>
>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=r
>efs
>/heads/4.3
>Commit: 6a6ec648099553a42f830dcd566eab2452428908
>
>
>
>List of changes:
>
>New Features in 4.3:
>https://issues.apache.org/jira/issues/?filter=12325248
>
>Improvement in 4.3:
>https://issues.apache.org/jira/issues/?filter=12325249
>
>Issues fixed in 4.3
>https://issues.apache.org/jira/issues/?filter=12326161
>
>Known Issues in 4.3:
>https://issues.apache.org/jira/issues/?filter=12326162
>
>
>
>
>
>
>
>Source release (checksums and signatures are available at the same
>
>location):
>
>https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/
>
>
>
>PGP release keys (signed using 94BE0D7C):
>
>https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
>
>
>Testing instructions are here:
>
>https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+pro
>ced
>ure
>
>
>
>Vote will be open for 72 hours (Monday evening PST 5:30 PM)
>
>
>
>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)
>
>
>
>Thanks
>
>Animesh
>
>
>
>IMPORTANT NOTE: The information in this e-mail (and any attachments) is
>confidential. The contents may not be disclosed or used by anyone other
>than the addressee. If you are not the intended recipient, please
>notify the sender immediately or telephone: +353 (0)1 6204700. We
>cannot accept any responsibility for the accuracy or completeness of
>this message as it has been transmitted over a public network. If you
>suspect that the message may have been intercepted or amended, please call the 
>sender.
>
>
>IMPORTANT NOTE: The information in this e-mail (and any attachments) is
>confidential. The contents may not be disclosed or used by anyone other
>than the addressee. If you are not the intended recipient, please
>notify the sender immediately or telephone: +353 (0)1 6204700. We
>cannot accept any responsibility for the accuracy or completeness of
>this message as it has been transmitted over a public network. If you
>suspect that the message may have been intercepted or amended, please call the 
>sender.


IMPORTANT NOTE: The information in this e-mail (and any attachments) is 
confidential. The contents may not be disclosed or used by anyone other than 
the addressee. If you are not the intended recipient, please notify the sender 
immediately or telephone: +353 (0)1 6204700. We cannot accept any 
responsibility for the accuracy or completeness of this message as it has been 
transmitted over a public network. If you suspect that the message may have 
been intercepted or amended, please call the sender.

Re: Review Request 19062: Per contrail implementation, CS ingress policy mapping: rule cidr should be mapped to src net, dst net is 'local' i.e same as 'guest network' on which rule is applied

2014-03-18 Thread Sheng Yang


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

Ship it!


Ship It!

- Sheng Yang


On March 11, 2014, 7:42 p.m., Suresh Balineni wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/19062/
> ---
> 
> (Updated March 11, 2014, 7:42 p.m.)
> 
> 
> Review request for cloudstack.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Fix for ACL ingress rule mapping to Contrail Network policy implementation.
> 
> Per contrail implementation, CS ingress policy mapping: rule cidr should be 
> mapped to src net, dst net is 'local' i.e same as 'guest network' on which 
> rule is applied
> 
> 
> Diffs
> -
> 
>   
> plugins/network-elements/juniper-contrail/src/org/apache/cloudstack/network/contrail/model/NetworkPolicyModel.java
>  3092cad 
> 
> Diff: https://reviews.apache.org/r/19062/diff/
> 
> 
> Testing
> ---
> 
> verified locally.
> 
> 
> Thanks,
> 
> Suresh Balineni
> 
>

Re: Review Request 19062: Per contrail implementation, CS ingress policy mapping: rule cidr should be mapped to src net, dst net is 'local' i.e same as 'guest network' on which rule is applied

2014-03-18 Thread Sheng Yang



> On March 18, 2014, 6 p.m., Sheng Yang wrote:
> > Ship It!

Committed to MASTER.

Thanks!


- Sheng


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


On March 11, 2014, 7:42 p.m., Suresh Balineni wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/19062/
> ---
> 
> (Updated March 11, 2014, 7:42 p.m.)
> 
> 
> Review request for cloudstack.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Fix for ACL ingress rule mapping to Contrail Network policy implementation.
> 
> Per contrail implementation, CS ingress policy mapping: rule cidr should be 
> mapped to src net, dst net is 'local' i.e same as 'guest network' on which 
> rule is applied
> 
> 
> Diffs
> -
> 
>   
> plugins/network-elements/juniper-contrail/src/org/apache/cloudstack/network/contrail/model/NetworkPolicyModel.java
>  3092cad 
> 
> Diff: https://reviews.apache.org/r/19062/diff/
> 
> 
> Testing
> ---
> 
> verified locally.
> 
> 
> Thanks,
> 
> Suresh Balineni
> 
>

FW: cloudbyte storage plugin for cloudstack 4.4 and above.

2014-03-18 Thread Edison Su

Seems 4.4 branch is created already, but we(Mike and I) forgot to push 
CloudByte plugin into 4.4 branch last week, due to miscommunication between us.
Is it still ok to push cloudByte plugin into 4.4 branch? The plugin code is 
self-contained, good to add it into 4.4 branch.

From: Punith S [mailto:punit...@cloudbyte.com]
Sent: Monday, March 17, 2014 10:41 PM
To: Mike Tutkowski; Edison Su
Subject: cloudbyte storage plugin for cloudstack 4.4 and above.

hi guys,

thanks for accepting my patch before 4.4 feature freeze, and i was just curious 
to know when my plugin will be pushed to 4.4 and master cloudstack github so 
that i can sync with it.
ref - https://reviews.apache.org/r/19021/

thanks
--
regards,

punith s
cloudbyte.com

Re: CloudStack implementations

2014-03-18 Thread Marcus

If you do the math on that twitter slide, it looks like the poll
represents ~140 responses. I wonder how that poll was marketed as
opposed to Giles' 270 responses.

On Tue, Mar 18, 2014 at 11:08 AM, Nux!  wrote:
> On 18.03.2014 11:07, Marcus wrote:
>>
>> Do we have any general stats on how cloudstack is being used? Common
>> deployment sizes, largest deployments, etc? I'm curious as to how far
>> people have actually scaled it in real deployments, although I realize
>> that
>> the info can be proprietary.
>
>
> (copying same message from users@)
>
> That's a very good question. A good indicator might be similar stats from
> Openstack:
> https://twitter.com/cdaffara/status/438700618975154176/photo/1
>
> I realise there are some large deployments out there, but I suspect most
> installations are quite "modest", i.e. "VPS" level.
>
> Lucian
>
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro

Re: Review Request 18552: Internal LB support for Juniper contrail VPC implementation


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


1) Why you've decided to introduce a new provider for the Internal LB? What 
different does it make from the class its extending? I can't find anything 
different, neither in capabilities terms, nor in other behavior. Why your 
feature can't just use existing InternalLbProvider? Please update

2) If you introduce a new provider element, how are you planning to 
add/configure/stop-start it? I dont see you've introduced any new APIs for that 
matter. Adding a provider is much more than just adding the class for the 
element. Its also adding the API logic for handling all the operations. Look at 
api package, commands/internallb folder. Each element is gotta have its own set 
of APIs.




- Alena Prokharchyk


On March 12, 2014, 6:19 p.m., Suresh Balineni wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/18552/
> ---
> 
> (Updated March 12, 2014, 6:19 p.m.)
> 
> 
> Review request for cloudstack and Alena Prokharchyk.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Internal LB support for Juniper contrail VPC implementation.
> 
> - This implementation just extends the existing implementation of internal lb.
> - New element  uses juniper contrail network offering so that nics are 
> impelemented by contrail element. 
> - LB VM deployment functionality is reused (new element is extended from 
> existing Internal LB element implementation).
> 
> 
> Diffs
> -
> 
>   api/src/com/cloud/network/Network.java 6dc6752 
>   api/src/org/apache/cloudstack/api/BaseCmd.java 0e83cee 
>   plugins/network-elements/juniper-contrail/pom.xml 8c6877d 
>   
> plugins/network-elements/juniper-contrail/resources/META-INF/cloudstack/contrail/spring-contrail-context.xml
>  99ab02e 
>   
> plugins/network-elements/juniper-contrail/src/org/apache/cloudstack/network/contrail/management/ContrailInternalLbElementImpl.java
>  PRE-CREATION 
>   
> plugins/network-elements/juniper-contrail/src/org/apache/cloudstack/network/contrail/management/ContrailManagerImpl.java
>  01be7db 
>   server/src/com/cloud/network/vpc/VpcManagerImpl.java 2157eac 
> 
> Diff: https://reviews.apache.org/r/18552/diff/
> 
> 
> Testing
> ---
> 
> Tested LB VM deployment. Traffic tests are done.
> 
> 
> Thanks,
> 
> Suresh Balineni
> 
>

RE: cloudbyte storage plugin for cloudstack 4.4 and above.

2014-03-18 Thread Edison Su

I checked the patch into master branch already, if no objection, I'll merge it 
into 4.4 at the end of today.

> -Original Message-
> From: Edison Su [mailto:edison...@citrix.com]
> Sent: Tuesday, March 18, 2014 11:08 AM
> To: dev@cloudstack.apache.org
> Subject: FW: cloudbyte storage plugin for cloudstack 4.4 and above.
> 
> Seems 4.4 branch is created already, but we(Mike and I) forgot to push
> CloudByte plugin into 4.4 branch last week, due to miscommunication
> between us.
> Is it still ok to push cloudByte plugin into 4.4 branch? The plugin code is 
> self-
> contained, good to add it into 4.4 branch.
> 
> From: Punith S [mailto:punit...@cloudbyte.com]
> Sent: Monday, March 17, 2014 10:41 PM
> To: Mike Tutkowski; Edison Su
> Subject: cloudbyte storage plugin for cloudstack 4.4 and above.
> 
> hi guys,
> 
> thanks for accepting my patch before 4.4 feature freeze, and i was just
> curious to know when my plugin will be pushed to 4.4 and master cloudstack
> github so that i can sync with it.
> ref - https://reviews.apache.org/r/19021/
> 
> thanks
> --
> regards,
> 
> punith s
> cloudbyte.com

Re: Review Request 19021: Cloudbyte Elastistor storage plug-in

2014-03-18 Thread edison su


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

Ship it!


Ship It!

- edison su


On March 13, 2014, 9:16 a.m., punith s wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/19021/
> ---
> 
> (Updated March 13, 2014, 9:16 a.m.)
> 
> 
> Review request for cloudstack, edison su and Mike Tutkowski.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> This patch implements a basic storage plug-in for cloudbyte elastistor 
> v1.3.0, The plug-in is a new feature for cloudstack 4.4 and above.
> 
> this does not implement managed storage yet, it is been integrated only with 
> CreateStoragePool and DeleteStoragePool api's.
> 
> the desired behavior of the plugin are:
> 
> * Allow an Admin to create a primary storage at cluster level, hence creates 
> a volume in elastistor and gets attached to the host with the given 
> capacityiops and capacitybytes through CreateStoragePool api with provider 
> being elastistor.
> 
> *Allow an admin to delete a primary storage at cluster level, hence it 
> deletes the volume from host in cloudstack and deletes the respective volume 
> in elastistor.
> 
> * volume and datadisks fuctions performs the default storage fuctions, ie. 
> the driver extends the CloudStackPrimaryDataStoreDriverImpl.
> 
> * support for both nfs and icsci primary storage.
> 
> 
> Diffs
> -
> 
>   client/pom.xml af724b1 
>   plugins/pom.xml 097f224 
>   plugins/storage/volume/cloudbyte/pom.xml PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/resources/META-INF/cloudstack/storage-volume-cloudbyte/module.properties
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/resources/META-INF/cloudstack/storage-volume-cloudbyte/spring-storage-volume-cloudbyte-context.xml
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/driver/ElastistorPrimaryDataStoreDriver.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/lifecycle/ElastistorPrimaryDataStoreLifeCycle.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/provider/ElastistorHostListener.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/provider/ElastistorPrimaryDataStoreProvider.java
>  PRE-CREATION 
>   
> plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/util/ElastistorUtil.java
>  PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/19021/diff/
> 
> 
> Testing
> ---
> 
> Build test using, 
> 
> mvn -P developer,systemvm clean install, which is successful.
> 
> Manual testing has been performed using cloudmonkey.
> 
> * Creating a primary storage based on cloudbyte storage plugin.
> 
> cloudmonkey# create storagepool scope=cluster 
> zoneid=dac7223c-6d09-4dcb-82fb-bdecf7c657f5 
> podid=20a613c4-eccf-4fdc-b8ca-c51df483326f 
> clusterid=9a89bc12-bf00-496b-b1d8-8e92cdf1795f name=cloudbytevolume 
> provider=elastistor url=nfs://10.10.171.137/cloudbytetest capacityiops=500 
> capacitybytes=214748364800 tags=cloudbytetest
> storagepool:
> name = cloudbytevolume
> id = 57f70aa4-659b-3b53-b8ab-2f712474f107
> capacityiops = 500
> clusterid = 9a89bc12-bf00-496b-b1d8-8e92cdf1795f
> clustername = test000
> created = 2014-03-11T12:42:38+0530
> disksizeallocated = 0
> disksizetotal = 214748364800
> hypervisor = Any
> ipaddress = 10.10.171.137
> path = /cloudbytetest
> podid = 20a613c4-eccf-4fdc-b8ca-c51df483326f
> podname = test00
> scope = CLUSTER
> state = Up
> tags = cloudbytetest
> type = NetworkFilesystem
> zoneid = dac7223c-6d09-4dcb-82fb-bdecf7c657f5
> zonename = DevCloud0
> 
> * Deleting the primary storage based on cloudbyte storage plugin.
> 
> cloudmonkey# delete storagepool id=57f70aa4-659b-3b53-b8ab-2f712474f107
> success = true
> 
> * creation of primary storage with negative capacityiops throws an exception.
> 
> * creation of primary storage with already available name and ip throws an 
> exception.
> 
> * if the elastistor params which are required for plugin configuration are 
> not injected through spring-storage-volume-cloudbyte-context.xml, it can be 
> set from details map.
> 
> cloudmonkey# create storagepool scope=cluster 
> zoneid=afacc706-3f4d-4f50-82e6-bf0f82959ba8 
> podid=821ad540-6c98-43f3-935d-72a47a319b20 
> clusterid=e0ced156-532e-4941-99c0-f34ff1727544 name=nfsvol 
> provider=elastistor url=nfs://10.10.171.143/volnfs 
> details[0].esaccountid=9e9f67d5-e06f-4d63-a0b8-e7255cba84b8 
> details[1].espoolid=d2d15d11-0f06-3426-a097-3e6e8b36f85c 
> details[2].esdefaultgateway=10.10.1.1 details[3].essubnet=8  
> details[4].estntinterfac

Re: Review Request 19351: Fixed updating ipset on acquiring vm nic secondary ip for advanced SG zone


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


Jayapal, you shoudldn't rely on SG attribute of the zone. You should check if 
the SG service is supported by the network you are adding your rule to.

- Alena Prokharchyk


On March 18, 2014, 1:14 p.m., Jayapal Reddy wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/19351/
> ---
> 
> (Updated March 18, 2014, 1:14 p.m.)
> 
> 
> Review request for cloudstack, Abhinandan Prateek and edison su.
> 
> 
> Bugs: CLOUDSTACK-6240
> https://issues.apache.org/jira/browse/CLOUDSTACK-6240
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Updated adding SG rules for nic secondary ips in Advacned SG.
> 
> 
> Diffs
> -
> 
>   api/src/org/apache/cloudstack/api/command/user/vm/AddIpToVmNicCmd.java 
> b5e2239 
> 
> Diff: https://reviews.apache.org/r/19351/diff/
> 
> 
> Testing
> ---
> 
> Tested 'ipset -L' output on xenserver after acquiring secondary ip for vm nic
> 
> 
> Thanks,
> 
> Jayapal Reddy
> 
>

Re: cloudbyte storage plugin for cloudstack 4.4 and above.

2014-03-18 Thread Mike Tutkowski

Sounds good - thanks!


On Tue, Mar 18, 2014 at 12:18 PM, Edison Su  wrote:

> I checked the patch into master branch already, if no objection, I'll
> merge it into 4.4 at the end of today.
>
> > -Original Message-
> > From: Edison Su [mailto:edison...@citrix.com]
> > Sent: Tuesday, March 18, 2014 11:08 AM
> > To: dev@cloudstack.apache.org
> > Subject: FW: cloudbyte storage plugin for cloudstack 4.4 and above.
> >
> > Seems 4.4 branch is created already, but we(Mike and I) forgot to push
> > CloudByte plugin into 4.4 branch last week, due to miscommunication
> > between us.
> > Is it still ok to push cloudByte plugin into 4.4 branch? The plugin code
> is self-
> > contained, good to add it into 4.4 branch.
> >
> > From: Punith S [mailto:punit...@cloudbyte.com]
> > Sent: Monday, March 17, 2014 10:41 PM
> > To: Mike Tutkowski; Edison Su
> > Subject: cloudbyte storage plugin for cloudstack 4.4 and above.
> >
> > hi guys,
> >
> > thanks for accepting my patch before 4.4 feature freeze, and i was just
> > curious to know when my plugin will be pushed to 4.4 and master
> cloudstack
> > github so that i can sync with it.
> > ref - https://reviews.apache.org/r/19021/
> >
> > thanks
> > --
> > regards,
> >
> > punith s
> > cloudbyte.com
>



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

Re: cloudbyte storage plugin for cloudstack 4.4 and above.

2014-03-18 Thread Mike Tutkowski

It's all third-party code, so I don't see any problem checking it in the
week after feature freeze (i.e. this week).


On Tue, Mar 18, 2014 at 12:26 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> Sounds good - thanks!
>
>
> On Tue, Mar 18, 2014 at 12:18 PM, Edison Su  wrote:
>
>> I checked the patch into master branch already, if no objection, I'll
>> merge it into 4.4 at the end of today.
>>
>> > -Original Message-
>> > From: Edison Su [mailto:edison...@citrix.com]
>> > Sent: Tuesday, March 18, 2014 11:08 AM
>> > To: dev@cloudstack.apache.org
>> > Subject: FW: cloudbyte storage plugin for cloudstack 4.4 and above.
>> >
>> > Seems 4.4 branch is created already, but we(Mike and I) forgot to push
>> > CloudByte plugin into 4.4 branch last week, due to miscommunication
>> > between us.
>> > Is it still ok to push cloudByte plugin into 4.4 branch? The plugin
>> code is self-
>> > contained, good to add it into 4.4 branch.
>> >
>> > From: Punith S [mailto:punit...@cloudbyte.com]
>> > Sent: Monday, March 17, 2014 10:41 PM
>> > To: Mike Tutkowski; Edison Su
>> > Subject: cloudbyte storage plugin for cloudstack 4.4 and above.
>> >
>> > hi guys,
>> >
>> > thanks for accepting my patch before 4.4 feature freeze, and i was just
>> > curious to know when my plugin will be pushed to 4.4 and master
>> cloudstack
>> > github so that i can sync with it.
>> > ref - https://reviews.apache.org/r/19021/
>> >
>> > thanks
>> > --
>> > regards,
>> >
>> > punith s
>> > cloudbyte.com
>>
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the 
> cloud
> *(tm)*
>



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

Re: Review Request 19351: Fixed updating ipset on acquiring vm nic secondary ip for advanced SG zone


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


And the reason why you have to do so - in SG enabled Advance zone, you can have 
non-sg enabled networks. For those, the SG shouldn't be allowed to add.

- Alena Prokharchyk


On March 18, 2014, 1:14 p.m., Jayapal Reddy wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/19351/
> ---
> 
> (Updated March 18, 2014, 1:14 p.m.)
> 
> 
> Review request for cloudstack, Abhinandan Prateek and edison su.
> 
> 
> Bugs: CLOUDSTACK-6240
> https://issues.apache.org/jira/browse/CLOUDSTACK-6240
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Updated adding SG rules for nic secondary ips in Advacned SG.
> 
> 
> Diffs
> -
> 
>   api/src/org/apache/cloudstack/api/command/user/vm/AddIpToVmNicCmd.java 
> b5e2239 
> 
> Diff: https://reviews.apache.org/r/19351/diff/
> 
> 
> Testing
> ---
> 
> Tested 'ipset -L' output on xenserver after acquiring secondary ip for vm nic
> 
> 
> Thanks,
> 
> Jayapal Reddy
> 
>

Re: Review Request 19351: Fixed updating ipset on acquiring vm nic secondary ip for advanced SG zone


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


Even for the Basic zone, we should send the ipSet command on nicplug only when 
the SG is supported by the Basic zone network. Because we also support a model 
when Basic zone is deployed with SG disabled.

- Alena Prokharchyk


On March 18, 2014, 1:14 p.m., Jayapal Reddy wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/19351/
> ---
> 
> (Updated March 18, 2014, 1:14 p.m.)
> 
> 
> Review request for cloudstack, Abhinandan Prateek and edison su.
> 
> 
> Bugs: CLOUDSTACK-6240
> https://issues.apache.org/jira/browse/CLOUDSTACK-6240
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Updated adding SG rules for nic secondary ips in Advacned SG.
> 
> 
> Diffs
> -
> 
>   api/src/org/apache/cloudstack/api/command/user/vm/AddIpToVmNicCmd.java 
> b5e2239 
> 
> Diff: https://reviews.apache.org/r/19351/diff/
> 
> 
> Testing
> ---
> 
> Tested 'ipset -L' output on xenserver after acquiring secondary ip for vm nic
> 
> 
> Thanks,
> 
> Jayapal Reddy
> 
>

RE: [VOTE] Apache CloudStack 4.3.0 (eighth round)

2014-03-18 Thread Animesh Chaturvedi



> -Original Message-
> From: Nux! [mailto:n...@li.nux.ro]
> Sent: Tuesday, March 18, 2014 7:04 AM
> To: Animesh Chaturvedi
> Cc: dev@cloudstack.apache.org; Edison Su
> Subject: RE: [VOTE] Apache CloudStack 4.3.0 (eighth round)
> 
> On 17.03.2014 22:39, Animesh Chaturvedi wrote:
> > Edison
> >
> > Thanks for taking care of this issue. Nux can you try with this fix
> > and I will go off building RC
> 
> Animesh, can you also pull in the patches Jayapal wrote to fix the ipset 
> issue?
> 
> https://issues.apache.org/jira/browse/CLOUDSTACK-6240
[Animesh] Looks like that will need more work and given that there is a 
workaround we can track this for maintenance release
> 
> Thanks!
> Lucian
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro

[VOTE] Apache CloudStack 4.3.0 (ninth round)

2014-03-18 Thread Animesh Chaturvedi




Hi All,



I've created a 4.3.0 release, with the following artifacts up for a

vote:





Git Branch and Commit SH:

https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.3
Commit:  0810029f274878eca8fd74b44ab1117054e929a5


List of changes:

New Features in 4.3: https://issues.apache.org/jira/issues/?filter=12325248

Improvement in 4.3: https://issues.apache.org/jira/issues/?filter=12325249

Issues fixed in 4.3 https://issues.apache.org/jira/issues/?filter=12326161

Known Issues in 4.3: https://issues.apache.org/jira/issues/?filter=12326162







Source release (checksums and signatures are available at the same

location):

https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/



PGP release keys (signed using 94BE0D7C):

https://dist.apache.org/repos/dist/release/cloudstack/KEYS



Testing instructions are here:

https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure



Vote will be open for 72 hours (Friday 3/21 12:05 PM 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)



Thanks

Animesh

RE: Java Coding Convention Errors

2014-03-18 Thread Soheil Eizadi

Here is a proposed solution to evaluate, use the maven-checkstyle-plugin 
exclude feature to make exception for modules that have code convention to 
conform to external structures. Here is sample for my use case:

maven-checkstyle-plugin

   **/infoblox/InfobloxNetworkView.java 

-Soheil

From: Soheil Eizadi [seiz...@infoblox.com]
Sent: Tuesday, March 18, 2014 6:26 AM
To: dev@cloudstack.apache.org
Subject: RE: Java Coding Convention Errors

Here is a code fragment for serialization:

result = (T)gson.fromJson(resultString, 
TypeToken.get(newObject.getClass()).getType());

It is just generic/single handler for all generic type corresponding to the 
same raw type.

-Soheil

From: Hugo Trippaers [trip...@gmail.com]
Sent: Monday, March 17, 2014 11:30 PM
To: dev@cloudstack.apache.org
Subject: Re: Java Coding Convention Errors

Soheil,

How are these classes serialized? There are different ways to solve this like 
annotations with the serialized name or a gson policy.

Cheers,
Hugo

Sent from my iPhone

> On 18 mrt. 2014, at 03:33, Soheil Eizadi  wrote:
>
> Looks like in the new trunk we have turned on checks to enforce coding 
> conventions in Eclipse? I have errors with some classes that I need to turn 
> off:
> "Name 'is_default' must match pattern '^_?[a-zA-Z0-9]*$'."
>
> For example a declaration:
>
>private boolean is_default;
>
> These classes are part of the interface for REST communication so the strings 
> must match the corresponding JSON objects. What is the best practice to turn 
> this off in the project for a particular Class?
> -Soheil

Re: Java Coding Convention Errors

2014-03-18 Thread Hugo Trippaers

Hey Soheil,

Isn't is possible to stick to the CloudStack standards and use the 
SerializedName annotation? 
http://google-gson.googlecode.com/svn/tags/1.2.3/docs/javadocs/com/google/gson/annotations/SerializedName.html

Another option is to set a policy on gson that will automagically translate the 
java name into the underscore standard upon serialization. So isBoolean would 
become is_boolean. Look at the NiciraNvpApi, the gson policy is activated in 
the constructor.

Cheers,

Hugo

Sent from my iPhone

> On 18 mrt. 2014, at 20:34, Soheil Eizadi  wrote:
> 
> Here is a proposed solution to evaluate, use the maven-checkstyle-plugin 
> exclude feature to make exception for modules that have code convention to 
> conform to external structures. Here is sample for my use case:
> 
>maven-checkstyle-plugin
> 
>   **/infoblox/InfobloxNetworkView.java 
> 
> 
> -Soheil
> 
> From: Soheil Eizadi [seiz...@infoblox.com]
> Sent: Tuesday, March 18, 2014 6:26 AM
> To: dev@cloudstack.apache.org
> Subject: RE: Java Coding Convention Errors
> 
> Here is a code fragment for serialization:
> 
>result = (T)gson.fromJson(resultString, 
> TypeToken.get(newObject.getClass()).getType());
> 
> It is just generic/single handler for all generic type corresponding to the 
> same raw type.
> 
> -Soheil
> 
> 
> From: Hugo Trippaers [trip...@gmail.com]
> Sent: Monday, March 17, 2014 11:30 PM
> To: dev@cloudstack.apache.org
> Subject: Re: Java Coding Convention Errors
> 
> Soheil,
> 
> How are these classes serialized? There are different ways to solve this like 
> annotations with the serialized name or a gson policy.
> 
> Cheers,
> Hugo
> 
> Sent from my iPhone
> 
>> On 18 mrt. 2014, at 03:33, Soheil Eizadi  wrote:
>> 
>> Looks like in the new trunk we have turned on checks to enforce coding 
>> conventions in Eclipse? I have errors with some classes that I need to turn 
>> off:
>> "Name 'is_default' must match pattern '^_?[a-zA-Z0-9]*$'."
>> 
>> For example a declaration:
>> 
>>   private boolean is_default;
>> 
>> These classes are part of the interface for REST communication so the 
>> strings must match the corresponding JSON objects. What is the best practice 
>> to turn this off in the project for a particular Class?
>> -Soheil

Re: Anybody saw this error on master?

2014-03-18 Thread Nitin Mehta

Hi Sanjay - I still this issue popping up right after starting MS in 4.4.
You might want to check.
My XS version - 6.0.2 , commit - 30a9838

[INFO] Started Jetty Server
WARN  [c.c.h.x.r.CitrixResourceBase] (DirectAgent-6:ctx-7cd2f40f) Unable
to get GPU statsYou tried to call a method that does not exist.  The
method name that you used is echoed.
You tried to call a method that does not exist.  The method name that you
used is echoed.
at com.xensource.xenapi.Types.checkResponse(Types.java:1254)
at com.xensource.xenapi.Connection.dispatch(Connection.java:350)
at 
com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnecti
on.dispatch(XenServerConnectionPool.java:499)
at com.xensource.xenapi.GPUGroup.getEnabledVGPUTypes(GPUGroup.java:394)
at 
com.cloud.hypervisor.xen.resource.CitrixResourceBase.getGPUGroupDetails(Cit
rixResourceBase.java:1338)
at 
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResource
Base.java:2357)
at 
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixR
esourceBase.java:446)


Thanks,
-Nitin

On 14/03/14 1:05 AM, "Sanjay Tripathi"  wrote:

>I have resolved this issue under this ticket:
>https://issues.apache.org/jira/browse/CLOUDSTACK-6238
>
>--Sanjay
>
>-Original Message-
>From: Marcus [mailto:shadow...@gmail.com]
>Sent: Friday, March 14, 2014 1:09 PM
>To: dev@cloudstack.apache.org
>Cc: Sanjay Tripathi
>Subject: Re: Anybody saw this error on master?
>
>oh yes, I do remember this. We probably need to fix the null pointer, but
>I think it's more or less just noise.
>
>On Fri, Mar 14, 2014 at 1:15 AM, Marcus  wrote:
>> I see this on KVM as well. I don't recall hearing about the GPU
>> feature, sounds interesting.
>>
>> 014-03-14 01:14:06,302 DEBUG [agent.manager.AgentManagerImpl]
>> (StatsCollector-1:ctx-b3b2e81f) Details from executing class
>> com.cloud.agent.api.GetGPUStatsCommand: Unsupported command
>> issued:com.cloud.agent.api.GetGPUStatsCommand.  Are you sure you got
>> the right type of server?
>> 2014-03-14 01:14:06,302 ERROR [cloud.server.StatsCollector]
>> (StatsCollector-1:ctx-b3b2e81f) Error trying to retrieve host stats
>> java.lang.NullPointerException at
>> com.cloud.resource.ResourceManagerImpl.updateGPUDetails(ResourceManage
>> rImpl.java:2539) at
>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j
>> ava:57) at 
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
>> orImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606)
>>
>>
>>
>> On Thu, Mar 13, 2014 at 9:12 PM, Rajesh Battala
>>  wrote:
>>> Sanjay has worked on vGPU for xenserver.
>>> AFAIK, new xenserver sdk is pushed and it is required.
>>> Are you able to build latest xenserver sdk in master.
>>>
>>> Thanks
>>> Rajesh Battala
>>> -Original Message-
>>> From: Min Chen [mailto:min.c...@citrix.com]
>>> Sent: Friday, March 14, 2014 6:18 AM
>>> To: dev@cloudstack.apache.org
>>> Subject: Anybody saw this error on master?
>>>
>>> Hi there,
>>>
>>> Anybody has seen this error on master? It is not blocking, but still
>>>an eyesore to see it in the log.
>>>
>>> 2014-03-13 16:31:54,357 DEBUG [c.c.h.x.r.CitrixResourceBase]
>>> (DirectAgent-8:ctx-87d8612e) Vm cpu utilization 0.08
>>> 2014-03-13 16:31:54,357 DEBUG [c.c.h.x.r.CitrixResourceBase]
>>> (DirectAgent-8:ctx-87d8612e) Vm cpu utilization 0.06
>>> 2014-03-13 16:31:54,364 WARN  [c.c.h.x.r.CitrixResourceBase]
>>>(DirectAgent-6:ctx-6c5e0497) Unable to get GPU statsYou tried to call a
>>>method that does not exist.  The method name that you used is echoed.
>>> You tried to call a method that does not exist.  The method name that
>>>you used is echoed.
>>> at com.xensource.xenapi.Types.checkResponse(Types.java:1254)
>>> at 
>>>com.xensource.xenapi.Connection.dispatch(Connection.java:350)
>>> at 
>>>com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConne
>>>ction.dispatch(XenServerConnectionPool.java:499)
>>> at 
>>>com.xensource.xenapi.GPUGroup.getEnabledVGPUTypes(GPUGroup.java:394)
>>> at 
>>>com.cloud.hypervisor.xen.resource.CitrixResourceBase.getGPUGroupDetails(
>>>CitrixResourceBase.java:1308)
>>> at 
>>>com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResou
>>>rceBase.java:2327)
>>> at 
>>>com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(Citr
>>>ixResourceBase.java:444)
>>> at 
>>>com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(Xen
>>>Server56Resource.java:59)
>>> at 
>>>com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(Xe
>>>nServer610Resource.java:107)
>>> at 
>>>com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgent
>>>Attache.java:216)
>>> at 
>>>org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(Manag
>>>

Re: [VOTE] Apache CloudStack 4.3.0 (ninth round)

2014-03-18 Thread ilya musayev


+1 binding
On 3/18/14, 3:05 PM, Animesh Chaturvedi wrote:



Hi All,



I've created a 4.3.0 release, with the following artifacts up for a

vote:





Git Branch and Commit SH:

https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.3
Commit:  0810029f274878eca8fd74b44ab1117054e929a5


List of changes:

New Features in 4.3: https://issues.apache.org/jira/issues/?filter=12325248

Improvement in 4.3: https://issues.apache.org/jira/issues/?filter=12325249

Issues fixed in 4.3 https://issues.apache.org/jira/issues/?filter=12326161

Known Issues in 4.3: https://issues.apache.org/jira/issues/?filter=12326162







Source release (checksums and signatures are available at the same

location):

https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/



PGP release keys (signed using 94BE0D7C):

https://dist.apache.org/repos/dist/release/cloudstack/KEYS



Testing instructions are here:

https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure



Vote will be open for 72 hours (Friday 3/21 12:05 PM 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)



Thanks

Animesh

RE: [VOTE] Apache CloudStack 4.3.0 (ninth round)

2014-03-18 Thread Wilder Rodrigues

Hi there Ilya,

Could you please provide which tests cases you have covered? I would like to 
add them to my tests round as well.

Currently I'm testing multiple zones, networks, instances, ACLs, Port 
Forwarding and will add security groups. If you have more points, I would be 
glad to test them as well.

Thanks in advance.

Cheers,
Wilder

-Original Message-
From: ilya musayev [mailto:ilya.mailing.li...@gmail.com] 
Sent: Tuesday, March 18, 2014 9:11 PM
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] Apache CloudStack 4.3.0 (ninth round)

+1 binding
On 3/18/14, 3:05 PM, Animesh Chaturvedi wrote:
>
>
> Hi All,
>
>
>
> I've created a 4.3.0 release, with the following artifacts up for a
>
> vote:
>
>
>
>
>
> Git Branch and Commit SH:
>
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.3
> Commit:  0810029f274878eca8fd74b44ab1117054e929a5
>
>
> List of changes:
>
> New Features in 4.3: https://issues.apache.org/jira/issues/?filter=12325248
>
> Improvement in 4.3: https://issues.apache.org/jira/issues/?filter=12325249
>
> Issues fixed in 4.3 https://issues.apache.org/jira/issues/?filter=12326161
>
> Known Issues in 4.3: https://issues.apache.org/jira/issues/?filter=12326162
>
>
>
>
>
>
>
> Source release (checksums and signatures are available at the same
>
> location):
>
> https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/
>
>
>
> PGP release keys (signed using 94BE0D7C):
>
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
>
>
> Testing instructions are here:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure
>
>
>
> Vote will be open for 72 hours (Friday 3/21 12:05 PM 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)
>
>
>
> Thanks
>
> Animesh
>
>
>

[EVENT] CloudStack Bay Area Meetup

2014-03-18 Thread Amogh Vasekar

Hi All,

The CloudStack Bay Area meet-up is tomm, this time at NetApp! Do swing by
for a hands-on session by David Nalley. Here are the details:



Date: Wednesday, March 19th, 2014

Time: 6:00pm - 9:00pm

Details: Registration / Refreshments from 6:00pm - 6:30pm. Hands-on
CloudStack Session with David Nalley from 6:30pm - 9:00pm.

Link to event page: http://clds.co/1lx1GgN

Thanks,
Amogh

Re: upgrading from CloudPlatform 4.2.0 to CloudStack 4.3.0

2014-03-18 Thread Yichi Lu

Marcus:
Thank you for responding to me. I use XenServer. I noticed the relationship
between the vm_template::id and the directory names under
/mnt/secondary/template/tmpl/. The original installation is CloudPlatform
4.2.0, all templates are under /mnt/secondary/template/tmpl/1/. Once I upgraded it to CloudStack 4.3.0, all new registered templates
are under /mnt/secondary/template/tmpl/2/. For instance:
MariaDB [cloud]> select id,unique_name,name,type,bits,state from
vm_template where name like '%XenServer%';
+-++---+-+--+--+
| id  | unique_name| name
   | type| bits | state|
+-++---+-+--+--+
|   1 | routing-1  | SystemVM Template
(XenServer) | SYSTEM  |   32 | Active   |
|   2 | centos53-x86_64| CentOS 5.3(64-bit) no
GUI (XenServer) | BUILTIN |   64 | Inactive |
|   5 | centos56-x86_64-xen| CentOS 5.6(64-bit) no
GUI (XenServer) | BUILTIN |   64 | Active   |
| 205 | 205-2-e114251d-0eba-3b2c-9799-66253a82c365 | systemvm-xenserver-4.3
   | USER|   64 | Inactive |
| 206 | 206-2-d9dc3603-f98d-37f0-a9c6-9ce7dae6b6ad | systemvm-xenserver-4.3
   | SYSTEM  |   64 | Active   |
+-++---+-+--+--+
5 rows in set (0.00 sec)

Templates with ID's of 1, 2, 5 are under /mnt/secondary/template/tmpl/1/,
205 and 206 under /mnt/secondary/template/tmpl/2/. So there is a tight
connection, at least for XenServer, between the template id and where the
template is located.

What's interesting is the vm_instance,
MariaDB [cloud]> select
id,name,vm_template_id,guest_os_id,vm_type,hypervisor_type  from
vm_instance order by id desc;
++++-++-+
| id | name   | vm_template_id | guest_os_id | vm_type|
hypervisor_type |
++++-++-+
|  6 | cs6-2  |204 | 144 | User   |
XenServer   |
|  5 | r-5-VM |206 | 183 | DomainRouter   |
XenServer   |
|  4 | r-4-VM |206 | 183 | DomainRouter   |
XenServer   |
|  3 | cs6-1  |204 | 144 | User   |
XenServer   |
|  2 | v-2-VM |206 | 183 | ConsoleProxy   |
XenServer   |
|  1 | s-1-VM |206 | 183 | SecondaryStorageVm |
XenServer   |
++++-++-+
6 rows in set (0.00 sec)

It says s-1-VM uses vm_template id 206, which should be a 64-bit system,
but guest os id says it is a 32-bit os:
| 183 | NULL | Debian GNU/Linux 7(32-bit) |
| 184 | NULL | Debian GNU/Linux 7(64-bit) |

Eventually I was able to run ssvm with the new systemvm template, by
destroying the existing console vm and ssvm. Without destroying them, you
just get the old vms again and again.
MariaDB [cloud]> select
id,name,vm_template_id,guest_os_id,vm_type,hypervisor_type  from
vm_instance order by id desc;
++-++-++-+
| id | name| vm_template_id | guest_os_id | vm_type|
hypervisor_type |
++-++-++-+
| 15 | s-15-VM |206 | 184 | SecondaryStorageVm |
XenServer   |
| 14 | v-14-VM |206 | 184 | ConsoleProxy   |
XenServer   |
| 13 | s-13-VM |206 | 184 | SecondaryStorageVm |
XenServer   |
| 10 | cs6-5   |204 | 144 | User   |
XenServer   |
|  7 | cs6-4   |204 | 144 | User   |
XenServer   |
|  6 | cs6-2   |204 | 144 | User   |
XenServer   |
|  5 | r-5-VM  |206 | 183 | DomainRouter   |
XenServer   |
|  4 | r-4-VM  |206 | 183 | DomainRouter   |
XenServer   |
|  3 | cs6-1   |204 | 144 | User   |
XenServer   |
|  2 | v-2-VM  |206 | 183 | ConsoleProxy   |
XenServer   |
|  1 | s-1-VM  |206 | 183 | SecondaryStorageVm |
XenServer   |
++-++-++-+
11 rows in set (0.00 sec)
root@s-15-VM:~# uname -a
Linux s-15-VM 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2 x86_64 GNU/Linux


Yichi

On Tue, Mar 18, 2014 at 12:15 AM, Marcus  wrote:

> I never did get an answer as to how those upgrade instructions are supposed

Re: Review Request 19038: CLOUDSTACK-6090: Virtual Router Service Failure Alerting

2014-03-18 Thread Sheng Yang

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

core/src/com/cloud/agent/api/GetRouterAlertsAnswer.java

What's use of routerName field here? Is it the same as 
NetworkElementCommand.ROUTER_NAME?

core/src/com/cloud/agent/resource/virtualnetwork/VirtualRoutingResource.java

Put it in query command rather than here. It would demand immediate answer 
with details rather than a simple true/false answer. See GetDomRVersionCommand.

core/src/com/cloud/agent/resource/virtualnetwork/VirtualRoutingResource.java

This comment is wrong. result.isSuccess() would only indicate the execution 
of scripts in the VR is success, regardless of it provides result or not. The 
result is still success if it provides output as well. If result is not 
success, it would cause a error.

Though your logic seems still honor the success? But what if command fail 
due to e.g. communication fail? I didn't see you have a place for failed answer.

core/src/com/cloud/agent/resource/virtualnetwork/VirtualRoutingResource.java

You won't need generateConfig. This command should be categoried as 
querycommand since it would demand immediately result. We cannot aggregate it. 

server/src/com/cloud/network/router/VirtualNetworkApplianceManagerImpl.java

I think you can use listRunningBy() and skip the routers which are not 
managed by this mgmt server? Get both GuestType routers separately seems 
strange.

server/src/com/cloud/network/router/VirtualNetworkApplianceManagerImpl.java

you can just avoid this null by generate the object and putting a timestamp 
in it, e.g. 1970-01-01 00:00:00 UTC

systemvm/patches/debian/config/opt/cloud/bin/getRouterAlerts.sh

You can use "tac" or alike tools to reverse the reading file, and stop when 
find old alerts.

systemvm/patches/debian/config/opt/cloud/bin/getRouterAlerts.sh

Just compare the seconds since epoch. "date +%s"

systemvm/patches/debian/config/opt/cloud/bin/getRouterAlerts.sh

It should be fine to always use alerts="${alerts}\n${line}" anyway... You 
don't need so complex if statement here.

- Sheng Yang

On March 14, 2014, 9:36 a.m., Harikrishna Patnala wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/19038/
> ---
> 
> (Updated March 14, 2014, 9:36 a.m.)
> 
> 
> Review request for cloudstack, Chiradeep Vittal, Jayapal Reddy, and Murali 
> Reddy.
> 
> 
> Bugs: CLOUDSTACK-6090
> https://issues.apache.org/jira/browse/CLOUDSTACK-6090
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> CLOUDSTACK-6090: Virtual Router Service Failure Alerting
> Currently in CS we can monitor the running services on Virtual Router and 
> ensure they are running through the lifetime of VR. 
> Upon failure of any service in VR, monitoring service logs the alerts in VR 
> logs. 
> With this feature those alerts will be sent to MS.
> 
> Added marvin tests
> 
> 
> Diffs
> -
> 
>   core/src/com/cloud/agent/api/GetRouterAlertsAnswer.java PRE-CREATION 
>   core/src/com/cloud/agent/api/routing/GetRouterAlertsCommand.java 
> PRE-CREATION 
>   
> core/src/com/cloud/agent/resource/virtualnetwork/VirtualRoutingResource.java 
> 3712aba 
>   
> engine/schema/resources/META-INF/cloudstack/core/spring-engine-schema-core-daos-context.xml
>  765d86c 
>   engine/schema/src/com/cloud/network/dao/OpRouterMonitorServiceDao.java 
> PRE-CREATION 
>   engine/schema/src/com/cloud/network/dao/OpRouterMonitorServiceDaoImpl.java 
> PRE-CREATION 
>   engine/schema/src/com/cloud/network/dao/OpRouterMonitorServiceVO.java 
> PRE-CREATION 
>   server/src/com/cloud/network/router/VirtualNetworkApplianceManagerImpl.java 
> eeab91d 
>   setup/db/db/schema-430to440.sql 056c5f8 
>   systemvm/patches/debian/config/opt/cloud/bin/getRouterAlerts.sh 
> PRE-CREATION 
>   systemvm/patches/debian/config/root/monitorServices.py 0319ece 
>   test/integration/smoke/test_VirtualRouter_alerts.py PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/19038/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Harikrishna Patnala
> 
>

RE: Java Coding Convention Errors

2014-03-18 Thread Soheil Eizadi

Hi Hugo,
Thanks for the direction, I followed that pattern,
-Soheil

From: Hugo Trippaers [trip...@gmail.com]
Sent: Tuesday, March 18, 2014 12:43 PM
To: dev@cloudstack.apache.org
Subject: Re: Java Coding Convention Errors

Hey Soheil,

Isn't is possible to stick to the CloudStack standards and use the 
SerializedName annotation? 
http://google-gson.googlecode.com/svn/tags/1.2.3/docs/javadocs/com/google/gson/annotations/SerializedName.html

Another option is to set a policy on gson that will automagically translate the 
java name into the underscore standard upon serialization. So isBoolean would 
become is_boolean. Look at the NiciraNvpApi, the gson policy is activated in 
the constructor.

Cheers,

Hugo

Sent from my iPhone

> On 18 mrt. 2014, at 20:34, Soheil Eizadi  wrote:
>
> Here is a proposed solution to evaluate, use the maven-checkstyle-plugin 
> exclude feature to make exception for modules that have code convention to 
> conform to external structures. Here is sample for my use case:
>
>maven-checkstyle-plugin
> 
>   **/infoblox/InfobloxNetworkView.java 
> 
>
> -Soheil
> 
> From: Soheil Eizadi [seiz...@infoblox.com]
> Sent: Tuesday, March 18, 2014 6:26 AM
> To: dev@cloudstack.apache.org
> Subject: RE: Java Coding Convention Errors
>
> Here is a code fragment for serialization:
>
>result = (T)gson.fromJson(resultString, 
> TypeToken.get(newObject.getClass()).getType());
>
> It is just generic/single handler for all generic type corresponding to the 
> same raw type.
>
> -Soheil
>
> 
> From: Hugo Trippaers [trip...@gmail.com]
> Sent: Monday, March 17, 2014 11:30 PM
> To: dev@cloudstack.apache.org
> Subject: Re: Java Coding Convention Errors
>
> Soheil,
>
> How are these classes serialized? There are different ways to solve this like 
> annotations with the serialized name or a gson policy.
>
> Cheers,
> Hugo
>
> Sent from my iPhone
>
>> On 18 mrt. 2014, at 03:33, Soheil Eizadi  wrote:
>>
>> Looks like in the new trunk we have turned on checks to enforce coding 
>> conventions in Eclipse? I have errors with some classes that I need to turn 
>> off:
>> "Name 'is_default' must match pattern '^_?[a-zA-Z0-9]*$'."
>>
>> For example a declaration:
>>
>>   private boolean is_default;
>>
>> These classes are part of the interface for REST communication so the 
>> strings must match the corresponding JSON objects. What is the best practice 
>> to turn this off in the project for a particular Class?
>> -Soheil

Re: [MERGE] resize-root branch

Verified your fix, my IAM test passed. Thanks for the fix, Marcus.

-min

On 3/17/14 10:39 PM, "Marcus"  wrote:

>This commit in 4.4 should fix it (cherry picked to master as well):
>
>commit 8eed3c5113d1141be820077e121db802566faec6
>Author: Marcus Sorensen 
>Date:   Fri Mar 14 07:13:34 2014 -0600
>
>Change newly added details map for deployVirtualMachine to an empty
>map, instead of passing all possible keys as empty values
>
>diff --git a/tools/marvin/marvin/integration/lib/base.py
>b/tools/marvin/marvin/integration/lib/base.py
>index ca9f2b4..38e8568 100755
>--- a/tools/marvin/marvin/integration/lib/base.py
>+++ b/tools/marvin/marvin/integration/lib/base.py
>@@ -413,7 +413,7 @@ class VirtualMachine:
> if "userdata" in services:
> cmd.userdata = base64.urlsafe_b64encode(services["userdata"])
>
>-cmd.details = [{"cpuNumber":
>"","cpuSpeed":"","memory":"","rootdisksize":""}]
>+cmd.details = [{}]
>
> if customcpunumber:
> cmd.details[0]["cpuNumber"] = customcpunumber
>
>On Mon, Mar 17, 2014 at 11:26 PM, Marcus  wrote:
>> Looks like all of the items in 'details' are getting added to the API
>> call as empty params:
>>
>> GET 
>>/client/api?domainid=7193957c-ab53-11e3-a79c-000c29d82947&zoneid=bfc93d0d
>>-9531-4648-9d04-ca1f47fcd5a6&apiKey=8d6jxAVly_B6asBBjuL5S5bxXzNhx3CyiPLCJ
>>Q7Qa4hti3HLlQQkP-x-ayenmO6t8vfZt5nDRHixsJc7XKdIGA&details%5B0%5D.rootdisk
>>size=&serviceofferingid=80bc069b-8283-4357-a995-e429d34b65d6&displayname=
>>Test+VM&signature=fHopjtezyTNYP2zPU4rHySxt%2FnM%3D&details%5B0%5D.cpuNumb
>>er=&templateid=719528ec-ab53-11e3-a79c-000c29d82947&response=json&details
>>%5B0%5D.memory=&account=test-TestDeployVM-test_deploy_vm_multiple-QTF0VD&
>>name=testvm&details%5B0%5D.cpuSpeed=&command=deployVirtualMachine&hypervi
>>sor=kvm
>> HTTP/1.1
>>
>> I've changed the default details map to be empty, instead of defining
>> all possible details as having empty strings as the original commit
>> did. Testing now and will commit if it works. I hope it doesn't break
>> *their* tests...
>>
>> commit 3f7b628c707cd9c30542efd670416be5fbb473f0
>> Author: Gaurav Aradhye 
>> Date:   Fri Feb 28 01:46:24 2014 -0500
>>
>> CLOUDSTACK-6147: Adding first set of test caess for Dynamic
>> Compute Offering feature
>>
>> Signed-off-by: SrikanteswaraRao Talluri 
>>
>>
>> On Mon, Mar 17, 2014 at 11:01 PM, Marcus  wrote:
>>> I'll take a look. I wasn't the one who added the details map to
>>> base.py, although I did add to it and can probably figure out what's
>>> wrong. The original commit didn't change any deployVirtualMachine
>>> calls. Can you give me an example of a test that is faling? Is it
>>> test_deploy_vm.py?
>>>
>>> On Mon, Mar 17, 2014 at 5:43 PM, Min Chen  wrote:
 Hi Marcus,

 I found an issue with this merge, my previous marvin test is
broken in
 deployVirtualMachine if no rootdisksize is passed. All previous marvin
 tests are written without passing this parameter. Can you take a look
at
 base.py to make sure that old marvin tests without passing those
custom
 parameters are still working fine?

 Thanks
 -min

 On 3/11/14 1:17 PM, "Marcus"  wrote:

>I'd like to merge the resize-root branch for the requested feature of
>being able to resize root volumes. I have pulled from master and
>tested.
>
>I should note that this feature is affected by an existing bug in
>master that was introduced recently, breaking the existing data disk
>resize feature on Ubuntu 12.04 + stock libvirt, but has otherwise been
>tested to work with Ubuntu 12.04 + recent libvirt and CentOS 6.4,6.5.
>We are discussing how to proceed with that separate issue on-list.
>
>Integration tests were added for deploy in a new file
>"test_deploy_vm_root_resize.py" and existing resize tests were
>extended to root volumes in the existing test_volumes.py.
>
>Findbugs indicates there are no new issues introduced (220/220), as
>reported by running the following on both master and resize-root. This
>was just my stab in the dark at trying to make sense of the output in
>absence of familiarity with findbugs:
>
># mvn -P enablefindbugs verify
># find . -name findbugs.xml -exec xmllint --format {} \; | grep -c
>BugInstance
>
>FS:
>https://cwiki.apache.org/confluence/display/CLOUDSTACK/Root+Resize+Sup
>port
>JIRA: https://issues.apache.org/jira/browse/CLOUDSTACK-6181

Re: random template from zones