Re: [ACS44]release 4.4.2 release candidate RC20141121T0341 (#2)

[Nux!]

Pierre,

In my case it did not, everything worked well, but do note I manually patched 
the sysvm tmpl for CLOUDSTACK-7781.

HTH
Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Pierre-Luc Dion" 
> To: dev@cloudstack.apache.org
> Sent: Tuesday, 25 November, 2014 23:43:41
> Subject: Re: [ACS44]release 4.4.2 release candidate RC20141121T0341 (#2)

> Does 4.4.2 require new set of systemvm compare to 4.4.1 ?
> 
> 
> On Tue, Nov 25, 2014 at 11:15 AM, Tomasz Zięba  wrote:
> 
>> +1
>>
>> for:
>>
>> http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-package-rpm/
>> <-- build 317
>> http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm64/
>> <-- build 171
>>
>> Regards
>> Tom
>>
>> 2014-11-21 3:59 GMT+01:00 Daan Hoogland :
>>
>> > Hi All,
>> >
>> > I've created a 4.4.2 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.4
>> > Commit: e0420a6fec738d728bc59ba65bc5e12809bde0eb
>> >
>> > List of changes:
>> > `CLOUDSTACK-7887
>> > `_  fail to
>> > push snapshot to secondary storage if using multipart using swift...
>> >
>> > `CLOUDSTACK-7883
>> > `_  Allow
>> > infrastructure to handle delete of volume from DB...
>> >
>> > `CLOUDSTACK-7871
>> > `_  Fix update
>> > VirtualMachine/Template API to allow nic/disk controller details for
>> > ...
>> >
>> > `CLOUDSTACK-7855
>> > `_  Sec
>> > storage/network MTU should be on nic3 and not nic1...
>> >
>> > `CLOUDSTACK-7826
>> > `_  UI - dialog
>> > widget - dependent dropdown field (dependsOn property specified) -
>> > f...
>> >
>> > `CLOUDSTACK-7822
>> > `_  test SSL
>> > cert expired...
>> >
>> > `CLOUDSTACK-7752
>> > `_  Management
>> > Server goes in infinite loop while creating a vm with tagged local
>> > da...
>> >
>> > `CLOUDSTACK-7722
>> > `_  add.label:
>> > Add button for tags show the label not "Add" text...
>> >
>> > `CLOUDSTACK-7246
>> > `_  VM
>> > deployment failed due to wrong in  script name createipalias.sh...
>> >
>> > Source release (checksums and signatures are available at the same
>> > location):
>> > https://dist.apache.org/repos/dist/dev/cloudstack/4.4.2
>> >
>> > PGP release keys (signed using 4096R/AA4736F3):
>> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>> >
>> > Vote will be open for 72 hours.
>> >
>> > 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)
>> >
>> >
>> > --
>> > Daan
>> >
>>
>>
>>
>> --
>> Regards,
>> Tomasz Zięba
>> Twitter: @TZieba
>> LinkedIn: pl.linkedin.com/pub/tomasz-zięba-ph-d/3b/7a8/ab6/
>> 
>> 

Build failed in Jenkins: build-master-noredist #3857

[jenkins]

See 

Changes:

[sanjay.tripathi] CLOUDSTACK-7969: SC: Win8.1: Key translation fails for some  
EN-US  keyboard keys.

--
[...truncated 1828 lines...]
460/547 KB   206/439 KB   162/256 KB   276/276 KB   
460/547 KB   206/439 KB   166/256 KB   276/276 KB   
460/547 KB   206/439 KB   170/256 KB   276/276 KB   
460/547 KB   206/439 KB   174/256 KB   276/276 KB   
460/547 KB   206/439 KB   178/256 KB   276/276 KB   
460/547 KB   206/439 KB   182/256 KB   276/276 KB   
460/547 KB   206/439 KB   186/256 KB   276/276 KB   
460/547 KB   206/439 KB   190/256 KB   276/276 KB   
460/547 KB   206/439 KB   194/256 KB   276/276 KB   
460/547 KB   206/439 KB   198/256 KB   276/276 KB   
460/547 KB   206/439 KB   202/256 KB   276/276 KB   
460/547 KB   206/439 KB   206/256 KB   276/276 KB   
460/547 KB   206/439 KB   210/256 KB   276/276 KB   
460/547 KB   206/439 KB   214/256 KB   276/276 KB   
460/547 KB   206/439 KB   218/256 KB   276/276 KB   
460/547 KB   206/439 KB   222/256 KB   276/276 KB   
460/547 KB   206/439 KB   225/256 KB   276/276 KB   
464/547 KB   206/439 KB   225/256 KB   276/276 KB   
468/547 KB   206/439 KB   225/256 KB   276/276 KB   
472/547 KB   206/439 KB   225/256 KB   276/276 KB   
476/547 KB   206/439 KB   225/256 KB   276/276 KB   
480/547 KB   206/439 KB   225/256 KB   276/276 KB   
484/547 KB   206/439 KB   225/256 KB   276/276 KB   
488/547 KB   206/439 KB   225/256 KB   276/276 KB   
492/547 KB   206/439 KB   225/256 KB   276/276 KB   
496/547 KB   206/439 KB   225/256 KB   276/276 KB   
500/547 KB   206/439 KB   225/256 KB   276/276 KB   
504/547 KB   206/439 KB   225/256 KB   276/276 KB   
508/547 KB   206/439 KB   225/256 KB   276/276 KB   
512/547 KB   206/439 KB   225/256 KB   276/276 KB   
516/547 KB   206/439 KB   225/256 KB   276/276 KB   
520/547 KB   206/439 KB   225/256 KB   276/276 KB   
524/547 KB   206/439 KB   225/256 KB   276/276 KB   
460/547 KB   206/439 KB   126/256 KB   273/276 KB   
528/547 KB   206/439 KB   225/256 KB   276/276 KB   
528/547 KB   210/439 KB   225/256 KB   276/276 KB   
532/547 KB   210/439 KB   225/256 KB   276/276 KB   
532/547 KB   214/439 KB   225/256 KB   276/276 KB   
536/547 KB   214/439 KB   225/256 KB   276/276 KB   
540/547 KB   214/439 KB   225/256 KB   276/276 KB   
544/547 KB   214/439 KB   225/256 KB   276/276 KB   
547/547 KB   214/439 KB   225/256 KB   276/276 KB   
547/547 KB   214/439 KB   229/256 KB   276/276 KB   
547/547 KB   214/439 KB   233/256 KB   276/276 KB   
547/547 KB   214/439 KB   237/256 KB   276/276 KB   
547/547 KB   214/439 KB   241/256 KB   276/276 KB   
547/547 KB   214/439 KB   245/256 KB   276/276 KB   
547/547 KB   214/439 KB   249/256 KB   276/276 KB   
547/547 KB   214/439 KB   253/256 KB   276/276 KB   
547/547 KB   214/439 KB   256/256 KB   276/276 KB   
547/547 KB   216/439 KB   256/256 KB   276/276 KB   
547/547 KB   219/439 KB   256/256 KB   276/276 KB   
547/547 KB   222/439 KB   256/256 KB   276/276 KB   
547/547 KB   224/439 KB   256/256 KB   276/276 KB   
547/547 KB   228/439 KB   256/256 KB   276/276 KB   
547/547 KB   232/439 KB   256/256 KB   276/276 KB   
547/547 KB   236/439 KB   256/256 KB   276/276 KB   
547/547 KB   240/439 KB   256/256 KB   276/276 KB   
547/547 KB   244/439 KB   256/256 KB   276/276 KB   
547/547 KB   248/439 KB   256/256 KB   276/276 KB   
547/547 KB   252/439 KB   256/256 KB   276/276 KB   
547/547 KB   256/439 KB   256/256 KB   276/276 KB   
547/547 KB   260/439 KB   256/256 KB   276/276 KB   
547/547 KB   264/439 KB   256/256 KB   276/276 KB   
547/547 KB   268/439 KB   256/256 KB   276/276 KB   
547/547 KB   270/439 KB   256/256 KB   276/276 KB   

Downloaded: 
http://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/1.5.12/plexus-utils-1.5.12.jar
 (276 KB at 4365.1 KB/sec)
547/547 KB   273/439 KB   256/256 KB
547/547 KB   276/439 KB   256/256 KB   
547/547 KB   279/439 KB   256/256 KB   
547/547 KB   280/439 KB   256/256 KB   
547/547 KB   281/439 KB   256/256 KB   
547/547 KB   284/439 KB   256/256 KB   
547/547 KB   288/439 KB   256/256 KB   
547/547 KB   292/439 KB   256/256 KB   
547/547 KB   296/439 KB   256/256 KB   
547/547 KB   300/439 KB   256/256 KB   
547/547 KB   304/439 KB   256/256 KB   
547/547 KB   308/439 KB   256/256 KB   
547/547 KB   312/439 KB   256/256 KB   
547/547 KB   316/439 KB   256/256 KB   
547/547 KB   320/439 KB   256/256 KB   
547/547 KB   324/439 KB   256/256 KB   
547/547 KB   327/439 KB   256/256 KB   
   
Downloaded: 
http://repo.maven.apache.org/maven2/commons-collections/commons-collections/3.1/commons-collections-3.1.jar
 (547 KB at 8955.0 KB/sec)
   
Downloaded: 
http://repo.maven.apache.org/maven2/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
 (256 KB at 4123.8 KB/sec

Re: [DISCUSS] Any issues to be fixed for 4.3.1?

[Rohit Yadav]

Thanks Rajani!
How do you add a new version in JIRA, does that require special privileges?

> On 26-Nov-2014, at 10:13 am, Rajani Karuturi  wrote:
>
> I added 4.3.2 fixversion in jira and also moved unresolved tickets from
> 4.1.*, 4.2.*, 4.3.0 and 4.3.1 to 4.3.2
>
> jira filter:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CLOUDSTACK%20AND%20fixVersion%20%3D%204.3.2%20AND%20resolution%20%3D%20Unresolved%20
>
> ~Rajani
>
> On Mon, Nov 24, 2014 at 11:56 PM, Rohit Yadav 
> wrote:
>
>> Thanks Mike, done.
>>
>>> On 24-Nov-2014, at 10:15 pm, Mike Tutkowski <
>> mike.tutkow...@solidfire.com> wrote:
>>>
>>> Hi Rohit,
>>>
>>> Please go ahead and cherry pick 6602ad71ac97fb1875131f41bb5f92ff1e3a1c7b
>>> into 4.3.2.
>>>
>>> Thanks!
>>> Mike
>>>
>>> On Thu, Nov 20, 2014 at 3:14 PM, Rohit Yadav 
>>> wrote:
>>>
 Thanks Wido, I’ve cherry-picked the fix and another fix from Will
 (Stevens). I’m buildling/testing it, will push on 4.3 as soon as that is
 done.

 @Mike: If your change is not changing the schema, or adding something
>> that
 could break upgrade paths please go for it. If it’s already fixed, you
>> can
 share the SHA with me and I can cherry-pick it and run basic build
>> tests on
 it.

> On 20-Nov-2014, at 3:46 pm, Wido den Hollander  wrote:
>
>
>
> On 11/20/2014 10:15 AM, Rohit Yadav wrote:
>> Hi,
>>
>> We’ve some bugfixes backported to 4.3 branch since 4.3.1 was released
 and I think we should at least support this branch with a 4.3.2 release
>> in
 next couple of weeks until a stable 4.5.0 is released in next couple of
 months.
>>
>> I’m going through JIRA and list of issues and will help backport fixes
 to the 4.3 branch. So, please share if you’ve found any
 blocker/critical/major issue that you found in 4.3.0 or 4.3.1 and want
>> to
 be fixed. Thanks.
>>
>
> I think that backporting this one would be useful for users:
> https://issues.apache.org/jira/browse/CLOUDSTACK-3383
>
> Simple fix, it's in master with
>> 69ee01af9df8d72ccd8901d146726e74edda95d7
>
> Wido
>
>> Regards,
>> Rohit Yadav
>> Software Architect, ShapeBlue
>> M. +91 88 262 30892 | rohit.ya...@shapeblue.com
>> Blog: bhaisaab.org | Twitter: @_bhaisaab
>>
>> Find out more about ShapeBlue and our range of CloudStack related
 services
>>
>> IaaS Cloud Design & Build<
 http://shapeblue.com/iaas-cloud-design-and-build//>
>> CSForge – rapid IaaS deployment framework<
>> http://shapeblue.com/csforge/
>
>> CloudStack Consulting
>> CloudStack Software Engineering<
 http://shapeblue.com/cloudstack-software-engineering/>
>> CloudStack Infrastructure Support<
 http://shapeblue.com/cloudstack-infrastructure-support/>
>> CloudStack Bootcamp Training Courses<
 http://shapeblue.com/cloudstack-training/>
>>
>> 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 SA Pty Ltd is a company registered by The Republic
>> of
 South Africa and is traded under license from Shape Blue Ltd. ShapeBlue
>> is
 a registered trademark.
>>

 Regards,
 Rohit Yadav
 Software Architect, ShapeBlue
 M. +91 88 262 30892 | rohit.ya...@shapeblue.com
 Blog: bhaisaab.org | Twitter: @_bhaisaab



 Find out more about ShapeBlue and our range of CloudStack related
>> services

 IaaS Cloud Design & Build<
 http://shapeblue.com/iaas-cloud-design-and-build//>
 CSForge – rapid IaaS deployment framework>>
 CloudStack Consulting
 CloudStack Software Engineering<
 http://shapeblue.com/cloudstack-software-engineering/>
 CloudStack Infrastructure Support<
 http://shapeblue.com/cloudstack-infrastructure-support/>
 CloudStack Bootcamp Training Courses<
 http://shapeblue.com/cloudstack-training/>

 This email and any attachments to it may be confidential and are
>> intended
 solely for the use of the individual to whom it is address

Re: [DISCUSS] Major business logic refactoring: Move from Account to UserAccount

[Rohit Yadav]

Hi Chiradeep,

> On 26-Nov-2014, at 4:32 am, Chiradeep Vittal  
> wrote:
>
> Instead of adding yet another parameter, could we look into adding a generic 
> filter as in:
> http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-DescribeInstances.html

But there already are so many parameters on the API, adding a filter param 
(map) will break semantics? May be we should do this for the next (restful) API 
layer we create?

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 88 262 30892 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab



Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Software 
Engineering
CloudStack Infrastructure 
Support
CloudStack Bootcamp Training Courses

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 SA Pty Ltd is a company 
registered by The Republic of South Africa and is traded under license from 
Shape Blue Ltd. ShapeBlue is a registered trademark.

Jenkins build is still unstable: simulator-singlerun #697

[jenkins]

See 

Re: [DISCUSS] Any issues to be fixed for 4.3.1?

[Rajani Karuturi]

I think it requires additional permissions

~Rajani

On Wed, Nov 26, 2014 at 2:16 PM, Rohit Yadav 
wrote:

> Thanks Rajani!
> How do you add a new version in JIRA, does that require special privileges?
>
> > On 26-Nov-2014, at 10:13 am, Rajani Karuturi  wrote:
> >
> > I added 4.3.2 fixversion in jira and also moved unresolved tickets from
> > 4.1.*, 4.2.*, 4.3.0 and 4.3.1 to 4.3.2
> >
> > jira filter:
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CLOUDSTACK%20AND%20fixVersion%20%3D%204.3.2%20AND%20resolution%20%3D%20Unresolved%20
> >
> > ~Rajani
> >
> > On Mon, Nov 24, 2014 at 11:56 PM, Rohit Yadav  >
> > wrote:
> >
> >> Thanks Mike, done.
> >>
> >>> On 24-Nov-2014, at 10:15 pm, Mike Tutkowski <
> >> mike.tutkow...@solidfire.com> wrote:
> >>>
> >>> Hi Rohit,
> >>>
> >>> Please go ahead and cherry pick
> 6602ad71ac97fb1875131f41bb5f92ff1e3a1c7b
> >>> into 4.3.2.
> >>>
> >>> Thanks!
> >>> Mike
> >>>
> >>> On Thu, Nov 20, 2014 at 3:14 PM, Rohit Yadav <
> rohit.ya...@shapeblue.com>
> >>> wrote:
> >>>
>  Thanks Wido, I’ve cherry-picked the fix and another fix from Will
>  (Stevens). I’m buildling/testing it, will push on 4.3 as soon as that
> is
>  done.
> 
>  @Mike: If your change is not changing the schema, or adding something
> >> that
>  could break upgrade paths please go for it. If it’s already fixed, you
> >> can
>  share the SHA with me and I can cherry-pick it and run basic build
> >> tests on
>  it.
> 
> > On 20-Nov-2014, at 3:46 pm, Wido den Hollander 
> wrote:
> >
> >
> >
> > On 11/20/2014 10:15 AM, Rohit Yadav wrote:
> >> Hi,
> >>
> >> We’ve some bugfixes backported to 4.3 branch since 4.3.1 was
> released
>  and I think we should at least support this branch with a 4.3.2
> release
> >> in
>  next couple of weeks until a stable 4.5.0 is released in next couple
> of
>  months.
> >>
> >> I’m going through JIRA and list of issues and will help backport
> fixes
>  to the 4.3 branch. So, please share if you’ve found any
>  blocker/critical/major issue that you found in 4.3.0 or 4.3.1 and want
> >> to
>  be fixed. Thanks.
> >>
> >
> > I think that backporting this one would be useful for users:
> > https://issues.apache.org/jira/browse/CLOUDSTACK-3383
> >
> > Simple fix, it's in master with
> >> 69ee01af9df8d72ccd8901d146726e74edda95d7
> >
> > Wido
> >
> >> Regards,
> >> Rohit Yadav
> >> Software Architect, ShapeBlue
> >> M. +91 88 262 30892 | rohit.ya...@shapeblue.com
> >> Blog: bhaisaab.org | Twitter: @_bhaisaab
> >>
> >> Find out more about ShapeBlue and our range of CloudStack related
>  services
> >>
> >> IaaS Cloud Design & Build<
>  http://shapeblue.com/iaas-cloud-design-and-build//>
> >> CSForge – rapid IaaS deployment framework<
> >> http://shapeblue.com/csforge/
> >
> >> CloudStack Consulting
> >> CloudStack Software Engineering<
>  http://shapeblue.com/cloudstack-software-engineering/>
> >> CloudStack Infrastructure Support<
>  http://shapeblue.com/cloudstack-infrastructure-support/>
> >> CloudStack Bootcamp Training Courses<
>  http://shapeblue.com/cloudstack-training/>
> >>
> >> 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 SA Pty Ltd is a company registered by The Republic
> >> of
>  South Africa and is traded under license from Shape Blue Ltd.
> ShapeBlue
> >> is
>  a registered trademark.
> >>
> 
>  Regards,
>  Rohit Yadav
>  Software Architect, ShapeBlue
>  M. +91 88 262 30892 | rohit.ya...@shapeblue.com
>  Blog: bhaisaab.org | Twitter: @_bhaisaab
> 
> 
> 
>  Find out more about ShapeBlue and our range of CloudStack related
> >> services
> 
>  IaaS Cloud Design & Build<
>  http://shapeblue.com/iaas-cloud-design-and-build//>
>  CSForge – rapid IaaS deployment framework<
> http://shapeblue.com/csforge/
> >>>
>  CloudStack Consulting
>  CloudSt

Jenkins build is still unstable: simulator-singlerun #698

[jenkins]

See 

Jenkins build is back to normal : build-master-noredist #3858

[jenkins]

See 

Re: Moving ec2stack and gstack to the cloudstack repos.

[Ian Duffy]

> I think unit tests are great for type checking and the like, but are
there any integration tests?

At the moment there aren't any, we could add some using eutester very
easily and chain it onto the current CI tasks. As Sebastien has mentioned
earlier in this thread he has already looked at doing this a little bit.

Not to sound tit-for-tat but awsapi has same issue and has much less unit
testing.

> Any plans to add any?

Its not *my personal* immediate plan, but isn't that the beauty of open
source and community building? The project is open to everybody to
contribute, if you see value for integration tests to be added and wish to
do it then go ahead. Its a donation of code, not a we'll supply xyz
software to do xyz service and be the sole maintainers of it forever. If we
want things that work we need community(user and dev) support, want and
time.

For me EC2Stack had two primary goals:

1) Make contributing easy, we wanted to produce clean(ish) code that was
easily extendable by the community so we could get some support if/when it
takes off. AWSAPI is a bit terrifying to look at, there's a large amount of
auto generated code and its a bit scary at first.

 In brief to add a new API command:
- Open controllers.py, add a new API call into the actions object: e.g.
'AttachVolume': volumes.attach_volume,
- Head over to the referenced module/function and fill it out e.g.
https://github.com/BroganD1993/ec2stack/blob/master/ec2stack/providers/cloudstack/volumes.py
- Done.

2) Make it portable. We didn't want the AWS compatibility layer to always
have to be hosted by the Cloudstack provider. We wanted the flexibility to
use it against any Cloudstack 4.0.0> API. This was a success and we
successfully use EC2Stack against ExoScale as shown in the earlier
referenced screencast.

Hope this answers your questions,

Ian


On 26 November 2014 at 02:47, ChunFeng  wrote:

> hi all,
>
>
> I need help for  a clean picture about  the umbrella projects of
> cloudstack:
> such as :
> 1. the umbrella project links in cloudstack.org homepage
> 2. the source code structure and relations with cloudstack source code in
> git repos.
> 3. the rules for us to agree one as umbrella projects
>
>
>
> BTW,  is there any others umbrella proejcts as cloudmonkey ?
>
>
> --
> Regards,
>
>
> ChunFeng
>
>
>
>
>
>
>
>
>
> -- Original --
> From:  "Sebastien Goasguen";
> Date:  Tue, Nov 25, 2014 06:29 AM
> To:  "dev";
>
> Subject:  Re: Moving ec2stack and gstack to the cloudstack repos.
>
>
>
> On Nov 24, 2014, at 5:05 PM, Chiradeep Vittal 
> wrote:
>
> > I do see a bug fix this year from Likitha  and the fact that Hugo etc
> are making fixes is positive as well.
> > But, the end state we desire is (a) good AWSAPI implementation with
> automated tests, not (b) 2 AWSAPI implementations with no tests!
> >
>
> time for bed here, but to keep the conversation going, couple things:
>
> Hugo is fixing coverity issues kind of automatically, I don't think it
> represents a need.
> One fix from Likitha and one applied patch from me in a year is really
> slim.
>
> We don't test the current awsapi during the release process or upgrade, so
> I actually have no clue if it's working with 4.3 and 4.4.
>
> Right now I don't see tests for the current awsapi, at least not on
> jenkins.buildacloud.org.
> Current awsapi also includes S3 stuff which I think we can all agree is
> confusing and unused since it's really an interface to an NFS store and not
> a distributed object store.
>
> So the choice for me is between:
>
> -current awsapi, not clearly maintained, without tests and which state in
> the release is unknown
>
> and
>
> -a new implementation < 6 months old, smaller code base, up to date with
> AWS version number, tested manually with boto, eutester and awscli and with
> 99% unit test coverage.
>
>
> > —
> > Chiradeep
> >
> > From: Sebastien Goasguen mailto:run...@gmail.com>>
> > Reply-To: "dev@cloudstack.apache.org"
> mailto:dev@cloudstack.apache.org>>
> > Date: Monday, November 24, 2014 at 1:36 PM
> > To: "dev@cloudstack.apache.org" <
> dev@cloudstack.apache.org>
> > Subject: Re: Moving ec2stack and gstack to the cloudstack repos.
> >
> >
> > On Nov 24, 2014, at 3:44 PM, Chiradeep Vittal <
> chiradeep.vit...@citrix.com> wrote:
> >
> > “..nobody in the community (aside from you, Likitha and Prachi) have
> actually touched that code in the last two years. So if we don't maintain
> that code.."
> > That’s false equivalence. Clearly it has been maintained since there are
> bug fixes.
> >
> > I don't know…I look at:
> >
> > https://github.com/apache/cloudstack/tree/master/awsapi
> >
> > I see Hugo has fixed some coverity issues
> >
> > I applied a review 8 months ago
> >
> > the rest is older. but maybe I am not looking at this the right way.
> >
> > there is one review 

[GitHub] cloudstack-docs pull request: Update vxlan.rst

[andrijapanic]

GitHub user andrijapanic opened a pull request:

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

Update vxlan.rst

Added section about MTU sizes and examples. If I'v done something wrong, 
please let me know...

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

$ git pull https://github.com/andrijapanic/cloudstack-docs master

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

https://github.com/apache/cloudstack-docs/pull/8.patch

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

This closes #8


commit cbd7a13622780142127f06bf2f0d2888afea3c68
Author: andrijapanic 
Date:   2014-11-26T12:10:32Z

Update vxlan.rst

Added section about MTU sizes and examples.




---
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: Moving ec2stack and gstack to the cloudstack repos.

[sebgoa]

On Nov 26, 2014, at 1:46 PM, Ian Duffy  wrote:

>> I think unit tests are great for type checking and the like, but are
> there any integration tests?
> 
> At the moment there aren't any, we could add some using eutester very
> easily and chain it onto the current CI tasks. As Sebastien has mentioned
> earlier in this thread he has already looked at doing this a little bit.
> 
> Not to sound tit-for-tat but awsapi has same issue and has much less unit
> testing.
> 
>> Any plans to add any?
> 
> Its not *my personal* immediate plan, but isn't that the beauty of open
> source and community building? The project is open to everybody to
> contribute, if you see value for integration tests to be added and wish to
> do it then go ahead. Its a donation of code, not a we'll supply xyz
> software to do xyz service and be the sole maintainers of it forever. If we
> want things that work we need community(user and dev) support, want and
> time.
> 

agreed with Ian.

I think this falls in the category of non official roadmap items.

Shall we have integration tests for this ? Yes we should

What they are going to be and how they are going to be implemented (by whom and 
when) and run is still unknown and will depend on user traction.


> For me EC2Stack had two primary goals:
> 
> 1) Make contributing easy, we wanted to produce clean(ish) code that was
> easily extendable by the community so we could get some support if/when it
> takes off. AWSAPI is a bit terrifying to look at, there's a large amount of
> auto generated code and its a bit scary at first.
> 
> In brief to add a new API command:
>- Open controllers.py, add a new API call into the actions object: e.g.
> 'AttachVolume': volumes.attach_volume,
> - Head over to the referenced module/function and fill it out e.g.
> https://github.com/BroganD1993/ec2stack/blob/master/ec2stack/providers/cloudstack/volumes.py
> - Done.
> 
> 2) Make it portable. We didn't want the AWS compatibility layer to always
> have to be hosted by the Cloudstack provider. We wanted the flexibility to
> use it against any Cloudstack 4.0.0> API. This was a success and we
> successfully use EC2Stack against ExoScale as shown in the earlier
> referenced screencast.
> 
> Hope this answers your questions,
> 
> Ian
> 
> 
> On 26 November 2014 at 02:47, ChunFeng  wrote:
> 
>> hi all,
>> 
>> 
>> I need help for  a clean picture about  the umbrella projects of
>> cloudstack:
>> such as :
>> 1. the umbrella project links in cloudstack.org homepage
>> 2. the source code structure and relations with cloudstack source code in
>> git repos.
>> 3. the rules for us to agree one as umbrella projects
>> 
>> 
>> 
>> BTW,  is there any others umbrella proejcts as cloudmonkey ?
>> 
>> 
>> --
>> Regards,
>> 
>> 
>> ChunFeng
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> -- Original --
>> From:  "Sebastien Goasguen";
>> Date:  Tue, Nov 25, 2014 06:29 AM
>> To:  "dev";
>> 
>> Subject:  Re: Moving ec2stack and gstack to the cloudstack repos.
>> 
>> 
>> 
>> On Nov 24, 2014, at 5:05 PM, Chiradeep Vittal 
>> wrote:
>> 
>>> I do see a bug fix this year from Likitha  and the fact that Hugo etc
>> are making fixes is positive as well.
>>> But, the end state we desire is (a) good AWSAPI implementation with
>> automated tests, not (b) 2 AWSAPI implementations with no tests!
>>> 
>> 
>> time for bed here, but to keep the conversation going, couple things:
>> 
>> Hugo is fixing coverity issues kind of automatically, I don't think it
>> represents a need.
>> One fix from Likitha and one applied patch from me in a year is really
>> slim.
>> 
>> We don't test the current awsapi during the release process or upgrade, so
>> I actually have no clue if it's working with 4.3 and 4.4.
>> 
>> Right now I don't see tests for the current awsapi, at least not on
>> jenkins.buildacloud.org.
>> Current awsapi also includes S3 stuff which I think we can all agree is
>> confusing and unused since it's really an interface to an NFS store and not
>> a distributed object store.
>> 
>> So the choice for me is between:
>> 
>> -current awsapi, not clearly maintained, without tests and which state in
>> the release is unknown
>> 
>> and
>> 
>> -a new implementation < 6 months old, smaller code base, up to date with
>> AWS version number, tested manually with boto, eutester and awscli and with
>> 99% unit test coverage.
>> 
>> 
>>> —
>>> Chiradeep
>>> 
>>> From: Sebastien Goasguen mailto:run...@gmail.com>>
>>> Reply-To: "dev@cloudstack.apache.org"
>> mailto:dev@cloudstack.apache.org>>
>>> Date: Monday, November 24, 2014 at 1:36 PM
>>> To: "dev@cloudstack.apache.org" <
>> dev@cloudstack.apache.org>
>>> Subject: Re: Moving ec2stack and gstack to the cloudstack repos.
>>> 
>>> 
>>> On Nov 24, 2014, at 3:44 PM, Chiradeep Vittal <
>> chiradeep.vit...@citrix.com> wrote:
>>> 

Re: Moving ec2stack and gstack to the cloudstack repos.

[sebgoa]

On Nov 26, 2014, at 3:47 AM, ChunFeng  wrote:

> hi all,
> 
> 
> I need help for  a clean picture about  the umbrella projects of cloudstack:
> such as :
> 1. the umbrella project links in cloudstack.org homepage

I don't understand your question here.

> 2. the source code structure and relations with cloudstack source code in git 
> repos.
> 3. the rules for us to agree one as umbrella projects 
> 
> 
> 
> BTW,  is there any others umbrella proejcts as cloud monkey
> ?
> 

CloudStack as a top level project at the ASF can use as many git repos as it 
wants.

For instance we moved the docs to separate and repo, and we moved cloudmonkey 
to a separate repo.

For another code based to "join" CloudStack, it either needs to be developed 
directly in the cloudstack source code or it needs to go through a process 
known as IP clearance.

Once IP clearance is filed and approved, a new code base can be "dropped" in 
CloudStack. It could be committed to the main source tree or in a separate repo.

In this thread we are discussing about making ec2stack and gstack part of 
CloudStack (most likely in separate git repos). If we agree then we will go 
through IP clearance for those. this should be an easy process since they are 
already apache v2 and were developed by 3 members of the community.

Hope that helps answer your question.

> 
> --
> Regards,
> 
> 
> ChunFeng
> 
> 
> 
> 
> 
> 
> 
> 
> 
> -- Original --
> From:  "Sebastien Goasguen";
> Date:  Tue, Nov 25, 2014 06:29 AM
> To:  "dev"; 
> 
> Subject:  Re: Moving ec2stack and gstack to the cloudstack repos.
> 
> 
> 
> On Nov 24, 2014, at 5:05 PM, Chiradeep Vittal  
> wrote:
> 
>> I do see a bug fix this year from Likitha  and the fact that Hugo etc are 
>> making fixes is positive as well.
>> But, the end state we desire is (a) good AWSAPI implementation with 
>> automated tests, not (b) 2 AWSAPI implementations with no tests!
>> 
> 
> time for bed here, but to keep the conversation going, couple things:
> 
> Hugo is fixing coverity issues kind of automatically, I don't think it 
> represents a need.
> One fix from Likitha and one applied patch from me in a year is really slim.
> 
> We don't test the current awsapi during the release process or upgrade, so I 
> actually have no clue if it's working with 4.3 and 4.4.
> 
> Right now I don't see tests for the current awsapi, at least not on 
> jenkins.buildacloud.org.
> Current awsapi also includes S3 stuff which I think we can all agree is 
> confusing and unused since it's really an interface to an NFS store and not a 
> distributed object store.
> 
> So the choice for me is between:
> 
> -current awsapi, not clearly maintained, without tests and which state in the 
> release is unknown
> 
> and
> 
> -a new implementation < 6 months old, smaller code base, up to date with AWS 
> version number, tested manually with boto, eutester and awscli and with 99% 
> unit test coverage.
> 
> 
>> —
>> Chiradeep
>> 
>> From: Sebastien Goasguen mailto:run...@gmail.com>>
>> Reply-To: "dev@cloudstack.apache.org" 
>> mailto:dev@cloudstack.apache.org>>
>> Date: Monday, November 24, 2014 at 1:36 PM
>> To: "dev@cloudstack.apache.org" 
>> mailto:dev@cloudstack.apache.org>>
>> Subject: Re: Moving ec2stack and gstack to the cloudstack repos.
>> 
>> 
>> On Nov 24, 2014, at 3:44 PM, Chiradeep Vittal 
>> mailto:chiradeep.vit...@citrix.com>> wrote:
>> 
>> “..nobody in the community (aside from you, Likitha and Prachi) have 
>> actually touched that code in the last two years. So if we don't maintain 
>> that code.."
>> That’s false equivalence. Clearly it has been maintained since there are bug 
>> fixes.
>> 
>> I don't know…I look at:
>> 
>> https://github.com/apache/cloudstack/tree/master/awsapi
>> 
>> I see Hugo has fixed some coverity issues
>> 
>> I applied a review 8 months ago
>> 
>> the rest is older. but maybe I am not looking at this the right way.
>> 
>> there is one review still pending:
>> 
>> https://reviews.apache.org/r/21776/
>> 
>> So from looking at it this way it does not look actively maintained. No ?
>> 
>> But we’re looking to make things better. I am not sure HOW bringing in 
>> another compatibility layer brings benefits, UNLESS WE propose to commit 
>> time to provide a suite of integration tests (say, via eutester)
>> 
>> Do we have a suite of integration tests for awsapi that is running right now 
>> ? where ?
>> 
>> I did play with eutester and actually patched it to work with cloudstack 
>> when I worked on ec2stack:
>> 
>> http://sebgoa.blogspot.de/2014/06/eutester-interesting-tool-based-on-boto.html
>> 
>> -sebastien
>> 
>> Thanks
>> —
>> Chiradeep
>> From: sebgoa 
>> mailto:run...@gmail.com>>
>> Reply-To: 
>> "dev@cloudstack.apache.org"
>>  
>> mailto:dev@cloudstack.apache.org>

Jenkins build is still unstable: simulator-singlerun #699

[jenkins]

See 

[GitHub] cloudstack-docs pull request: Update vxlan.rst

[bhaisaab]

Github user bhaisaab commented on the pull request:

https://github.com/apache/cloudstack-docs/pull/8#issuecomment-64636942
  
+1

LGTM


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

[GitHub] cloudstack-docs pull request: Update vxlan.rst

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] cloudstack-docs pull request: updated instructions to install jdk1...

[bhaisaab]

Github user bhaisaab commented on the pull request:

https://github.com/apache/cloudstack-docs/pull/6#issuecomment-64644513
  
+1

LGTM.


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

[GitHub] cloudstack-docs pull request: Update vxlan.rst

[andrijapanic]

Github user andrijapanic commented on the pull request:

https://github.com/apache/cloudstack-docs/pull/8#issuecomment-64644476
  
if there is more work to be done from my side - please let me know, 
otherwise I guess someone else will do the merging or similar...


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

[GitHub] cloudstack-docs pull request: updated instructions to install jdk1...

[asfgit]

Github user asfgit closed the pull request at:

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


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

[GitHub] cloudstack-docs pull request: Update vxlan.rst

[bhaisaab]

Github user bhaisaab commented on the pull request:

https://github.com/apache/cloudstack-docs/pull/8#issuecomment-64658114
  
@andrijapanic feel free to edit/add more documentation and send pull 
requests. Thanks.


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

release procedure

[Daan Hoogland]

H,

I updated the release procedure page and ported my version of
build_asf.sh to the 4.5 and master branches. please have questions
after a look

presently yours,
-- 
Daan

[GitHub] cloudstack pull request: Add improved support for packaging CloudS...

[spark404]

Github user spark404 commented on the pull request:

https://github.com/apache/cloudstack/pull/46#issuecomment-64660575
  
@damodarreddy That commit is good, but incomplete. I used that as the basis 
for this commit, but there are so many small changes between centos 6 and 
centos 7, that a simple if-then-else would not work. It would become unreadable.

Another thing is that the old rpms have a lot of legacy code to deal with 
upgrades of older packages. For CentOS 7 we don't need that and would only 
cause more problems. So in short, yes that commit was good and hopefully i have 
improved on that commit with this extension.


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

[GitHub] cloudstack pull request: Add improved support for packaging CloudS...

[spark404]

Github user spark404 commented on the pull request:

https://github.com/apache/cloudstack/pull/46#issuecomment-64660807
  
@bhaisaab @damodarreddy @wilderrodrigues To be clear, any objections to 
merging this?

The jenkins build is here, as travis does not do packaging: 
http://jenkins.buildacloud.org/job/package-centos7-test/


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

[JENKINS] Added CentOS 7 slaves

[Hugo Trippaers]

If any one needs something build or tested on CentOS 7 let me know or create a 
build tagged for cloudstack-buildslave-centos7 

Cheers,

Hugo

P.S. Still looking for people willing to add slaves to jenkins. What we need 
are one or two fast machines capable of running the simulator tests. 

Re: [JENKINS] Added CentOS 7 slaves

[Pierre-Luc Dion]

does it only require to run jenkins as slave?  or their is any other
particular requirements?


*Pierre-Luc DION*
Architecte de Solution Cloud | Cloud Solutions Architect
t 855.652.5683

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


On Wed, Nov 26, 2014 at 10:25 AM, Hugo Trippaers  wrote:

> If any one needs something build or tested on CentOS 7 let me know or
> create a build tagged for cloudstack-buildslave-centos7
>
> Cheers,
>
> Hugo
>
> P.S. Still looking for people willing to add slaves to jenkins. What we
> need are one or two fast machines capable of running the simulator tests.

Re: [JENKINS] Added CentOS 7 slaves

[Ian Duffy]

Just throwing this out there All committers have access to a msdn
subscription that gives 125eur worth of azure credits.
You can get a decent VM for that.
On 26 Nov 2014 15:37, "Pierre-Luc Dion"  wrote:

> does it only require to run jenkins as slave?  or their is any other
> particular requirements?
>
>
> *Pierre-Luc DION*
> Architecte de Solution Cloud | Cloud Solutions Architect
> t 855.652.5683
>
> *CloudOps* Votre partenaire infonuagique* | *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
>
>
> On Wed, Nov 26, 2014 at 10:25 AM, Hugo Trippaers 
> wrote:
>
> > If any one needs something build or tested on CentOS 7 let me know or
> > create a build tagged for cloudstack-buildslave-centos7
> >
> > Cheers,
> >
> > Hugo
> >
> > P.S. Still looking for people willing to add slaves to jenkins. What we
> > need are one or two fast machines capable of running the simulator tests.
>

[GitHub] cloudstack pull request: Add improved support for packaging CloudS...

[DaanHoogland]

Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/46#issuecomment-64665068
  
on no word the coming 24h I'll do the honours.


---
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: [JENKINS] Added CentOS 7 slaves

[Hugo Trippaers]

Basically it only needs to allow connections on port 22 with either a key or a 
password and Jenkins will pretty much auto configure itself to run it as a 
slave. So Jenkins isn’t even running on the machine, just the slave process.

What i do to prepare a machine to be a (centos) slave is:
 * install rpmbuild, git, yum-utils
 * git clone the cloudstack source (or download just the spec file)
 * run yum-builddep on packaging/centos(63|7)/cloud.spec to install all 
dependencies
 * install mysql-server or mariadb-server (for the simulator)
 * remove the cloudstack sources again

Cheers,

Hugo


> On 26 nov. 2014, at 16:34, Pierre-Luc Dion  wrote:
> 
> does it only require to run jenkins as slave?  or their is any other
> particular requirements?
> 
> 
> *Pierre-Luc DION*
> Architecte de Solution Cloud | Cloud Solutions Architect
> t 855.652.5683
> 
> *CloudOps* Votre partenaire infonuagique* | *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
> 
> 
> On Wed, Nov 26, 2014 at 10:25 AM, Hugo Trippaers  wrote:
> 
>> If any one needs something build or tested on CentOS 7 let me know or
>> create a build tagged for cloudstack-buildslave-centos7
>> 
>> Cheers,
>> 
>> Hugo
>> 
>> P.S. Still looking for people willing to add slaves to jenkins. What we
>> need are one or two fast machines capable of running the simulator tests.

Re: [JENKINS] Added CentOS 7 slaves

[Hugo Trippaers]

Good point,

i’ll need to check if jclouds supports azure but a few dynamic slaves could be 
nice.

Cheers,

Hugo

> On 26 nov. 2014, at 16:39, Ian Duffy  wrote:
> 
> Just throwing this out there All committers have access to a msdn
> subscription that gives 125eur worth of azure credits.
> You can get a decent VM for that.
> On 26 Nov 2014 15:37, "Pierre-Luc Dion"  wrote:
> 
>> does it only require to run jenkins as slave?  or their is any other
>> particular requirements?
>> 
>> 
>> *Pierre-Luc DION*
>> Architecte de Solution Cloud | Cloud Solutions Architect
>> t 855.652.5683
>> 
>> *CloudOps* Votre partenaire infonuagique* | *Cloud Solutions Experts
>> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
>> w cloudops.com *|* tw @CloudOps_
>> 
>> 
>> On Wed, Nov 26, 2014 at 10:25 AM, Hugo Trippaers 
>> wrote:
>> 
>>> If any one needs something build or tested on CentOS 7 let me know or
>>> create a build tagged for cloudstack-buildslave-centos7
>>> 
>>> Cheers,
>>> 
>>> Hugo
>>> 
>>> P.S. Still looking for people willing to add slaves to jenkins. What we
>>> need are one or two fast machines capable of running the simulator tests.
>> 

[GitHub] cloudstack pull request: Add improved support for packaging CloudS...

[wilderrodrigues]

Github user wilderrodrigues commented on the pull request:

https://github.com/apache/cloudstack/pull/46#issuecomment-64671315
  
No objections...


---
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: [ACS44]release 4.4.2 release candidate RC20141121T0341 (#2)

[Pierre-Luc Dion]

Did anyone try an upgrade from a fresh 4.4.0 to 4.4.2?  so far I did not
had too much success but before do a negative vote I want to make sure my
test env, is ok.

thanks,

PL


On Wed, Nov 26, 2014 at 3:46 AM, Nux!  wrote:

> Pierre,
>
> In my case it did not, everything worked well, but do note I manually
> patched the sysvm tmpl for CLOUDSTACK-7781.
>
> HTH
> Lucian
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> - Original Message -
> > From: "Pierre-Luc Dion" 
> > To: dev@cloudstack.apache.org
> > Sent: Tuesday, 25 November, 2014 23:43:41
> > Subject: Re: [ACS44]release 4.4.2 release candidate RC20141121T0341 (#2)
>
> > Does 4.4.2 require new set of systemvm compare to 4.4.1 ?
> >
> >
> > On Tue, Nov 25, 2014 at 11:15 AM, Tomasz Zięba 
> wrote:
> >
> >> +1
> >>
> >> for:
> >>
> >> http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-package-rpm/
> >> <-- build 317
> >> http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm64/
> >> <-- build 171
> >>
> >> Regards
> >> Tom
> >>
> >> 2014-11-21 3:59 GMT+01:00 Daan Hoogland :
> >>
> >> > Hi All,
> >> >
> >> > I've created a 4.4.2 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.4
> >> > Commit: e0420a6fec738d728bc59ba65bc5e12809bde0eb
> >> >
> >> > List of changes:
> >> > `CLOUDSTACK-7887
> >> > `_  fail to
> >> > push snapshot to secondary storage if using multipart using swift...
> >> >
> >> > `CLOUDSTACK-7883
> >> > `_  Allow
> >> > infrastructure to handle delete of volume from DB...
> >> >
> >> > `CLOUDSTACK-7871
> >> > `_  Fix update
> >> > VirtualMachine/Template API to allow nic/disk controller details for
> >> > ...
> >> >
> >> > `CLOUDSTACK-7855
> >> > `_  Sec
> >> > storage/network MTU should be on nic3 and not nic1...
> >> >
> >> > `CLOUDSTACK-7826
> >> > `_  UI -
> dialog
> >> > widget - dependent dropdown field (dependsOn property specified) -
> >> > f...
> >> >
> >> > `CLOUDSTACK-7822
> >> > `_  test SSL
> >> > cert expired...
> >> >
> >> > `CLOUDSTACK-7752
> >> > `_  Management
> >> > Server goes in infinite loop while creating a vm with tagged local
> >> > da...
> >> >
> >> > `CLOUDSTACK-7722
> >> > `_  add.label:
> >> > Add button for tags show the label not "Add" text...
> >> >
> >> > `CLOUDSTACK-7246
> >> > `_  VM
> >> > deployment failed due to wrong in  script name createipalias.sh...
> >> >
> >> > Source release (checksums and signatures are available at the same
> >> > location):
> >> > https://dist.apache.org/repos/dist/dev/cloudstack/4.4.2
> >> >
> >> > PGP release keys (signed using 4096R/AA4736F3):
> >> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >> >
> >> > Vote will be open for 72 hours.
> >> >
> >> > 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)
> >> >
> >> >
> >> > --
> >> > Daan
> >> >
> >>
> >>
> >>
> >> --
> >> Regards,
> >> Tomasz Zięba
> >> Twitter: @TZieba
> >> LinkedIn: pl.linkedin.com/pub/tomasz-zięba-ph-d/3b/7a8/ab6/
> 
> >> 
> >> 
>

Re: [ACS44]release 4.4.2 release candidate RC20141121T0341 (#2)

[Nux!]

I tried from 4.4.1; what problems are you seeing?

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Pierre-Luc Dion" 
> To: dev@cloudstack.apache.org
> Sent: Wednesday, 26 November, 2014 17:11:10
> Subject: Re: [ACS44]release 4.4.2 release candidate RC20141121T0341 (#2)

> Did anyone try an upgrade from a fresh 4.4.0 to 4.4.2?  so far I did not
> had too much success but before do a negative vote I want to make sure my
> test env, is ok.
> 
> thanks,
> 
> PL
> 
> 
> On Wed, Nov 26, 2014 at 3:46 AM, Nux!  wrote:
> 
>> Pierre,
>>
>> In my case it did not, everything worked well, but do note I manually
>> patched the sysvm tmpl for CLOUDSTACK-7781.
>>
>> HTH
>> Lucian
>>
>> --
>> Sent from the Delta quadrant using Borg technology!
>>
>> Nux!
>> www.nux.ro
>>
>> - Original Message -
>> > From: "Pierre-Luc Dion" 
>> > To: dev@cloudstack.apache.org
>> > Sent: Tuesday, 25 November, 2014 23:43:41
>> > Subject: Re: [ACS44]release 4.4.2 release candidate RC20141121T0341 (#2)
>>
>> > Does 4.4.2 require new set of systemvm compare to 4.4.1 ?
>> >
>> >
>> > On Tue, Nov 25, 2014 at 11:15 AM, Tomasz Zięba 
>> wrote:
>> >
>> >> +1
>> >>
>> >> for:
>> >>
>> >> http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-package-rpm/
>> >> <-- build 317
>> >> http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm64/
>> >> <-- build 171
>> >>
>> >> Regards
>> >> Tom
>> >>
>> >> 2014-11-21 3:59 GMT+01:00 Daan Hoogland :
>> >>
>> >> > Hi All,
>> >> >
>> >> > I've created a 4.4.2 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.4
>> >> > Commit: e0420a6fec738d728bc59ba65bc5e12809bde0eb
>> >> >
>> >> > List of changes:
>> >> > `CLOUDSTACK-7887
>> >> > `_  fail to
>> >> > push snapshot to secondary storage if using multipart using swift...
>> >> >
>> >> > `CLOUDSTACK-7883
>> >> > `_  Allow
>> >> > infrastructure to handle delete of volume from DB...
>> >> >
>> >> > `CLOUDSTACK-7871
>> >> > `_  Fix update
>> >> > VirtualMachine/Template API to allow nic/disk controller details for
>> >> > ...
>> >> >
>> >> > `CLOUDSTACK-7855
>> >> > `_  Sec
>> >> > storage/network MTU should be on nic3 and not nic1...
>> >> >
>> >> > `CLOUDSTACK-7826
>> >> > `_  UI -
>> dialog
>> >> > widget - dependent dropdown field (dependsOn property specified) -
>> >> > f...
>> >> >
>> >> > `CLOUDSTACK-7822
>> >> > `_  test SSL
>> >> > cert expired...
>> >> >
>> >> > `CLOUDSTACK-7752
>> >> > `_  Management
>> >> > Server goes in infinite loop while creating a vm with tagged local
>> >> > da...
>> >> >
>> >> > `CLOUDSTACK-7722
>> >> > `_  add.label:
>> >> > Add button for tags show the label not "Add" text...
>> >> >
>> >> > `CLOUDSTACK-7246
>> >> > `_  VM
>> >> > deployment failed due to wrong in  script name createipalias.sh...
>> >> >
>> >> > Source release (checksums and signatures are available at the same
>> >> > location):
>> >> > https://dist.apache.org/repos/dist/dev/cloudstack/4.4.2
>> >> >
>> >> > PGP release keys (signed using 4096R/AA4736F3):
>> >> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>> >> >
>> >> > Vote will be open for 72 hours.
>> >> >
>> >> > 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)
>> >> >
>> >> >
>> >> > --
>> >> > Daan
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Regards,
>> >> Tomasz Zięba
>> >> Twitter: @TZieba
>> >> LinkedIn: pl.linkedin.com/pub/tomasz-zięba-ph-d/3b/7a8/ab6/
>> 
>> >> 
>> >> 

Re: [ACS44]release 4.4.2 release candidate RC20141121T0341 (#2)

[Pierre-Luc Dion]

ok, then, I will test 4.4.0 -> 4.4.1 -> 4.4.2.while doing 4.4.0 to
4.4.2 I've endup behing unable to create network because the systemvm
template was not mark as ready, although, ssvm and cpvm as been upgraded to
4.4.1 system-vm template without issue. also still need the manual mysql
query...




On Wed, Nov 26, 2014 at 12:14 PM, Nux!  wrote:

> I tried from 4.4.1; what problems are you seeing?
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> - Original Message -
> > From: "Pierre-Luc Dion" 
> > To: dev@cloudstack.apache.org
> > Sent: Wednesday, 26 November, 2014 17:11:10
> > Subject: Re: [ACS44]release 4.4.2 release candidate RC20141121T0341 (#2)
>
> > Did anyone try an upgrade from a fresh 4.4.0 to 4.4.2?  so far I did not
> > had too much success but before do a negative vote I want to make sure my
> > test env, is ok.
> >
> > thanks,
> >
> > PL
> >
> >
> > On Wed, Nov 26, 2014 at 3:46 AM, Nux!  wrote:
> >
> >> Pierre,
> >>
> >> In my case it did not, everything worked well, but do note I manually
> >> patched the sysvm tmpl for CLOUDSTACK-7781.
> >>
> >> HTH
> >> Lucian
> >>
> >> --
> >> Sent from the Delta quadrant using Borg technology!
> >>
> >> Nux!
> >> www.nux.ro
> >>
> >> - Original Message -
> >> > From: "Pierre-Luc Dion" 
> >> > To: dev@cloudstack.apache.org
> >> > Sent: Tuesday, 25 November, 2014 23:43:41
> >> > Subject: Re: [ACS44]release 4.4.2 release candidate RC20141121T0341
> (#2)
> >>
> >> > Does 4.4.2 require new set of systemvm compare to 4.4.1 ?
> >> >
> >> >
> >> > On Tue, Nov 25, 2014 at 11:15 AM, Tomasz Zięba 
> >> wrote:
> >> >
> >> >> +1
> >> >>
> >> >> for:
> >> >>
> >> >>
> http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-package-rpm/
> >> >> <-- build 317
> >> >>
> http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm64/
> >> >> <-- build 171
> >> >>
> >> >> Regards
> >> >> Tom
> >> >>
> >> >> 2014-11-21 3:59 GMT+01:00 Daan Hoogland :
> >> >>
> >> >> > Hi All,
> >> >> >
> >> >> > I've created a 4.4.2 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.4
> >> >> > Commit: e0420a6fec738d728bc59ba65bc5e12809bde0eb
> >> >> >
> >> >> > List of changes:
> >> >> > `CLOUDSTACK-7887
> >> >> > `_  fail to
> >> >> > push snapshot to secondary storage if using multipart using
> swift...
> >> >> >
> >> >> > `CLOUDSTACK-7883
> >> >> > `_  Allow
> >> >> > infrastructure to handle delete of volume from DB...
> >> >> >
> >> >> > `CLOUDSTACK-7871
> >> >> > `_  Fix
> update
> >> >> > VirtualMachine/Template API to allow nic/disk controller details
> for
> >> >> > ...
> >> >> >
> >> >> > `CLOUDSTACK-7855
> >> >> > `_  Sec
> >> >> > storage/network MTU should be on nic3 and not nic1...
> >> >> >
> >> >> > `CLOUDSTACK-7826
> >> >> > `_  UI -
> >> dialog
> >> >> > widget - dependent dropdown field (dependsOn property specified) -
> >> >> > f...
> >> >> >
> >> >> > `CLOUDSTACK-7822
> >> >> > `_  test
> SSL
> >> >> > cert expired...
> >> >> >
> >> >> > `CLOUDSTACK-7752
> >> >> > `_
> Management
> >> >> > Server goes in infinite loop while creating a vm with tagged local
> >> >> > da...
> >> >> >
> >> >> > `CLOUDSTACK-7722
> >> >> > `_
> add.label:
> >> >> > Add button for tags show the label not "Add" text...
> >> >> >
> >> >> > `CLOUDSTACK-7246
> >> >> > `_  VM
> >> >> > deployment failed due to wrong in  script name createipalias.sh...
> >> >> >
> >> >> > Source release (checksums and signatures are available at the same
> >> >> > location):
> >> >> > https://dist.apache.org/repos/dist/dev/cloudstack/4.4.2
> >> >> >
> >> >> > PGP release keys (signed using 4096R/AA4736F3):
> >> >> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >> >> >
> >> >> > Vote will be open for 72 hours.
> >> >> >
> >> >> > 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)
> >> >> >
> >> >> >
> >> >> > --
> >> >> > Daan
> >> >> >
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Regards,
> >> >> Tomasz Zięba
> >> >> Twitter: @TZieba
> >> >> LinkedIn: pl.linkedin.com/pub/tomasz-zięba-ph-d/3b/7a8/ab6/
> 
> >> 

Re: [ACS44]release 4.4.2 release candidate RC20141121T0341 (#2)

[Nux!]

What is your setup and zone type?

Some logs might help, too.

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Pierre-Luc Dion" 
> To: dev@cloudstack.apache.org
> Sent: Wednesday, 26 November, 2014 17:20:24
> Subject: Re: [ACS44]release 4.4.2 release candidate RC20141121T0341 (#2)

> ok, then, I will test 4.4.0 -> 4.4.1 -> 4.4.2.while doing 4.4.0 to
> 4.4.2 I've endup behing unable to create network because the systemvm
> template was not mark as ready, although, ssvm and cpvm as been upgraded to
> 4.4.1 system-vm template without issue. also still need the manual mysql
> query...
> 
> 
> 
> 
> On Wed, Nov 26, 2014 at 12:14 PM, Nux!  wrote:
> 
>> I tried from 4.4.1; what problems are you seeing?
>>
>> --
>> Sent from the Delta quadrant using Borg technology!
>>
>> Nux!
>> www.nux.ro
>>
>> - Original Message -
>> > From: "Pierre-Luc Dion" 
>> > To: dev@cloudstack.apache.org
>> > Sent: Wednesday, 26 November, 2014 17:11:10
>> > Subject: Re: [ACS44]release 4.4.2 release candidate RC20141121T0341 (#2)
>>
>> > Did anyone try an upgrade from a fresh 4.4.0 to 4.4.2?  so far I did not
>> > had too much success but before do a negative vote I want to make sure my
>> > test env, is ok.
>> >
>> > thanks,
>> >
>> > PL
>> >
>> >
>> > On Wed, Nov 26, 2014 at 3:46 AM, Nux!  wrote:
>> >
>> >> Pierre,
>> >>
>> >> In my case it did not, everything worked well, but do note I manually
>> >> patched the sysvm tmpl for CLOUDSTACK-7781.
>> >>
>> >> HTH
>> >> Lucian
>> >>
>> >> --
>> >> Sent from the Delta quadrant using Borg technology!
>> >>
>> >> Nux!
>> >> www.nux.ro
>> >>
>> >> - Original Message -
>> >> > From: "Pierre-Luc Dion" 
>> >> > To: dev@cloudstack.apache.org
>> >> > Sent: Tuesday, 25 November, 2014 23:43:41
>> >> > Subject: Re: [ACS44]release 4.4.2 release candidate RC20141121T0341
>> (#2)
>> >>
>> >> > Does 4.4.2 require new set of systemvm compare to 4.4.1 ?
>> >> >
>> >> >
>> >> > On Tue, Nov 25, 2014 at 11:15 AM, Tomasz Zięba 
>> >> wrote:
>> >> >
>> >> >> +1
>> >> >>
>> >> >> for:
>> >> >>
>> >> >>
>> http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-package-rpm/
>> >> >> <-- build 317
>> >> >>
>> http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm64/
>> >> >> <-- build 171
>> >> >>
>> >> >> Regards
>> >> >> Tom
>> >> >>
>> >> >> 2014-11-21 3:59 GMT+01:00 Daan Hoogland :
>> >> >>
>> >> >> > Hi All,
>> >> >> >
>> >> >> > I've created a 4.4.2 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.4
>> >> >> > Commit: e0420a6fec738d728bc59ba65bc5e12809bde0eb
>> >> >> >
>> >> >> > List of changes:
>> >> >> > `CLOUDSTACK-7887
>> >> >> > `_  fail to
>> >> >> > push snapshot to secondary storage if using multipart using
>> swift...
>> >> >> >
>> >> >> > `CLOUDSTACK-7883
>> >> >> > `_  Allow
>> >> >> > infrastructure to handle delete of volume from DB...
>> >> >> >
>> >> >> > `CLOUDSTACK-7871
>> >> >> > `_  Fix
>> update
>> >> >> > VirtualMachine/Template API to allow nic/disk controller details
>> for
>> >> >> > ...
>> >> >> >
>> >> >> > `CLOUDSTACK-7855
>> >> >> > `_  Sec
>> >> >> > storage/network MTU should be on nic3 and not nic1...
>> >> >> >
>> >> >> > `CLOUDSTACK-7826
>> >> >> > `_  UI -
>> >> dialog
>> >> >> > widget - dependent dropdown field (dependsOn property specified) -
>> >> >> > f...
>> >> >> >
>> >> >> > `CLOUDSTACK-7822
>> >> >> > `_  test
>> SSL
>> >> >> > cert expired...
>> >> >> >
>> >> >> > `CLOUDSTACK-7752
>> >> >> > `_
>> Management
>> >> >> > Server goes in infinite loop while creating a vm with tagged local
>> >> >> > da...
>> >> >> >
>> >> >> > `CLOUDSTACK-7722
>> >> >> > `_
>> add.label:
>> >> >> > Add button for tags show the label not "Add" text...
>> >> >> >
>> >> >> > `CLOUDSTACK-7246
>> >> >> > `_  VM
>> >> >> > deployment failed due to wrong in  script name createipalias.sh...
>> >> >> >
>> >> >> > Source release (checksums and signatures are available at the same
>> >> >> > location):
>> >> >> > https://dist.apache.org/repos/dist/dev/cloudstack/4.4.2
>> >> >> >
>> >> >> > PGP release keys (signed using 4096R/AA4736F3):
>> >> >> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>> >> >> >
>> >> >> > Vote will be open for 72 hours.
>> >> >> >
>> >> >> > For sanity in tallying the vote, can PMC members please be

Re: Moving ec2stack and gstack to the cloudstack repos.

[Chiradeep Vittal]

I’m +1 on this. I hope the original contributors and developers continue to 
invest energy into maintaining it (rather than hoping that the community comes 
for free, just as a side-effect of being in ACS).

From: Ian Duffy mailto:i...@ianduffy.ie>>
Reply-To: "dev@cloudstack.apache.org" 
mailto:dev@cloudstack.apache.org>>
Date: Wednesday, November 26, 2014 at 4:46 AM
To: "dev@cloudstack.apache.org" 
mailto:dev@cloudstack.apache.org>>
Subject: Re: Moving ec2stack and gstack to the cloudstack repos.

I think unit tests are great for type checking and the like, but are
there any integration tests?

At the moment there aren't any, we could add some using eutester very
easily and chain it onto the current CI tasks. As Sebastien has mentioned
earlier in this thread he has already looked at doing this a little bit.

Not to sound tit-for-tat but awsapi has same issue and has much less unit
testing.

Any plans to add any?

Its not *my personal* immediate plan, but isn't that the beauty of open
source and community building? The project is open to everybody to
contribute, if you see value for integration tests to be added and wish to
do it then go ahead. Its a donation of code, not a we'll supply xyz
software to do xyz service and be the sole maintainers of it forever. If we
want things that work we need community(user and dev) support, want and
time.

For me EC2Stack had two primary goals:

1) Make contributing easy, we wanted to produce clean(ish) code that was
easily extendable by the community so we could get some support if/when it
takes off. AWSAPI is a bit terrifying to look at, there's a large amount of
auto generated code and its a bit scary at first.

In brief to add a new API command:
- Open controllers.py, add a new API call into the actions object: e.g.
'AttachVolume': volumes.attach_volume,
- Head over to the referenced module/function and fill it out e.g.
https://github.com/BroganD1993/ec2stack/blob/master/ec2stack/providers/cloudstack/volumes.py
- Done.

2) Make it portable. We didn't want the AWS compatibility layer to always
have to be hosted by the Cloudstack provider. We wanted the flexibility to
use it against any Cloudstack 4.0.0> API. This was a success and we
successfully use EC2Stack against ExoScale as shown in the earlier
referenced screencast.

Hope this answers your questions,

Ian


On 26 November 2014 at 02:47, ChunFeng 
mailto:chunf...@domolo.com>> wrote:

hi all,


I need help for  a clean picture about  the umbrella projects of
cloudstack:
such as :
1. the umbrella project links in cloudstack.org homepage
2. the source code structure and relations with cloudstack source code in
git repos.
3. the rules for us to agree one as umbrella projects



BTW,  is there any others umbrella proejcts as cloudmonkey ?


--
Regards,


ChunFeng









-- Original --
From:  "Sebastien Goasguen"mailto:run...@gmail.com>>;
Date:  Tue, Nov 25, 2014 06:29 AM
To:  "dev"mailto:dev@cloudstack.apache.org>>;

Subject:  Re: Moving ec2stack and gstack to the cloudstack repos.



On Nov 24, 2014, at 5:05 PM, Chiradeep Vittal 
mailto:chiradeep.vit...@citrix.com>>
wrote:

> I do see a bug fix this year from Likitha  and the fact that Hugo etc
are making fixes is positive as well.
> But, the end state we desire is (a) good AWSAPI implementation with
automated tests, not (b) 2 AWSAPI implementations with no tests!
>

time for bed here, but to keep the conversation going, couple things:

Hugo is fixing coverity issues kind of automatically, I don't think it
represents a need.
One fix from Likitha and one applied patch from me in a year is really
slim.

We don't test the current awsapi during the release process or upgrade, so
I actually have no clue if it's working with 4.3 and 4.4.

Right now I don't see tests for the current awsapi, at least not on
jenkins.buildacloud.org.
Current awsapi also includes S3 stuff which I think we can all agree is
confusing and unused since it's really an interface to an NFS store and not
a distributed object store.

So the choice for me is between:

-current awsapi, not clearly maintained, without tests and which state in
the release is unknown

and

-a new implementation < 6 months old, smaller code base, up to date with
AWS version number, tested manually with boto, eutester and awscli and with
99% unit test coverage.


> —
> Chiradeep
>
> From: Sebastien Goasguen 
> mailto:run...@gmail.com>>
> Reply-To: 
> "dev@cloudstack.apache.org"
mailto:dev@cloudstack.apache.org>>
> Date: Monday, November 24, 2014 at 1:36 PM
> To: 
> "dev@cloudstack.apache.org"
>  <
dev@cloudstack.apache.org>
> Subject: Re: Moving ec

Re: [DISCUSS] Major business logic refactoring: Move from Account to UserAccount

[Chiradeep Vittal]

Agreed, you can’t just break the old parameters. But an alternate version of 
the API?
listVirtualMachines (idType1=id1, idType2=id2, idType3=id3,….) [existing]
listVirtualMachines(Filter1.Name=idType1, Filter1.Value.1=id1, ….) [new]

From: Rohit Yadav mailto:rohit.ya...@shapeblue.com>>
Reply-To: "dev@cloudstack.apache.org" 
mailto:dev@cloudstack.apache.org>>
Date: Wednesday, November 26, 2014 at 12:56 AM
To: "dev@cloudstack.apache.org" 
mailto:dev@cloudstack.apache.org>>
Subject: Re: [DISCUSS] Major business logic refactoring: Move from Account to 
UserAccount

Hi Chiradeep,

On 26-Nov-2014, at 4:32 am, Chiradeep Vittal 
mailto:chiradeep.vit...@citrix.com>> wrote:

Instead of adding yet another parameter, could we look into adding a generic 
filter as in:
http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-DescribeInstances.html

But there already are so many parameters on the API, adding a filter param 
(map) will break semantics? May be we should do this for the next (restful) API 
layer we create?

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 88 262 30892 | 
rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab



Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Software 
Engineering
CloudStack Infrastructure 
Support
CloudStack Bootcamp Training Courses

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 SA Pty Ltd is a company 
registered by The Republic of South Africa and is traded under license from 
Shape Blue Ltd. ShapeBlue is a registered trademark.

Jenkins build is back to stable : simulator-singlerun #700

[jenkins]

See 

Re: [DISCUSS] LTS Releases

[Pierre-Luc Dion]

I'm not really in favor of LTS support, it's a good idea, but not sure it
can be backed by the community?[open question here ;)]. I don't think it
fit in our current model for few reasons:

- Upgrade path might become impossible as patches become part of multiple
versions. We could end up with problem at database schema with the current
db upgrade model.

- Enforcing user to stay on a legacy ACS release disallow usage of future
hypervisor version, Guest OSes and new hardware used by hypervisors. As
hypervisors will become out of date, they won't be able to support new
Guest OSes and new hardware.

- I think the initiative would dilute the effort on the upgrade path and
making sure the upgrade path is easy and always work. Since 4.3.1 as been
released after 4.4.0, do we know if a 4.3.1 can be upgrade to 4.4.1 or
event 4.5?

- Contribution to ACS and bugfixing become nightmare  as bugfix might end
up in 4 branches (4.3, 4.4, 4.5, master,...)

Why not as community (let's face it, not very a big one) we all focus on
the next 4.5 version, make sure it's properly tested, make sure upgrade
"just work"  and have ACS 4 as the LTS ? ;-)

I know a production system is not likely to run the latest version of ACS
and upgrade of such a prod tool can occur maybe one or two time a year.

That's just my opinion on the subject, nothing against anyone or to block
the idea.



On Tue, Nov 25, 2014 at 11:35 AM, Hugo Trippaers  wrote:

> Top posting here as my remarks are mainly on the original topic.
>
> I’m not in favor of supporting LTS releases as a community. The reasoning
> here is that there is a huge chance that we will fragment the community in
> people that just want to work on the latest and greatest and some other
> folks who are trying to keep older releases from being updated with newer
> fixes. It requires a lot of dedicated commitment to keep an LTS release
> going. Particularly if you yourself are already working with a newer
> release in your environment. So from a personal standpoint i can almost
> guarantee that i will probably not spend the time and effort of back
> porting any fixes i do to older versions of CloudStack.
>
> That doesn’t mean that it can’t happen. If people are willing to take
> charge of an LTS branch and are willing to do the work to back port fixes
> where appropriate i would happily support them and even try to test the
> releases so we can have an official release.
>
> New developers might also be scared by the fact that a fix they make has
> to be supported on multiple branches and might decide not to commit such a
> fix because of the work involved. With the rate of change in the code at
> the moment this is also very hard for seasoned developers, so much little,
> but important stuff changes all the time that back porting is very
> difficult. It is an open source project and generally people will want to
> focus on the latest and greatest and just get their features in. I’m
> already regularly having some trouble back porting between master and 4.5.
> Consider back porting to master, 4.5 and 4.3 as well and having to test
> each branch.
>
> Basically my point is, everyone who wants to LTS support a certain branch
> is free to do so. Whether or not other contributors or committers will want
> to do that is their choice. As a community we should not make any promises
> about LTS support for a certain branch.
>
> Cheers,
>
> Hugo
>
>
>
>
>
> > On 25 nov. 2014, at 16:16, Rohit Yadav 
> wrote:
> >
> > Hey Daan,
> >
> >> On 25-Nov-2014, at 7:26 pm, Daan Hoogland 
> wrote:
> >>
> >> That is worrying, Rohit. As the rest of your mail is already a vote of
> >> distrust, this part says we should not release 4.4.2 as it contains
> >> regressions.
> >
> > Looks like you skimmed my email and missed the following from my
> previous email:
> > “Note: This is not to say that 4.4.x is not stable, we’re simply saying
> we recommend 4.3.x because we have a confidence of its stability and we
> encourage serious CloudStack users to use it.”
> >
> > 4.4.x is probably the greatest ACS feature release ever but I would
> still recommend conservative users (who consult me) to stick to 4.3.x for
> production since we know it just works with least amount of pain. The other
> issue is I know a lot of people who are on ACS 4.3.x still (including
> ShapeBlue’s customers) want to have bugfix releases and they may not want
> to migrate to 4.4.x right now since 4.5.x is about 2–3 months away.
> >
> > ACS when consumed by enterprise companies has a typical lifecycle that
> lasts at least 6 months, that means someone needs to support it, therefore
> the idea of official LTS releases.
> >
> >> This is a very bad signal to users and the rest of the
> >> community. What you are saying is (you in transitive form), 'we won't
> >> port fixes to 4.4 but only to 4.3 so upgrade to newer 4.3 versions and
> >> not to a 4.4 version. You have the right to do so but I don't like it.
> >
> > In any form I did not say anything about n

Re: Review Request 24991: CLOUDSTACK-6697: BigSwitchVns plugin update

[Kuang-Ching Wang]

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

(Updated Nov. 26, 2014, 10:52 p.m.)


Review request for cloudstack, Chiradeep Vittal, David Nalley, Sebastien 
Goasguen, and Hugo Trippaers.


Changes
---

further enhancement


Repository: cloudstack-git


Description (updated)
---

CLOUDSTACK-6697: Big Switch network plugin update
1. provide compatibility with the Big Cloud Fabric (BCF) controller
   L2 Connectivity Service in both VPC and non-VPC modes
2. virtual network terminology updates: VNS --> BCF_SEGMENT
3. uses HTTPS with trust-always certificate handling
4. topology sync support with BCF controller
5. support multiple (two) BCF controllers with HA
6. support VM migration


Diffs (updated)
-

  api/src/com/cloud/network/Network.java 
c5a9bf286df8d502a6ca33661fb52ee717643566 
  api/src/com/cloud/network/PhysicalNetwork.java 
7c9349d932771fdbecc4a0b1ae4cad28b3d67857 
  client/WEB-INF/classes/resources/messages.properties 
3228578ce81a826f49166a72a6c67143fb12c95d 
  client/WEB-INF/classes/resources/messages_fr_FR.properties 
54dc6215a8339b9f8c2bad9fe4c3ed18b4a702e7 
  client/WEB-INF/classes/resources/messages_ja_JP.properties 
1962e92a4cf47978dae35a3d2b090b4c1765fecb 
  client/WEB-INF/classes/resources/messages_ko_KR.properties 
ced576cb23598e7d3e5005bc24c2adf20b66a826 
  client/WEB-INF/classes/resources/messages_nl_NL.properties 
86653a5f5144c75e67b5a6f02c47d37bd5a71ef0 
  client/WEB-INF/classes/resources/messages_pt_BR.properties 
fa77633a650f1b37d8398a8936bbf84f5b4a40e3 
  client/WEB-INF/classes/resources/messages_ru_RU.properties 
7f57daa58bef379ddb47acb88965d0defe32ad73 
  client/WEB-INF/classes/resources/messages_zh_CN.properties 
217849582b41cb2c63a0e305e5613af6f659d11d 
  client/pom.xml 6803f9a11fd2c80523ea16bdd35f2a4d163f953c 
  client/tomcatconf/commands.properties.in 
a87d1677f24657299ec24d4ce9df9a180a62bd0c 
  engine/schema/src/com/cloud/user/dao/VmDiskStatisticsDaoImpl.java 
e1136d3cf567b73fd1198181aea4d6995df6b78a 
  plugins/network-elements/bigswitch-vns/pom.xml 
afb267cdb5bc52aea23bc6739ea21d8f52e94ede 
  
plugins/network-elements/bigswitch-vns/resources/META-INF/cloudstack/vns/module.properties
 5783d38e5cb78be0d418c80981246d721d18b62a 
  
plugins/network-elements/bigswitch-vns/resources/META-INF/cloudstack/vns/spring-vns-context.xml
 d5bb92afe3d3051dbdd4b4d49698c313c77d255f 
  
plugins/network-elements/bigswitch-vns/src/com/cloud/agent/api/CreateVnsNetworkAnswer.java
 e950abe3bed85b75a20be2b8c4537a2fbd6be39e 
  
plugins/network-elements/bigswitch-vns/src/com/cloud/agent/api/CreateVnsNetworkCommand.java
 534bb7f9f9154a652a20310fe020bddc4249ef54 
  
plugins/network-elements/bigswitch-vns/src/com/cloud/agent/api/CreateVnsPortAnswer.java
 82c2fe90d63e0148bca8de9ce8612e4dd53cf735 
  
plugins/network-elements/bigswitch-vns/src/com/cloud/agent/api/CreateVnsPortCommand.java
 c3b9a9d6d9504e34cbe1294ac640f56aab101395 
  
plugins/network-elements/bigswitch-vns/src/com/cloud/agent/api/DeleteVnsNetworkAnswer.java
 72ac98ac9e0a1ae4858019e3baccc160300e24bf 
  
plugins/network-elements/bigswitch-vns/src/com/cloud/agent/api/DeleteVnsNetworkCommand.java
 6cf169bbfc97b57561af729aef297c76230fd118 
  
plugins/network-elements/bigswitch-vns/src/com/cloud/agent/api/DeleteVnsPortAnswer.java
 076b187fdf48cf776902dc9a91dc26e00396158a 
  
plugins/network-elements/bigswitch-vns/src/com/cloud/agent/api/DeleteVnsPortCommand.java
 0cae01d471dd9c5c504002c24f865ded59812d9e 
  
plugins/network-elements/bigswitch-vns/src/com/cloud/agent/api/StartupBigSwitchVnsCommand.java
 8310b0763708c3f049ef4ce427d09f0c07cd05b3 
  
plugins/network-elements/bigswitch-vns/src/com/cloud/agent/api/UpdateVnsPortAnswer.java
 39cd26649c9bb0c4993f55bef65edfc326c4ceda 
  
plugins/network-elements/bigswitch-vns/src/com/cloud/agent/api/UpdateVnsPortCommand.java
 40f09207606115a5d0ec7f9378c4c52d16405dfd 
  
plugins/network-elements/bigswitch-vns/src/com/cloud/api/commands/AddBigSwitchVnsDeviceCmd.java
 5c6f555c8a40a4b785aed6fdfa743131006be209 
  
plugins/network-elements/bigswitch-vns/src/com/cloud/api/commands/DeleteBigSwitchVnsDeviceCmd.java
 1e2155dcd899bc11f9e9463cec432c020751e905 
  
plugins/network-elements/bigswitch-vns/src/com/cloud/api/commands/ListBigSwitchVnsDevicesCmd.java
 4cde78e503935f7ba3b4a90a6f4568f0dd32c7ab 
  
plugins/network-elements/bigswitch-vns/src/com/cloud/api/commands/VnsConstants.java
 7942b6f2be3467465334b0628577b87564dbdab2 
  
plugins/network-elements/bigswitch-vns/src/com/cloud/api/response/BigSwitchVnsDeviceResponse.java
 790ac9c6afbee9156cb8d26ee2a2b5980fe4ce18 
  
plugins/network-elements/bigswitch-vns/src/com/cloud/network/BigSwitchVnsDeviceVO.java
 01b5d49a90bb4428716d6b9c344d4ccfc97fb34f 
  
plugins/network-elements/bigswitch-vns/src/com/cloud/network/bigswitch/AttachmentData.java
 f1866e2621b6f9c19e4a9be310791b086ce3a350 
  
p

Build failed in Jenkins: cloudstack-4.3-maven-build #658

[jenkins]

See 

--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on cloudstack-buildslave-centos6-87d 
(cloudstack-buildslave-centos6) in workspace 

 > /usr/bin/git rev-parse --is-inside-work-tree # timeout=400
Fetching changes from the remote Git repository
 > /usr/bin/git config remote.origin.url git://git.apache.org/cloudstack.git # 
 > timeout=400
Fetching upstream changes from git://git.apache.org/cloudstack.git
 > /usr/bin/git --version # timeout=400
 > /usr/bin/git fetch --tags --progress git://git.apache.org/cloudstack.git 
 > +refs/heads/*:refs/remotes/origin/*
FATAL: Failed to fetch from git://git.apache.org/cloudstack.git
hudson.plugins.git.GitException: Failed to fetch from 
git://git.apache.org/cloudstack.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:647)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:889)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:914)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1258)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528)
at hudson.model.Run.execute(Run.java:1759)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
Caused by: hudson.plugins.git.GitException: Command "/usr/bin/git fetch --tags 
--progress git://git.apache.org/cloudstack.git 
+refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: git.apache.org[0: 192.87.106.249]: errno=Connection timed out
fatal: unable to connect a socket (Connection timed out)

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1435)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1223)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:85)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:280)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
at hudson.remoting.UserRequest.perform(UserRequest.java:121)
at hudson.remoting.UserRequest.perform(UserRequest.java:49)
at hudson.remoting.Request$2.run(Request.java:324)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:701)
at ..remote call to cloudstack-buildslave-centos6-87d(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)
at hudson.remoting.Channel.call(Channel.java:752)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146)
at sun.reflect.GeneratedMethodAccessor172.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132)
at sun.proxy.$Proxy109.execute(Unknown Source)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:645)
... 10 more

Jenkins build is back to normal : cloudstack-4.3-maven-build #659

[jenkins]

See 

Build failed in Jenkins: build-master #1967

[jenkins]

See 

Changes:

[amogh.vasekar] CLOUDSTACK-7977

--
[...truncated 22781 lines...]
206/405 KB   
210/405 KB   
214/405 KB   
218/405 KB   
222/405 KB   
226/405 KB   
229/405 KB   
233/405 KB   
237/405 KB   
241/405 KB   
245/405 KB   
249/405 KB   
253/405 KB   
257/405 KB   
261/405 KB   
265/405 KB   
269/405 KB   
273/405 KB   
277/405 KB   
281/405 KB   
285/405 KB   
289/405 KB   
293/405 KB   
297/405 KB   
301/405 KB   
305/405 KB   
309/405 KB   
313/405 KB   
317/405 KB   
321/405 KB   
325/405 KB   
329/405 KB   
333/405 KB   
337/405 KB   
338/405 KB   
341/405 KB   
345/405 KB   
349/405 KB   
353/405 KB   
357/405 KB   
361/405 KB   
365/405 KB   
369/405 KB   
373/405 KB   
377/405 KB   
381/405 KB   
385/405 KB   
389/405 KB   
393/405 KB   
397/405 KB   
401/405 KB   
405/405 KB   
405/405 KB   
 
Downloaded: http://repo.maven.apache.org/maven2/jstl/jstl/1.2/jstl-1.2.jar (405 
KB at 4815.8 KB/sec)
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
cloud-engine-network ---
[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:compile (default-compile) @ 
cloud-engine-network ---
[INFO] Compiling 1 source file to 

[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-usage ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloud-engine-orchestration ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.7:run (generate-resource) @ cloud-usage ---
[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] 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 19 source files to 

[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
cloud-engine-network ---
[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-network ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12:test (default-test) @ 
cloud-engine-network ---
[INFO] Surefire report directory: 


---
 T E S T S
---

Results :

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

[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] Reactor Summary:
[INFO] 
[INFO] Apache CloudStack Developer Tools - Checkstyle Configuration  SUCCESS 
[1.844s]
[INFO] Apache CloudStack . SUCCESS [1.471s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [2.536s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [5.104s]
[INFO] Apache CloudStack Utils ... SUCCESS [14.241s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.205s]
[INFO] Apache Clou

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

[jenkins]

See 

Review Request 28489: CLOUDSTACK-7978 : Fixed the script 'test_egress_rules.py' - Zone Network Type Information should to be passed to VirtualMachine create method

[Chandan Purushothama]

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

Review request for cloudstack and sangeetha hariharan.


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


Repository: cloudstack-git


Description
---

Currently, test cases in the test suite do not pass the Zone Network Type to 
the Virtual Machine class create method. This doesn't cause any problem with 
majority of the configurations except EIP-ELB Configuration. Hence Zone Network 
Type Information should be passed consciously to the create method to cover 
EIP-ELB Configuration.


Diffs
-

  test/integration/component/test_egress_rules.py 0f05c07 

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


Testing
---

Executed One Test to prove the fix:

Test authorize ingress rule ... === TestName: test_authorizeIngressRule | 
Status : SUCCESS ===
ok

--
Ran 1 test in 126.613s

OK


Thanks,

Chandan Purushothama

Review Request 28490: CLOUDSTACK-7979 : Fixed the script 'test_security_groups.py' - Zone Network Type Information should to be passed to VirtualMachine create method

[Chandan Purushothama]

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

Review request for cloudstack and sangeetha hariharan.


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


Repository: cloudstack-git


Description
---

Currently, test cases in the test suite do not pass the Zone Network Type to 
the Virtual Machine class create method. This doesn't cause any problem with 
majority of the configurations except EIP-ELB Configuration. Hence Zone Network 
Type Information should be passed consciously to the create method to cover 
EIP-ELB Configuration.


Diffs
-

  test/integration/component/test_security_groups.py 89317f4 

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


Testing
---

Executed One Test to prove the fix. This test belongs to a different test 
suite. But the fix is the same:

Test authorize ingress rule ... === TestName: test_authorizeIngressRule | 
Status : SUCCESS ===
ok


Ran 1 test in 126.613s

OK


Thanks,

Chandan Purushothama

Review Request 28492: CLOUDSTACK-7980 : Fixed the script '/maint/test_egress_rules_host_maintenance.py' - Zone Network Type Information should to be passed to VirtualMachine create method

[Chandan Purushothama]

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

Review request for cloudstack and sangeetha hariharan.


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


Repository: cloudstack-git


Description
---

Currently, test cases in the test suite do not pass the Zone Network Type to 
the Virtual Machine class create method. This doesn't cause any problem with 
majority of the configurations except EIP-ELB Configuration. Hence Zone Network 
Type Information should be passed consciously to the create method to cover 
EIP-ELB Configuration.


Diffs
-

  test/integration/component/maint/test_egress_rules_host_maintenance.py 
a27ada3 

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


Testing
---

Executed One Test to prove the fix. This test belongs to a different test 
suite. But the fix is the same:

Test authorize ingress rule ... === TestName: test_authorizeIngressRule | 
Status : SUCCESS ===
ok

Ran 1 test in 126.613s

OK


Thanks,

Chandan Purushothama

Jenkins build became unstable: simulator-singlerun #702

[jenkins]

See 

Re: Review Request 28489: CLOUDSTACK-7978 : Fixed the script 'test_egress_rules.py' - Zone Network Type Information should to be passed to VirtualMachine create method

[sangeetha hariharan]

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

Ship it!


Ship It!

- sangeetha hariharan


On Nov. 27, 2014, 12:09 a.m., Chandan Purushothama wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28489/
> ---
> 
> (Updated Nov. 27, 2014, 12:09 a.m.)
> 
> 
> Review request for cloudstack and sangeetha hariharan.
> 
> 
> Bugs: CLOUDSTACK-7978
> https://issues.apache.org/jira/browse/CLOUDSTACK-7978
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Currently, test cases in the test suite do not pass the Zone Network Type to 
> the Virtual Machine class create method. This doesn't cause any problem with 
> majority of the configurations except EIP-ELB Configuration. Hence Zone 
> Network Type Information should be passed consciously to the create method to 
> cover EIP-ELB Configuration.
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_egress_rules.py 0f05c07 
> 
> Diff: https://reviews.apache.org/r/28489/diff/
> 
> 
> Testing
> ---
> 
> Executed One Test to prove the fix:
> 
> Test authorize ingress rule ... === TestName: test_authorizeIngressRule | 
> Status : SUCCESS ===
> ok
> 
> --
> Ran 1 test in 126.613s
> 
> OK
> 
> 
> Thanks,
> 
> Chandan Purushothama
> 
>

Re: Review Request 28490: CLOUDSTACK-7979 : Fixed the script 'test_security_groups.py' - Zone Network Type Information should to be passed to VirtualMachine create method

[sangeetha hariharan]

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

Ship it!


Ship It!

- sangeetha hariharan


On Nov. 27, 2014, 12:14 a.m., Chandan Purushothama wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28490/
> ---
> 
> (Updated Nov. 27, 2014, 12:14 a.m.)
> 
> 
> Review request for cloudstack and sangeetha hariharan.
> 
> 
> Bugs: CLOUDSTACK-7979
> https://issues.apache.org/jira/browse/CLOUDSTACK-7979
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Currently, test cases in the test suite do not pass the Zone Network Type to 
> the Virtual Machine class create method. This doesn't cause any problem with 
> majority of the configurations except EIP-ELB Configuration. Hence Zone 
> Network Type Information should be passed consciously to the create method to 
> cover EIP-ELB Configuration.
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_security_groups.py 89317f4 
> 
> Diff: https://reviews.apache.org/r/28490/diff/
> 
> 
> Testing
> ---
> 
> Executed One Test to prove the fix. This test belongs to a different test 
> suite. But the fix is the same:
> 
> Test authorize ingress rule ... === TestName: test_authorizeIngressRule | 
> Status : SUCCESS ===
> ok
> 
> 
> Ran 1 test in 126.613s
> 
> OK
> 
> 
> Thanks,
> 
> Chandan Purushothama
> 
>

Re: Review Request 28492: CLOUDSTACK-7980 : Fixed the script '/maint/test_egress_rules_host_maintenance.py' - Zone Network Type Information should to be passed to VirtualMachine create method

[sangeetha hariharan]

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

Ship it!


Ship It!

- sangeetha hariharan


On Nov. 27, 2014, 12:19 a.m., Chandan Purushothama wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/28492/
> ---
> 
> (Updated Nov. 27, 2014, 12:19 a.m.)
> 
> 
> Review request for cloudstack and sangeetha hariharan.
> 
> 
> Bugs: CLOUDSTACK-7980
> https://issues.apache.org/jira/browse/CLOUDSTACK-7980
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Currently, test cases in the test suite do not pass the Zone Network Type to 
> the Virtual Machine class create method. This doesn't cause any problem with 
> majority of the configurations except EIP-ELB Configuration. Hence Zone 
> Network Type Information should be passed consciously to the create method to 
> cover EIP-ELB Configuration.
> 
> 
> Diffs
> -
> 
>   test/integration/component/maint/test_egress_rules_host_maintenance.py 
> a27ada3 
> 
> Diff: https://reviews.apache.org/r/28492/diff/
> 
> 
> Testing
> ---
> 
> Executed One Test to prove the fix. This test belongs to a different test 
> suite. But the fix is the same:
> 
> Test authorize ingress rule ... === TestName: test_authorizeIngressRule | 
> Status : SUCCESS ===
> ok
> 
> Ran 1 test in 126.613s
> 
> OK
> 
> 
> Thanks,
> 
> Chandan Purushothama
> 
>

What is this BaremetalDhcpProvider?

[Nux!]

Hi,

I'm playing with various network settings in ACS, today I was trying to create 
a network that uses BaremetalDhcpProvider.
What is this provider? `list networkserviceproviders` doesn't say anything 
about Bare metal.

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

Build failed in Jenkins: simulator-singlerun #704

[jenkins]

See 

Changes:

[sangeetha.hariharan] CLOUDSTACK-7978 : Fixed the script 'test_egress_rules.py' 
- Zone Network Type Information should to be passed to VirtualMachine create 
method

[sangeetha.hariharan] CLOUDSTACK-7979 : Fixed the script 
'test_security_groups.py' - Zone Network Type Information should to be passed 
to VirtualMachine create method

[sangeetha.hariharan] CLOUDSTACK-7980 : Fixed the script 
'/maint/test_egress_rules_host_maintenance.py' - Zone Network Type Information 
should to be passed to VirtualMachine create method

--
[...truncated 575 lines...]
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at 
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at 
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
2014-11-26 20:35:20,446 ERROR [utils.rest.RESTServiceConnector] (main:) Failed 
to retrieve object : null
2014-11-26 20:35:20,453 ERROR [utils.rest.RESTServiceConnector] (main:) 
IOException caught while trying to connect to the REST Service
java.io.IOException
at 
com.cloud.utils.rest.RESTValidationStrategy.executeMethod(RESTValidationStrategy.java:106)
at 
com.cloud.utils.rest.RESTServiceConnector.executeMethod(RESTServiceConnector.java:277)
at 
com.cloud.utils.rest.RESTServiceConnector.executeUpdateObject(RESTServiceConnector.java:183)
at 
com.cloud.utils.rest.RESTServiceConnectorTest.testExecuteUpdateObjectException(RESTServiceConnectorTest.java:273)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:19)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at 
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at 
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
Tests run

Jenkins build is still unstable: simulator-singlerun #703

[jenkins]

See 

Jenkins build is unstable: simulator-singlerun #705

[jenkins]

See 

Jenkins build is still unstable: simulator-singlerun #706

[jenkins]

See 

[GitHub] cloudstack pull request: Add improved support for packaging CloudS...

[damodarreddy]

Github user damodarreddy commented on the pull request:

https://github.com/apache/cloudstack/pull/46#issuecomment-64747208
  
No Objections


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

Fwd: CloudStack Job offering @exoscale

[sebgoa]

I think this is legitimate on dev@

Note that there are also jobs available at interoute.

Begin forwarded message:

> From: "Coetsier, Antoine" 
> Subject: CloudStack Job offering @exoscale
> Date: November 26, 2014 5:20:57 PM GMT+01:00
> To: "us...@cloudstack.apache.org" 
> Reply-To: us...@cloudstack.apache.org
> 
> Hello All,
> 
> We are looking for a developer that already has some knowledge of CloudStack 
> to join our team at Exoscale. Trendy topics about network 
> functions/distributed LB in CS for this full time job.
> 
> This is based in Switzerland of course. The job description is here: 
> https://www.exoscale.ch/jobs/
> Get in touch with us at: hr -AT- exoscale.ch
> 
> Thank you,
> --
> Antoine COETSIER – EXOSCALE CEO