Re: Help with JUnits

[Mike Tutkowski]

So, yeah, unit tests are written in Java while integration tests are
written in Python using Marvin...if that helps clarify things a bit more.

On Tue, Jan 19, 2016 at 12:45 AM, B Prakash  wrote:

> Thanks Mike, I read through the link and also saw the video, this answers
> part of my question about executing the unit tests.  The other part of the
> questions still remains ie were are junits written in Java for this class
> and operation UserVmManagerImpl.commitUserVm.
>
> How do we check the junit coverage for a particular class and
> implementation in it?  Where do I start looking for them and confirm if
> they exist?
>
> 
> From: Mike Tutkowski 
> Sent: Monday, January 18, 2016 11:51 PM
> To: dev@cloudstack.apache.org
> Subject: Re: Help with JUnits
>
> Here's a video of a presentation I gave about Marvin (from CloudStack Days
> in Austin last year):
>
> https://www.youtube.com/watch?v=N_eKBA_TeOs
>
> On Mon, Jan 18, 2016 at 9:49 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
> > Does this help?
> >
> >
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> >
> > On Mon, Jan 18, 2016 at 8:56 PM, B Prakash  wrote:
> >
> >> Hi,
> >>
> >>
> >> Please can someone help me with identifying and amending junits for
> >> UserVmManagerImpl.commitUserVm?  I see a test class called
> >> UserVmManagerTest but I dont see a good junits coverage here.  Also
> link in
> >> the 'Developer > Testing > Unit testing with JUnit and Spring' doesnt
> give
> >> out lot of details on junits.
> >>
> >>   1.  Am I looking at the right place for junits for the class
> >> UserVmManagerImpl.commitUserVm?
> >>   2.  Is there any other link that provides more details on JUnits?
> >>   3.  Any document or resource explaing cloudstack JUnit implementation
> >> in greater detail would be of great help.
> >>   4.  If I want to track junit of this class, how do I track and execute
> >> them?
> >>
> >>
> >> Regards,
> >>
> >> Prakash
> >>
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the cloud
> > *™*
> >
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud
> *™*
>



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

[GitHub] cloudstack pull request: CLOUDSTACK-9132: API createVolume takes e...

[milamberspace]

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

https://github.com/apache/cloudstack/pull/1319#discussion_r50086554
  
--- Diff: ui/scripts/docs.js ---
@@ -1008,7 +1008,7 @@ cloudStack.docs = {
 },
 // Add volume
 helpVolumeName: {
-desc: 'Give the volume a unique name so you can find it later.',
+desc: 'Give a unique volume name. If it is not provided, a name 
will be generated randomly.',
--- End diff --

Yes will not a -1. Better if the string is localize in the current PR, but 
not a -1 if not.


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

Build failed in Jenkins: build-master-slowbuild #3022

[jenkins]

See 

--
[...truncated 28713 lines...]
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.1:findbugs (findbugs) @ cloud-quickcloud 
---
[INFO] 
[INFO] <<< findbugs-maven-plugin:3.0.1:check (cloudstack-findbugs) @ 
cloud-quickcloud <<<
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.1:check (cloudstack-findbugs) @ 
cloud-quickcloud ---
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:instrument (default-cli) @ 
cloud-quickcloud ---
[WARNING] No files to instrument.
[INFO] NOT adding cobertura ser file to attached artifacts list.
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
cloud-quickcloud ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @ 
cloud-quickcloud ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ cloud-quickcloud 
---
[INFO] 
[INFO] <<< cobertura-maven-plugin:2.6:cobertura (default-cli) @ 
cloud-quickcloud <<<
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:cobertura (default-cli) @ 
cloud-quickcloud ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache CloudStack Developer Tools - Checkstyle Configuration  SUCCESS 
[1.793s]
[INFO] Apache CloudStack . SUCCESS [2.097s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.784s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.843s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:31.050s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.100s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [53.237s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.564s]
[INFO] Apache CloudStack API . SUCCESS [1:48.505s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.272s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [30.043s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.090s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.186s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.837s]
[INFO] Apache CloudStack Core  SUCCESS [1:22.062s]
[INFO] Apache CloudStack Agents .. SUCCESS [35.861s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.849s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.034s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:06.837s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.387s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.182s]
[INFO] Apache CloudStack Server .. SUCCESS [4:15.170s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [38.585s]
[INFO] Apache CloudStack Usage Server  SUCCESS [43.690s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:22.688s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.074s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.467s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [55.063s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [50.494s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [29.596s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.169s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [26.804s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [22.785s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [34.786s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.384s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [7.862s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.970s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [27.653s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.437s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[37.328s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.300s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.348s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [15.986s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[17.553s]
[INFO] Apache Cloud

[GitHub] cloudstack pull request: CLOUDSTACK-9132: API createVolume takes e...

[DaanHoogland]

Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/1319#issuecomment-172807056
  
LGTM, the one error in the files below is a known error in the test 
environment and unrelated. This has been reviewed extensively.


[1319.network.results.txt](https://github.com/apache/cloudstack/files/95699/1319.network.results.txt)

[1319.vpc.results.txt](https://github.com/apache/cloudstack/files/95700/1319.vpc.results.txt)



---
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: [PROPOSAL] LTS Release Cycle

[Nux!]

+1 LTS, but FWIW I also think Daan has a point here and it should be taken into 
consideration.

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Daan Hoogland" 
> To: "dev" 
> Sent: Tuesday, 19 January, 2016 07:45:57
> Subject: Re: [PROPOSAL] LTS Release Cycle

> On Tue, Jan 19, 2016 at 4:20 AM, John Burwell 
> wrote:
> 
>> In terms of the merge strategy, nothing about the current process would
>> change. Defects would be fixed on the branch where they occurred and then
>> forward ported to master. For each maintained LTS branch less than 14
>> months old, only blocker and critical defects that fall within the LTS’
>> branch scope would be pulled back from master. Therefore, the number of
>> defects backported should be relatively small. Any defects found and fixed
>> in an LTS branch would be forward ported to master. I will clarify the
>> proposal to establish this merge pattern to ensure that LTS does not
>> violate or impede the flow of defect fixes on master and maintained monthly
>> releases.
>>
> 
> ​John, Any backporting should be avoided. Any fix review should include the
> contemplation of the question, 'Is this on the right branch?'. That is my
> point. I am not against LTS. I want fixes to be traceable by their commit
> id over all branches. Backporting is killing in that respect.​
> 
> ​I am not the release manager so rest assured I will not ​make an issue of
> this any more. I won't hold my peace either, though.
> 
> 
> --
> Daan

Re: [PROPOSAL] LTS Release Cycle

[Remi Bergsma]

On a certain night when a release had been cut and there was some worry about a 
security fix not being included. The root cause was that we cherry-picked that 
fix and as a result its commit hash had changed. Hence we couldn’t find it.

I’d recommend using forward merging instead of back porting aka cherry-picking, 
so the commit hashes stay the same and fixes are easily traceable. 

Just my $0.02.

Regards,
Remi





On 19/01/16 08:45, "Daan Hoogland"  wrote:

>On Tue, Jan 19, 2016 at 4:20 AM, John Burwell 
>wrote:
>
>> In terms of the merge strategy, nothing about the current process would
>> change. Defects would be fixed on the branch where they occurred and then
>> forward ported to master. For each maintained LTS branch less than 14
>> months old, only blocker and critical defects that fall within the LTS’
>> branch scope would be pulled back from master. Therefore, the number of
>> defects backported should be relatively small. Any defects found and fixed
>> in an LTS branch would be forward ported to master. I will clarify the
>> proposal to establish this merge pattern to ensure that LTS does not
>> violate or impede the flow of defect fixes on master and maintained monthly
>> releases.
>>
>
>​John, Any backporting should be avoided. Any fix review should include the
>contemplation of the question, 'Is this on the right branch?'. That is my
>point. I am not against LTS. I want fixes to be traceable by their commit
>id over all branches. Backporting is killing in that respect.​
>
>​I am not the release manager so rest assured I will not ​make an issue of
>this any more. I won't hold my peace either, though.
>
>
>-- 
>Daan

Re: [PROPOSAL] LTS Release Cycle

[Jeff Hair]

Maybe require all cherry-picks to use the -x option, which puts the
original commit hash in the cherry-picked commit message?

On Tue, Jan 19, 2016 at 10:53 AM, Remi Bergsma 
wrote:

> On a certain night when a release had been cut and there was some worry
> about a security fix not being included. The root cause was that we
> cherry-picked that fix and as a result its commit hash had changed. Hence
> we couldn’t find it.
>
> I’d recommend using forward merging instead of back porting aka
> cherry-picking, so the commit hashes stay the same and fixes are easily
> traceable.
>
> Just my $0.02.
>
> Regards,
> Remi
>
>
>
>
>
> On 19/01/16 08:45, "Daan Hoogland"  wrote:
>
> >On Tue, Jan 19, 2016 at 4:20 AM, John Burwell  >
> >wrote:
> >
> >> In terms of the merge strategy, nothing about the current process would
> >> change. Defects would be fixed on the branch where they occurred and
> then
> >> forward ported to master. For each maintained LTS branch less than 14
> >> months old, only blocker and critical defects that fall within the LTS’
> >> branch scope would be pulled back from master. Therefore, the number of
> >> defects backported should be relatively small. Any defects found and
> fixed
> >> in an LTS branch would be forward ported to master. I will clarify the
> >> proposal to establish this merge pattern to ensure that LTS does not
> >> violate or impede the flow of defect fixes on master and maintained
> monthly
> >> releases.
> >>
> >
> >​John, Any backporting should be avoided. Any fix review should include
> the
> >contemplation of the question, 'Is this on the right branch?'. That is my
> >point. I am not against LTS. I want fixes to be traceable by their commit
> >id over all branches. Backporting is killing in that respect.​
> >
> >​I am not the release manager so rest assured I will not ​make an issue of
> >this any more. I won't hold my peace either, though.
> >
> >
> >--
> >Daan
>



-- 
*Jeff Hair*
Technical Lead and Software Developer

Tel: (+354) 415 0200
j...@greenqloud.com
www.greenqloud.com

Re: [PROPOSAL] LTS Release Cycle

[Daan Hoogland]

Jeff, That we did before. I don't think that's good enough. It must be the
same commit as far as I'm concerned. Any conflict will be made explicit in
a merge commit that way.

On Tue, Jan 19, 2016 at 12:08 PM, Jeff Hair  wrote:

> Maybe require all cherry-picks to use the -x option, which puts the
> original commit hash in the cherry-picked commit message?
>
> On Tue, Jan 19, 2016 at 10:53 AM, Remi Bergsma <
> rberg...@schubergphilis.com>
> wrote:
>
> > On a certain night when a release had been cut and there was some worry
> > about a security fix not being included. The root cause was that we
> > cherry-picked that fix and as a result its commit hash had changed. Hence
> > we couldn’t find it.
> >
> > I’d recommend using forward merging instead of back porting aka
> > cherry-picking, so the commit hashes stay the same and fixes are easily
> > traceable.
> >
> > Just my $0.02.
> >
> > Regards,
> > Remi
> >
> >
> >
> >
> >
> > On 19/01/16 08:45, "Daan Hoogland"  wrote:
> >
> > >On Tue, Jan 19, 2016 at 4:20 AM, John Burwell <
> john.burw...@shapeblue.com
> > >
> > >wrote:
> > >
> > >> In terms of the merge strategy, nothing about the current process
> would
> > >> change. Defects would be fixed on the branch where they occurred and
> > then
> > >> forward ported to master. For each maintained LTS branch less than 14
> > >> months old, only blocker and critical defects that fall within the
> LTS’
> > >> branch scope would be pulled back from master. Therefore, the number
> of
> > >> defects backported should be relatively small. Any defects found and
> > fixed
> > >> in an LTS branch would be forward ported to master. I will clarify the
> > >> proposal to establish this merge pattern to ensure that LTS does not
> > >> violate or impede the flow of defect fixes on master and maintained
> > monthly
> > >> releases.
> > >>
> > >
> > >​John, Any backporting should be avoided. Any fix review should include
> > the
> > >contemplation of the question, 'Is this on the right branch?'. That is
> my
> > >point. I am not against LTS. I want fixes to be traceable by their
> commit
> > >id over all branches. Backporting is killing in that respect.​
> > >
> > >​I am not the release manager so rest assured I will not ​make an issue
> of
> > >this any more. I won't hold my peace either, though.
> > >
> > >
> > >--
> > >Daan
> >
>
>
>
> --
> *Jeff Hair*
> Technical Lead and Software Developer
>
> Tel: (+354) 415 0200
> j...@greenqloud.com
> www.greenqloud.com
>



-- 
Daan

[ANNOUNCE] New PMC member: Boris Roman Schrijver

[Wilder Rodrigues]

The Project Management Committee (PMC) for Apache CloudStack is pleased to
announce that Boris Roman Schrijver has accepted our invitation to join the PMC.

Please join me in congratulating him.

On behalf of the Apache CloudStack PMC
Wilder Rodrigues

Build failed in Jenkins: build-master-slowbuild #3023

[jenkins]

See 

--
[...truncated 28713 lines...]
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.1:findbugs (findbugs) @ cloud-quickcloud 
---
[INFO] 
[INFO] <<< findbugs-maven-plugin:3.0.1:check (cloudstack-findbugs) @ 
cloud-quickcloud <<<
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.1:check (cloudstack-findbugs) @ 
cloud-quickcloud ---
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:instrument (default-cli) @ 
cloud-quickcloud ---
[WARNING] No files to instrument.
[INFO] NOT adding cobertura ser file to attached artifacts list.
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
cloud-quickcloud ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @ 
cloud-quickcloud ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ cloud-quickcloud 
---
[INFO] 
[INFO] <<< cobertura-maven-plugin:2.6:cobertura (default-cli) @ 
cloud-quickcloud <<<
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:cobertura (default-cli) @ 
cloud-quickcloud ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache CloudStack Developer Tools - Checkstyle Configuration  SUCCESS 
[1.784s]
[INFO] Apache CloudStack . SUCCESS [2.141s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.813s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [18.872s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:29.721s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.111s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [52.196s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.147s]
[INFO] Apache CloudStack API . SUCCESS [1:48.494s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.058s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [30.333s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.094s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.542s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.994s]
[INFO] Apache CloudStack Core  SUCCESS [1:21.758s]
[INFO] Apache CloudStack Agents .. SUCCESS [35.437s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [37.069s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.007s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:07.107s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [41.066s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.443s]
[INFO] Apache CloudStack Server .. SUCCESS [4:13.151s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.461s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.796s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:22.023s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.073s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.488s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.317s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.744s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [30.433s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.181s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [25.815s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [21.337s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [34.877s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.508s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [7.675s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.956s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.341s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[24.159s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[35.164s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.782s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.643s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [16.948s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.612s]
[INFO] Apache Cloud

Re: [ANNOUNCE] New PMC member: Boris Roman Schrijver

[Wilder Rodrigues]

Better later than never! :)

Welcome, dude! Let’s make this boat rock!

Cheers,
Wilder

> On 19 Jan 2016, at 13:15, Wilder Rodrigues  
> wrote:
> 
> The Project Management Committee (PMC) for Apache CloudStack is pleased to
> announce that Boris Roman Schrijver has accepted our invitation to join the 
> PMC.
> 
> Please join me in congratulating him.
> 
> On behalf of the Apache CloudStack PMC
> Wilder Rodrigues

Re: [ANNOUNCE] New PMC member: Boris Roman Schrijver

[Erik Weber]

On Tue, Jan 19, 2016 at 1:15 PM, Wilder Rodrigues <
wrodrig...@schubergphilis.com> wrote:

> The Project Management Committee (PMC) for Apache CloudStack is pleased to
> announce that Boris Roman Schrijver has accepted our invitation to join
> the PMC.
>
> Please join me in congratulating him.
>
>
Congratulations Boris, well deserved.

-- 
Erik

Re: [ANNOUNCE] New PMC member: Boris Roman Schrijver

[Sebastien Goasguen]

Well done Boris, looking forward for more contributions from you

> On Jan 19, 2016, at 1:17 PM, Erik Weber  wrote:
> 
> On Tue, Jan 19, 2016 at 1:15 PM, Wilder Rodrigues <
> wrodrig...@schubergphilis.com> wrote:
> 
>> The Project Management Committee (PMC) for Apache CloudStack is pleased to
>> announce that Boris Roman Schrijver has accepted our invitation to join
>> the PMC.
>> 
>> Please join me in congratulating him.
>> 
>> 
> Congratulations Boris, well deserved.
> 
> -- 
> Erik

Re: [ANNOUNCE] New PMC member: Boris Roman Schrijver

[Wido den Hollander]

Welcome Boris! :)

On 19-01-16 13:15, Wilder Rodrigues wrote:
> The Project Management Committee (PMC) for Apache CloudStack is pleased to
> announce that Boris Roman Schrijver has accepted our invitation to join the 
> PMC.
> 
> Please join me in congratulating him.
> 
> On behalf of the Apache CloudStack PMC
> Wilder Rodrigues
> 

Re: [ANNOUNCE] New PMC member: Boris Roman Schrijver

[Nux!]

Congrats, Boris. :)

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Wilder Rodrigues" 
> To: dev@cloudstack.apache.org
> Sent: Tuesday, 19 January, 2016 12:15:42
> Subject: [ANNOUNCE] New PMC member: Boris Roman Schrijver

> The Project Management Committee (PMC) for Apache CloudStack is pleased to
> announce that Boris Roman Schrijver has accepted our invitation to join the 
> PMC.
> 
> Please join me in congratulating him.
> 
> On behalf of the Apache CloudStack PMC
> Wilder Rodrigues

[GitHub] cloudstack-cloudmonkey pull request: Summary: Allow 'sync' as a ve...

[bhaisaab]

Github user bhaisaab commented on the pull request:


https://github.com/apache/cloudstack-cloudmonkey/pull/12#issuecomment-172875848
  
LGTM, merging. Thanks for fixing this @waegemae 


---
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-cloudmonkey pull request: Summary: Allow 'sync' as a ve...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cloudstack-cloudmonkey/pull/12


---
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: [ANNOUNCE] New PMC member: Boris Roman Schrijver

[Rohit Yadav]

Congrats and welcome Boris!

>

[ShapeBlue]
Rohit Yadav
Software Architect  ,   ShapeBlue


d:   | s: +44 203 603 0540  |  
m:  +91 8826230892

e:  rohit.ya...@shapeblue.com | t: 
   |  w:  
www.shapeblue.com

a:  53 Chandos Place, Covent Garden London WC2N 4HS UK


[cid:image8e4fd5.png@a670e55c.40b88367]


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




On 19-Jan-2016, at 2:56 PM, Nux!  wrote:
>
> Congrats, Boris. :)
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> - Original Message -
>> From: "Wilder Rodrigues" 
>> To: dev@cloudstack.apache.org
>> Sent: Tuesday, 19 January, 2016 12:15:42
>> Subject: [ANNOUNCE] New PMC member: Boris Roman Schrijver
>
>> The Project Management Committee (PMC) for Apache CloudStack is pleased to
>> announce that Boris Roman Schrijver has accepted our invitation to join the 
>> PMC.
>>
>> Please join me in congratulating him.
>>
>> On behalf of the Apache CloudStack PMC
>> Wilder Rodrigues

Regards.

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

Re: [ANNOUNCE] New PMC member: Boris Roman Schrijver

[Daan Hoogland]

Welcome Boris, Hope you stay with us long long time :)

On Tue, Jan 19, 2016 at 3:52 PM, Rohit Yadav 
wrote:

> Congrats and welcome Boris!
>
> >
>
> [image: ShapeBlue] 
> Rohit Yadav
> Software Architect ,  ShapeBlue
> d:  * | s: +44 203 603 0540* <%7C%20s:%20+44%20203%20603%200540>  |  m:
> *+91 8826230892* <+91%208826230892>
> e:  *rohit.ya...@shapeblue.com | t: *
>   |  w:  *www.shapeblue.com*
> 
> a:  53 Chandos Place, Covent Garden London WC2N 4HS UK
> 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.
> 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.
>
>
> On 19-Jan-2016, at 2:56 PM, Nux!  wrote:
> >
> > Congrats, Boris. :)
> >
> > --
> > Sent from the Delta quadrant using Borg technology!
> >
> > Nux!
> > www.nux.ro
> >
> > - Original Message -
> >> From: "Wilder Rodrigues" 
> >> To: dev@cloudstack.apache.org
> >> Sent: Tuesday, 19 January, 2016 12:15:42
> >> Subject: [ANNOUNCE] New PMC member: Boris Roman Schrijver
> >
> >> The Project Management Committee (PMC) for Apache CloudStack is pleased
> to
> >> announce that Boris Roman Schrijver has accepted our invitation to join
> the PMC.
> >>
> >> Please join me in congratulating him.
> >>
> >> On behalf of the Apache CloudStack PMC
> >> Wilder Rodrigues
>
> Regards.
>
> 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 
>



-- 
Daan

Build failed in Jenkins: build-master-slowbuild #3024

[jenkins]

See 

--
[...truncated 28713 lines...]
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.1:findbugs (findbugs) @ cloud-quickcloud 
---
[INFO] 
[INFO] <<< findbugs-maven-plugin:3.0.1:check (cloudstack-findbugs) @ 
cloud-quickcloud <<<
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.1:check (cloudstack-findbugs) @ 
cloud-quickcloud ---
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:instrument (default-cli) @ 
cloud-quickcloud ---
[WARNING] No files to instrument.
[INFO] NOT adding cobertura ser file to attached artifacts list.
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
cloud-quickcloud ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @ 
cloud-quickcloud ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ cloud-quickcloud 
---
[INFO] 
[INFO] <<< cobertura-maven-plugin:2.6:cobertura (default-cli) @ 
cloud-quickcloud <<<
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:cobertura (default-cli) @ 
cloud-quickcloud ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache CloudStack Developer Tools - Checkstyle Configuration  SUCCESS 
[1.767s]
[INFO] Apache CloudStack . SUCCESS [2.066s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.785s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.045s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:32.501s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.108s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [54.287s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.476s]
[INFO] Apache CloudStack API . SUCCESS [1:48.808s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [17.398s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [29.926s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.097s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.806s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [25.035s]
[INFO] Apache CloudStack Core  SUCCESS [1:21.629s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.134s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.666s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.400s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:07.415s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.798s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.370s]
[INFO] Apache CloudStack Server .. SUCCESS [4:14.440s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [38.045s]
[INFO] Apache CloudStack Usage Server  SUCCESS [43.817s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:22.224s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.073s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.444s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.830s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [47.931s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [30.583s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.139s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [25.700s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [20.932s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.829s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.132s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [8.361s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.927s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.495s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.577s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[36.974s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.818s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.232s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [16.873s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[17.284s]
[INFO] Apache Cloud

[GitHub] cloudstack pull request: CLOUDSTACK-8847: ListServiceOfferings is ...

[remibergsma]

Github user remibergsma commented on the pull request:

https://github.com/apache/cloudstack/pull/1321#issuecomment-172892988
  
LGTM based on these tests:

```
nosetests --with-marvin --marvin-config=${marvinCfg} -s -a 
tags=advanced,required_hardware=true \
component/test_vpc_redundant.py \
component/test_routers_iptables_default_policy.py \
component/test_routers_network_ops.py \
component/test_vpc_router_nics.py \
smoke/test_loadbalance.py \
smoke/test_internal_lb.py \
smoke/test_ssvm.py \
smoke/test_network.py

```

Result:

```
Check the password file in the Router VM ... === TestName: 
test_isolate_network_password_server | Status : SUCCESS ===
ok
Create a redundant VPC with two networks with two VMs in each network ... 
=== TestName: test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | Status : 
SUCCESS ===
ok
Create a redundant VPC with two networks with two VMs in each network and 
check default routes ... === TestName: test_02_redundant_VPC_default_routes | 
Status : SUCCESS ===
ok
Create a redundant VPC with two networks with two VMs in each network ... 
=== TestName: 
test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | Status : 
SUCCESS ===
ok
Create a redundant VPC with 1 Tier, 1 VM, 1 ACL, 1 PF and test Network GC 
Nics ... === TestName: test_04_rvpc_network_garbage_collector_nics | Status : 
SUCCESS ===
ok
Create a redundant VPC with 1 Tier, 1 VM, 1 ACL, 1 PF and test Network GC 
Nics ... === TestName: test_05_rvpc_multi_tiers | Status : SUCCESS ===
ok
Test iptables default INPUT/FORWARD policy on RouterVM ... === TestName: 
test_02_routervm_iptables_policies | Status : SUCCESS ===
ok
Test iptables default INPUT/FORWARD policies on VPC router ... === 
TestName: test_01_single_VPC_iptables_policies | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName: 
test_01_isolate_network_FW_PF_default_routes_egress_true | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName: 
test_02_isolate_network_FW_PF_default_routes_egress_false | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName: 
test_01_RVR_Network_FW_PF_SSH_default_routes_egress_true | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName: 
test_02_RVR_Network_FW_PF_SSH_default_routes_egress_false | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName: 
test_03_RVR_Network_check_router_state | Status : SUCCESS ===
ok
Create a VPC with two networks with one VM in each network and test nics 
after destroy ... === TestName: test_01_VPC_nics_after_destroy | Status : 
SUCCESS ===
ok
Create a VPC with two networks with one VM in each network and test default 
routes ... === TestName: test_02_VPC_default_routes | Status : SUCCESS ===
ok
Check that the /etc/dhcphosts.txt doesn't contain duplicate IPs ... === 
TestName: test_router_dhcphosts | Status : SUCCESS ===
ok
Test to create Load balancing rule with source NAT ... === TestName: 
test_01_create_lb_rule_src_nat | Status : SUCCESS ===
ok
Test to create Load balancing rule with non source NAT ... === TestName: 
test_02_create_lb_rule_non_nat | Status : SUCCESS ===
ok
Test for assign & removing load balancing rule ... === TestName: 
test_assign_and_removal_lb | Status : SUCCESS ===
ok
Test create, assign, remove of an Internal LB with roundrobin http traffic 
to 3 vm's in a Single VPC ... === TestName: 
test_01_internallb_roundrobin_1VPC_3VM_HTTP_port80 | Status : SUCCESS ===
ok
Test create, assign, remove of an Internal LB with roundrobin http traffic 
to 3 vm's in a Redundant VPC ... === TestName: 
test_02_internallb_roundrobin_1RVPC_3VM_HTTP_port80 | Status : SUCCESS ===
ok
Test to verify access to loadbalancer haproxy admin stats page ... === 
TestName: test_03_vpc_internallb_haproxy_stats_on_all_interfaces | Status : 
SUCCESS ===
ok
Test to verify access to loadbalancer haproxy admin stats page ... === 
TestName: test_04_rvpc_internallb_haproxy_stats_on_all_interfaces | Status : 
SUCCESS ===
ok
Test SSVM Internals ... === TestName: test_03_ssvm_internals | Status : 
SUCCESS ===
ok
Test CPVM Internals ... === TestName: test_04_cpvm_internals | Status : 
SUCCESS ===
ok
Test stop SSVM ... === TestName: test_05_stop_ssvm | Status : SUCCESS ===
ok
Test stop CPVM ... === TestName: test_06_stop_cpvm | Status : SUCCESS ===
ok
Test reboot SSVM ... === TestName: test_07_reboot_ssvm | Status : SUCCESS 
===
ok
Test reboot CPVM ... === TestName: test_08_reboot_cpvm | Status : SUCCESS 
===
ok
Test destroy SSVM ... === TestName: test_09_destroy_ssvm | Status : SUCCESS 
===
ok
Test destroy CPVM ... === TestName: test_10_destroy_cpvm | Status : SUCCESS 
===
ok
Test Site

[GitHub] cloudstack pull request: CLOUDSTACK-8847: ListServiceOfferings is ...

[DaanHoogland]

Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/1321#issuecomment-172903549
  
@remibergsma I am puzzled. You don't agree with the contents of the PR but 
you did run the tests? or did I misread your comment? I though you and 
@agneya2001 didn't like this tag check.


---
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: CLOUDSTACK-8847: ListServiceOfferings is ...

[DaanHoogland]

Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/1321#issuecomment-172911093
  
ok, clear


---
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: [ANNOUNCE] New PMC member: Boris Roman Schrijver

[Paul Angus]

Congratulations Boris.


[ShapeBlue]
Paul Angus
VP Technology   ,   ShapeBlue


d:  +44 203 617 0528 | s: +44 203 603 
0540 |  
m:  +44 7711 418784

e:  paul.an...@shapeblue.com | t: 
@cloudyangus  |
  w:  www.shapeblue.com

a:  53 Chandos Place, Covent Garden London WC2N 4HS UK


[cid:image6c7924.png@5e3cccf0.478f4530]


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




-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
Sent: Tuesday, January 19, 2016 3:09 PM
To: dev 
Subject: Re: [ANNOUNCE] New PMC member: Boris Roman Schrijver

Welcome Boris, Hope you stay with us long long time :)

On Tue, Jan 19, 2016 at 3:52 PM, Rohit Yadav 
wrote:

> Congrats and welcome Boris!
>
> >
>
> [image: ShapeBlue]  Rohit Yadav Software
> Architect , ShapeBlue
> d: * | s: +44 203 603 0540* <%7C%20s:%20+44%20203%20603%200540> | m:
> *+91 8826230892* <+91%208826230892>
> e: *rohit.ya...@shapeblue.com | t: *
>  | w: *www.shapeblue.com*
> 
> a: 53 Chandos Place, Covent Garden London WC2N 4HS UK 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.
> 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.
>
>
> On 19-Jan-2016, at 2:56 PM, Nux!  wrote:
> >
> > Congrats, Boris. :)
> >
> > --
> > Sent from the Delta quadrant using Borg technology!
> >
> > Nux!
> > www.nux.ro
> >
> > - Original Message -
> >> From: "Wilder Rodrigues" 
> >> To: dev@cloudstack.apache.org
> >> Sent: Tuesday, 19 January, 2016 12:15:42
> >> Subject: [ANNOUNCE] New PMC member: Boris Roman Schrijver
> >
> >> The Project Management Committee (PMC) for Apache CloudStack is
> >> pleased
> to
> >> announce that Boris Roman Schrijver has accepted our invitation to
> >> join
> the PMC.
> >>
> >> Please join me in congratulating him.
> >>
> >> On behalf of the Apache CloudStack PMC Wilder Rodrigues
>
> Regards.
>
> 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 
>



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

[GitHub] cloudstack pull request: CLOUDSTACK-9132: API createVolume takes e...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: CLOUDSTACK-8847: ListServiceOfferings is ...

[remibergsma]

Github user remibergsma commented on the pull request:

https://github.com/apache/cloudstack/pull/1321#issuecomment-172908360
  
@DaanHoogland This PR is better than the current situation and would 
improve even more if the whole check would disappear. If the PR is changed, 
I'll happily run the tests again.


---
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: test: Fix Libvirt test so that it works o...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: Vmdk findbugs

[DaanHoogland]

GitHub user DaanHoogland opened a pull request:

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

Vmdk findbugs

these are two of the findbugs errors coming out of our jenkins all the 
time. The author seems to be unavailable so I kicked and screamed at it.
notice that this is noredist code. I did the compile without it. there is 
one with running.

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

$ git pull https://github.com/DaanHoogland/cloudstack vmdk-findbugs

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

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


commit 18ba5bbf6d95e9056b981c05f88d1b914bf49cb5
Author: Daan Hoogland 
Date:   2016-01-19T15:55:05Z

findbugs: pre-fix reformat

commit b106f574a4828c7f45cc5711e13909fe1e6d3340
Author: Daan Hoogland 
Date:   2016-01-19T15:56:20Z

findbugs: use explicit encoding




---
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: Vmdk findbugs

[DaanHoogland]

Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/1351#issuecomment-172917596
  
note that jenkins isn't responding to the PR (so far)


---
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: [PROPOSAL] LTS Release Cycle

[John Burwell]

All,

LTS branches will be maintained for 20 months. In that time, some defects will 
be fixed in an LTS branch and forward merged. Some defects will be identified 
in master, and we will need to determine whether or not they should be pulled 
back to one or more of the active LTS branches. As master evolves, there will 
not always be a straight line from LTS to master. Requiring a direct path 
between LTS branches and master would either severely constrain the development 
of master or compromise the stability expected by LTS users. We should also not 
assume that all backports will be merges/cherry picks — some will be 
re-implementations due to divergence over time. Like the Ubuntu and Red Hat 
maintenance cycles, the proposal places the burden of determining the best 
approach to defect backporting on LTS maintainers to avoid impacting the 
velocity of feature development. While we should prefer fixing in LTS merging 
forward, the reality is that maintaining long running maintenance branches will 
require some cherry picking and re-implementation of defects due to the length 
of the support window.

It’s also important to note I propose only pulling back blockers and critical 
severity defects within the scope of the LTS’ functionality from master. The 
goal of LTS is not to fix every defect. It is to fix those defects that impact 
system stability or severely degrade functionality. Previously, we conflated 
feature development and maintenance into a single set of release branches using 
the same release cycle. With the monthly releases, users have a path to acquire 
new functionality independent of bug fix/maintenance efforts — removing 
potential justification to pull back new features or enhancements. As we have 
discussed this proposal, I think it should be amended to require that all PRs 
to an LTS branch include an LGTM from the LTS branch RM to ensure that only 
defects that fit within the narrowly defined constraints.

Based on our history, I share your concerns about cherry picking abuse, and 
have attempt to design the proposal to address them. I believe that the tighter 
constraints on the defects that are allowed to be backported, a clearly defined 
policy about the LTS release cycle schedule, and monthly releases will allow us 
to avoid the mistakes of the past.

Thanks,
-John

>

[ShapeBlue]
John Burwell
ShapeBlue

d:  +44 (20) 3603 0542 | s: +1 (571) 403-2411 


e:  john.burw...@shapeblue.com | t: 
 |  w:  
www.shapeblue.com

a:  53 Chandos Place, Covent Garden London WC2N 4HS UK


[cid:imagefafe75.png@d43a0b58.41a20f1c]


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




On Jan 19, 2016, at 6:14 AM, Daan Hoogland  wrote:
>
> Jeff, That we did before. I don't think that's good enough. It must be the
> same commit as far as I'm concerned. Any conflict will be made explicit in
> a merge commit that way.
>
> On Tue, Jan 19, 2016 at 12:08 PM, Jeff Hair  wrote:
>
>> Maybe require all cherry-picks to use the -x option, which puts the
>> original commit hash in the cherry-picked commit message?
>>
>> On Tue, Jan 19, 2016 at 10:53 AM, Remi Bergsma <
>> rberg...@schubergphilis.com>
>> wrote:
>>
>>> On a certain night when a release had been cut and there was some worry
>>> about a security fix not being included. The root cause was that we
>>> cherry-picked that fix and as a result its commit hash had changed. Hence
>>> we couldn’t find it.
>>>
>>> I’d recommend using forward merging instead of back porting aka
>>> cherry-picking, so the commit hashes stay the same and fixes are easily
>>> traceable.
>>>
>>> Just my $0.02.
>>>
>>> Regards,
>>> Remi
>>>
>>>
>>>
>>>
>>>
>>> On 19/01/16 08:45, "Daan Hoogland"  wrote:
>>>
 On Tue, Jan 19, 2016 at 4:20 AM, John Burwell <
>> john.burw...@shapeblue.com

 wrote:

> In terms of the merge strategy, nothing about the current process
>> would
> change. Defects would be fixed on the branch where they occurred 

[GitHub] cloudstack pull request: CLOUDSTACK-9244 Fix setting up RFC1918 ro...

[remibergsma]

GitHub user remibergsma opened a pull request:

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

CLOUDSTACK-9244 Fix setting up RFC1918 routes

Public ip var was empty so routes were always set. Corrected this.

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

$ git pull https://github.com/remibergsma/cloudstack 
cloud-early-config-route-fix

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

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


commit d6015700532c7c4676f4d402611fa4738cd4045d
Author: Remi Bergsma 
Date:   2016-01-19T17:24:49Z

CLOUDSTACK-9244 Fix setting up RFC1918 routes




---
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: CLOUDSTACK-9244 Fix setting up RFC1918 ro...

[nislim]

Github user nislim commented on the pull request:

https://github.com/apache/cloudstack/pull/1352#issuecomment-172929285
  
Fixed my problem, my routing tables are now looking as I expected.
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.
---

Build failed in Jenkins: build-master-slowbuild #3025

[jenkins]

See 

Changes:

[wido] test: Fix Libvirt test so that it works on Windows

[nitin.maharana] CLOUDSTACK-9132: API createVolume takes empty string for name 
parameter

[Rohit Yadav] ui: improve metrics view implementation

--
[...truncated 28713 lines...]
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.1:findbugs (findbugs) @ cloud-quickcloud 
---
[INFO] 
[INFO] <<< findbugs-maven-plugin:3.0.1:check (cloudstack-findbugs) @ 
cloud-quickcloud <<<
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.1:check (cloudstack-findbugs) @ 
cloud-quickcloud ---
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:instrument (default-cli) @ 
cloud-quickcloud ---
[WARNING] No files to instrument.
[INFO] NOT adding cobertura ser file to attached artifacts list.
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
cloud-quickcloud ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @ 
cloud-quickcloud ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ cloud-quickcloud 
---
[INFO] 
[INFO] <<< cobertura-maven-plugin:2.6:cobertura (default-cli) @ 
cloud-quickcloud <<<
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:cobertura (default-cli) @ 
cloud-quickcloud ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache CloudStack Developer Tools - Checkstyle Configuration  SUCCESS 
[1.732s]
[INFO] Apache CloudStack . SUCCESS [2.089s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.794s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [20.093s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:29.425s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.105s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [53.462s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.191s]
[INFO] Apache CloudStack API . SUCCESS [1:51.049s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [17.470s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [29.755s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.097s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [27.881s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.631s]
[INFO] Apache CloudStack Core  SUCCESS [1:21.144s]
[INFO] Apache CloudStack Agents .. SUCCESS [37.228s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.943s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.226s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:07.811s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.206s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.413s]
[INFO] Apache CloudStack Server .. SUCCESS [4:12.079s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [36.813s]
[INFO] Apache CloudStack Usage Server  SUCCESS [43.932s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:23.646s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.068s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.441s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [55.217s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [50.313s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [29.679s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.096s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [25.764s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [20.603s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.969s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.542s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [7.550s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [1.031s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.428s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.320s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[36.991s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.433s]
[INFO] Apache CloudStack Plugin - 

Re: [ANNOUNCE] New PMC member: Boris Roman Schrijver

[Mike Tutkowski]

Congratulations, Boris!

On Tue, Jan 19, 2016 at 5:15 AM, Wilder Rodrigues <
wrodrig...@schubergphilis.com> wrote:

> The Project Management Committee (PMC) for Apache CloudStack is pleased to
> announce that Boris Roman Schrijver has accepted our invitation to join
> the PMC.
>
> Please join me in congratulating him.
>
> On behalf of the Apache CloudStack PMC
> Wilder Rodrigues




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

Re: [PROPOSAL] LTS Release Cycle

[ilya]

> Therefore, the process should strive to make as a few releases as
necessary to achieve this goal.

I guess part two to this question would be - we need the automated
testing environments. This can ensure rapid release testing and acutal
release, and we dont have to restrains ourselves to limited number of
releases LTS release due to QA pains.

We need a separate initiative with CloudStack testing framework.

On 1/18/16 6:54 PM, John Burwell wrote:
> Ilya,
> 
> Unless we have a bug fix that addresses a significant, widespread system 
> stability problem or a high priority/impact security issue, an LTS will roll 
> up a number of fixes.   Each release would receive the full system test to 
> verify that the patch set does not introduce regression defects.  I believe 
> that most LTS users want a few releases as necessary to keep their systems 
> up-to-date and stable because each upgrade carries operational risk and 
> downtime.  Therefore, the process should strive to make as a few releases as 
> necessary to achieve this goal.
> 
> Thanks,
> -John
> 
>> On Jan 15, 2016, at 3:22 PM, ilya  wrote:
>>
>> John
>>
>> Thank you for taking time writing out the LTS proposal.
>>
>>> Broad community support is vital to guarantee the twenty (20) month
>>> support period for each LTS branch. Given the ebbs and flows of
>>> contribution and committer priorities, ShapeBlue will provide a release
>>> manager, as well as, engineering support to fill any contribution gaps
>>> to ensure that the community fulfills LTS commitments.
>>
>> You guys rock!!
>>
>> I'm +1 on this,
>>
>> Can you please expand on the QA side of LTS. Since this is more around
>> long term bug/security fix - i'd think - the testing will be minimal, to
>> the scope that fix applies - which will speed up the release process in
>> general. What are your thoughts on this?
>>
>>
>> Thanks
>> ilya
>>
>>
>>
>>
>>
>> On 1/15/16 10:48 AM, John Burwell wrote:
>>> Motivation
>>> 
>>>
>>> The current monthly release cycle addresses the needs of users focused
>>> on deploying new functionality as quickly as possible. It does not
>>> address the needs of users oriented towards stability rather than new
>>> functionality. These users typically employ QA processes to comply with
>>> corporate policy and/or regulatory requirements. To maintain a growing,
>>> thriving community, we must address the needs of both user types.
>>> Therefore, I propose that we overlay a LTS release cycle onto the
>>> monthly release cycle to address the needs of stability-oriented users
>>> with minimal to no impact on the monthly release cycle. This proposed
>>> LTS release cycle has the following goals:
>>>
>>> * Prefer Stability to New Functionality: Deliver releases that only
>>> address defects and CVEs. This narrowly focused change scope greatly
>>> reduces the upgrade risk/operational impact and shorter internal QA cycles.
>>> * Reliable Release Lifetimes: Embracing a time-based release strategy,
>>> the LTS release cycle will provide users with a reliable support time
>>> frames. Users can use these time frames provide users with an 20 month
>>> window in which to plan upgrades.
>>> * Support Sustainability: With a defined end of support for LTS releases
>>> and a maximum of two (2) LTS releases under active maintenance at any
>>> given time, community members can better plan their commitments to
>>> release support activities. We also have a agreed upon policy for
>>> release end-of-life (EOL) to debate about continuing work on old releases.
>>>
>>> Proposed Process
>>> ==
>>>
>>> LTS release branches will be cut twice year on 1 Jan and 1 July from the
>>> tag of the most recent monthly release. The branch will be named >> version>-LTS and each LTS release will be versioned in the form of >> version>-. For example, if we cut an LTS branch
>>> based on 4.7.0, the branch would be named 4.7.0-LTS and the version of
>>> the first LTS release would be 4.7.0-0, the second would be 4.7.0-1,
>>> etc. This release naming convention differentiates LTS and monthly
>>> releases, communicates the version on which the LTS release is based,
>>> and allows the maintenance releases for monthly releases without version
>>> number contention/conflict. Finally, like master, an LTS branch would be
>>> always deployable following its initial release. While it is unlikely
>>> that LTS users would deploy from the branch, the quality discipline of
>>> this requirement will benefit the long term stability of LTS releases.
>>> All PRs targeting an LTS would require two LGTMs in order to be merged.
>>>
>>> The following are the types of changes that would permitted and
>>> guarantees provided to users:
>>>
>>> * No features or enhancements would be backported to LTS release branches.
>>> * Database changes would be limited to those required to address the
>>> backported defect fixes.
>>> * Support for the release/version of the following components from the
>>> release on which the LTS i

Re: [ANNOUNCE] New PMC member: Boris Roman Schrijver

[ilya]

Warm welcome Boris..

On 1/19/16 4:15 AM, Wilder Rodrigues wrote:
> The Project Management Committee (PMC) for Apache CloudStack is pleased to
> announce that Boris Roman Schrijver has accepted our invitation to join the 
> PMC.
> 
> Please join me in congratulating him.
> 
> On behalf of the Apache CloudStack PMC
> Wilder Rodrigues
> 

[GitHub] cloudstack pull request: CLOUDSTACK-9236: Load Balancing Health Ch...

[DaanHoogland]

Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/1338#issuecomment-172966645
  
I have some remarks about style (made one) but the logic looks fine. 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 pull request: CLOUDSTACK-9244 Fix setting up RFC1918 ro...

[DaanHoogland]

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

https://github.com/apache/cloudstack/pull/1352#discussion_r50168987
  
--- Diff: systemvm/patches/debian/config/etc/init.d/cloud-early-config ---
@@ -1166,6 +1166,9 @@ setup_storage_network() {
 }
 
 setup_system_rfc1918_internal() {
+  public_ip=$ETH2_IP
+  [ "$ETH2_IP" == "0.0.0.0" ] && public_ip=$ETH1_IP
--- End diff --

shouldn't line 1195 begone, then? I think it does the same


---
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: CLOUDSTACK-9244 Fix setting up RFC1918 ro...

[DaanHoogland]

Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/1352#issuecomment-172975452
  
If this helps @nislim And is tested it should go in.
I feel uncertain of this functionality. It is called from sestro and 
console proxy setup functions but the code is also present in those functions. 
I think the lines 1195 and 1252 should be removed and the functionality 
abstracted out.


---
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: CLOUDSTACK-9244 Fix setting up RFC1918 ro...

[remibergsma]

Github user remibergsma commented on the pull request:

https://github.com/apache/cloudstack/pull/1352#issuecomment-172977865
  
@DaanHoogland I think we agree cloud-early-config needs major refactoring 
as it is one big copy/paste thing. Just don't think this is the time to do it.

All this does is pickup the public ip address and use it, like other parts 
also do.


---
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: CLOUDSTACK-9236: Load Balancing Health Ch...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: [PROPOSAL] LTS Release Cycle

[Paul Angus]

Hi Ilya (and all others),

We (ShapeBlue) agree with you regarding the importance of automated integration 
testing. The consulting team are currently working to understand Marvin fully 
and what pieces we need to be able deploy properly representative (virtualised) 
infrastructures to test against. We intend to open source our resultant 
framework, with a view to community members being able to use it themselves in 
their own labs but also so that as a community we can build it out somewhere to 
be used as part of the projects' testing regime.

We'll be reaching out to the community soon to work on the failures we're 
seeing currently and understand where they come from - ie Marvin build, the 
environment, the tests or CloudStack (watch out Mike T - I'm about to watch 
your presentation video).

We see this an important initiative for CloudStack as a whole, agile or 
otherwise. But ultimately this is 'only' regression testing and the 
organisations which need/want LTS, require it for a number of reasons, 
including the fact new features bring new bugs which, if we knew we had to test 
for, probably wouldn't have been there in the first place.



Paul Angus
VP Technology   ,   ShapeBlue


t:  @cloudyangus

e:  paul.an...@shapeblue.com|  
w:  www.shapeblue.com





-Original Message-
From: ilya [mailto:ilya.mailing.li...@gmail.com]
Sent: Tuesday, January 19, 2016 6:39 PM
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSAL] LTS Release Cycle

> Therefore, the process should strive to make as a few releases as
necessary to achieve this goal.

I guess part two to this question would be - we need the automated testing 
environments. This can ensure rapid release testing and acutal release, and we 
dont have to restrains ourselves to limited number of releases LTS release due 
to QA pains.

We need a separate initiative with CloudStack testing framework.

On 1/18/16 6:54 PM, John Burwell wrote:
> Ilya,
>
> Unless we have a bug fix that addresses a significant, widespread system 
> stability problem or a high priority/impact security issue, an LTS will roll 
> up a number of fixes. Each release would receive the full system test to 
> verify that the patch set does not introduce regression defects. I believe 
> that most LTS users want a few releases as necessary to keep their systems 
> up-to-date and stable because each upgrade carries operational risk and 
> downtime. Therefore, the process should strive to make as a few releases as 
> necessary to achieve this goal.
>
> Thanks,
> -John
>
>> On Jan 15, 2016, at 3:22 PM, ilya  wrote:
>>
>> John
>>
>> Thank you for taking time writing out the LTS proposal.
>>
>>> Broad community support is vital to guarantee the twenty (20) month
>>> support period for each LTS branch. Given the ebbs and flows of
>>> contribution and committer priorities, ShapeBlue will provide a
>>> release manager, as well as, engineering support to fill any
>>> contribution gaps to ensure that the community fulfills LTS commitments.
>>
>> You guys rock!!
>>
>> I'm +1 on this,
>>
>> Can you please expand on the QA side of LTS. Since this is more
>> around long term bug/security fix - i'd think - the testing will be
>> minimal, to the scope that fix applies - which will speed up the
>> release process in general. What are your thoughts on this?
>>
>>
>> Thanks
>> ilya
>>
>>
>>
>>
>>
>> On 1/15/16 10:48 AM, John Burwell wrote:
>>> Motivation
>>> 
>>>
>>> The current monthly release cycle addresses the needs of users
>>> focused on deploying new functionality as quickly as possible. It
>>> does not address the needs of users oriented towards stability
>>> rather than new functionality. These users typically employ QA
>>> processes to comply with corporate policy and/or regulatory
>>> requirements. To maintain a growing, thriving community, we must address 
>>> the needs of both user types.
>>> Therefore, I propose that we overlay a LTS release cycle onto the
>>> monthly release cycle to address the needs of stability-oriented
>>> users with minimal to no impact on the monthly release cycle. This
>>> proposed LTS release cycle has the following goals:
>>>
>>> * Prefer Stability to New Functionality: Deliver releases that only
>>> address defects and CVEs. This narrowly focused change scope greatly
>>> reduces the upgrade risk/operational impact and shorter internal QA cycles.
>>> * Reliable Release Lifetimes: Embracing a time-based release
>>> strategy, the LTS release cycle will provide users with a reliable
>>> support time frames. Users can use these time frames provide users
>>> with an 20 month window in which to plan upgrades.
>>> * Support Sustainability: With a defined end of support for LTS
>>> releases and a maximum of two (2) LTS releases under active
>>> maintenance at any given time, community members can better plan
>>> their commitments to release support activities. We also have 

Build failed in Jenkins: build-master-slowbuild #3026

[jenkins]

See 

--
[...truncated 28713 lines...]
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.1:findbugs (findbugs) @ cloud-quickcloud 
---
[INFO] 
[INFO] <<< findbugs-maven-plugin:3.0.1:check (cloudstack-findbugs) @ 
cloud-quickcloud <<<
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.1:check (cloudstack-findbugs) @ 
cloud-quickcloud ---
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:instrument (default-cli) @ 
cloud-quickcloud ---
[WARNING] No files to instrument.
[INFO] NOT adding cobertura ser file to attached artifacts list.
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
cloud-quickcloud ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @ 
cloud-quickcloud ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ cloud-quickcloud 
---
[INFO] 
[INFO] <<< cobertura-maven-plugin:2.6:cobertura (default-cli) @ 
cloud-quickcloud <<<
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:cobertura (default-cli) @ 
cloud-quickcloud ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache CloudStack Developer Tools - Checkstyle Configuration  SUCCESS 
[1.712s]
[INFO] Apache CloudStack . SUCCESS [2.120s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.776s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.474s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:32.964s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.108s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [54.080s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.494s]
[INFO] Apache CloudStack API . SUCCESS [1:49.289s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.197s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [30.660s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.084s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.043s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.492s]
[INFO] Apache CloudStack Core  SUCCESS [1:19.938s]
[INFO] Apache CloudStack Agents .. SUCCESS [37.131s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.750s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.852s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:06.514s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.509s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.408s]
[INFO] Apache CloudStack Server .. SUCCESS [4:16.548s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.349s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.257s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:22.116s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.071s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.458s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [55.339s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.463s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [30.217s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [25.908s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [26.041s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [21.547s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.424s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.338s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [7.861s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.953s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [27.661s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.413s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[35.794s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.260s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.627s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [15.960s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.669s]
[INFO] Apache Cloud

[GitHub] cloudstack pull request: CLOUDSTACK-9244 Fix setting up RFC1918 ro...

[remibergsma]

Github user remibergsma commented on the pull request:

https://github.com/apache/cloudstack/pull/1352#issuecomment-173002681
  
Discussed with @DaanHoogland and he sent me a patch ;-)


---
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: CLOUDSTACK-9244 Fix setting up RFC1918 ro...

[remibergsma]

Github user remibergsma commented on the pull request:

https://github.com/apache/cloudstack/pull/1352#issuecomment-173002828
  
@nislim Can you please test the enhanced patch?


---
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: CLOUDSTACK-9244 Fix setting up RFC1918 ro...

[remibergsma]

Github user remibergsma commented on the pull request:

https://github.com/apache/cloudstack/pull/1352#issuecomment-173005222
  
`cloud-early-config` now logs:

```
Not setting up route of RFC1918 space to 192.168.22.1 befause 192.168.23.2 
is RFC1918..
```

Routes are not set as expected:
```
root@v-85-VM: # route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse 
Iface
0.0.0.0 192.168.23.10.0.0.0 UG0  00 eth2
169.254.0.0 0.0.0.0 255.255.0.0 U 0  00 eth0
192.168.22.00.0.0.0 255.255.255.0   U 0  00 eth1
192.168.23.00.0.0.0 255.255.255.0   U 0  00 eth2
```

And when it has a real public ip a route is set to the internal gw. That 
functionality still works and didn't change.

```
Setting up route of RFC1918 space to 192.168.22.1 
```

Routes are setup now:
```
root@v-1357-VM: # route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse 
Iface
0.0.0.0 x.y.227.1   0.0.0.0 UG0  00 eth2
10.0.0.0192.168.22.1255.0.0.0   UG0  00 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 0  00 eth0
172.16.0.0  192.168.22.1255.240.0.0 UG0  00 eth1
192.168.0.0 192.168.22.1255.255.0.0 UG0  00 eth1
192.168.22.00.0.0.0 255.255.255.0   U 0  00 eth1
 x.y.227.0  0.0.0.0 255.255.255.0   U 0  00 eth2
```


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

Build failed in Jenkins: build-master-slowbuild #3027

[jenkins]

See 

--
[...truncated 28723 lines...]
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.1:findbugs (findbugs) @ cloud-quickcloud 
---
[INFO] 
[INFO] <<< findbugs-maven-plugin:3.0.1:check (cloudstack-findbugs) @ 
cloud-quickcloud <<<
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.1:check (cloudstack-findbugs) @ 
cloud-quickcloud ---
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:instrument (default-cli) @ 
cloud-quickcloud ---
[WARNING] No files to instrument.
[INFO] NOT adding cobertura ser file to attached artifacts list.
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
cloud-quickcloud ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @ 
cloud-quickcloud ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ cloud-quickcloud 
---
[INFO] 
[INFO] <<< cobertura-maven-plugin:2.6:cobertura (default-cli) @ 
cloud-quickcloud <<<
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:cobertura (default-cli) @ 
cloud-quickcloud ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache CloudStack Developer Tools - Checkstyle Configuration  SUCCESS 
[1.728s]
[INFO] Apache CloudStack . SUCCESS [2.155s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.787s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [18.653s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:30.550s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.110s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [53.396s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [26.920s]
[INFO] Apache CloudStack API . SUCCESS [1:50.390s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [17.707s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [29.923s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.086s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [27.744s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.712s]
[INFO] Apache CloudStack Core  SUCCESS [1:21.607s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.743s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.380s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.239s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:06.745s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.861s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.181s]
[INFO] Apache CloudStack Server .. SUCCESS [4:14.807s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.697s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.201s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:22.848s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.070s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.435s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.201s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.150s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [29.893s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [25.989s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [26.073s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [23.134s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.001s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.004s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [7.340s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.995s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.584s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[24.613s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[37.241s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.375s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.190s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [15.857s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.635s]
[INFO] Apache Cloud

Build failed in Jenkins: build-master-slowbuild #3028

[jenkins]

See 

--
[...truncated 28713 lines...]
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.1:findbugs (findbugs) @ cloud-quickcloud 
---
[INFO] 
[INFO] <<< findbugs-maven-plugin:3.0.1:check (cloudstack-findbugs) @ 
cloud-quickcloud <<<
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.1:check (cloudstack-findbugs) @ 
cloud-quickcloud ---
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:instrument (default-cli) @ 
cloud-quickcloud ---
[WARNING] No files to instrument.
[INFO] NOT adding cobertura ser file to attached artifacts list.
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
cloud-quickcloud ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @ 
cloud-quickcloud ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ cloud-quickcloud 
---
[INFO] 
[INFO] <<< cobertura-maven-plugin:2.6:cobertura (default-cli) @ 
cloud-quickcloud <<<
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:cobertura (default-cli) @ 
cloud-quickcloud ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache CloudStack Developer Tools - Checkstyle Configuration  SUCCESS 
[2.149s]
[INFO] Apache CloudStack . SUCCESS [3.615s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [1.126s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.566s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:30.856s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.113s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [54.097s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.957s]
[INFO] Apache CloudStack API . SUCCESS [1:52.018s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.173s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [29.289s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.089s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.160s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.201s]
[INFO] Apache CloudStack Core  SUCCESS [1:21.933s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.633s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.818s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.297s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:07.594s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.780s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.276s]
[INFO] Apache CloudStack Server .. SUCCESS [4:12.758s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.381s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.582s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:23.831s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.076s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.483s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.364s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.562s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [30.192s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.289s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [31.002s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [20.740s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.336s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.548s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [7.902s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [1.013s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.801s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.451s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[37.800s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.144s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.291s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [15.158s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.558s]
[INFO] Apache Cloud

Re: Help with JUnits

[B Prakash]

Yes it does, thanks.  Next I am going through the code to identify a pattern 
(like class name ending with TEST :-)) to identify junit code.   I am unable to 
zero in on few of the operations ie I am unable to find unit test for this 
operation UserVmManagerImpl.commitUserVm.   I am still looking for it.  Is the 
Junit coverage 100%?  


From: Mike Tutkowski 
Sent: Tuesday, January 19, 2016 3:01 AM
To: dev@cloudstack.apache.org
Subject: Re: Help with JUnits

So, yeah, unit tests are written in Java while integration tests are
written in Python using Marvin...if that helps clarify things a bit more.

On Tue, Jan 19, 2016 at 12:45 AM, B Prakash  wrote:

> Thanks Mike, I read through the link and also saw the video, this answers
> part of my question about executing the unit tests.  The other part of the
> questions still remains ie were are junits written in Java for this class
> and operation UserVmManagerImpl.commitUserVm.
>
> How do we check the junit coverage for a particular class and
> implementation in it?  Where do I start looking for them and confirm if
> they exist?
>
> 
> From: Mike Tutkowski 
> Sent: Monday, January 18, 2016 11:51 PM
> To: dev@cloudstack.apache.org
> Subject: Re: Help with JUnits
>
> Here's a video of a presentation I gave about Marvin (from CloudStack Days
> in Austin last year):
>
> https://www.youtube.com/watch?v=N_eKBA_TeOs
>
> On Mon, Jan 18, 2016 at 9:49 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
> > Does this help?
> >
> >
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> >
> > On Mon, Jan 18, 2016 at 8:56 PM, B Prakash  wrote:
> >
> >> Hi,
> >>
> >>
> >> Please can someone help me with identifying and amending junits for
> >> UserVmManagerImpl.commitUserVm?  I see a test class called
> >> UserVmManagerTest but I dont see a good junits coverage here.  Also
> link in
> >> the 'Developer > Testing > Unit testing with JUnit and Spring' doesnt
> give
> >> out lot of details on junits.
> >>
> >>   1.  Am I looking at the right place for junits for the class
> >> UserVmManagerImpl.commitUserVm?
> >>   2.  Is there any other link that provides more details on JUnits?
> >>   3.  Any document or resource explaing cloudstack JUnit implementation
> >> in greater detail would be of great help.
> >>   4.  If I want to track junit of this class, how do I track and execute
> >> them?
> >>
> >>
> >> Regards,
> >>
> >> Prakash
> >>
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the cloud
> > *™*
> >
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud
> *™*
>



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

Re: [ANNOUNCE] New PMC member: Boris Roman Schrijver

[Sanjeev N]

Congrats Boris !!

On Wed, Jan 20, 2016 at 12:10 AM, ilya  wrote:

> Warm welcome Boris..
>
> On 1/19/16 4:15 AM, Wilder Rodrigues wrote:
> > The Project Management Committee (PMC) for Apache CloudStack is pleased
> to
> > announce that Boris Roman Schrijver has accepted our invitation to join
> the PMC.
> >
> > Please join me in congratulating him.
> >
> > On behalf of the Apache CloudStack PMC
> > Wilder Rodrigues
> >
>

Re: Help with JUnits

[Mike Tutkowski]

I'm not sure what CloudStack's test-coverage numbers look like (for either
unit or integration), but I suspect we are quite well below 100% coverage.

On Tue, Jan 19, 2016 at 10:34 PM, B Prakash  wrote:

> Yes it does, thanks.  Next I am going through the code to identify a
> pattern (like class name ending with TEST :-)) to identify junit code.   I
> am unable to zero in on few of the operations ie I am unable to find unit
> test for this operation UserVmManagerImpl.commitUserVm.   I am still
> looking for it.  Is the Junit coverage 100%?
>
> 
> From: Mike Tutkowski 
> Sent: Tuesday, January 19, 2016 3:01 AM
> To: dev@cloudstack.apache.org
> Subject: Re: Help with JUnits
>
> So, yeah, unit tests are written in Java while integration tests are
> written in Python using Marvin...if that helps clarify things a bit more.
>
> On Tue, Jan 19, 2016 at 12:45 AM, B Prakash  wrote:
>
> > Thanks Mike, I read through the link and also saw the video, this answers
> > part of my question about executing the unit tests.  The other part of
> the
> > questions still remains ie were are junits written in Java for this class
> > and operation UserVmManagerImpl.commitUserVm.
> >
> > How do we check the junit coverage for a particular class and
> > implementation in it?  Where do I start looking for them and confirm if
> > they exist?
> >
> > 
> > From: Mike Tutkowski 
> > Sent: Monday, January 18, 2016 11:51 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: Help with JUnits
> >
> > Here's a video of a presentation I gave about Marvin (from CloudStack
> Days
> > in Austin last year):
> >
> > https://www.youtube.com/watch?v=N_eKBA_TeOs
> >
> > On Mon, Jan 18, 2016 at 9:49 PM, Mike Tutkowski <
> > mike.tutkow...@solidfire.com> wrote:
> >
> > > Does this help?
> > >
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python
> > >
> > > On Mon, Jan 18, 2016 at 8:56 PM, B Prakash  wrote:
> > >
> > >> Hi,
> > >>
> > >>
> > >> Please can someone help me with identifying and amending junits
> for
> > >> UserVmManagerImpl.commitUserVm?  I see a test class called
> > >> UserVmManagerTest but I dont see a good junits coverage here.  Also
> > link in
> > >> the 'Developer > Testing > Unit testing with JUnit and Spring' doesnt
> > give
> > >> out lot of details on junits.
> > >>
> > >>   1.  Am I looking at the right place for junits for the class
> > >> UserVmManagerImpl.commitUserVm?
> > >>   2.  Is there any other link that provides more details on JUnits?
> > >>   3.  Any document or resource explaing cloudstack JUnit
> implementation
> > >> in greater detail would be of great help.
> > >>   4.  If I want to track junit of this class, how do I track and
> execute
> > >> them?
> > >>
> > >>
> > >> Regards,
> > >>
> > >> Prakash
> > >>
> > >
> > >
> > >
> > > --
> > > *Mike Tutkowski*
> > > *Senior CloudStack Developer, SolidFire Inc.*
> > > e: mike.tutkow...@solidfire.com
> > > o: 303.746.7302
> > > Advancing the way the world uses the cloud
> > > *™*
> > >
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the cloud
> > *™*
> >
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud
> *™*
>



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

[GitHub] cloudstack pull request: OSPF: WIP: adding dynamically routing cap...

[agneya2001]

GitHub user agneya2001 opened a pull request:

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

OSPF: WIP: adding dynamically routing capability to VPS 

Ticket: https://issues.apache.org/jira/browse/CLOUDSTACK-9163

FS: 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Dynamically+routed+VPC

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

$ git pull https://github.com/shapeblue/cloudstack master-ospf

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

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


commit d8d178f5ca45d565c4e31fea05f4e45ada410daa
Author: Abhinandan Prateek 
Date:   2015-12-24T11:53:27Z

OSPF: WIP: addign dynamically routing capability to VPS and adding config
item structure to VR quagga configuration




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

Build failed in Jenkins: build-master-slowbuild #3029

[jenkins]

See 

--
[...truncated 28713 lines...]
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.1:findbugs (findbugs) @ cloud-quickcloud 
---
[INFO] 
[INFO] <<< findbugs-maven-plugin:3.0.1:check (cloudstack-findbugs) @ 
cloud-quickcloud <<<
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.1:check (cloudstack-findbugs) @ 
cloud-quickcloud ---
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:instrument (default-cli) @ 
cloud-quickcloud ---
[WARNING] No files to instrument.
[INFO] NOT adding cobertura ser file to attached artifacts list.
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
cloud-quickcloud ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @ 
cloud-quickcloud ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ cloud-quickcloud 
---
[INFO] 
[INFO] <<< cobertura-maven-plugin:2.6:cobertura (default-cli) @ 
cloud-quickcloud <<<
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:cobertura (default-cli) @ 
cloud-quickcloud ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache CloudStack Developer Tools - Checkstyle Configuration  SUCCESS 
[1.702s]
[INFO] Apache CloudStack . SUCCESS [2.127s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.766s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [18.725s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:30.109s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.108s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [53.620s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.438s]
[INFO] Apache CloudStack API . SUCCESS [1:48.630s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [17.839s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [29.115s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.086s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [27.367s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.616s]
[INFO] Apache CloudStack Core  SUCCESS [1:20.797s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.210s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [38.183s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.200s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:08.219s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.819s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.234s]
[INFO] Apache CloudStack Server .. SUCCESS [4:10.612s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [38.346s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.824s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:20.697s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.066s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.425s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.054s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.410s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [30.307s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.364s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [25.620s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [20.632s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.319s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.473s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [8.282s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.967s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.541s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.645s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[35.583s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.049s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.438s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [15.819s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.682s]
[INFO] Apache Cloud

[GitHub] cloudstack pull request: CLOUDSTACK-9244 Fix setting up RFC1918 ro...

[DaanHoogland]

Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/1352#issuecomment-173112205
  
looks good


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