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

[nitin-maharana]

Github user nitin-maharana commented on the pull request:

https://github.com/apache/cloudstack/pull/1273#issuecomment-169927533
  
Closing this PR as made a new PR #1319 (Against 4.7 which will be merged in 
master later).


---
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-9132: API createVolume takes e...

[nitin-maharana]

Github user nitin-maharana closed the pull request at:

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


---
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-9132: API createVolume takes e...

[nitin-maharana]

Github user nitin-maharana commented on the pull request:

https://github.com/apache/cloudstack/pull/1319#issuecomment-169927365
  
Reference PR #1273 (Against master) with 3 LGTMs. This PR (against 4.7) 
contains the same code change.


---
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: Minor releases!

[Daan Hoogland]

​I totally agree Marcus, with one small addition. In our present scheme we
can mark any 4.x as LTS if we maintain the discipline ​of fixing any bug on
the oldest version known to contain the bug and merge the fix forward. some
LIMITATION OF WARRANTY  (tm) apply of course; if a fix requires some kind
of database change...

Basically our present release scheme was designed to address the concerns
you are describing.

On Thu, Jan 7, 2016 at 10:30 PM, Marcus  wrote:

> A few things to note:
>
> 1. I repeated this until I felt bad about harping on it, but we were seeing
> new functionality slip into minors all the time. The idea that 4.4.x ->
> 4.4.y upgrade was safer than 4.4.x -> 4.5.0 (just made up versions as an
> example) is unfortunately wrong.
>
> 2. I agree that large production environments will probably only want to
> upgrade their cloud once every few months, at the most. Probably less, due
> to internal testing and qualification for each chosen major.  I understand
> the mindset someone might have when they're told that they need to jump six
> major releases and pull in dozens of new features to fix one or two bugs
> they have come across in their otherwise stable cloud. Suddenly they're
> thinking they need to do far more integration testing with their internal
> CloudStack consumers and their infrastructure.  Even if the releases are
> more stable, any major release is going to be treated as an unknown and
> require rigorous qualifications.  Due to #1, this point is largely moot,
> but if we were doing proper bugfix releases, or chose to go that direction,
> it might be something important to think about.
>
> In the end, it probably doesn't matter much either way for routine
> maintenance. If you were upgrading once every 6-12 months to keep up with
> the previous major cycle, you can still upgrade at that pace and the delta
> in changes between your chosen minors will be roughly what it was before,
> even if the minors aren't contiguous numbers. The place this breaks down is
> that while you can pick a release from any month and decide to use that as
> your next 6-12 month version, there are far fewer people running your
> version or focusing on it for bugfixes; you've been left behind once you've
> settled on running that version. So you either have to get with the program
> and figure out how to do rapid releases in your environment that is averse
> to change and full of red tape, or start maintaining your own release
> builds. That's kind of a crappy choice that we're putting on our less agile
> users.
>
> To that end, I like the idea of the LTS, simply tagging majors as the
> preferred version for people who require a slower upgrade. This would focus
> those users into certain versions and improve maintenance on them. It could
> even just be unofficial, a version that CloudStack users agree on. From a
> versioning perspective this doesn't sound a whole lot different from the
> old scheme where 4.4 and 4.5 were essentially an LTS, but it is still
> better because we've improved the release process. Of course, we still have
> to reign in the changes to these LTS versions and stop allowing new
> features to creep in simply because customers who are on that LTS need the
> feature.
>




-- 
Daan

Re: Minor releases!

[Daan Hoogland]

one other remark: no matter what our release scheme, we need for every one
to do twice as much reviews as contributions in order for our present way
of working to be successful. And in this doing a review means sticking with
a PR until it is good enough to go in, not just make initial remarks. We
have close to 200 open PRs now and it has not been getting better since we
moved to github. I am starting to feel this move was no good.

Not really related but: We can not easily close PRs or merge them wich is
only a hassle and not stopping us but it's a bother to the RM.

On Thu, Jan 7, 2016 at 10:30 PM, Marcus  wrote:

> A few things to note:
>
> 1. I repeated this until I felt bad about harping on it, but we were seeing
> new functionality slip into minors all the time. The idea that 4.4.x ->
> 4.4.y upgrade was safer than 4.4.x -> 4.5.0 (just made up versions as an
> example) is unfortunately wrong.
>
> 2. I agree that large production environments will probably only want to
> upgrade their cloud once every few months, at the most. Probably less, due
> to internal testing and qualification for each chosen major.  I understand
> the mindset someone might have when they're told that they need to jump six
> major releases and pull in dozens of new features to fix one or two bugs
> they have come across in their otherwise stable cloud. Suddenly they're
> thinking they need to do far more integration testing with their internal
> CloudStack consumers and their infrastructure.  Even if the releases are
> more stable, any major release is going to be treated as an unknown and
> require rigorous qualifications.  Due to #1, this point is largely moot,
> but if we were doing proper bugfix releases, or chose to go that direction,
> it might be something important to think about.
>
> In the end, it probably doesn't matter much either way for routine
> maintenance. If you were upgrading once every 6-12 months to keep up with
> the previous major cycle, you can still upgrade at that pace and the delta
> in changes between your chosen minors will be roughly what it was before,
> even if the minors aren't contiguous numbers. The place this breaks down is
> that while you can pick a release from any month and decide to use that as
> your next 6-12 month version, there are far fewer people running your
> version or focusing on it for bugfixes; you've been left behind once you've
> settled on running that version. So you either have to get with the program
> and figure out how to do rapid releases in your environment that is averse
> to change and full of red tape, or start maintaining your own release
> builds. That's kind of a crappy choice that we're putting on our less agile
> users.
>
> To that end, I like the idea of the LTS, simply tagging majors as the
> preferred version for people who require a slower upgrade. This would focus
> those users into certain versions and improve maintenance on them. It could
> even just be unofficial, a version that CloudStack users agree on. From a
> versioning perspective this doesn't sound a whole lot different from the
> old scheme where 4.4 and 4.5 were essentially an LTS, but it is still
> better because we've improved the release process. Of course, we still have
> to reign in the changes to these LTS versions and stop allowing new
> features to creep in simply because customers who are on that LTS need the
> feature.
>
> On Thu, Jan 7, 2016 at 12:30 PM Wei ZHOU  wrote:
>
> > 2016-01-07 15:24 GMT+01:00 Rene Moser :
> >
> > > Hi Remi
> > >
> > > On 01/07/2016 02:28 PM, Remi Bergsma wrote:
> > > > I simply don’t understand why you need lots and lots of minor
> versions.
> > > I do understand you need a stable cloud, and that’s exactly what we’re
> > > achieving here.
> > > >
> > > > We changed our way of working from 4.6 on. Before that, it took _a
> > long_
> > > time to release new versions (be it major, minor or patch). Releases
> were
> > > not high quality so people waited for .1 or .2 to be released. When you
> > did
> > > eventually upgrade, you’d hit major trouble. It was simply not OK. And
> > many
> > > minor releases don’t help here. The root cause of the trouble is that
> the
> > > whole idea of branching off a new version and have a QA team make it
> > stable
> > > (while the rest continues on master) doesn’t make sense (any more).
> > That’s
> > > why in the summer of 2015 we decided to stabilise master instead and
> > > release from that. [1] One final time it took a great effort to make a
> > > branch stable.
> > > >
> > > > We released 4.6 in Nov 2015
> > > > We released 4.7 in Dec 2015
> > > > We will release 4.8 in Jan 2016 (unless people think I should stop
> > doing
> > > this)
> > > >
> > > > In between, we submitted patch releases to quickly address bugs
> (4.6.1,
> > > 4.6.2 etc).
> > >
> > > What about 4.5? 4.4? Is 4.6 still getting 4.6.3? Users don't see that.
> > >
> > > > You know what? It’s 

Re: CloudStack 4.6.2 RPMs

[mvs babu]

Hi Rohit,

Thanks for the information. Sorry for late reply, I was in leave.

As per Apache  CloudStack documentation 
(http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.6.0/upgrade/upgrade-4.3.html#update-system-vm-templates)
 we need to register two systemvm templates (4.5 and 4.6) while upgrading from 
4.4 or lower version to 4.6. Can we use same templates for 4.6.2 too? 

Thank you,
Suneel Mallela





From: Rohit Yadav
Sent: ‎Monday‎, ‎January‎ ‎4‎, ‎2016 ‎10‎:‎00‎ ‎PM
To: us...@cloudstack.apache.org
Cc: dev@cloudstack.apache.org




Hi, 



You may use the following for CentOS6.x:

http://packages.shapeblue.com/cloudstack/upstream/centos/4.6/




Regards..







 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


 



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 04-Jan-2016, at 11:48 AM, mvs babu  wrote:



Hi All,




We are trying to upgrade ACS from 4.3.1 to 4.6.2. But found there are no RPMs 
at http://cloudstack.apt-get.eu/centos/6/4.6/. Where can we get RPMs for 
ACS4.6.2?






Thank you,
Suneel Mallela


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-8968: UI icon over VM snapshot...

[nitin-maharana]

Github user nitin-maharana commented on the pull request:

https://github.com/apache/cloudstack/pull/1150#issuecomment-169931078
  
Closing this PR as made a new PR #1320 (Against 4.7 which will be merged in 
master later).


---
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-8968: UI icon over VM snapshot...

[nitin-maharana]

Github user nitin-maharana closed the pull request at:

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


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

[nitin-maharana]

Github user nitin-maharana closed the pull request at:

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


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

[nitin-maharana]

Github user nitin-maharana commented on the pull request:

https://github.com/apache/cloudstack/pull/823#issuecomment-169935147
  
Closing this PR as made a new PR #1321 (Against 4.7 which will be merged in 
master later).


---
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-9132: API createVolume takes e...

[nitin-maharana]

Github user nitin-maharana commented on the pull request:

https://github.com/apache/cloudstack/pull/1319#issuecomment-169935900
  
Hi @remibergsma, I created all my pending PRs against 4.7. Can you please 
review once. 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 #2934

[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.797s]
[INFO] Apache CloudStack . SUCCESS [2.099s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.801s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [20.640s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:30.832s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.110s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [53.871s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.623s]
[INFO] Apache CloudStack API . SUCCESS [1:48.521s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.493s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [30.954s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.087s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [27.967s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [25.068s]
[INFO] Apache CloudStack Core  SUCCESS [1:20.971s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.766s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.365s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [15.787s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:05.939s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.928s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [26.229s]
[INFO] Apache CloudStack Server .. SUCCESS [4:15.060s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [36.978s]
[INFO] Apache CloudStack Usage Server  SUCCESS [43.649s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:23.475s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.068s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.441s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [53.788s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [49.256s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [30.785s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [25.862s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [31.385s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [21.072s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.515s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.425s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [7.621s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [1.014s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.742s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.377s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[36.536s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [18.155s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.232s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [15.298s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[17.245s]
[INFO] Apache 

Re: CloudStack 4.6.2 RPMs

[Rohit Yadav]

Hi,

> On 08-Jan-2016, at 11:52 AM, mvs babu  wrote:
>
> Hi Rohit,
>
> Thanks for the information. Sorry for late reply, I was in leave.
>
> As per Apache  CloudStack documentation 
> (http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.6.0/upgrade/upgrade-4.3.html#update-system-vm-templates)
>  we need to register two systemvm templates (4.5 and 4.6) while upgrading 
> from 4.4 or lower version to 4.6. Can we use same templates for 4.6.2 too?

Yes, use the same 4.6 template as there is not 4.6.2 specific template.

Note: if you’ve multiple zones, you might need to copy templates across various 
secondary storage if you’re upgrading from 4.3 to 4.5+

>
> Thank you,
> Suneel Mallela
>
>
>
>
>
> From: Rohit Yadav
> Sent: ‎Monday‎, ‎January‎ ‎4‎, ‎2016 ‎10‎:‎00‎ ‎PM
> To: us...@cloudstack.apache.org
> Cc: dev@cloudstack.apache.org
>
>
>
>
> Hi,
>
>
>
> You may use the following for CentOS6.x:
>
> http://packages.shapeblue.com/cloudstack/upstream/centos/4.6/
>
>
>
>
> Regards..
>
>
>
>
>
>
>
> 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
>
>
>
>
>
>
> 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 04-Jan-2016, at 11:48 AM, mvs babu  wrote:
>
>
>
> Hi All,
>
>
>
>
> We are trying to upgrade ACS from 4.3.1 to 4.6.2. But found there are no RPMs 
> at http://cloudstack.apt-get.eu/centos/6/4.6/. Where can we get RPMs for 
> ACS4.6.2?
>
>
>
>
>
>
> Thank you,
> Suneel Mallela
>
>
> 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

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

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

[nitin-maharana]

GitHub user nitin-maharana opened a pull request:

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

CLOUDSTACK-9132: API createVolume takes empty string for name parameter

Steps to Reproduce:


Create a volume using createVolume API where parameter name is empty.
It creates a volume with empty name.
But the name parameter is mandatory.(Issue)

Expected Behaviour:


It shouldn't create a volume with an empty name. Error should be returned.

Solution:
===

Added a condition to check in case of empty string. If the name is an empty 
string, it generates a random name for the volume. Made the name field optional 
in UI as well as in API.

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

$ git pull https://github.com/nitin-maharana/CloudStack 
CloudStack-Nitin15_4.7

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

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


commit 55f8b32aa00baf0609f54891230269ed97bedb5a
Author: Nitin Kumar Maharana 
Date:   2015-12-29T11:15:41Z

CLOUDSTACK-9132: API createVolume takes empty string for name parameter

Added conditions to check if the name is empty or blank.
If it is empty or blank, then it generates a random name.
Made the name field as optional in UI as well as in API.
Added required unit tests.




---
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: [4.7] Critical VPCVR issues fixed: CLOUDS...

[wilderrodrigues]

Github user wilderrodrigues commented on the pull request:

https://github.com/apache/cloudstack/pull/1277#issuecomment-169928856
  
Hi @DaanHoogland and @koushik-das 

Now I see your point. Thanks for the screenshot, @DaanHoogland. I checked 
the Github diff but did not notice that the file was omitted, hence my question.

I'm splitting the NetworkOrchestrator related commits (formatting and 
fixing) so you can analyse the changes.

Cheers,
Wilder


---
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-8968: UI icon over VM snapshot...

[nitin-maharana]

GitHub user nitin-maharana opened a pull request:

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

CLOUDSTACK-8968: UI icon over VM snapshot to deploy user instance

Added a new Icon in Instance page to launch the VM from the snapshot.

A new icon over VM snapshot object, which upon invoked will open a deploy 
user instance wizard, where there is no choice to choose zone and ISO or 
template to deploy the user instance from.

1) A new icon to indicate deploy user instance from VM snapshot
2) The new icon is placed as an operation over each VM snapshot object.
3) Clicking this icon will show the wizard to deploy user instance, which 
is same as wizard for normal user instance except that zone selection page and 
ISO/template selection page would not be present in this wizard.

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

$ git pull https://github.com/nitin-maharana/CloudStack 
CloudStack-Nitin12_4.7

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

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


commit 55183fd81804e41f9fa8e335a3282ef42e536af7
Author: Nitin Kumar Maharana 
Date:   2015-12-07T18:14:37Z

CLOUDSTACK-8968: UI icon over VM snapshot to deploy user instance

Added a new Icon in Instance page to launch the VM from the snapshot.
Only supports in case of VMware.

Conflicts:
client/WEB-INF/classes/resources/messages.properties




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

gitlab.apache.org

[Daan Hoogland]

We, cloudstack-dev-list-users have been talking about moving more
functionality to github. This is being rejected by the foundation so far
for (in my view obvious) reasons of governance. The functionality is
however missed dearly so speaking with an ex-member he suggested we install
a machine with gitlab under the apache domain and let it administer our git
repos to gain similar functionality. Is this being discussed already and
should we do so?

-- 
Daan

[GitHub] cloudstack pull request: CLOUDSTACK-8968: UI icon over VM snapshot...

[nitin-maharana]

Github user nitin-maharana commented on the pull request:

https://github.com/apache/cloudstack/pull/1320#issuecomment-169931271
  
Reference PR #1150 (Against 4.6). This PR (against 4.7) contains the same 
code change with one conflict which I resolved.


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

[nitin-maharana]

GitHub user nitin-maharana opened a pull request:

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

CLOUDSTACK-8847: ListServiceOfferings is returning incompatible tagged 
offerings when called with VM id

When calling listServiceOfferings with VM id as parameter. It is returning 
incompatible tagged offerings. It should only list all compatible tagged 
offerings. Compatible means the new service offering should contain all the 
tags of the existing service offering(Existing offering SUBSET of new 
offering). If that is the case It should list in the result and can be upgraded 
to that offering.

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

$ git pull https://github.com/nitin-maharana/CloudStack 
CloudStack-Nitin5_4.7

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

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


commit ba0503d000250e233701a71bd8e406e52b6ad110
Author: Nitin Kumar Maharana 
Date:   2015-09-14T16:32:37Z

CLOUDSTACK-8847: ListServiceOfferings is returning incompatible tagged 
offerings when called with VM id

Fixed the subset and superset issue.
Added unit test for 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-8847: ListServiceOfferings is ...

[nitin-maharana]

Github user nitin-maharana commented on the pull request:

https://github.com/apache/cloudstack/pull/1321#issuecomment-169934934
  
Reference PR #823 (Against master). This PR (against 4.7) contains the same 
code change.


---
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: [4.7] Critical VPCVR issues fixed: CLOUDS...

[wilderrodrigues]

Github user wilderrodrigues commented on the pull request:

https://github.com/apache/cloudstack/pull/1277#issuecomment-169939093
  
@DaanHoogland and @koushik-das 

I split the commits and pushed the changes. You now should be able to 
review the actual changes I have applied to NetworkOchestrator file. The commit 
ID is a0a230af7b1eb1bf24da8ed0d9e2d1a4fc6a5fe4

I built the source, including unit tests execution, to make sure all 
compiles and I also did a diff between the old file and the 1 changes after the 
2 commits.

* Build result
```
[INFO] 

[INFO] BUILD SUCCESS
[INFO] 

[INFO] Total time: 17:44 min
[INFO] Finished at: 2016-01-08T09:49:24+01:00
[INFO] Final Memory: 121M/947M
[INFO] 

```

* Diff output
```
sbpltk1zffh04:asf_cloudstack wrodrigues$ diff ~/dev/gc_net.java 
engine/orchestration/src/org/apache/cloudstack/engine/orchestration/NetworkOrchestrator.java
3352d3351
< 
```

As you can see, the difference is irrelevant.

Cheers,
Wilder


---
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-9104: VM naming convention in ...

[priyankparihar]

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

https://github.com/apache/cloudstack/pull/1302#discussion_r49171092
  
--- Diff: 
plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/resource/VmwareResource.java
 ---
@@ -2032,11 +2032,20 @@ int getReservedCpuMHZ(VirtualMachineTO vmSpec) {
 
 // Pair
 private Pair composeVmNames(VirtualMachineTO vmSpec) {
-String vmInternalCSName = vmSpec.getName();
-String vmNameOnVcenter = vmSpec.getName();
-if (_instanceNameFlag && vmSpec.getHostName() != null) {
-vmNameOnVcenter = vmSpec.getHostName();
+
+String vmInternalCSName = null;
+String vmNameOnVcenter  = null;
+if(vmSpec != null)
--- End diff --

@rafaelweingartner Currently. it is not possible. Because user does not 
generate it. Cloud stack generates it only if it has all required info. 
otherwise it does not call this function.


---
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: Fix mariadb related listCapacity bug (CLO...

[remibergsma]

Github user remibergsma commented on the pull request:

https://github.com/apache/cloudstack/pull/1314#issuecomment-170095829
  
LGTM, works fine:
![screen shot 2016-01-08 at 15 43 
45](https://cloud.githubusercontent.com/assets/1630096/12206866/a89be932-b643-11e5-8570-0e7bc9c81170.png)



---
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-9216: Fix DHCP lease removal l...

[remibergsma]

Github user remibergsma commented on the pull request:

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

```
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
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
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 the password file in the Router VM ... === TestName: 
test_isolate_network_password_server | 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 to verify access to loadbalancer haproxy admin stats page ... === 
TestName: test02_internallb_haproxy_stats_on_all_interfaces | Status : SUCCESS 
===
ok
Test create, assign, remove of an Internal LB with roundrobin http traffic 
to 3 vm's ... === TestName: test_01_internallb_roundrobin_1VPC_3VM_HTTP_port80 
| 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 Remote Access VPN in VPC ... === TestName: test_vpc_remote_access_vpn 
| Status : SUCCESS ===
ok
Test VPN in VPC ... === TestName: test_vpc_site2site_vpn | Status : SUCCESS 
===
ok
Test for port forwarding on source NAT ... === TestName: 
test_01_port_fwd_on_src_nat | Status : SUCCESS ===
ok
Test for port forwarding on non source NAT ... === TestName: 
test_02_port_fwd_on_non_src_nat | Status : SUCCESS ===
ok
Test for reboot router ... === TestName: test_reboot_router | Status : 
SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... === 
TestName: test_network_rules_acquired_public_ip_1_static_nat_rule | Status : 
SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... === 
TestName: test_network_rules_acquired_public_ip_2_nat_rule | Status : SUCCESS 
===

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

[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.945s]
[INFO] Apache CloudStack . SUCCESS [2.229s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.800s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [20.493s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:29.882s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.106s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [53.782s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [28.137s]
[INFO] Apache CloudStack API . SUCCESS [1:58.386s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.305s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [29.716s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.085s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [27.445s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.805s]
[INFO] Apache CloudStack Core  SUCCESS [1:22.811s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.400s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.376s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.562s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:09.645s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.552s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.246s]
[INFO] Apache CloudStack Server .. SUCCESS [4:15.137s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.464s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.761s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:22.226s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.068s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.441s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.737s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [47.677s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [28.843s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.541s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [22.115s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [22.722s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.111s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.355s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [8.432s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.968s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.157s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.402s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[37.238s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.487s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.169s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [14.955s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[17.512s]
[INFO] Apache 

[GitHub] cloudstack pull request: CLOUDSTACK-9202 Bump ssh timeout for VR c...

[remibergsma]

Github user remibergsma commented on the pull request:

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

```
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
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
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 the password file in the Router VM ... === TestName: 
test_isolate_network_password_server | 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 to verify access to loadbalancer haproxy admin stats page ... === 
TestName: test02_internallb_haproxy_stats_on_all_interfaces | Status : SUCCESS 
===
ok
Test create, assign, remove of an Internal LB with roundrobin http traffic 
to 3 vm's ... === TestName: test_01_internallb_roundrobin_1VPC_3VM_HTTP_port80 
| 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 Remote Access VPN in VPC ... === TestName: test_vpc_remote_access_vpn 
| Status : SUCCESS ===
ok
Test VPN in VPC ... === TestName: test_vpc_site2site_vpn | Status : SUCCESS 
===
ok
Test for port forwarding on source NAT ... === TestName: 
test_01_port_fwd_on_src_nat | Status : SUCCESS ===
ok
Test for port forwarding on non source NAT ... === TestName: 
test_02_port_fwd_on_non_src_nat | Status : SUCCESS ===
ok
Test for reboot router ... === TestName: test_reboot_router | Status : 
SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... === 
TestName: test_network_rules_acquired_public_ip_1_static_nat_rule | Status : 
SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... === 
TestName: test_network_rules_acquired_public_ip_2_nat_rule | Status : SUCCESS 
===

[GitHub] cloudstack pull request: CLOUDSTACK-8988: Removed unused adapters ...

[rodrigo93]

Github user rodrigo93 commented on the pull request:

https://github.com/apache/cloudstack/pull/943#issuecomment-170073454
  
Many thanks for the help everyone! 


---
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: Fixed return type Void to void in DataMot...

[rodrigo93]

Github user rodrigo93 commented on the pull request:

https://github.com/apache/cloudstack/pull/969#issuecomment-170073320
  
Hello everyone. Sorry to bother you but, how are the tests going?
Is there anything else that I can 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-9181 Prevent syntax error in c...

[remibergsma]

Github user remibergsma commented on the pull request:

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

```
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
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
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 the password file in the Router VM ... === TestName: 
test_isolate_network_password_server | 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 to verify access to loadbalancer haproxy admin stats page ... === 
TestName: test02_internallb_haproxy_stats_on_all_interfaces | Status : SUCCESS 
===
ok
Test create, assign, remove of an Internal LB with roundrobin http traffic 
to 3 vm's ... === TestName: test_01_internallb_roundrobin_1VPC_3VM_HTTP_port80 
| 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 Remote Access VPN in VPC ... === TestName: test_vpc_remote_access_vpn 
| Status : SUCCESS ===
ok
Test VPN in VPC ... === TestName: test_vpc_site2site_vpn | Status : SUCCESS 
===
ok
Test for port forwarding on source NAT ... === TestName: 
test_01_port_fwd_on_src_nat | Status : SUCCESS ===
ok
Test for port forwarding on non source NAT ... === TestName: 
test_02_port_fwd_on_non_src_nat | Status : SUCCESS ===
ok
Test for reboot router ... === TestName: test_reboot_router | Status : 
SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... === 
TestName: test_network_rules_acquired_public_ip_1_static_nat_rule | Status : 
SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... === 
TestName: test_network_rules_acquired_public_ip_2_nat_rule | Status : SUCCESS 
===

[GitHub] cloudstack pull request: [4.7] ADD Force UDP encapsulation option ...

[remibergsma]

Github user remibergsma commented on the pull request:

https://github.com/apache/cloudstack/pull/1317#issuecomment-170097102
  
LGTM

https://cloud.githubusercontent.com/assets/1630096/12206985/64ba76d8-b644-11e5-89dd-91626b5bf5e4.png;>

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:

```
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
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
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 the password file in the Router VM ... === TestName: 
test_isolate_network_password_server | 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 to verify access to loadbalancer haproxy admin stats page ... === 
TestName: test02_internallb_haproxy_stats_on_all_interfaces | Status : SUCCESS 
===
ok
Test create, assign, remove of an Internal LB with roundrobin http traffic 
to 3 vm's ... === TestName: test_01_internallb_roundrobin_1VPC_3VM_HTTP_port80 
| 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 Remote Access VPN in VPC ... === TestName: test_vpc_remote_access_vpn 
| Status : SUCCESS ===
ok
Test VPN in VPC ... === TestName: test_vpc_site2site_vpn | Status : SUCCESS 
===
ok
Test for port forwarding on source NAT ... === TestName: 
test_01_port_fwd_on_src_nat | Status : SUCCESS ===
ok
Test for port forwarding on non source NAT ... === TestName: 
test_02_port_fwd_on_non_src_nat | Status : SUCCESS ===
ok
Test for reboot router ... === TestName: test_reboot_router | Status : 
SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... === 
TestName: test_network_rules_acquired_public_ip_1_static_nat_rule | Status : 
SUCCESS ===
ok
Test for Router rules for network rules on acquired 

[GitHub] cloudstack pull request: CLOUDSTACK-9204 Do not error when staticr...

[remibergsma]

Github user remibergsma commented on the pull request:

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

```
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
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
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 the password file in the Router VM ... === TestName: 
test_isolate_network_password_server | 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 to verify access to loadbalancer haproxy admin stats page ... === 
TestName: test02_internallb_haproxy_stats_on_all_interfaces | Status : SUCCESS 
===
ok
Test create, assign, remove of an Internal LB with roundrobin http traffic 
to 3 vm's ... === TestName: test_01_internallb_roundrobin_1VPC_3VM_HTTP_port80 
| 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 Remote Access VPN in VPC ... === TestName: test_vpc_remote_access_vpn 
| Status : SUCCESS ===
ok
Test VPN in VPC ... === TestName: test_vpc_site2site_vpn | Status : SUCCESS 
===
ok
Test for port forwarding on source NAT ... === TestName: 
test_01_port_fwd_on_src_nat | Status : SUCCESS ===
ok
Test for port forwarding on non source NAT ... === TestName: 
test_02_port_fwd_on_non_src_nat | Status : SUCCESS ===
ok
Test for reboot router ... === TestName: test_reboot_router | Status : 
SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... === 
TestName: test_network_rules_acquired_public_ip_1_static_nat_rule | Status : 
SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... === 
TestName: test_network_rules_acquired_public_ip_2_nat_rule | Status : SUCCESS 
===

[GitHub] cloudstack pull request: CLOUDSTACK-6485 prevent ip asignment of p...

[remibergsma]

Github user remibergsma commented on the pull request:

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

```
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
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
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 the password file in the Router VM ... === TestName: 
test_isolate_network_password_server | 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 to verify access to loadbalancer haproxy admin stats page ... === 
TestName: test02_internallb_haproxy_stats_on_all_interfaces | Status : SUCCESS 
===
ok
Test create, assign, remove of an Internal LB with roundrobin http traffic 
to 3 vm's ... === TestName: test_01_internallb_roundrobin_1VPC_3VM_HTTP_port80 
| 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 Remote Access VPN in VPC ... === TestName: test_vpc_remote_access_vpn 
| Status : SUCCESS ===
ok
Test VPN in VPC ... === TestName: test_vpc_site2site_vpn | Status : SUCCESS 
===
ok
Test for port forwarding on source NAT ... === TestName: 
test_01_port_fwd_on_src_nat | Status : SUCCESS ===
ok
Test for port forwarding on non source NAT ... === TestName: 
test_02_port_fwd_on_non_src_nat | Status : SUCCESS ===
ok
Test for reboot router ... === TestName: test_reboot_router | Status : 
SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... === 
TestName: test_network_rules_acquired_public_ip_1_static_nat_rule | Status : 
SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... === 
TestName: test_network_rules_acquired_public_ip_2_nat_rule | Status : SUCCESS 
===

[GitHub] cloudstack pull request: [4.7] Critical VPCVR issues fixed: CLOUDS...

[remibergsma]

Github user remibergsma commented on the pull request:

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

```
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
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
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 the password file in the Router VM ... === TestName: 
test_isolate_network_password_server | 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 to verify access to loadbalancer haproxy admin stats page ... === 
TestName: test02_internallb_haproxy_stats_on_all_interfaces | Status : SUCCESS 
===
ok
Test create, assign, remove of an Internal LB with roundrobin http traffic 
to 3 vm's ... === TestName: test_01_internallb_roundrobin_1VPC_3VM_HTTP_port80 
| 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 Remote Access VPN in VPC ... === TestName: test_vpc_remote_access_vpn 
| Status : SUCCESS ===
ok
Test VPN in VPC ... === TestName: test_vpc_site2site_vpn | Status : SUCCESS 
===
ok
Test for port forwarding on source NAT ... === TestName: 
test_01_port_fwd_on_src_nat | Status : SUCCESS ===
ok
Test for port forwarding on non source NAT ... === TestName: 
test_02_port_fwd_on_non_src_nat | Status : SUCCESS ===
ok
Test for reboot router ... === TestName: test_reboot_router | Status : 
SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... === 
TestName: test_network_rules_acquired_public_ip_1_static_nat_rule | Status : 
SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... === 
TestName: test_network_rules_acquired_public_ip_2_nat_rule | Status : SUCCESS 
===

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

[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.723s]
[INFO] Apache CloudStack . SUCCESS [2.096s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.770s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.410s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:30.113s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.103s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [52.537s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.604s]
[INFO] Apache CloudStack API . SUCCESS [1:48.195s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.091s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [31.072s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.086s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.569s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.759s]
[INFO] Apache CloudStack Core  SUCCESS [1:22.116s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.065s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.425s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [15.661s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:07.991s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [41.047s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.269s]
[INFO] Apache CloudStack Server .. SUCCESS [4:10.381s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [39.009s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.969s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:21.658s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.066s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.459s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.228s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.903s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [30.124s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [25.457s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [30.860s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [23.419s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [34.870s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.894s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [8.548s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.933s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.625s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.308s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[36.340s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.291s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [24.227s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [14.822s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.612s]
[INFO] Apache 

What happened to the Jenkins CI test on PRs?

[Remi Bergsma]

Hi,

What happened to the Jenkins test on PRs? It seems PR 1287 was the last one to 
have both Travis CI and Jenkins. Since then, it’s only Travis CI.

Why was it removed? (did I miss the mail?).

Regards,
Remi

[GitHub] cloudstack pull request: Admin cannot see VMs on port forwarding p...

[remibergsma]

GitHub user remibergsma opened a pull request:

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

Admin cannot see VMs on port forwarding page

On commit a902443708ee10acb9f68fff74af346a6a9fb370 the 'listAll=true' is 
removed. On some places the domainid and accountid are added but not on these. 
I added them now.

It's either doing this, or readding listAll is true. I've seeing other 
folks doing that so let's see what performs best.

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

$ git pull https://github.com/remibergsma/cloudstack vpc_ui_fix_47

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

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


commit f1861819104c43b776fa1c4083112adece6a5cf5
Author: Remi Bergsma 
Date:   2016-01-08T21:00:01Z

Admin cannot see VMs on port forwarding page

On commir a902443708ee10acb9f68fff74af346a6a9fb370 the 'listAll=true'
is removed. On some places the domainid and accountid are added but not
on these. I added them now.

It's either doing this, or readding listAll is true. I've seeing other
folks doing that so let's see what performs best.




---
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-9182: Some running VMs turned ...

[rodrigo93]

Github user rodrigo93 commented on the pull request:

https://github.com/apache/cloudstack/pull/1252#issuecomment-170130323
  
Did someone tested it? This can be very handy.

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

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

[jenkins]

See 

--
[...truncated 28733 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.742s]
[INFO] Apache CloudStack . SUCCESS [2.207s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.785s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [18.991s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:30.619s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.108s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [54.464s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.199s]
[INFO] Apache CloudStack API . SUCCESS [1:50.360s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [17.709s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [29.081s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.084s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.209s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.882s]
[INFO] Apache CloudStack Core  SUCCESS [1:21.562s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.122s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [37.286s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [13.939s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:07.694s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.064s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.885s]
[INFO] Apache CloudStack Server .. SUCCESS [4:09.304s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [38.507s]
[INFO] Apache CloudStack Usage Server  SUCCESS [43.518s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:22.157s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.076s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.465s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.434s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.903s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [30.445s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.492s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [32.032s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [20.647s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.380s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.270s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [8.844s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [1.020s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [27.059s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[24.142s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[36.379s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.508s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.402s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [16.868s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.706s]
[INFO] Apache 

[GitHub] cloudstack pull request: Fix mariadb related listCapacity bug (CLO...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-9218]Test to verify restart n...

[sanju1010]

GitHub user sanju1010 opened a pull request:

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

[CLOUDSTACK-9218]Test to verify restart network after master VR destroyed

Please refer CLOUDSTACK-9218 for more details

Test Results:
===

Test restarting RvR network without cleanup after destroying master VR ... 
=== TestName: test_restart_ntwk_MVR_destroyed | Status : SUCCESS ===
ok

--
Ran 1 test in 581.194s

OK

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

$ git pull https://github.com/sanju1010/cloudstack cs-9218

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

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


commit 43cd5ae355b637f484ad9b2c54c359a0b62d11de
Author: sanjeevn 
Date:   2016-01-07T14:02:22Z

Added new test to verify restart network after destorying master VR
Bug-Id: CLOUDSTACK-9218




---
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: [GitHub] cloudstack pull request: [CLOUDSTACK-9215]Test to verify vm deploy...

[Sanjeev N]

Will add some validations

On Fri, Jan 8, 2016 at 7:51 PM, DaanHoogland  wrote:

> Github user DaanHoogland commented on the pull request:
>
> https://github.com/apache/cloudstack/pull/1316#issuecomment-170016433
>
> test succeeds as is :
> ```
> [root@daans-dev-machinina ~]# ssh cs1 nosetests --with-marvin
> --marvin-config=/data/shared/marvin/mct-zone1-kvm1-kvm2.cfg  -s -a
> tags=advanced,required_hardware=true
> /data/git/cs1/cloudstack/test/integration/component/maint/test_vpc.py
> root@cs1's password:
>
>  Marvin Init Started 
>
> === Marvin Parse Config Successful ===
>
> === Marvin Setting TestData Successful===
>
>  Log Folder Path: /tmp//MarvinLogs//Jan_08_2016_14_17_12_EBMCRT.
> All logs will be available here 
>
> === Marvin Init Logging Successful===
>
>  Marvin Init Successful 
> ===final results are now copied to: /tmp//MarvinLogs/test_vpc_1F4ULR===
> ```
>
> LGTM but seems less useful due to my remark on line 354
>
>
> ---
> 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 #2941

[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.712s]
[INFO] Apache CloudStack . SUCCESS [2.100s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.783s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [18.996s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:30.632s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.110s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [54.617s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.706s]
[INFO] Apache CloudStack API . SUCCESS [1:49.273s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.513s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [29.842s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.086s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.144s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.485s]
[INFO] Apache CloudStack Core  SUCCESS [1:21.735s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.121s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.884s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.225s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:06.373s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [41.229s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.391s]
[INFO] Apache CloudStack Server .. SUCCESS [4:15.139s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.520s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.357s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:20.779s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.067s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.460s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.733s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [47.929s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [29.929s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.583s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [32.200s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [20.182s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.237s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.248s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [7.571s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.996s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.410s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[25.122s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[35.278s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.170s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.139s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [15.858s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.648s]
[INFO] Apache 

[GitHub] cloudstack pull request: [4.7] Critical VPCVR issues fixed: CLOUDS...

[koushik-das]

Github user koushik-das commented on the pull request:

https://github.com/apache/cloudstack/pull/1277#issuecomment-170202865
  
On latest master (without any fixes) I see that the config values 
(network.gc.interval and network.gc.wait) are read correctly. Did the following:
- Started MS
- Changed the config values to 10 secs.
- Restarted MS
- Values read correctly and GC thread was running every 10 secs. Inside the 
GC thread correct value was shown for gc.wait

@wilderrodrigues On which branch did you notice this issue? Or is it 
possible that the issue is something else?
-1 for commit a0a230a/CLOUDSTACK-9188 based on the test on master.

Regarding these network gc configs, the only cleanup that can be done on 
the code is to remove the entries from Config.java as they are already defined 
in NetworkOrchestrator.java. This can go as a separate PR as well.


---
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: [DISCUSS] Move to Github

[chunfeng tian]

+1 to moving to github.

On Wed, Jan 6, 2016 at 6:17 PM, ilya  wrote:

> +1 to moving to github.
>
> On 1/3/16 3:25 AM, Sebastien Goasguen wrote:
> > Bringing this one discuss thread to the top of the ML to get stronger
> consensus.
> >
> > We need it if we want to request a move to GitHub.
> >
> > Note that this is not about leaving the ASF, it is about using GitHub to
> its full potential.
> >
> > The ASF board is investigating ways for a project to use Github and
> still maintain strong provenance of commits to keep the high quality and
> provenance standards of ASF code.
> >
> > If we get consensus we can request to the board to be part of the
> “trial” and move to Github.
> >
> >> On Dec 21, 2015, at 11:37 AM, Sebastien Goasguen 
> wrote:
> >>
> >>
> >>> On Dec 21, 2015, at 11:34 AM, Daan Hoogland 
> wrote:
> >>>
> >>> Sebastien, This will create a github repo under the apache organisation
> >>> right? one that we can not merge to.
> >>>
> >>
> >> Yes , that’s how I created all the docs repo and the repos for ec2stack
> and gstack.
> >>
> >>
> >>
> >>> On Mon, Dec 21, 2015 at 10:51 AM, Sebastien Goasguen  >
> >>> wrote:
> >>>
>  BTW
> 
>  Anyone can ask for a new git repo which will be mirrored on github at:
> 
>  https://issues.apache.org/jira/servicedesk/customer/portal/1/create/8
> 
>  Not sure if the link will work, but it’s available through issues.
> 
> > On Dec 19, 2015, at 7:03 PM, Sebastien Goasguen 
>  wrote:
> >
> >
> >
> >> On 19 Dec 2015, at 16:28, Rene Moser  wrote:
> >>
> >> Hi Seb
> >>
> >>> On 12/19/2015 10:12 AM, sebgoa wrote:
> >>>
> >>> Late October I started thread [1] about moving our repo to GitHub,
> I
>  would like to re-open this discussion.
> >>>
> >>> Now that we have stabilized master and release 4.6.0, 4.6.1, 4.6.2
> and
>  4.7.0 we need to think about the next steps.
> >>>
> >>> To me Git and GitHub has become an essential tool to any software
>  development, not using it to its full potential is hurting us.
> >>>
> >>> Just as an example I would like to point you to [2], this a PR I
> made
>  to Kubernetes (a container orchestrator), it literally added 14
> characters
>  in a json file.
> >>> This was really a very minor change.
> >>>
> >>> The PR automatically triggered 3 bots which created 7 labels, it
> ran
>  end to end testss, Jenkins jobs and triggered third part builds.
> >>> It was automatically merged.
> >>
> >> I am fine moving to github.
> >>
> >> But IMHO the git hosting is not the problem, the problem is how far
> do
> >> we trust the current tests and how we can them improve.
> >>
> >> Moving to github doesn't improve testing. Doing manual tests is
> okay and
> >> hard work, it does not speed up things.
> >>
> >> We need fully automated unit _and_ integration tests that we trust.
> I do
> >> not trust in mocking and simulating infrastructure.
> >>
> >> We discovered most of the major problems running cloudstack on real
> >> hardware in real world scenarios. Race conditions, unexpected VR
> >> reboots, VMs not getting IPs from DHCP, etc.
> >>
> >> Rating complexity of changes: easy_fix, minor_change, major_change
> >>
> >> Running tests according complexity:
> >>
> >> - easy_fix: just merge it.
> >> - minor_change: unit and simulator test passed
> >> - major_change: the full blown integration testing
> >>
> >> IMHO we should work on solid testing and development is fun,
> merging a
> >> click and releasing a breath.
> >>
> >> Just my 2 cents.
> >
> > Fully agree
> >
> > I do think moving to github would allow us to run tests on real
> systems
>  more easily.
> >
> >
> >>
> >> Regards
> >> René
> >>
> >>
> >>
> >>
> >>
> 
> 
> >>>
> >>>
> >>> --
> >>> Daan
> >>
> >
>



-- 
Tian ChunFeng
http://cloud.domolo.com

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

[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.766s]
[INFO] Apache CloudStack . SUCCESS [2.106s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.801s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.013s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:30.830s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.107s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [53.808s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.119s]
[INFO] Apache CloudStack API . SUCCESS [1:50.209s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [17.116s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [30.500s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.089s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [27.951s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.823s]
[INFO] Apache CloudStack Core  SUCCESS [1:20.250s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.317s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [35.811s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.011s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:06.980s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.754s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.183s]
[INFO] Apache CloudStack Server .. SUCCESS [4:13.614s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [36.949s]
[INFO] Apache CloudStack Usage Server  SUCCESS [45.059s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:22.584s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.084s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.499s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.786s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.195s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [29.707s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [25.868s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [25.789s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [21.035s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.063s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.216s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [7.944s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [1.014s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.526s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.446s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[35.789s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.325s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.244s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [15.780s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.865s]
[INFO] Apache 

[Issue] XenServer local storage

[Mike Tutkowski]

Hi,

Has anyone noticed the following issue?

I create a zone where I use local storage to house my system VMs.

After the system VMs are all started, I sometimes (but rarely) notice that
the local SR that was used to retrieve the system template remains (as
opposed to going away once the system VMs have been kicked off).

It doesn't seem to be a big deal until I happen to re-start my management
server.

At that point, CloudStack sees this local storage that should have gone
away, but didn't as new local primary storage and adds it as such.

If I go to Infrastructure and Primary Storage, I can see I now have a
second local primary storage for one of my XenServer hosts.

Has anyone seen this issue before?

What I've done at this point is simply remove the new primary storage from
the DB, but I can't (easily) seem to get rid of the extraneous SR.

Thanks!

-- 
*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: Automation for CLOUDSTACK-9217

[pavanb018]

GitHub user pavanb018 opened a pull request:

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

Automation for CLOUDSTACK-9217

This script automates the below functionality: 
CloudStack should block migration to a Storage pool which is in maintenance 
mode.


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

$ git pull https://github.com/pavanb018/cloudstack cs9217

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

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


commit 0c014cd6540bbfab3c5bba4e18fd7f3e0f655c60
Author: pavanb018 
Date:   2016-01-08T09:51:34Z

Automation for CLOUDSTACK-9217




---
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: Automation for CLOUDSTACK-9217

[pavanb018]

Github user pavanb018 commented on the pull request:

https://github.com/apache/cloudstack/pull/1322#issuecomment-169954673
  
Test Results:
== 
Trying to migrate a volume to a pool in maintenance mode should fail ... 
=== TestName: test_02_migrate_volume_to_maintenance_pool | Status : SUCCESS ===
ok

--
Ran 1 test in 173.482s

OK


---
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: Automation for CLOUDSTACK-9214 , detect w...

[shwetaag]

Github user shwetaag commented on the pull request:

https://github.com/apache/cloudstack/pull/1315#issuecomment-169947496
  
@DaanHoogland  I did the code review by code walk through and the code 
looks good to me


---
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: [4.7] account table does NOT have AUTO_INCREMENT set for id

[Remi Bergsma]

Hi Wido,

FYI: I run two 4.7 clouds and both have the AUTO_INCREMENT set properly.

Regards,
Remi




On 08/01/16 14:31, "Wido den Hollander"  wrote:

>Hi,
>
>I've been investigating a issue with a freshly installed 4.7 CloudStack
>setup and I was wondering if somebody else has seen this.
>
>The table account was looking like this:
>
>account | CREATE TABLE `account` (
>  `id` bigint(20) unsigned NOT NULL,
>  `account_name` varchar(100) DEFAULT NULL COMMENT 'an account name set
>by the creator of the account, defaults to username for single accounts',
>  `uuid` varchar(40) DEFAULT NULL,
>  `type` int(1) unsigned NOT NULL,
>  `domain_id` bigint(20) unsigned DEFAULT NULL,
>  `state` varchar(10) NOT NULL DEFAULT 'enabled',
>  `removed` datetime DEFAULT NULL COMMENT 'date removed',
>  `cleanup_needed` tinyint(1) NOT NULL DEFAULT '0',
>  `network_domain` varchar(100) DEFAULT NULL COMMENT 'Network domain
>name of the Vms of the account',
>  `default_zone_id` bigint(20) unsigned DEFAULT NULL,
>  `default` int(1) unsigned NOT NULL DEFAULT '0' COMMENT '1 if account
>is default',
>  PRIMARY KEY (`id`),
>  UNIQUE KEY `uc_account__uuid` (`uuid`),
>  KEY `i_account__removed` (`removed`)
>) ENGINE=InnoDB DEFAULT CHARSET=utf8;
>
>The most important part is that the ID is lacking the AUTO_INCREMENT
>flag which caused new account creations to fail.
>
>I've been trying to track this back to where it was modified, but so far
>I haven't been able to find this.
>
>In non of our SQL files I can actually see the account table being created.
>
>Has anybody seen this before?
>
>Wido

[GitHub] cloudstack pull request: [4.7] Critical VPCVR issues fixed: CLOUDS...

[wilderrodrigues]

Github user wilderrodrigues commented on the pull request:

https://github.com/apache/cloudstack/pull/1277#issuecomment-170017549
  
Try something, @koushik-das:

```
Do not use this code for the steps below, but Master instead.
```

1. Deploy a DC
2. Create a VPC + Tier + VM
3. Change the GC settings for 10 seconds, for example
4. Restart the Management Server
5. Remove the VM from the tier
6. Observe if the Network GC is actually running every 10 seconds - as now 
defined in the DB - or if it is still using the 600 seconds hardcoded in the 
nested Enum.

That's why a changed it. I needed to make sure that the changes applied in 
the global settings would be retrieved from the Database. But don't bother, 
it's already deployed in our production here and working really nice.

Concerning gradually refactoring code, I agree with that - I'm not an 
idiot. Actually, I have done a lot of refactoring on ACS since I started. I 
haven't been adding glue to things or not writing tests. But in that case, the 
whole configuration is messed and I don't agree with someone adding separate 
things to classes and letting them be for years.

If for some reason I did not get the way it should work, you can do one of 
two things:

1. Mark the PR with a -1; or
2. Checkout the code; fix the way you want; make sure the tests passes; and 
push a PR on top of this one.

Have a happy coding.

Cheers,
Wilder


---
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: gitlab.apache.org

[Wido den Hollander]

On 08-01-16 09:25, Daan Hoogland wrote:
> We, cloudstack-dev-list-users have been talking about moving more
> functionality to github. This is being rejected by the foundation so far
> for (in my view obvious) reasons of governance. The functionality is
> however missed dearly so speaking with an ex-member he suggested we install
> a machine with gitlab under the apache domain and let it administer our git
> repos to gain similar functionality. Is this being discussed already and
> should we do so?
> 

Well, it could be an idea to do I think. However, I think most people
prefer using Github since they use it daily.

My problem with Gitlab is maintenance. Are we going to maintain it or
the Infra team?

Wido

[GitHub] cloudstack pull request: [CLOUDSTACK-9215]Test to verify vm deploy...

[DaanHoogland]

Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/1316#issuecomment-170016433
  
test succeeds as is : 
```
[root@daans-dev-machinina ~]# ssh cs1 nosetests --with-marvin 
--marvin-config=/data/shared/marvin/mct-zone1-kvm1-kvm2.cfg  -s -a 
tags=advanced,required_hardware=true 
/data/git/cs1/cloudstack/test/integration/component/maint/test_vpc.py
root@cs1's password:

 Marvin Init Started 

=== Marvin Parse Config Successful ===

=== Marvin Setting TestData Successful===

 Log Folder Path: /tmp//MarvinLogs//Jan_08_2016_14_17_12_EBMCRT. All 
logs will be available here 

=== Marvin Init Logging Successful===

 Marvin Init Successful 
===final results are now copied to: /tmp//MarvinLogs/test_vpc_1F4ULR===
```

LGTM but seems less useful due to my remark on line 354


---
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-9203 Implement security group ...

[DaanHoogland]

Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/1297#issuecomment-170016899
  
@borisroman @wido @resmo @llambiel @pyr @bhaisaab @wilderrodrigues I can 
run the tests again but I am the contributor. Can someone else, please?


---
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: [4.7] Critical VPCVR issues fixed: CLOUDS...

[koushik-das]

Github user koushik-das commented on the pull request:

https://github.com/apache/cloudstack/pull/1277#issuecomment-169979032
  
As a general cleanup, all configs defined in Config.java should be 
gradually moved to the appropriate java classes from where they are used. We 
should do away with the old way of managing configs and switch to the new 
mechanism.



---
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-9104: VM naming convention in ...

[rafaelweingartner]

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

https://github.com/apache/cloudstack/pull/1302#discussion_r49183061
  
--- Diff: 
plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/resource/VmwareResource.java
 ---
@@ -2032,11 +2032,20 @@ int getReservedCpuMHZ(VirtualMachineTO vmSpec) {
 
 // Pair
 private Pair composeVmNames(VirtualMachineTO vmSpec) {
-String vmInternalCSName = vmSpec.getName();
-String vmNameOnVcenter = vmSpec.getName();
-if (_instanceNameFlag && vmSpec.getHostName() != null) {
-vmNameOnVcenter = vmSpec.getHostName();
+
+String vmInternalCSName = null;
+String vmNameOnVcenter  = null;
+if(vmSpec != null)
--- End diff --

If today there is no way a null value is received in that method, I see no 
reason to have that check in 2038. 


---
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: [4.7] Critical VPCVR issues fixed: CLOUDS...

[wilderrodrigues]

Github user wilderrodrigues commented on the pull request:

https://github.com/apache/cloudstack/pull/1277#issuecomment-169996476
  
Do you agree that it is a completely different issue you are trying to 
address?

ACS needs refactor in each corner of its code, but we cannot work on a 
issue and do a massive refactor in the whole configuration model.

There should be a group of people defining the new design for the 
configuration and work on it, not scattered people around the world doing 
things at their will.

Cheers,
Wilder


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

[4.7] account table does NOT have AUTO_INCREMENT set for id

[Wido den Hollander]

Hi,

I've been investigating a issue with a freshly installed 4.7 CloudStack
setup and I was wondering if somebody else has seen this.

The table account was looking like this:

account | CREATE TABLE `account` (
  `id` bigint(20) unsigned NOT NULL,
  `account_name` varchar(100) DEFAULT NULL COMMENT 'an account name set
by the creator of the account, defaults to username for single accounts',
  `uuid` varchar(40) DEFAULT NULL,
  `type` int(1) unsigned NOT NULL,
  `domain_id` bigint(20) unsigned DEFAULT NULL,
  `state` varchar(10) NOT NULL DEFAULT 'enabled',
  `removed` datetime DEFAULT NULL COMMENT 'date removed',
  `cleanup_needed` tinyint(1) NOT NULL DEFAULT '0',
  `network_domain` varchar(100) DEFAULT NULL COMMENT 'Network domain
name of the Vms of the account',
  `default_zone_id` bigint(20) unsigned DEFAULT NULL,
  `default` int(1) unsigned NOT NULL DEFAULT '0' COMMENT '1 if account
is default',
  PRIMARY KEY (`id`),
  UNIQUE KEY `uc_account__uuid` (`uuid`),
  KEY `i_account__removed` (`removed`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

The most important part is that the ID is lacking the AUTO_INCREMENT
flag which caused new account creations to fail.

I've been trying to track this back to where it was modified, but so far
I haven't been able to find this.

In non of our SQL files I can actually see the account table being created.

Has anybody seen this before?

Wido

Re: gitlab.apache.org

[Erik Weber]

This has been discussed rather intensively on the infra ML previously.

Here's an answer from David: http://markmail.org/message/msxi7bhkfijydckq

It's about half years old, so "short term" might have changed.

-- 
Erik

On Fri, Jan 8, 2016 at 2:36 PM, Daan Hoogland 
wrote:

> Wido, you are touching on the point of governance there. The maintenance is
> the price for keeping the goods under your control. Apache wants to make
> sure force pushes are not garbage collected but tagged for audit purposes,
> I understand. Btw, let's include infra in the discussion.
>
> On Fri, Jan 8, 2016 at 2:32 PM, Wido den Hollander  wrote:
>
> >
> >
> > On 08-01-16 09:25, Daan Hoogland wrote:
> > > We, cloudstack-dev-list-users have been talking about moving more
> > > functionality to github. This is being rejected by the foundation so
> far
> > > for (in my view obvious) reasons of governance. The functionality is
> > > however missed dearly so speaking with an ex-member he suggested we
> > install
> > > a machine with gitlab under the apache domain and let it administer our
> > git
> > > repos to gain similar functionality. Is this being discussed already
> and
> > > should we do so?
> > >
> >
> > Well, it could be an idea to do I think. However, I think most people
> > prefer using Github since they use it daily.
> >
> > My problem with Gitlab is maintenance. Are we going to maintain it or
> > the Infra team?
> >
> > Wido
> >
>
>
>
> --
> Daan
>

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

[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.812s]
[INFO] Apache CloudStack . SUCCESS [2.261s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.821s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.377s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:31.815s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.119s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [53.785s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.511s]
[INFO] Apache CloudStack API . SUCCESS [1:54.868s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.558s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [29.414s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.096s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.192s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [25.407s]
[INFO] Apache CloudStack Core  SUCCESS [1:21.641s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.815s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.223s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.170s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:07.142s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.897s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.473s]
[INFO] Apache CloudStack Server .. SUCCESS [4:14.509s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.083s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.249s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:21.386s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.084s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.511s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.140s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [49.991s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [29.836s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.469s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [22.305s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [21.019s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.143s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.441s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [8.574s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.973s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.376s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.687s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[35.979s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.320s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.357s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [15.885s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[17.340s]
[INFO] Apache 

Re: gitlab.apache.org

[Daan Hoogland]

Wido, you are touching on the point of governance there. The maintenance is
the price for keeping the goods under your control. Apache wants to make
sure force pushes are not garbage collected but tagged for audit purposes,
I understand. Btw, let's include infra in the discussion.

On Fri, Jan 8, 2016 at 2:32 PM, Wido den Hollander  wrote:

>
>
> On 08-01-16 09:25, Daan Hoogland wrote:
> > We, cloudstack-dev-list-users have been talking about moving more
> > functionality to github. This is being rejected by the foundation so far
> > for (in my view obvious) reasons of governance. The functionality is
> > however missed dearly so speaking with an ex-member he suggested we
> install
> > a machine with gitlab under the apache domain and let it administer our
> git
> > repos to gain similar functionality. Is this being discussed already and
> > should we do so?
> >
>
> Well, it could be an idea to do I think. However, I think most people
> prefer using Github since they use it daily.
>
> My problem with Gitlab is maintenance. Are we going to maintain it or
> the Infra team?
>
> Wido
>



-- 
Daan

[GitHub] cloudstack pull request: [4.7] Critical VPCVR issues fixed: CLOUDS...

[koushik-das]

Github user koushik-das commented on the pull request:

https://github.com/apache/cloudstack/pull/1277#issuecomment-170011469
  
I have clearly mentioned that the refactoring needs to be done gradually. 
But in the changes you have reverted to using the config defined in Config.java 
when existing code is already using the config defined in 
NetworkOrchestrator.java. Why are you changing back to the old config mechanism 
when the configs are already defined in NetworkOrchestrator?


---
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-9215]Test to verify vm deploy...

[DaanHoogland]

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

https://github.com/apache/cloudstack/pull/1316#discussion_r49191905
  
--- Diff: test/integration/component/maint/test_vpc.py ---
@@ -0,0 +1,360 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+#
+#   http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+
+""" Component tests for VPC functionality
+"""
+# Import Local Modules
+from nose.plugins.attrib import attr
+from marvin.cloudstackTestCase import cloudstackTestCase
+from marvin.lib.utils import cleanup_resources, validateList
+from marvin.lib.base import (Account,
+ VPC,
+ VpcOffering,
+ VirtualMachine,
+ ServiceOffering,
+ Network,
+ NetworkOffering,
+ Configurations)
+from marvin.lib.common import (get_domain,
+   get_zone,
+   get_template)
+from marvin.sshClient import SshClient
+from marvin.codes import PASS
+import time
+
+class Services:
+
+"""Test VPC services
+"""
+
+def __init__(self):
+self.services = {
+"account": {
+"email": "t...@test.com",
+"firstname": "Test",
+"lastname": "User",
+"username": "test",
+# Random characters are appended for unique
+# username
+"password": "password",
+},
+"domain_admin": {
+"email": "dom...@admin.com",
+"firstname": "Domain",
+"lastname": "Admin",
+"username": "DoA",
+# Random characters are appended for unique
+# username
+"password": "password",
+},
+"service_offering": {
+"name": "Tiny Instance",
+"displaytext": "Tiny Instance",
+"cpunumber": 1,
+"cpuspeed": 100,
+"memory": 128,
+},
+"network_offering": {
+"name": 'VPC Network offering',
+"displaytext": 'VPC Network off',
+"guestiptype": 'Isolated',
+"supportedservices": 
'Vpn,Dhcp,Dns,SourceNat,PortForwarding,Lb,UserData,StaticNat,NetworkACL',
+"traffictype": 'GUEST',
+"availability": 'Optional',
+"useVpc": 'on',
+"serviceProviderList": {
+"Vpn": 'VpcVirtualRouter',
+"Dhcp": 'VpcVirtualRouter',
+"Dns": 'VpcVirtualRouter',
+"SourceNat": 'VpcVirtualRouter',
+"PortForwarding": 'VpcVirtualRouter',
+"Lb": 'VpcVirtualRouter',
+"UserData": 'VpcVirtualRouter',
+"StaticNat": 'VpcVirtualRouter',
+"NetworkACL": 'VpcVirtualRouter'
+},
+},
+"network_offering_no_lb": {
+"name": 'VPC Network offering',
+"displaytext": 'VPC Network off',
+"guestiptype": 'Isolated',
+"supportedservices": 
'Vpn,Dhcp,Dns,SourceNat,PortForwarding,UserData,StaticNat,NetworkACL',
+"traffictype": 'GUEST',
+"availability": 'Optional',
+"useVpc": 'on',
+"serviceProviderList": {
+"Vpn": 'VpcVirtualRouter',
+"Dhcp": 'VpcVirtualRouter',
+"Dns": 'VpcVirtualRouter',
+"SourceNat": 'VpcVirtualRouter',
+"PortForwarding": 'VpcVirtualRouter',
+"UserData": 'VpcVirtualRouter',
+   

[GitHub] cloudstack pull request: Factor in inaccurancy of System.nanoTime ...

[bheuvel]

GitHub user bheuvel opened a pull request:

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

Factor in inaccurancy of System.nanoTime in class Profiler

The time diff measurement by the class Profiler, is done by 
System.nanoTime().
System.nanoTime() is not 100% accurate (lots of info on this on the web). 
The inaccurance seems to vary/depend with different dependencies 
(multi-core/OS/kernels).

Problem:
In my case the code which measures `Thread.sleep(ONE_SECOND);` ~~takes~~ 
measures 999 milliseconds, which breaks the test expecting the sleep of 1000 
milliseconds to ~~take~~ measure at least 1000 milliseconds.

Solution:
A `MARGIN` (of 100 milliseconds) is already present to factor in some time 
for overhead/surrounding code which adds time. Another margin could be added to 
factor in the possible time measurement error.
To limit additional lines of code, the constant `ONE_SECOND`, which is used 
by the testcase (sleep), is increased from 1000 milliseconds to `1000l + 
(MARGIN / 10)` (effectively 1010 milliseconds).

Thereby the inaccurancy on my system of ~1% ("faster") is caught as the 
`sleep(1010)` is measured as '1009' milliseconds.






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

$ git pull https://github.com/bheuvel/cloudstack testprofiler-second

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

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


commit dbb10a4ed5dc763b4c603e5cc3f2b70a202c0a2b
Author: Bob 
Date:   2016-01-08T12:31:27Z

Factor in inaccurancy of System.nanoTime




---
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: [4.7] account table does NOT have AUTO_INCREMENT set for id

[Erik Weber]

On Fri, Jan 8, 2016 at 2:31 PM, Wido den Hollander  wrote:

> Hi,
>
> I've been investigating a issue with a freshly installed 4.7 CloudStack
> setup and I was wondering if somebody else has seen this.
>
> The table account was looking like this:
>
> account | CREATE TABLE `account` (
>   `id` bigint(20) unsigned NOT NULL,
>   `account_name` varchar(100) DEFAULT NULL COMMENT 'an account name set
> by the creator of the account, defaults to username for single accounts',
>   `uuid` varchar(40) DEFAULT NULL,
>   `type` int(1) unsigned NOT NULL,
>   `domain_id` bigint(20) unsigned DEFAULT NULL,
>   `state` varchar(10) NOT NULL DEFAULT 'enabled',
>   `removed` datetime DEFAULT NULL COMMENT 'date removed',
>   `cleanup_needed` tinyint(1) NOT NULL DEFAULT '0',
>   `network_domain` varchar(100) DEFAULT NULL COMMENT 'Network domain
> name of the Vms of the account',
>   `default_zone_id` bigint(20) unsigned DEFAULT NULL,
>   `default` int(1) unsigned NOT NULL DEFAULT '0' COMMENT '1 if account
> is default',
>   PRIMARY KEY (`id`),
>   UNIQUE KEY `uc_account__uuid` (`uuid`),
>   KEY `i_account__removed` (`removed`)
> ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
>
> The most important part is that the ID is lacking the AUTO_INCREMENT
> flag which caused new account creations to fail.
>
> I've been trying to track this back to where it was modified, but so far
> I haven't been able to find this.
>
> In non of our SQL files I can actually see the account table being created.
>

Definition seems to be in setup/db/create-schema.sql (approx line 1319 in
master).


>
> Has anybody seen this before?
>
> Wido
>


-- 
Erik

[GitHub] cloudstack pull request: Fix mariadb related listCapacity bug (CLO...

[borisroman]

Github user borisroman commented on the pull request:

https://github.com/apache/cloudstack/pull/1314#issuecomment-170050753
  
All integration tests look fine!

```
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
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 Remote Access VPN in VPC ... === TestName: test_vpc_remote_access_vpn 
| Status : SUCCESS ===
ok
Test VPN in VPC ... === TestName: test_vpc_site2site_vpn | Status : SUCCESS 
===
ok
test_01_vpc_privategw_acl 
(integration.smoke.test_privategw_acl.TestPrivateGwACL) ... === TestName: 
test_01_vpc_privategw_acl | Status : SUCCESS ===
ok
test_02_vpc_privategw_static_routes 
(integration.smoke.test_privategw_acl.TestPrivateGwACL) ... === TestName: 
test_02_vpc_privategw_static_routes | Status : SUCCESS ===
ok
test_03_rvpc_privategw_static_routes 
(integration.smoke.test_privategw_acl.TestPrivateGwACL) ... === TestName: 
test_03_rvpc_privategw_static_routes | Status : SUCCESS ===
ok
Test for port forwarding on source NAT ... === 

Re: [4.7] account table does NOT have AUTO_INCREMENT set for id

[Wido den Hollander]

On 08-01-16 15:53, Remi Bergsma wrote:
> Hi Wido,
> 
> FYI: I run two 4.7 clouds and both have the AUTO_INCREMENT set properly.
> 

Hmm, weird. Were they fresh 4.7 installs? I manually fixed it here and
looking at the SQL files I don't understand how this might have gone wrong.

Wido

> Regards,
> Remi
> 
> 
> 
> 
> On 08/01/16 14:31, "Wido den Hollander"  wrote:
> 
>> Hi,
>>
>> I've been investigating a issue with a freshly installed 4.7 CloudStack
>> setup and I was wondering if somebody else has seen this.
>>
>> The table account was looking like this:
>>
>> account | CREATE TABLE `account` (
>>  `id` bigint(20) unsigned NOT NULL,
>>  `account_name` varchar(100) DEFAULT NULL COMMENT 'an account name set
>> by the creator of the account, defaults to username for single accounts',
>>  `uuid` varchar(40) DEFAULT NULL,
>>  `type` int(1) unsigned NOT NULL,
>>  `domain_id` bigint(20) unsigned DEFAULT NULL,
>>  `state` varchar(10) NOT NULL DEFAULT 'enabled',
>>  `removed` datetime DEFAULT NULL COMMENT 'date removed',
>>  `cleanup_needed` tinyint(1) NOT NULL DEFAULT '0',
>>  `network_domain` varchar(100) DEFAULT NULL COMMENT 'Network domain
>> name of the Vms of the account',
>>  `default_zone_id` bigint(20) unsigned DEFAULT NULL,
>>  `default` int(1) unsigned NOT NULL DEFAULT '0' COMMENT '1 if account
>> is default',
>>  PRIMARY KEY (`id`),
>>  UNIQUE KEY `uc_account__uuid` (`uuid`),
>>  KEY `i_account__removed` (`removed`)
>> ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
>>
>> The most important part is that the ID is lacking the AUTO_INCREMENT
>> flag which caused new account creations to fail.
>>
>> I've been trying to track this back to where it was modified, but so far
>> I haven't been able to find this.
>>
>> In non of our SQL files I can actually see the account table being created.
>>
>> Has anybody seen this before?
>>
>> Wido

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

[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.743s]
[INFO] Apache CloudStack . SUCCESS [2.150s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [1.000s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.141s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:29.203s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.111s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [54.228s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.242s]
[INFO] Apache CloudStack API . SUCCESS [1:49.730s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.635s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [30.301s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.089s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.339s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.492s]
[INFO] Apache CloudStack Core  SUCCESS [1:21.390s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.459s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.227s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.350s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:09.505s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [41.132s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.643s]
[INFO] Apache CloudStack Server .. SUCCESS [4:10.404s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.898s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.162s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:20.677s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.074s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.460s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.918s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.312s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [29.418s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.726s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [30.713s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [21.037s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.173s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.517s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [8.201s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [1.052s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.609s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.100s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[35.674s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.713s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.640s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [15.181s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.834s]
[INFO] Apache 

[GitHub] cloudstack-cloudmonkey pull request: Update requester.py

[bhaisaab]

Github user bhaisaab commented on the pull request:


https://github.com/apache/cloudstack-cloudmonkey/pull/11#issuecomment-170056433
  
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-cloudmonkey pull request: Update requester.py

[bhaisaab]

Github user bhaisaab commented on the pull request:


https://github.com/apache/cloudstack-cloudmonkey/pull/11#issuecomment-170059404
  
@phillipkent can you share examples of API/cloudmonkey commands where we 
would like to use * in the args?


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