Re: [DISCUSS] Stop using Review Board

[David Nalley]

On Fri, Apr 3, 2015 at 9:53 AM, Sateesh Chodapuneedi
 wrote:
>> -Original Message-
>> From: Sebastien Goasguen [mailto:run...@gmail.com]
>> Sent: Friday, April 3, 2015 1:57 PM
>> To: dev@cloudstack.apache.org
>> Subject: Re: [DISCUSS] Stop using Review Board
>>
>> Seems with have lazy consensus.
>>
>> Will Stevens contributed CONTRIBUTING instructions at:
>> https://github.com/apache/cloudstack/blob/master/CONTRIBUTING.md
>>
>> I am pushing that to 4.5,4.4 and 4.3 and I will update our website 
>> contribution
>> page, removing reference to RB.
>> I will then put a message in the RB current reviews.
>>
>> I propose to leave it a week with the message, this will give time to folks 
>> to
>> move their review to GH.
>>
>> After that, I will ask ASF infra to “hide” RB. They cannot make it readonly, 
>> we
>> can only hide the view.
>
> If RB is hidden, does that block us from seeing reviews of old patches on it?
> Some of the commits doesn't have much meat in commit message, and in such 
> cases used to go back to RB where we could get some information seeing review 
> history/comments.
>

All comments were copied to the mailing list.

--David

[GitHub] cloudstack pull request: write logfile just before rebooting the h...

[remibergsma]

GitHub user remibergsma opened a pull request:

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

write logfile just before rebooting the host

As discussed with @wido @pyr and @nuxro added an extra log line.

Tested it and it logs fine (tested to local disk) when syncing first:
Apr  3 15:31:23 mcctest2 heartbeat: kvmheartbeat.sh system because it was 
unable to write the heartbeat to the storage

By the way, it did also log to the agent.log but this extra log has the 
benefit of ending up in the system log so you'll probably find it easier there. 
Existing logs:
2015-04-03 15:27:23,943 WARN  [kvm.resource.KVMHAMonitor] (Thread-24:null) 
write heartbeat failed: timeout, retry: 0
2015-04-03 15:28:23,944 WARN  [kvm.resource.KVMHAMonitor] (Thread-24:null) 
write heartbeat failed: timeout, retry: 1
2015-04-03 15:29:23,946 WARN  [kvm.resource.KVMHAMonitor] (Thread-24:null) 
write heartbeat failed: timeout, retry: 2
2015-04-03 15:30:23,948 WARN  [kvm.resource.KVMHAMonitor] (Thread-24:null) 
write heartbeat failed: timeout, retry: 3
2015-04-03 15:31:23,950 WARN  [kvm.resource.KVMHAMonitor] (Thread-24:null) 
write heartbeat failed: timeout, retry: 4
2015-04-03 15:31:23,950 WARN  [kvm.resource.KVMHAMonitor] (Thread-24:null) 
write heartbeat failed: timeout; reboot the host

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

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

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

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


commit 3671b66892e4219dfc66cd1185acefd9662f5a89
Author: Remi Bergsma 
Date:   2015-04-03T19:46:02Z

write logfile just before rebooting the host

As discussed with @wido @pyr and @nuxro added an extra log line.

Tested it and it logs fine (tested to local disk) when syncing first:
Apr  3 15:31:23 mcctest2 heartbeat: kvmheartbeat.sh system because it was 
unable to write the heartbeat to the storage

By the way, it did also log to the agent.log but this extra log has the 
benefit of ending up in the system log so you'll probably find it easier there. 
Existing logs:
2015-04-03 15:27:23,943 WARN  [kvm.resource.KVMHAMonitor] (Thread-24:null) 
write heartbeat failed: timeout, retry: 0
2015-04-03 15:28:23,944 WARN  [kvm.resource.KVMHAMonitor] (Thread-24:null) 
write heartbeat failed: timeout, retry: 1
2015-04-03 15:29:23,946 WARN  [kvm.resource.KVMHAMonitor] (Thread-24:null) 
write heartbeat failed: timeout, retry: 2
2015-04-03 15:30:23,948 WARN  [kvm.resource.KVMHAMonitor] (Thread-24:null) 
write heartbeat failed: timeout, retry: 3
2015-04-03 15:31:23,950 WARN  [kvm.resource.KVMHAMonitor] (Thread-24:null) 
write heartbeat failed: timeout, retry: 4
2015-04-03 15:31:23,950 WARN  [kvm.resource.KVMHAMonitor] (Thread-24:null) 
write heartbeat failed: timeout; reboot the host




---
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] How to fix failing VR-mgmt server links

[Suresh Sadhu]

That’s true Somesh ,the recent VR aggregation functionality  yielding  better 
VR performance  in the customer location. i.e. VR upgrade time reduces from 
hours to minute and it's there in ACS as 
well(https://issues.apache.org/jira/browse/CLOUDSTACK-5779).  Earlier without 
this feature, MS is to ssh  to router to execute each and every commands  but 
now MS will  ssh to  router only once and runs all the commands at once.

Rohit : Agent on VR is  good idea but   I believe agent implementation   is 
heavy for router . we need to dig more.


Regards
Sadhu

-Original Message-
From: Somesh Naidu [mailto:somesh.na...@citrix.com] 
Sent: 03 April 2015 20:23
To: dev@cloudstack.apache.org
Subject: RE: [DISCUSS] How to fix failing VR-mgmt server links

It is true and I like the idea. I would just want to make sure the agent 
footprint isn't too high. As opposed to CP/SS VM, we expect to be a lot more 
VRs running in an environment.

Also, the recent VR aggregation, I believe ACS 4.5 has it, did reduce a lot of 
that barbaric stuff so we are still better than where we were earlier.

Somesh
CloudPlatform Escalations
Citrix Systems, Inc.


-Original Message-
From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com] 
Sent: Friday, April 03, 2015 5:53 AM
To: dev
Subject: [DISCUSS] How to fix failing VR-mgmt server links

Hi,

In large environments, one of the issues of a VM deployment or a network rule 
failing that I find commonly is that the mgmt server is unable to reach to the 
VR via the host because of network lag or issues between the host and the mgmt 
server. The sending operation on the link is tried about 5 times (hardcoded) 
before it gives up and we see something like this in the logs: "Unable to reach 
the peer that the agent is connected”.

Should we add a global setting to allow sysadmins to configure the agent 
link/socket (in various AgentAttaches in 
engine/orchestration/src/com/cloud/agent/manager ?) timeout or please share if 
something like this already exists or any other solution to this problem?

The other issue I see is that since VRs don’t have an agent running in it, to 
execute an operation mgmt server SSH-es into it to run scripts, for a high load 
the number of open FDs (so also TCP ports) on a VR/systemvm are limited which 
again can cause connections to fail/timeout due to high number of requests VR 
is processing. A long term solution could be to implement an agent (like 
ssvm/cpvm) that runs inside of the VR and talks to mgmt server over multiplexed 
connection so we limit the number of connections from one mgmt server and we 
can get rid of the SSH code and execution of barbaric scripts. Comments, 
suggestions, flames?

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

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

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

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

Re: [DISCUSS] How to fix failing VR-mgmt server links

[Wido den Hollander]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



On 04/03/2015 04:52 PM, Somesh Naidu wrote:
> It is true and I like the idea. I would just want to make sure the
> agent footprint isn't too high. As opposed to CP/SS VM, we expect
> to be a lot more VRs running in an environment.
> 

I agree. Wouldn't a (simple) daemon in Python using something like
Flask be enough?

> Also, the recent VR aggregation, I believe ACS 4.5 has it, did
> reduce a lot of that barbaric stuff so we are still better than
> where we were earlier.
> 
> Somesh CloudPlatform Escalations Citrix Systems, Inc.
> 
> 
> -Original Message- From: Rohit Yadav
> [mailto:rohit.ya...@shapeblue.com] Sent: Friday, April 03, 2015
> 5:53 AM To: dev Subject: [DISCUSS] How to fix failing VR-mgmt
> server links
> 
> Hi,
> 
> In large environments, one of the issues of a VM deployment or a
> network rule failing that I find commonly is that the mgmt server
> is unable to reach to the VR via the host because of network lag or
> issues between the host and the mgmt server. The sending operation
> on the link is tried about 5 times (hardcoded) before it gives up
> and we see something like this in the logs: "Unable to reach the
> peer that the agent is connected”.
> 
> Should we add a global setting to allow sysadmins to configure the
> agent link/socket (in various AgentAttaches in
> engine/orchestration/src/com/cloud/agent/manager ?) timeout or
> please share if something like this already exists or any other
> solution to this problem?
> 
> The other issue I see is that since VRs don’t have an agent running
> in it, to execute an operation mgmt server SSH-es into it to run
> scripts, for a high load the number of open FDs (so also TCP ports)
> on a VR/systemvm are limited which again can cause connections to
> fail/timeout due to high number of requests VR is processing. A
> long term solution could be to implement an agent (like ssvm/cpvm)
> that runs inside of the VR and talks to mgmt server over
> multiplexed connection so we limit the number of connections from
> one mgmt server and we can get rid of the SSH code and execution of
> barbaric scripts. Comments, suggestions, flames?
> 
> Regards, Rohit Yadav Software Architect, ShapeBlue M. +91 88 262
> 30892 | rohit.ya...@shapeblue.com Blog: bhaisaab.org | Twitter:
> @_bhaisaab
> 
> Find out more about ShapeBlue and our range of CloudStack related
> services
> 
> IaaS Cloud Design &
> Build CSForge –
> rapid IaaS deployment framework 
> CloudStack
> Consulting CloudStack
> Software
> Engineering 
> CloudStack Infrastructure
> Support 
> CloudStack Bootcamp Training
> Courses
> 
> This email and any attachments to it may be confidential and are
> intended solely for the use of the individual to whom it is
> addressed. Any views or opinions expressed are solely those of the
> author and do not necessarily represent those of Shape Blue Ltd or
> related companies. If you are not the intended recipient of this
> email, you must neither take any action based upon its contents,
> nor copy or show it to anyone. Please contact the sender if you
> believe you have received this email in error. Shape Blue Ltd is a
> company incorporated in England & Wales. ShapeBlue Services India
> LLP is a company incorporated in India and is operated under
> license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is
> a company incorporated in Brasil and is operated under license from
> Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The
> Republic of South Africa and is traded under license from Shape
> Blue Ltd. ShapeBlue is a registered trademark.
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJVHqwQAAoJEAGbWC3bPspC/r4QAJKR3LaZkHBIzKeyBnVWId/k
ojCkdXGAjT5m2DXHLiRCnCPwVyp6cG22Ao+/pdRKynonlz0xvZVNY+hrHqTRurwy
GyHVyswRIDSF6aqkTC2HM540MF+OBq40EfeLAO0Ewczag3RjGyN8x1LPVh3Pjixi
Xxi25FMBXsgTZtz6HjykCbFlHHun791H5StkBXiF2YSjgo4nOSvRzCTtIraUP8Al
eLzNTWJRTORc/BKTxbYCi0agDn3BsaqOJkhIvBCXqT8LZI91vRtpfKdnSoUtnHlm
jc7ljarPfcvSlqdgmw6mrBd4bnpcT3AS8Il4wKCznxAs2fVBk3B8uEinmk8yQHz1
iWyEHdf8WGFtNlPdH01Erz83mSfnv9lSYO5DwFh9dxCsE82fXl79ru+k07FjsSve
IwAq7LPdnXzSABzw1+CwerCkTyJmx/MsAHaidATlzTwvA8AUT083Tm+qqjO5aLHK
9bfvziNtV3O3sdiZvYCTk/poxVcNrlJWLzkyyQmNCDHb5J9TNjqOIDOMUGEM4kgI
Cx7/LEYUvp+lNg8E4j7FjSiIEn9TNGx8tmW0AwjaeazPkTnoYoJcp7lhDvst7G/H
a4AhV0BwUqOyLqw+ilI54oKZbWVRJVdc2nRflKOtclxhK9S1KN98TGEbrIM5z5dB
GOqlkH8PiYdQIq4Oygdt
=udB0
-END PGP SIGNATURE-

RE: [DISCUSS] How to fix failing VR-mgmt server links

[Somesh Naidu]

It is true and I like the idea. I would just want to make sure the agent 
footprint isn't too high. As opposed to CP/SS VM, we expect to be a lot more 
VRs running in an environment.

Also, the recent VR aggregation, I believe ACS 4.5 has it, did reduce a lot of 
that barbaric stuff so we are still better than where we were earlier.

Somesh
CloudPlatform Escalations
Citrix Systems, Inc.


-Original Message-
From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com] 
Sent: Friday, April 03, 2015 5:53 AM
To: dev
Subject: [DISCUSS] How to fix failing VR-mgmt server links

Hi,

In large environments, one of the issues of a VM deployment or a network rule 
failing that I find commonly is that the mgmt server is unable to reach to the 
VR via the host because of network lag or issues between the host and the mgmt 
server. The sending operation on the link is tried about 5 times (hardcoded) 
before it gives up and we see something like this in the logs: "Unable to reach 
the peer that the agent is connected”.

Should we add a global setting to allow sysadmins to configure the agent 
link/socket (in various AgentAttaches in 
engine/orchestration/src/com/cloud/agent/manager ?) timeout or please share if 
something like this already exists or any other solution to this problem?

The other issue I see is that since VRs don’t have an agent running in it, to 
execute an operation mgmt server SSH-es into it to run scripts, for a high load 
the number of open FDs (so also TCP ports) on a VR/systemvm are limited which 
again can cause connections to fail/timeout due to high number of requests VR 
is processing. A long term solution could be to implement an agent (like 
ssvm/cpvm) that runs inside of the VR and talks to mgmt server over multiplexed 
connection so we limit the number of connections from one mgmt server and we 
can get rid of the SSH code and execution of barbaric scripts. Comments, 
suggestions, flames?

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

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

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

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

Jenkins build issue: build-master-slowbuild

[Pierre-Luc Dion]

For about 2 weeks we are having this build that is broken. does anyone
could have a look at it? is this cause by a recent commit ?

I'm not sure what this is and how to mitigate this...


Thanks

RE: [DISCUSS] Stop using Review Board

[Sateesh Chodapuneedi]

> -Original Message-
> From: Sebastien Goasguen [mailto:run...@gmail.com]
> Sent: Friday, April 3, 2015 1:57 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] Stop using Review Board
> 
> Seems with have lazy consensus.
> 
> Will Stevens contributed CONTRIBUTING instructions at:
> https://github.com/apache/cloudstack/blob/master/CONTRIBUTING.md
> 
> I am pushing that to 4.5,4.4 and 4.3 and I will update our website 
> contribution
> page, removing reference to RB.
> I will then put a message in the RB current reviews.
> 
> I propose to leave it a week with the message, this will give time to folks to
> move their review to GH.
> 
> After that, I will ask ASF infra to “hide” RB. They cannot make it readonly, 
> we
> can only hide the view.

If RB is hidden, does that block us from seeing reviews of old patches on it?
Some of the commits doesn't have much meat in commit message, and in such cases 
used to go back to RB where we could get some information seeing review 
history/comments.

Regards,
Sateesh
> 
> yell if you don’t like it :)
> 
> -sebastien
> 
> 
> > On Mar 31, 2015, at 5:17 AM, Rohit Yadav 
> wrote:
> >
> > +1
> >
> > Can we somehow disable RB for CloudStack project? We can run through
> pending RB patches and close them or move them to GH.
> >
> >> On 27-Mar-2015, at 8:50 pm, David Nalley  wrote:
> >>
> >> +1 for GH
> >>
> >>
> >> On Fri, Mar 27, 2015 at 4:52 AM, Sebastien Goasguen 
> wrote:
> >>> Hi everyone,
> >>>
> >>> Since GitHub pull requests have been enabled for cloudstack, we have
> closed 127 commits.
> >>>
> >>> I believe this is a nicer interface, one that folks are used to when
> contributing to other open source projects.
> >>>
> >>> In the meantime, we still have 73 open reviews on Review Board
> >>>
> >>> https://reviews.apache.org/
> >>>
> >>> * I propose that we stop using RB all together, and remove any links to it
> from our website and README.
> >>>
> >>> A few of us have tried to close some of the reviews by pinging the authors
> already.
> >>>
> >>> * My second proposition is that we write a comment in all reviews:
> >>>
> >>> “Thanks for the patch, the cloudstack community has decided to stop using
> Review Board in favor of github pull request.
> >>> You can see  to learn how to submit a pull request to cloudstack.
> Could you move your patch to a PR ?
> >>> Without response from you we will close this review within 7 days.
> >>> "
> >>>
> >>> There is good contribution guidelines in our docs README:
> >>> https://github.com/apache/cloudstack-docs
> >>>
> >>> -Sebastien
> >
> > Regards,
> > Rohit Yadav
> > Software Architect, ShapeBlue
> > M. +91 88 262 30892 | rohit.ya...@shapeblue.com
> > Blog: bhaisaab.org | Twitter: @_bhaisaab
> >
> >
> >
> > Find out more about ShapeBlue and our range of CloudStack related services
> >
> > IaaS Cloud Design & Build build//>
> > CSForge – rapid IaaS deployment framework
> > CloudStack Consulting
> > CloudStack Software Engineering engineering/>
> > CloudStack Infrastructure Support infrastructure-support/>
> > CloudStack Bootcamp Training Courses training/>
> >
> > This email and any attachments to it may be confidential and are intended
> solely for the use of the individual to whom it is addressed. Any views or
> opinions expressed are solely those of the author and do not necessarily
> represent those of Shape Blue Ltd or related companies. If you are not the
> intended recipient of this email, you must neither take any action based upon 
> its
> contents, nor copy or show it to anyone. Please contact the sender if you
> believe you have received this email in error. Shape Blue Ltd is a company
> incorporated in England & Wales. ShapeBlue Services India LLP is a company
> incorporated in India and is operated under license from Shape Blue Ltd. Shape
> Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
> operated
> under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
> registered
> by The Republic of South Africa and is traded under license from Shape Blue 
> Ltd.
> ShapeBlue is a registered trademark.

Dependecy issue with juniper-contrail-api.jar

[Radu Enea]

Hi everyone,

 

I tried to compile cloustack 4.5 and I need some help with the following
issue:

 

[ERROR] Failed to execute goal on project cloud-plugin-network-contrail:
Could not resolve dependencies for project
org.apache.cloudstack:cloud-plugin-network-contrail:jar:4.5.1-SNAPSHOT:
Could not find artifact net.juniper.contrail:juniper-contrail-api:jar:
1.0-SNAPSHOT

 

I did a little research and found out that the repository from where should
I download the specified files is not available anymore
(http://juniper.github.io/contrail-maven/releases ) and I did not found any
alternative location to download and install the dependency locally. (
1.0-Snapshoot version )

Can you please help me and provide a location for the required dependencies
?

 

Note: I used this as a guide:
http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201405.mbox/%3CCF953
7f6.13fe7%25sbalin...@juniper.net%3E

 

Thanks and

Best regards,

RADU ENEA

QA Tech Leader

  Ecommerce, Inc

Re: Doc Need to update for 4.5

[Pierre-Luc Dion]

Thanks for the clue, I'll update the doc for ACS 4.5. if you want to use
ACS + XS6.5 you should use CloudStack 4.5.x you can build package from the
4.5 git branch, 4.5.1 is currently in RC phase hopefully release in less
then a month.

Regards,


On Wed, Apr 1, 2015 at 12:35 PM, Keerthiraja SJ  wrote:

> Hi All,
>
> With below document link I couldn't see On Hypervisor Xenserver 6.5 is
> supported.
>
>
> http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/latest/hypervisor/xenserver.html
>
> Thanks,
> Keerthi
>

Build failed in Jenkins: simulator-singlerun #1079

[jenkins]

See 

Changes:

[talluri] CLOUDSTACK-8361: Adding functionality in marvin to check the port 
groups in VCenter corresponding to configuration of traffics in physical 
networks

--
[...truncated 10386 lines...]
> Running query: GRANT ALL ON cloudbridge.* to 'cloud'@`%` 
identified by 'cloud'
> Processing SQL file at 

> Processing SQL file at 

> Processing SQL file at 

> Processing SQL file at 

> Processing SQL file at 

> Processing SQL file at 

> Processing SQL file at 

> Processing SQL file at 

> Processing SQL file at 

> Processing SQL file at 

> Processing SQL file at 

> Processing SQL file at 

> Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker
[INFO] 
[INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ 
cloud-developer ---
[INFO] 
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
cloud-developer ---
[INFO] Installing 
 
to 
/var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-developer/4.6.0-SNAPSHOT/cloud-developer-4.6.0-SNAPSHOT.pom
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 1:54.063s
[INFO] Finished at: Fri Apr 03 06:28:10 EDT 2015
[INFO] Final Memory: 45M/217M
[INFO] 
[WARNING] The requested profile "simulator" could not be activated because it 
does not exist.
[simulator-singlerun] $ mvn -P developer -pl developer -Ddeploydb-simulator
[INFO] Scanning for projects...
[INFO] 
[INFO] 
[INFO] Building Apache CloudStack Developer Mode 4.6.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ 
cloud-developer ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] --- properties-maven-plugin:1.0-alpha-2:read-project-properties 
(default) @ cloud-developer ---
[WARNING] Ignoring missing properties file: 

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloud-developer ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.8:run (default) @ cloud-developer ---
[INFO] Executing tasks

main:
[INFO] Executed tasks
[INFO] 
[INFO] >>> exec-maven-plugin:1.2.1:java (create-schema-simulator) @ 
cloud-developer >>>
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ 
cloud-developer ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] <<< exec-maven-plugin:1.2.1:java (create-schema-simulator) @ 
cloud-developer <<<
[INFO] 
[INFO] --- exec-maven-plugin:1.2.1:java (create-schema-simulator) @ 
cloud-developer ---
log4j:WARN No appenders could be found for logger 
(org.springframework.core.env.StandardEnvironment).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
info.
> WARNING: Provided file does not exist: 

> Initializing database=simulator with host=localhost port=3306 
username=cloud password=cloud
===

Build failed in Jenkins: simulator-singlerun #1078

[jenkins]

See 

Changes:

[wrodrigues] Adding license headers that made RAT fail

--
[...truncated 10374 lines...]
> Running query: create database `cloud`
> Running query: GRANT ALL ON cloud.* to 'cloud'@`localhost` 
identified by 'cloud'
> Running query: GRANT ALL ON cloud.* to 'cloud'@`%` identified by 
'cloud'
> Initializing database=cloud_usage with host=localhost port=3306 
username=cloud password=cloud
> Running query: drop database if exists `cloud_usage`
> Running query: create database `cloud_usage`
> Running query: GRANT ALL ON cloud_usage.* to 'cloud'@`localhost` 
identified by 'cloud'
> Running query: GRANT ALL ON cloud_usage.* to 'cloud'@`%` 
identified by 'cloud'
> Initializing database=cloudbridge with host=localhost port=3306 
username=cloud password=cloud
> Running query: drop database if exists `cloudbridge`
> Running query: create database `cloudbridge`
> Running query: GRANT ALL ON cloudbridge.* to 'cloud'@`localhost` 
identified by 'cloud'
> Running query: GRANT ALL ON cloudbridge.* to 'cloud'@`%` 
identified by 'cloud'
> Processing SQL file at 

> Processing SQL file at 

> Processing SQL file at 

> Processing SQL file at 

> Processing SQL file at 

> Processing SQL file at 

> Processing SQL file at 

> Processing SQL file at 

> Processing SQL file at 

> Processing SQL file at 

> Processing SQL file at 

> Processing SQL file at 

> Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker
[INFO] 
[INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ 
cloud-developer ---
[INFO] 
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
cloud-developer ---
[INFO] Installing 
 
to 
/var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-developer/4.6.0-SNAPSHOT/cloud-developer-4.6.0-SNAPSHOT.pom
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 1:54.310s
[INFO] Finished at: Fri Apr 03 06:05:10 EDT 2015
[INFO] Final Memory: 45M/189M
[INFO] 
[WARNING] The requested profile "simulator" could not be activated because it 
does not exist.
[simulator-singlerun] $ mvn -P developer -pl developer -Ddeploydb-simulator
[INFO] Scanning for projects...
[INFO] 
[INFO] 
[INFO] Building Apache CloudStack Developer Mode 4.6.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ 
cloud-developer ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] --- properties-maven-plugin:1.0-alpha-2:read-project-properties 
(default) @ cloud-developer ---
[WARNING] Ignoring missing properties file: 

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloud-developer ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.8:run (default) @ cloud-developer ---
[INFO] Executing tasks

main:
[INFO] Executed tasks
[INFO] 
[INFO] >>> exec-maven-plugin:1.2.1:ja

[GitHub] cloudstack pull request: CLOUDSTACK-8361: Adding functionality in ...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-8361: Adding functionality in ...

[srikanteswartalluri]

Github user srikanteswartalluri commented on the pull request:

https://github.com/apache/cloudstack/pull/144#issuecomment-89240323
  
well written.


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

[DISCUSS] How to fix failing VR-mgmt server links

[Rohit Yadav]

Hi,

In large environments, one of the issues of a VM deployment or a network rule 
failing that I find commonly is that the mgmt server is unable to reach to the 
VR via the host because of network lag or issues between the host and the mgmt 
server. The sending operation on the link is tried about 5 times (hardcoded) 
before it gives up and we see something like this in the logs: "Unable to reach 
the peer that the agent is connected”.

Should we add a global setting to allow sysadmins to configure the agent 
link/socket (in various AgentAttaches in 
engine/orchestration/src/com/cloud/agent/manager ?) timeout or please share if 
something like this already exists or any other solution to this problem?

The other issue I see is that since VRs don’t have an agent running in it, to 
execute an operation mgmt server SSH-es into it to run scripts, for a high load 
the number of open FDs (so also TCP ports) on a VR/systemvm are limited which 
again can cause connections to fail/timeout due to high number of requests VR 
is processing. A long term solution could be to implement an agent (like 
ssvm/cpvm) that runs inside of the VR and talks to mgmt server over multiplexed 
connection so we limit the number of connections from one mgmt server and we 
can get rid of the SSH code and execution of barbaric scripts. Comments, 
suggestions, flames?

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

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

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

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

Jenkins build is still unstable: simulator-4.5-singlerun #196

[jenkins]

See 

[GitHub] cloudstack pull request: CLOUDSTACK-8361: Adding functionality in ...

[gauravaradhye]

GitHub user gauravaradhye opened a pull request:

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

CLOUDSTACK-8361: Adding functionality in marvin to check the port groups in 
VCenter corresponding to configuration of traffics in physical networks

Adding common function in marvin which can be called from any test case. 
The function verifies that Port groups are present in a VCenter corresponding 
the different traffics present in physical networks of zones.

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

$ git pull https://github.com/gauravaradhye/cloudstack 8361

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

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


commit 20eba5a6426f99676ef2fe12f6c8234a03139307
Author: Gaurav Aradhye 
Date:   2015-04-03T09:26:42Z

CLOUDSTACK-8361: Adding functionality in marvin to check the port groups in 
VCenter corresponding to configuration of traffics in physical networks




---
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: cloudstack-4.3-maven-build #710

[jenkins]

See 

Changes:

[runseb] Add CONTRIBUTING instructions

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

Cloning the remote Git repository
Cloning repository git://git.apache.org/cloudstack.git
 > /usr/bin/git init 
 >  # 
 > timeout=10
Fetching upstream changes from git://git.apache.org/cloudstack.git
 > /usr/bin/git --version # timeout=10
 > /usr/bin/git -c core.askpass=true fetch --tags --progress 
 > git://git.apache.org/cloudstack.git +refs/heads/*:refs/remotes/origin/*
 > /usr/bin/git config remote.origin.url git://git.apache.org/cloudstack.git # 
 > timeout=10
 > /usr/bin/git config --add remote.origin.fetch 
 > +refs/heads/*:refs/remotes/origin/* # timeout=10
 > /usr/bin/git config remote.origin.url git://git.apache.org/cloudstack.git # 
 > timeout=10
Fetching upstream changes from git://git.apache.org/cloudstack.git
 > /usr/bin/git -c core.askpass=true fetch --tags --progress 
 > git://git.apache.org/cloudstack.git +refs/heads/*:refs/remotes/origin/*
 > /usr/bin/git rev-parse origin/4.3^{commit} # timeout=10
Checking out Revision 7939787ef24ec42357cc2be793d0977e28fd3407 (origin/4.3)
 > /usr/bin/git config core.sparsecheckout # timeout=10
 > /usr/bin/git checkout -f 7939787ef24ec42357cc2be793d0977e28fd3407
 > /usr/bin/git rev-list 3af3c73083413f847a35845a818ff20b8c11c51f # timeout=10
FATAL: Couldn’t find any executable in /usr/share/apache-maven-3.0.5
Build step 'Invoke top-level Maven targets' marked build as failure

Build failed in Jenkins: simulator-singlerun #1077

[jenkins]

See 

Changes:

[Rohit Yadav] systemvmtemplate: increase /opt parititon by 100MB

[runseb] Exclude CONTRIBUTING from RAT and link it on README

--
[...truncated 10413 lines...]
> Processing SQL file at 

> Processing SQL file at 

> Processing SQL file at 

> Processing SQL file at 

> Processing SQL file at 

> Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker
[INFO] 
[INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ 
cloud-developer ---
[INFO] 
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
cloud-developer ---
[INFO] Installing 
 
to 
/var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-developer/4.6.0-SNAPSHOT/cloud-developer-4.6.0-SNAPSHOT.pom
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 1:55.542s
[INFO] Finished at: Fri Apr 03 04:38:03 EDT 2015
[INFO] Final Memory: 45M/206M
[INFO] 
[WARNING] The requested profile "simulator" could not be activated because it 
does not exist.
[simulator-singlerun] $ mvn -P developer -pl developer -Ddeploydb-simulator
[INFO] Scanning for projects...
[INFO] 
[INFO] 
[INFO] Building Apache CloudStack Developer Mode 4.6.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ 
cloud-developer ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] --- properties-maven-plugin:1.0-alpha-2:read-project-properties 
(default) @ cloud-developer ---
[WARNING] Ignoring missing properties file: 

[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
cloud-developer ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.8:run (default) @ cloud-developer ---
[INFO] Executing tasks

main:
[INFO] Executed tasks
[INFO] 
[INFO] >>> exec-maven-plugin:1.2.1:java (create-schema-simulator) @ 
cloud-developer >>>
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ 
cloud-developer ---
[INFO] Starting audit...
Audit done.

[INFO] 
[INFO] <<< exec-maven-plugin:1.2.1:java (create-schema-simulator) @ 
cloud-developer <<<
[INFO] 
[INFO] --- exec-maven-plugin:1.2.1:java (create-schema-simulator) @ 
cloud-developer ---
log4j:WARN No appenders could be found for logger 
(org.springframework.core.env.StandardEnvironment).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
info.
> WARNING: Provided file does not exist: 

> Initializing database=simulator with host=localhost port=3306 
username=cloud password=cloud
> Running query: drop database if exists `simulator`
> Running query: create database `simulator`
> Running query: GRANT ALL ON simulator.* to 'cloud'@`localhost` 
identified by 'cloud'
> Running query: GRANT ALL ON simulator.* to 'cloud'@`%` identified 
by 'cloud'
> Processing SQL file at 

> Processing SQL file at 

> Processing SQL file at 

> Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker
[INFO] 
[INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ 
cloud-developer ---
[INFO] 
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
cloud-developer ---
[INFO] Installing 

[GitHub] cloudstack pull request: Adding license headers that made RAT fail

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: Adding license headers that made RAT fail

[wilderrodrigues]

GitHub user wilderrodrigues opened a pull request:

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

Adding license headers that made RAT fail

   - Test classes affected

Build is passing fine and unit tests also running fine.

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

$ git pull https://github.com/schubergphilis/cloudstack fix_license_headers

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

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


commit c425f8d2bfda9cedbcfea856d337fcb0e34f7e98
Author: wilderrodrigues 
Date:   2015-04-03T08:37:58Z

Adding license headers that made RAT fail

   - Test classes affected




---
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: RAT failing

[Wilder Rodrigues]

On it!

Cheers,
Wilder

On 03 Apr 2015, at 10:14, Sebastien Goasguen  wrote:

> Wilder,
> 
> Looks like you committed code without the ASF license header:
> 
> https://github.com/apache/cloudstack/tree/master/plugins/hypervisors/xenserver/test/com/cloud/hypervisor/xenserver/resource/wrapper
> 
> Can you fix that asap ?
> 
> As a reminder ASF license header needs to be in every file or it needs to be 
> excluded in the root pom.xml...
> 
> thanks

Re: [DISCUSS] Stop using Review Board

[Sebastien Goasguen]

Seems with have lazy consensus.

Will Stevens contributed CONTRIBUTING instructions at:
https://github.com/apache/cloudstack/blob/master/CONTRIBUTING.md

I am pushing that to 4.5,4.4 and 4.3 and I will update our website contribution 
page, removing reference to RB.
I will then put a message in the RB current reviews.

I propose to leave it a week with the message, this will give time to folks to 
move their review to GH.

After that, I will ask ASF infra to “hide” RB. They cannot make it readonly, we 
can only hide the view.

yell if you don’t like it :)

-sebastien


> On Mar 31, 2015, at 5:17 AM, Rohit Yadav  wrote:
> 
> +1
> 
> Can we somehow disable RB for CloudStack project? We can run through pending 
> RB patches and close them or move them to GH.
> 
>> On 27-Mar-2015, at 8:50 pm, David Nalley  wrote:
>> 
>> +1 for GH
>> 
>> 
>> On Fri, Mar 27, 2015 at 4:52 AM, Sebastien Goasguen  wrote:
>>> Hi everyone,
>>> 
>>> Since GitHub pull requests have been enabled for cloudstack, we have closed 
>>> 127 commits.
>>> 
>>> I believe this is a nicer interface, one that folks are used to when 
>>> contributing to other open source projects.
>>> 
>>> In the meantime, we still have 73 open reviews on Review Board
>>> 
>>> https://reviews.apache.org/
>>> 
>>> * I propose that we stop using RB all together, and remove any links to it 
>>> from our website and README.
>>> 
>>> A few of us have tried to close some of the reviews by pinging the authors 
>>> already.
>>> 
>>> * My second proposition is that we write a comment in all reviews:
>>> 
>>> “Thanks for the patch, the cloudstack community has decided to stop using 
>>> Review Board in favor of github pull request.
>>> You can see  to learn how to submit a pull request to cloudstack. 
>>> Could you move your patch to a PR ?
>>> Without response from you we will close this review within 7 days.
>>> "
>>> 
>>> There is good contribution guidelines in our docs README:
>>> https://github.com/apache/cloudstack-docs
>>> 
>>> -Sebastien
> 
> Regards,
> Rohit Yadav
> Software Architect, ShapeBlue
> M. +91 88 262 30892 | rohit.ya...@shapeblue.com
> Blog: bhaisaab.org | Twitter: @_bhaisaab
> 
> 
> 
> Find out more about ShapeBlue and our range of CloudStack related services
> 
> IaaS Cloud Design & Build
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Software 
> Engineering
> CloudStack Infrastructure 
> Support
> CloudStack Bootcamp Training 
> Courses
> 
> This email and any attachments to it may be confidential and are intended 
> solely for the use of the individual to whom it is addressed. Any views or 
> opinions expressed are solely those of the author and do not necessarily 
> represent those of Shape Blue Ltd or related companies. If you are not the 
> intended recipient of this email, you must neither take any action based upon 
> its contents, nor copy or show it to anyone. Please contact the sender if you 
> believe you have received this email in error. Shape Blue Ltd is a company 
> incorporated in England & Wales. ShapeBlue Services India LLP is a company 
> incorporated in India and is operated under license from Shape Blue Ltd. 
> Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
> operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
> registered by The Republic of South Africa and is traded under license from 
> Shape Blue Ltd. ShapeBlue is a registered trademark.

RAT failing

[Sebastien Goasguen]

Wilder,

Looks like you committed code without the ASF license header:

https://github.com/apache/cloudstack/tree/master/plugins/hypervisors/xenserver/test/com/cloud/hypervisor/xenserver/resource/wrapper

Can you fix that asap ?

As a reminder ASF license header needs to be in every file or it needs to be 
excluded in the root pom.xml...

thanks

[GitHub] cloudstack pull request: fix yum install require java => 1.7.0 whe...

[karuturi]

Github user karuturi commented on the pull request:

https://github.com/apache/cloudstack/pull/108#issuecomment-89206971
  
@ghxandsky 
I fixed it on master yesterday. Please verify.

@bhaisaab
This is not pushed to 4.5

-Original Message-
From: "Rohit Yadav" 
Sent: ‎03-‎04-‎2015 12:05
To: "apache/cloudstack" 
Cc: "Rajani Karuturi" 
Subject: Re: [cloudstack] fix yum install require java => 1.7.0 when 
buildmanagement agent and us... (#108)

@ghxandsky can you send a new PR, both both master and 4.5 (separately)? 
Thanks.
—
Reply to this email directly or view it on GitHub.


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