date:20160307

Re: Question on compatibility matrix

2016-03-07 Thread Rohit Yadav

Hi Sadhu,

Thanks for confirming.

Regards.

> On 08-Mar-2016, at 5:35 AM, Suresh Sadhu  wrote:
>
> Yes you are right " that was done because that specific version/patch was the 
> latest available release at the time?" it should work with previous 
> releases(patches) as well.
>
>
> Regards
> Sadhu
>
>
> -Original Message-
> From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com]
> Sent: Monday, March 7, 2016 2:44 PM
> To: Pierre-Luc Dion; dev
> Subject: Re: Question on compatibility matrix
>
> Thanks Pierre-Luc, in that case anyone from Citrix has any idea?
>
> On 05-Mar-2016, at 1:05 AM, Pierre-Luc Dion 
> > wrote:
>
> Hi Rohit,
>
> I can't recall where that version specific come from for ACS 4.5 with VMware, 
> I think it was from the CloudPlatform 4.5 release notes.
> I never really tested  ACS with VMware so I cannot really comment on which 
> version is required.
>
> Anyone else would have an idea?
>
> Thanks
>
>
> On Fri, Mar 4, 2016 at 10:28 AM, Rohit Yadav 
> > wrote:
> Hi Pierre-Luc, (+dev@)
>
> Hope you're doing great. I've a question around compatibility matrix and 
> since you’ve been maintaining the docs I thought perhaps you may have an 
> answer.
>
> Refer: 
> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.5.2/compat.html
>
> I see that the VMware version supported is set to "5.0 update 3a". Any reason 
> why we support only "3a" and not previous 5.0 updates such as update1 etc.? 
> Or, maybe that was done because that specific version/patch was the latest 
> available release at the time?
>
> Appreciate if anyone can share if they are running VMware 5.0 with ACS 4.5.x. 
> Thanks.
>
> Regards.
>
>
> 
> 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.
>
>
>
>
> 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
>
>
>
> DISCLAIMER
> ==
> This e-mail may contain privileged and confidential information which is the 
> property of Accelerite, a Persistent Systems business. It is intended only 
> for the use of the individual or entity to which it is addressed. If you are 
> not the intended recipient, you are not authorized to read, retain, copy, 
> print, distribute or use this message. If you have received this 
> communication in error, please notify the sender and delete all

[GitHub] cloudstack pull request: CLOUDSTACK-9285 for 4.7.x

2016-03-07 Thread ustcweizhou

Github user ustcweizhou commented on the pull request:

https://github.com/apache/cloudstack/pull/1430#issuecomment-193648204
  
@kiwiflyer this is the log in jira:

```
2016-02-15 10:46:21,611 INFO  [utils.exception.CSExceptionErrorCode] 
(main:null) (logid:) Could not find exception: 
com.cloud.utils.exception.NioConnectionException in error code list for 
exceptions
2016-02-15 10:46:21,612 ERROR [cloud.agent.AgentShell] (main:null) (logid:) 
Unable to start agent:
com.cloud.utils.exception.CloudRuntimeException: Unable to start the 
connection!
at com.cloud.agent.Agent.start(Agent.java:230)
at com.cloud.agent.AgentShell.launchAgent(AgentShell.java:399)
at 
com.cloud.agent.AgentShell.launchAgentFromClassInfo(AgentShell.java:367)
```

@wilderrodrigues this issue was introduced by your commit 
79a3f8c5774c50dc128968c29da5096dc3dde39e, can you please have a look?

```
commit 79a3f8c5774c50dc128968c29da5096dc3dde39e
Refs: 4.5.1-2982-g79a3f8c
Author: wilderrodrigues 
AuthorDate: Tue Sep 8 12:12:55 2015 +0200
Commit: wilderrodrigues 
CommitDate: Fri Sep 11 11:28:40 2015 +0200

CLOUDSTACK-8822 - Replacing Runnable by Callable in the Taks and 
NioConnection classes

   - All the sub-classes were also updated according to the changes in 
the super-classes
   - There were also code formatting changes
```


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

Re: [PROPOSAL] Minimum Viable CI Integration

2016-03-07 Thread Bharat Kumar

Hi Suresh,

We can only get which assertion failed, but for getting the actual reason i.e. 
what happened in cloudstack  we need to check the cloudstack log. I am 
uploading the logs to dropBox.

Thanks,
Bharat.

> On 08-Mar-2016, at 11:36 AM, Suresh Anaparti  
> wrote:
> 
> Hi Bharat,
> 
> Good to see the list of failed and skipped ones in the report. Is it possible 
> to add some generic comment/reason to know why these test cases are 
> failed/skipped?
> 
> Thanks,
> Suresh
> 
> 
> 
> 
> On 08/03/16 11:05 am, "Bharat Kumar"  wrote:
> 
>> Hi Srinivas,
>> 
>> The tests get skipped because the hardware requirement for those tests is 
>> not satisfied. I will try to add more details to
>> the skipped tests so that people can run manually if needed.
>> 
>> The details of the hardware used can be added, but I am thinking of 
>> publishing it in the wiki
>> rather than adding these in the test results.
>> 
>> Thanks for the pointers.
>> 
>> —Bharat.
>> 
>> 
>> On 08-Mar-2016, at 10:36 AM, Gandikota Srinivas 
>> > wrote:
>> 
>> Hi Bharat,
>> 
>> Great job, report looks really cool.
>> Will you be able to add few more details like the setup info (number of 
>> hosts, etc)
>> 
>> Report indicates few tests are skipped. is this due to setup limitations? 
>> can the skipped tests be also listed so that some of us can run those 
>> specific tests (say manually) and post the results.
>> 
>> Thanks,
>> Srinivas
>> 
>> On Mon, Mar 7, 2016 at 11:06 PM, Bharat Kumar 
>> > wrote:
>> Hi guys,
>> 
>> I am also working on the similar reporting problem, here is what i did
>> 
>> link to the report https://github.com/bvbharatk/cloud-stack/pull/1
>> 
>> I am thinking this is good enough for now, I want to start posting the 
>> results on each pr as shown in the above link.
>> please give me your comments or suggestions.
>> 
>> Thanks,
>> Bharat
>> On 05-Mar-2016, at 7:02 PM, Will Stevens 
>> >>
>>  wrote:
>> 
>> Daan
>> 
>> Regarding the obligatory provider id.  I agree, but I am still trying to
>> figure out the details.  Creating distinct runs that have their own status
>> is done by setting the 'context'.  I think we would need to have two pieces
>> to this.  A provider id and an environment id.
>> 
>> So for example.  Lets assume that my provider id is 'CloudOps' and I have
>> two different environments, one for 'KVM' and one for 'Xen' (for example).
>> I would then the tool would produce the following two independent CI
>> statuses.
>> 'CloudOps - KVM' : with a basic description of the environment.
>> 'CloudOps - Xen' : again with a basic description of the env.
>> ... and so on ...
>> 
>> I am still sorting out the details here as well as making it easy for us to
>> integrate this into the apache/cloudstack repo with the access we currently
>> have.  Adding this is 'no biggy' for me because I am building this tool as
>> we speak, and trying to tailor it to our (ACS) needs, so this type of
>> feedback is perfect as it allows me to adapt the tool before I get too deep.
>> 
>> *Will STEVENS*
>> Lead Developer
>> 
>> *CloudOps* *| *Cloud Solutions Experts
>> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
>> w 
>> cloudops.com>
>>  *|* tw @CloudOps_
>> 
>> On Sat, Mar 5, 2016 at 4:17 AM, Daan Hoogland 
>> >>
>> wrote:
>> 
>> Will
>> 
>> Gret work, especially the thing you are showing in link [4], I would like
>> to make an enhancement request and that is a obligatory provider id. Only
>> if it is no biggy for you!
>> Several people may decide to do a XVM on ChildrensOS for instance and so we
>> may be aware of an obscurity that is different. If one fails and the other
>> succeeds it is easily identified.
>> 
>> Ilya,
>> 
>> I have been playing with go and it is a very nice language for such a
>> simple script, though it wasn't exactly designed for it. So don't read my
>> comment/question as an objection. But we do have
>> bash,python,c#,java,javascript,xslt,sql at least. That is not counting the
>> build system and I am sure the hyperv has some extra windows specific
>> stuff.
>> To me it is inherent to the nature of across platform orchestration and
>> provisioning system so it is fine. It is something to consider. On the
>> other hand when bringing in new tools we don't make the choice so I am
>> ranting, I guess.
>> 
>> 
>> 
>> On Sat, Mar 5, 2016 at 7:38 AM, ilya 
>> >>
>>  wrote:
>> 
>> I see where Daan

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

2016-03-07 Thread jenkins

See 

--
[...truncated 28679 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.838s]
[INFO] Apache CloudStack . SUCCESS [2.552s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.776s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.262s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:29.477s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.112s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [53.677s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.638s]
[INFO] Apache CloudStack API . SUCCESS [2:00.578s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.291s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [29.687s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.104s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.449s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [25.066s]
[INFO] Apache CloudStack Core  SUCCESS [1:22.274s]
[INFO] Apache CloudStack Agents .. SUCCESS [35.941s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [37.707s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [15.534s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:07.848s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.078s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.749s]
[INFO] Apache CloudStack Server .. SUCCESS [4:10.095s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [38.032s]
[INFO] Apache CloudStack Usage Server  SUCCESS [45.066s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:22.790s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.070s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.454s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [53.764s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [47.760s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [29.985s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.544s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [25.444s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [20.987s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.198s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.289s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [8.095s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.927s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.322s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.420s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[37.143s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.259s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.450s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [16.865s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.594s]
[INFO] Apache

Re: [PROPOSAL] Minimum Viable CI Integration

2016-03-07 Thread Suresh Anaparti

Hi Bharat,

Good to see the list of failed and skipped ones in the report. Is it possible 
to add some generic comment/reason to know why these test cases are 
failed/skipped?

Thanks,
Suresh




On 08/03/16 11:05 am, "Bharat Kumar"  wrote:

>Hi Srinivas,
>
>The tests get skipped because the hardware requirement for those tests is not 
>satisfied. I will try to add more details to
>the skipped tests so that people can run manually if needed.
>
>The details of the hardware used can be added, but I am thinking of publishing 
>it in the wiki
>rather than adding these in the test results.
>
>Thanks for the pointers.
>
>—Bharat.
>
>
>On 08-Mar-2016, at 10:36 AM, Gandikota Srinivas 
>> wrote:
>
>Hi Bharat,
>
>Great job, report looks really cool.
>Will you be able to add few more details like the setup info (number of hosts, 
>etc)
>
>Report indicates few tests are skipped. is this due to setup limitations? can 
>the skipped tests be also listed so that some of us can run those specific 
>tests (say manually) and post the results.
>
>Thanks,
>Srinivas
>
>On Mon, Mar 7, 2016 at 11:06 PM, Bharat Kumar 
>> wrote:
>Hi guys,
>
>I am also working on the similar reporting problem, here is what i did
>
>link to the report https://github.com/bvbharatk/cloud-stack/pull/1
>
>I am thinking this is good enough for now, I want to start posting the results 
>on each pr as shown in the above link.
>please give me your comments or suggestions.
>
>Thanks,
>Bharat
>On 05-Mar-2016, at 7:02 PM, Will Stevens 
>>>
> wrote:
>
>Daan
>
>Regarding the obligatory provider id.  I agree, but I am still trying to
>figure out the details.  Creating distinct runs that have their own status
>is done by setting the 'context'.  I think we would need to have two pieces
>to this.  A provider id and an environment id.
>
>So for example.  Lets assume that my provider id is 'CloudOps' and I have
>two different environments, one for 'KVM' and one for 'Xen' (for example).
>I would then the tool would produce the following two independent CI
>statuses.
>'CloudOps - KVM' : with a basic description of the environment.
>'CloudOps - Xen' : again with a basic description of the env.
>... and so on ...
>
>I am still sorting out the details here as well as making it easy for us to
>integrate this into the apache/cloudstack repo with the access we currently
>have.  Adding this is 'no biggy' for me because I am building this tool as
>we speak, and trying to tailor it to our (ACS) needs, so this type of
>feedback is perfect as it allows me to adapt the tool before I get too deep.
>
>*Will STEVENS*
>Lead Developer
>
>*CloudOps* *| *Cloud Solutions Experts
>420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
>w 
>cloudops.com> 
>*|* tw @CloudOps_
>
>On Sat, Mar 5, 2016 at 4:17 AM, Daan Hoogland 
>>>
>wrote:
>
>Will
>
>Gret work, especially the thing you are showing in link [4], I would like
>to make an enhancement request and that is a obligatory provider id. Only
>if it is no biggy for you!
>Several people may decide to do a XVM on ChildrensOS for instance and so we
>may be aware of an obscurity that is different. If one fails and the other
>succeeds it is easily identified.
>
>Ilya,
>
>I have been playing with go and it is a very nice language for such a
>simple script, though it wasn't exactly designed for it. So don't read my
>comment/question as an objection. But we do have
>bash,python,c#,java,javascript,xslt,sql at least. That is not counting the
>build system and I am sure the hyperv has some extra windows specific
>stuff.
>To me it is inherent to the nature of across platform orchestration and
>provisioning system so it is fine. It is something to consider. On the
>other hand when bringing in new tools we don't make the choice so I am
>ranting, I guess.
>
>
>
>On Sat, Mar 5, 2016 at 7:38 AM, ilya 
>>>
> wrote:
>
>I see where Daan is coming from :)  I thought this would be 4th, not
>exactly 7ths.
>
>I'm not against golang by any means (if anything - its my next "go" to
>language these days).
>
>Things to consider:
>
>Would notify-pr support proxy? I've been thinking on ways of
>contributing test runs, there would have to be few things i'd need to do.
>
>1) massage the log content - such that no environment details are
>exposed, i can probably handle this with sed/awk..
>
>2) i'm behind multiple firewalls with no internet access. however, some
>lab environments might have a

Re: [PROPOSAL] Minimum Viable CI Integration

2016-03-07 Thread Bharat Kumar

Hi Srinivas,

The tests get skipped because the hardware requirement for those tests is not 
satisfied. I will try to add more details to
the skipped tests so that people can run manually if needed.

The details of the hardware used can be added, but I am thinking of publishing 
it in the wiki
rather than adding these in the test results.

Thanks for the pointers.

—Bharat.

On 08-Mar-2016, at 10:36 AM, Gandikota Srinivas 
> wrote:

Hi Bharat,

Great job, report looks really cool.
Will you be able to add few more details like the setup info (number of hosts, 
etc)

Report indicates few tests are skipped. is this due to setup limitations? can 
the skipped tests be also listed so that some of us can run those specific 
tests (say manually) and post the results.

Thanks,
Srinivas

On Mon, Mar 7, 2016 at 11:06 PM, Bharat Kumar 
> wrote:
Hi guys,

I am also working on the similar reporting problem, here is what i did

link to the report https://github.com/bvbharatk/cloud-stack/pull/1

I am thinking this is good enough for now, I want to start posting the results 
on each pr as shown in the above link.
please give me your comments or suggestions.

Thanks,
Bharat
On 05-Mar-2016, at 7:02 PM, Will Stevens 
>>
 wrote:

Daan

Regarding the obligatory provider id.  I agree, but I am still trying to
figure out the details.  Creating distinct runs that have their own status
is done by setting the 'context'.  I think we would need to have two pieces
to this.  A provider id and an environment id.

So for example.  Lets assume that my provider id is 'CloudOps' and I have
two different environments, one for 'KVM' and one for 'Xen' (for example).
I would then the tool would produce the following two independent CI
statuses.
'CloudOps - KVM' : with a basic description of the environment.
'CloudOps - Xen' : again with a basic description of the env.
... and so on ...

I am still sorting out the details here as well as making it easy for us to
integrate this into the apache/cloudstack repo with the access we currently
have.  Adding this is 'no biggy' for me because I am building this tool as
we speak, and trying to tailor it to our (ACS) needs, so this type of
feedback is perfect as it allows me to adapt the tool before I get too deep.

*Will STEVENS*
Lead Developer

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

On Sat, Mar 5, 2016 at 4:17 AM, Daan Hoogland 
>>
wrote:

Will

Gret work, especially the thing you are showing in link [4], I would like
to make an enhancement request and that is a obligatory provider id. Only
if it is no biggy for you!
Several people may decide to do a XVM on ChildrensOS for instance and so we
may be aware of an obscurity that is different. If one fails and the other
succeeds it is easily identified.

Ilya,

I have been playing with go and it is a very nice language for such a
simple script, though it wasn't exactly designed for it. So don't read my
comment/question as an objection. But we do have
bash,python,c#,java,javascript,xslt,sql at least. That is not counting the
build system and I am sure the hyperv has some extra windows specific
stuff.
To me it is inherent to the nature of across platform orchestration and
provisioning system so it is fine. It is something to consider. On the
other hand when bringing in new tools we don't make the choice so I am
ranting, I guess.

On Sat, Mar 5, 2016 at 7:38 AM, ilya 
>>
 wrote:

I see where Daan is coming from :)  I thought this would be 4th, not
exactly 7ths.

I'm not against golang by any means (if anything - its my next "go" to
language these days).

Things to consider:

Would notify-pr support proxy? I've been thinking on ways of
contributing test runs, there would have to be few things i'd need to do.

1) massage the log content - such that no environment details are
exposed, i can probably handle this with sed/awk..

2) i'm behind multiple firewalls with no internet access. however, some
lab environments might have a proxy, so it would be nice to have a
support for it.

Thanks
ilya

On 3/4/16 6:56 AM, Will Stevens wrote:
Yes, I have most of it already built and will be releasing it later
today
or over the weekend.  The reason I chose Golang is because it can be
cross
compiled to be run on any system and distributed as a single binary
with
no
dependencies.  This means that no one will have to worry about building

Re: [PROPOSAL] Minimum Viable CI Integration

2016-03-07 Thread Gandikota Srinivas

Hi Bharat,

Great job, report looks really cool.
Will you be able to add few more details like the setup info (number of
hosts, etc)

Report indicates few tests are skipped. is this due to setup limitations?
can the skipped tests be also listed so that some of us can run those
specific tests (say manually) and post the results.

Thanks,
Srinivas

On Mon, Mar 7, 2016 at 11:06 PM, Bharat Kumar 
wrote:

> Hi guys,
>
> I am also working on the similar reporting problem, here is what i did
>
> link to the report https://github.com/bvbharatk/cloud-stack/pull/1
>
> I am thinking this is good enough for now, I want to start posting the
> results on each pr as shown in the above link.
> please give me your comments or suggestions.
>
> Thanks,
> Bharat
> On 05-Mar-2016, at 7:02 PM, Will Stevens > wrote:
>
> Daan
>
> Regarding the obligatory provider id.  I agree, but I am still trying to
> figure out the details.  Creating distinct runs that have their own status
> is done by setting the 'context'.  I think we would need to have two pieces
> to this.  A provider id and an environment id.
>
> So for example.  Lets assume that my provider id is 'CloudOps' and I have
> two different environments, one for 'KVM' and one for 'Xen' (for example).
> I would then the tool would produce the following two independent CI
> statuses.
> 'CloudOps - KVM' : with a basic description of the environment.
> 'CloudOps - Xen' : again with a basic description of the env.
> ... and so on ...
>
> I am still sorting out the details here as well as making it easy for us to
> integrate this into the apache/cloudstack repo with the access we currently
> have.  Adding this is 'no biggy' for me because I am building this tool as
> we speak, and trying to tailor it to our (ACS) needs, so this type of
> feedback is perfect as it allows me to adapt the tool before I get too
> deep.
>
> *Will STEVENS*
> Lead Developer
>
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
>
> On Sat, Mar 5, 2016 at 4:17 AM, Daan Hoogland  >
> wrote:
>
> Will
>
> Gret work, especially the thing you are showing in link [4], I would like
> to make an enhancement request and that is a obligatory provider id. Only
> if it is no biggy for you!
> Several people may decide to do a XVM on ChildrensOS for instance and so we
> may be aware of an obscurity that is different. If one fails and the other
> succeeds it is easily identified.
>
> Ilya,
>
> I have been playing with go and it is a very nice language for such a
> simple script, though it wasn't exactly designed for it. So don't read my
> comment/question as an objection. But we do have
> bash,python,c#,java,javascript,xslt,sql at least. That is not counting the
> build system and I am sure the hyperv has some extra windows specific
> stuff.
> To me it is inherent to the nature of across platform orchestration and
> provisioning system so it is fine. It is something to consider. On the
> other hand when bringing in new tools we don't make the choice so I am
> ranting, I guess.
>
>
>
> On Sat, Mar 5, 2016 at 7:38 AM, ilya > wrote:
>
> I see where Daan is coming from :)  I thought this would be 4th, not
> exactly 7ths.
>
> I'm not against golang by any means (if anything - its my next "go" to
> language these days).
>
> Things to consider:
>
> Would notify-pr support proxy? I've been thinking on ways of
> contributing test runs, there would have to be few things i'd need to do.
>
> 1) massage the log content - such that no environment details are
> exposed, i can probably handle this with sed/awk..
>
> 2) i'm behind multiple firewalls with no internet access. however, some
> lab environments might have a proxy, so it would be nice to have a
> support for it.
>
> Thanks
> ilya
>
>
>
> On 3/4/16 6:56 AM, Will Stevens wrote:
> Yes, I have most of it already built and will be releasing it later
> today
> or over the weekend.  The reason I chose Golang is because it can be
> cross
> compiled to be run on any system and distributed as a single binary
> with
> no
> dependencies.  This means that no one will have to worry about building
> it
> or having to change their environment at all in order to use it.  I am
> trying to lower the barrier to entry and make it as easy as possible
> for
> people to contribute back their CI execution details.
>
> *Will STEVENS*
> Lead Developer
>
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
>
> On Fri, Mar 4, 2016 at 8:53 AM, Daan Hoogland  
>
> wrote:
>
> Will, Do you have an implementation of notify-pr? I am asking as you
> specify it will be implemented

RE: Question on compatibility matrix

2016-03-07 Thread Suresh Sadhu

Yes you are right " that was done because that specific version/patch was the 
latest available release at the time?" it should work with previous 
releases(patches) as well.

Regards
Sadhu

-Original Message-
From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com] 
Sent: Monday, March 7, 2016 2:44 PM
To: Pierre-Luc Dion; dev
Subject: Re: Question on compatibility matrix

Thanks Pierre-Luc, in that case anyone from Citrix has any idea?

On 05-Mar-2016, at 1:05 AM, Pierre-Luc Dion 
> wrote:

Hi Rohit,

I can't recall where that version specific come from for ACS 4.5 with VMware, I 
think it was from the CloudPlatform 4.5 release notes.
I never really tested  ACS with VMware so I cannot really comment on which 
version is required.

Anyone else would have an idea?

Thanks

On Fri, Mar 4, 2016 at 10:28 AM, Rohit Yadav 
> wrote:
Hi Pierre-Luc, (+dev@)

Hope you're doing great. I've a question around compatibility matrix and since 
you’ve been maintaining the docs I thought perhaps you may have an answer.

Refer: 
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.5.2/compat.html

I see that the VMware version supported is set to "5.0 update 3a". Any reason 
why we support only "3a" and not previous 5.0 updates such as update1 etc.? Or, 
maybe that was done because that specific version/patch was the latest 
available release at the time?

Appreciate if anyone can share if they are running VMware 5.0 with ACS 4.5.x. 
Thanks.

Regards.

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.

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

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Accelerite, a Persistent Systems business. It is intended only for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient, you are not authorized to read, retain, copy, print, 
distribute or use this message. If you have received this communication in 
error, please notify the sender and delete all copies of this message. 
Accelerite, a Persistent Systems business does not accept any liability for 
virus infected mails.

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

2016-03-07 Thread jenkins

See 

--
[...truncated 28679 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.917s]
[INFO] Apache CloudStack . SUCCESS [2.115s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.792s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [18.911s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:29.716s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.110s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [53.737s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.677s]
[INFO] Apache CloudStack API . SUCCESS [1:49.254s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.573s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [29.985s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.092s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.228s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.395s]
[INFO] Apache CloudStack Core  SUCCESS [1:22.030s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.077s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [39.277s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.066s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:06.523s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.358s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.690s]
[INFO] Apache CloudStack Server .. SUCCESS [4:17.187s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [38.248s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.087s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:22.148s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.069s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.438s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.266s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [47.808s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [30.152s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.273s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [25.704s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [21.385s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.564s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.194s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [7.757s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.938s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.382s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.339s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[36.651s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.584s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.202s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [16.883s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.754s]
[INFO] Apache

Re: [PROPOSAL] Minimum Viable CI Integration

2016-03-07 Thread Will Stevens

Hmm. It probably is the right place, but I think a straight up "NO" is more
likely if we go that route.

It's hard to know if I should just implement 3) before we even ask in order
to improve our likelihood of getting something we can work with.

I will think about this and see what I can come up with as a simple yet
complete solution that will enable us to test against distributed CI
environments, while still fitting into a model that the Apache infra guys
will approve.
On Mar 7, 2016 6:36 PM, "Erik Weber"  wrote:

> I guess the appropriate channel would be to create a jira ticket for INFRA:
> https://issues.apache.org/jira/browse/INFRA
>
> --
> Erik
>
> On Mon, Mar 7, 2016 at 11:18 PM, Will Stevens 
> wrote:
>
> > This is kind of what I was expecting.  Do you know who I would be
> > contacting?  The permissions required are VERY minimal AND they have
> > already given the 'TravisCI' application the same permissions as we need
> > for this.
> >
> > How did we get the TravisCI application enabled and the permissions
> > accepted for that integration?
> >
> > I have been trying to thinking of ways to potentially work the system
> from
> > that side.  The main issue I have with this approach is that it is not a
> > single application that we want to give permission to.  Ideally, we would
> > give each individual/organization who is contributing a CI environment
> > their own token.  In that case, we would have to register the CI of each
> > party as their own CI integration.
> >
> > Here are some ideas I have as a 'work around' to the problem:
> >
> > 1) Register a single upr CI application with Github and have the apache
> > guys enable the integration.  This will give the application a single
> > access token.  I can then compile upr with the access token embedded into
> > the binary.  I don't like this approach and I feel we would probably be
> > violating some ToS somewhere.
> >
> > 2) Provide a web server implementation that each CI party can use to
> > register their own CI endpoint as a Github application integration.  Then
> > we have the apache guys enable each of them (which will be a harder sell
> to
> > them), but then each CI party will get their own token and will be able
> to
> > post back as themselves.  This is also nice because if someone is not a
> > good community member and misbehaves, their integration can be revoked
> > without it affecting everyone else who has a CI integration.
> >
> > 3) Provide a single web server implementation that is registered as a
> > Github Application Integration.  This implementation is then approved by
> > the apache guys for the cloudstack repo.  This web server implementation
> > (let's call it upr_server) keeps our one and only access token.  I then
> > modify the upr command line tool to take a token that is provided by the
> > upr_server when a CI party registers on the upr_server website.  The
> > upr command
> > will actually target the upr_server box when posting statuses, etc, which
> > will essentially proxy the calls on to Github using the token that was
> > approved for the integration.
> >
> > I think that 3) is probably the cleanest solution and would reduce our
> > chances of getting banned by someone for being too cheeky.  It is a whole
> > lot of trouble for nothing, but if they are going to be a stick in the
> mud
> > about this and not allow access tokens to anything other than official
> > github supported integrations, then I will have to make that work...
> >
> > Ideas?  Thoughts?  Rants?  :P
> >
> > *Will STEVENS*
> > Lead Developer
> >
> > *CloudOps* *| *Cloud Solutions Experts
> > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> > w cloudops.com *|* tw @CloudOps_
> >
> > On Mon, Mar 7, 2016 at 4:12 PM, Remi Bergsma <
> rberg...@schubergphilis.com>
> > wrote:
> >
> > > Hi Will,
> > >
> > > This is the main problem: there’s no one except Apache Infra with
> access
> > > to the Github CloudStack repo. Even committers have to push to Apache
> > git,
> > > which is mirrored to Github. We can’t close a PR, set a label, change a
> > > title or whatever basic operation. You can ask them for a token. When I
> > (as
> > > the release manager) asked for any more permission than an anonymous
> user
> > > has it was kindly refused. I really hope you’ll have more luck but I
> > > wouldn’t count on it.
> > >
> > >
> > >
> > > Regards,
> > > Remi
> > >
> > >
> > > On 07/03/16 19:10, "williamstev...@gmail.com on behalf of Will
> Stevens"
> > <
> > > williamstev...@gmail.com on behalf of wstev...@cloudops.com> wrote:
> > >
> > > >The main thing we have to sort out with this type of integration (as
> it
> > is
> > > >today) is the distribution of access tokens with the correct
> permissions
> > > on
> > > >the apache/cloudstack github repo.  The required permissions are very
> > > >limited, but I don't know if we have access to create new tokens.  If
> we
> > > >don't then I will have to develop an

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

2016-03-07 Thread jenkins

See 

--
[...truncated 28689 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.099s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.986s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [18.817s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:29.120s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.105s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [53.936s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.338s]
[INFO] Apache CloudStack API . SUCCESS [1:49.617s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.206s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [30.697s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.090s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [29.559s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.885s]
[INFO] Apache CloudStack Core  SUCCESS [1:22.249s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.089s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.191s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.086s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:07.905s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [41.893s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [26.020s]
[INFO] Apache CloudStack Server .. SUCCESS [4:13.563s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.520s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.362s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:22.642s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.070s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.450s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.434s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.358s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [30.193s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.793s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [25.586s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [20.493s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [36.170s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.411s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [8.053s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.955s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.428s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.661s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[35.629s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.285s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.280s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [16.380s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[17.079s]
[INFO] Apache

[GitHub] cloudstack pull request: CLOUDSTACK-9285 for 4.7.x

2016-03-07 Thread kiwiflyer

Github user kiwiflyer commented on the pull request:

https://github.com/apache/cloudstack/pull/1430#issuecomment-193508523
  
@ustcweizhou Thanks for the advice. Maybe I can catch you on the slack 
channel tomorrow to discuss a little, so I better understand the logic between 
start and reconnect.


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

Re: [PROPOSAL] Minimum Viable CI Integration

2016-03-07 Thread Erik Weber

I guess the appropriate channel would be to create a jira ticket for INFRA:
https://issues.apache.org/jira/browse/INFRA

-- 
Erik

On Mon, Mar 7, 2016 at 11:18 PM, Will Stevens  wrote:

> This is kind of what I was expecting.  Do you know who I would be
> contacting?  The permissions required are VERY minimal AND they have
> already given the 'TravisCI' application the same permissions as we need
> for this.
>
> How did we get the TravisCI application enabled and the permissions
> accepted for that integration?
>
> I have been trying to thinking of ways to potentially work the system from
> that side.  The main issue I have with this approach is that it is not a
> single application that we want to give permission to.  Ideally, we would
> give each individual/organization who is contributing a CI environment
> their own token.  In that case, we would have to register the CI of each
> party as their own CI integration.
>
> Here are some ideas I have as a 'work around' to the problem:
>
> 1) Register a single upr CI application with Github and have the apache
> guys enable the integration.  This will give the application a single
> access token.  I can then compile upr with the access token embedded into
> the binary.  I don't like this approach and I feel we would probably be
> violating some ToS somewhere.
>
> 2) Provide a web server implementation that each CI party can use to
> register their own CI endpoint as a Github application integration.  Then
> we have the apache guys enable each of them (which will be a harder sell to
> them), but then each CI party will get their own token and will be able to
> post back as themselves.  This is also nice because if someone is not a
> good community member and misbehaves, their integration can be revoked
> without it affecting everyone else who has a CI integration.
>
> 3) Provide a single web server implementation that is registered as a
> Github Application Integration.  This implementation is then approved by
> the apache guys for the cloudstack repo.  This web server implementation
> (let's call it upr_server) keeps our one and only access token.  I then
> modify the upr command line tool to take a token that is provided by the
> upr_server when a CI party registers on the upr_server website.  The
> upr command
> will actually target the upr_server box when posting statuses, etc, which
> will essentially proxy the calls on to Github using the token that was
> approved for the integration.
>
> I think that 3) is probably the cleanest solution and would reduce our
> chances of getting banned by someone for being too cheeky.  It is a whole
> lot of trouble for nothing, but if they are going to be a stick in the mud
> about this and not allow access tokens to anything other than official
> github supported integrations, then I will have to make that work...
>
> Ideas?  Thoughts?  Rants?  :P
>
> *Will STEVENS*
> Lead Developer
>
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
>
> On Mon, Mar 7, 2016 at 4:12 PM, Remi Bergsma 
> wrote:
>
> > Hi Will,
> >
> > This is the main problem: there’s no one except Apache Infra with access
> > to the Github CloudStack repo. Even committers have to push to Apache
> git,
> > which is mirrored to Github. We can’t close a PR, set a label, change a
> > title or whatever basic operation. You can ask them for a token. When I
> (as
> > the release manager) asked for any more permission than an anonymous user
> > has it was kindly refused. I really hope you’ll have more luck but I
> > wouldn’t count on it.
> >
> >
> >
> > Regards,
> > Remi
> >
> >
> > On 07/03/16 19:10, "williamstev...@gmail.com on behalf of Will Stevens"
> <
> > williamstev...@gmail.com on behalf of wstev...@cloudops.com> wrote:
> >
> > >The main thing we have to sort out with this type of integration (as it
> is
> > >today) is the distribution of access tokens with the correct permissions
> > on
> > >the apache/cloudstack github repo.  The required permissions are very
> > >limited, but I don't know if we have access to create new tokens.  If we
> > >don't then I will have to develop an application integration workaround
> to
> > >make it easier for the people with access to the apache/cloudstack repo
> to
> > >give the people running CI integrations access to update statuses (like
> > the
> > >current travis integration).
> >
> >
> >
> >
> >
> > >If you have questions or feedback, please don't be shy.
> > >
> > >*Will STEVENS*
> > >Lead Developer
> > >
> > >*CloudOps* *| *Cloud Solutions Experts
> > >420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> > >w cloudops.com *|* tw @CloudOps_
> > >
> > >On Mon, Mar 7, 2016 at 12:36 PM, Bharat Kumar <
> > bharat.ku...@accelerite.com>
> > >wrote:
> > >
> > >> Hi guys,
> > >>
> > >> I am also working on the similar reporting problem, here is what i did
> > >>
> > >> link to the report

[GitHub] cloudstack pull request: CLOUDSTACK-9285 for 4.7.x

2016-03-07 Thread ustcweizhou

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

https://github.com/apache/cloudstack/pull/1430#discussion_r55286730
  
--- Diff: agent/src/com/cloud/agent/Agent.java ---
@@ -412,7 +412,8 @@ protected void reconnect(final Link link) {
 try {
 _connection.start();
 } catch (final NioConnectionException e) {
-throw new CloudRuntimeException("Unable to start the 
connection!", e);
+   s_logger.info("Attempted to connect to the server, but 
received an unexpected exception, trying again...");
--- End diff --

1. I think you should fix line 230/238, that's the root cause of the issue. 
line 415 is not.
2. line 416 can be removed.


---
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: Addresses CLOUDSTACK-9300 where the MySQL...

2016-03-07 Thread kiwiflyer

Github user kiwiflyer commented on the pull request:

https://github.com/apache/cloudstack/pull/1428#issuecomment-193485886
  
@remibergsma In reference to other releases, yes this might also be broken 
on Ubuntu. We don't use Ubuntu, so having someone chime in who can test this 
would be nice.


---
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-9285 for 4.7.x

2016-03-07 Thread kiwiflyer

GitHub user kiwiflyer opened a pull request:

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

CLOUDSTACK-9285 for 4.7.x

Per Daan's request, here is a pull request for the 4.7.x release.

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

$ git pull https://github.com/myENA/cloudstack 4.7_cloudstack-9285

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

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


commit 5b6fbe6aebbe9cd24dfebe9271ecb5dc40877c94
Author: Simon Weller 
Date:   2016-03-07T22:23:35Z

Cloudstack 9285 for 4.7.x




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

Re: [PROPOSAL] Minimum Viable CI Integration

2016-03-07 Thread Will Stevens

This is kind of what I was expecting.  Do you know who I would be
contacting?  The permissions required are VERY minimal AND they have
already given the 'TravisCI' application the same permissions as we need
for this.

How did we get the TravisCI application enabled and the permissions
accepted for that integration?

I have been trying to thinking of ways to potentially work the system from
that side.  The main issue I have with this approach is that it is not a
single application that we want to give permission to.  Ideally, we would
give each individual/organization who is contributing a CI environment
their own token.  In that case, we would have to register the CI of each
party as their own CI integration.

Here are some ideas I have as a 'work around' to the problem:

1) Register a single upr CI application with Github and have the apache
guys enable the integration.  This will give the application a single
access token.  I can then compile upr with the access token embedded into
the binary.  I don't like this approach and I feel we would probably be
violating some ToS somewhere.

2) Provide a web server implementation that each CI party can use to
register their own CI endpoint as a Github application integration.  Then
we have the apache guys enable each of them (which will be a harder sell to
them), but then each CI party will get their own token and will be able to
post back as themselves.  This is also nice because if someone is not a
good community member and misbehaves, their integration can be revoked
without it affecting everyone else who has a CI integration.

3) Provide a single web server implementation that is registered as a
Github Application Integration.  This implementation is then approved by
the apache guys for the cloudstack repo.  This web server implementation
(let's call it upr_server) keeps our one and only access token.  I then
modify the upr command line tool to take a token that is provided by the
upr_server when a CI party registers on the upr_server website.  The
upr command
will actually target the upr_server box when posting statuses, etc, which
will essentially proxy the calls on to Github using the token that was
approved for the integration.

I think that 3) is probably the cleanest solution and would reduce our
chances of getting banned by someone for being too cheeky.  It is a whole
lot of trouble for nothing, but if they are going to be a stick in the mud
about this and not allow access tokens to anything other than official
github supported integrations, then I will have to make that work...

Ideas?  Thoughts?  Rants?  :P

*Will STEVENS*
Lead Developer

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

On Mon, Mar 7, 2016 at 4:12 PM, Remi Bergsma 
wrote:

> Hi Will,
>
> This is the main problem: there’s no one except Apache Infra with access
> to the Github CloudStack repo. Even committers have to push to Apache git,
> which is mirrored to Github. We can’t close a PR, set a label, change a
> title or whatever basic operation. You can ask them for a token. When I (as
> the release manager) asked for any more permission than an anonymous user
> has it was kindly refused. I really hope you’ll have more luck but I
> wouldn’t count on it.
>
>
>
> Regards,
> Remi
>
>
> On 07/03/16 19:10, "williamstev...@gmail.com on behalf of Will Stevens" <
> williamstev...@gmail.com on behalf of wstev...@cloudops.com> wrote:
>
> >The main thing we have to sort out with this type of integration (as it is
> >today) is the distribution of access tokens with the correct permissions
> on
> >the apache/cloudstack github repo.  The required permissions are very
> >limited, but I don't know if we have access to create new tokens.  If we
> >don't then I will have to develop an application integration workaround to
> >make it easier for the people with access to the apache/cloudstack repo to
> >give the people running CI integrations access to update statuses (like
> the
> >current travis integration).
>
>
>
>
>
> >If you have questions or feedback, please don't be shy.
> >
> >*Will STEVENS*
> >Lead Developer
> >
> >*CloudOps* *| *Cloud Solutions Experts
> >420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> >w cloudops.com *|* tw @CloudOps_
> >
> >On Mon, Mar 7, 2016 at 12:36 PM, Bharat Kumar <
> bharat.ku...@accelerite.com>
> >wrote:
> >
> >> Hi guys,
> >>
> >> I am also working on the similar reporting problem, here is what i did
> >>
> >> link to the report https://github.com/bvbharatk/cloud-stack/pull/1
> >>
> >> I am thinking this is good enough for now, I want to start posting the
> >> results on each pr as shown in the above link.
> >> please give me your comments or suggestions.
> >>
> >> Thanks,
> >> Bharat
> >> On 05-Mar-2016, at 7:02 PM, Will Stevens > wstev...@cloudops.com>> wrote:
> >>
> >> Daan
> >>
> >> Regarding the obligatory provider id.  I agree, but I

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

2016-03-07 Thread jenkins

See 

--
[...truncated 28679 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.786s]
[INFO] Apache CloudStack . SUCCESS [2.154s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.778s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [18.936s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:31.112s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.104s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [53.858s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.103s]
[INFO] Apache CloudStack API . SUCCESS [1:52.384s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.853s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [29.802s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.090s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.182s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [25.917s]
[INFO] Apache CloudStack Core  SUCCESS [1:21.783s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.547s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.374s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.502s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:08.410s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [41.739s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [26.018s]
[INFO] Apache CloudStack Server .. SUCCESS [4:14.211s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.737s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.814s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:21.037s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.069s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.432s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.208s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.311s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [30.032s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.407s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [22.381s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [21.089s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [36.396s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.736s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [7.404s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.961s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [28.227s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.664s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[37.201s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.479s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.154s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [14.699s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[17.089s]
[INFO] Apache

Re: [PROPOSAL] Minimum Viable CI Integration

2016-03-07 Thread Remi Bergsma

Hi Will,

This is the main problem: there’s no one except Apache Infra with access to the 
Github CloudStack repo. Even committers have to push to Apache git, which is 
mirrored to Github. We can’t close a PR, set a label, change a title or 
whatever basic operation. You can ask them for a token. When I (as the release 
manager) asked for any more permission than an anonymous user has it was kindly 
refused. I really hope you’ll have more luck but I wouldn’t count on it.



Regards,
Remi


On 07/03/16 19:10, "williamstev...@gmail.com on behalf of Will Stevens" 
 wrote:

>The main thing we have to sort out with this type of integration (as it is
>today) is the distribution of access tokens with the correct permissions on
>the apache/cloudstack github repo.  The required permissions are very
>limited, but I don't know if we have access to create new tokens.  If we
>don't then I will have to develop an application integration workaround to
>make it easier for the people with access to the apache/cloudstack repo to
>give the people running CI integrations access to update statuses (like the
>current travis integration).





>If you have questions or feedback, please don't be shy.
>
>*Will STEVENS*
>Lead Developer
>
>*CloudOps* *| *Cloud Solutions Experts
>420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
>w cloudops.com *|* tw @CloudOps_
>
>On Mon, Mar 7, 2016 at 12:36 PM, Bharat Kumar 
>wrote:
>
>> Hi guys,
>>
>> I am also working on the similar reporting problem, here is what i did
>>
>> link to the report https://github.com/bvbharatk/cloud-stack/pull/1
>>
>> I am thinking this is good enough for now, I want to start posting the
>> results on each pr as shown in the above link.
>> please give me your comments or suggestions.
>>
>> Thanks,
>> Bharat
>> On 05-Mar-2016, at 7:02 PM, Will Stevens  wstev...@cloudops.com>> wrote:
>>
>> Daan
>>
>> Regarding the obligatory provider id.  I agree, but I am still trying to
>> figure out the details.  Creating distinct runs that have their own status
>> is done by setting the 'context'.  I think we would need to have two pieces
>> to this.  A provider id and an environment id.
>>
>> So for example.  Lets assume that my provider id is 'CloudOps' and I have
>> two different environments, one for 'KVM' and one for 'Xen' (for example).
>> I would then the tool would produce the following two independent CI
>> statuses.
>> 'CloudOps - KVM' : with a basic description of the environment.
>> 'CloudOps - Xen' : again with a basic description of the env.
>> ... and so on ...
>>
>> I am still sorting out the details here as well as making it easy for us to
>> integrate this into the apache/cloudstack repo with the access we currently
>> have.  Adding this is 'no biggy' for me because I am building this tool as
>> we speak, and trying to tailor it to our (ACS) needs, so this type of
>> feedback is perfect as it allows me to adapt the tool before I get too
>> deep.
>>
>> *Will STEVENS*
>> Lead Developer
>>
>> *CloudOps* *| *Cloud Solutions Experts
>> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
>> w cloudops.com *|* tw @CloudOps_
>>
>> On Sat, Mar 5, 2016 at 4:17 AM, Daan Hoogland > >
>> wrote:
>>
>> Will
>>
>> Gret work, especially the thing you are showing in link [4], I would like
>> to make an enhancement request and that is a obligatory provider id. Only
>> if it is no biggy for you!
>> Several people may decide to do a XVM on ChildrensOS for instance and so we
>> may be aware of an obscurity that is different. If one fails and the other
>> succeeds it is easily identified.
>>
>> Ilya,
>>
>> I have been playing with go and it is a very nice language for such a
>> simple script, though it wasn't exactly designed for it. So don't read my
>> comment/question as an objection. But we do have
>> bash,python,c#,java,javascript,xslt,sql at least. That is not counting the
>> build system and I am sure the hyperv has some extra windows specific
>> stuff.
>> To me it is inherent to the nature of across platform orchestration and
>> provisioning system so it is fine. It is something to consider. On the
>> other hand when bringing in new tools we don't make the choice so I am
>> ranting, I guess.
>>
>>
>>
>> On Sat, Mar 5, 2016 at 7:38 AM, ilya  ilya.mailing.li...@gmail.com>> wrote:
>>
>> I see where Daan is coming from :)  I thought this would be 4th, not
>> exactly 7ths.
>>
>> I'm not against golang by any means (if anything - its my next "go" to
>> language these days).
>>
>> Things to consider:
>>
>> Would notify-pr support proxy? I've been thinking on ways of
>> contributing test runs, there would have to be few things i'd need to do.
>>
>> 1) massage the log content - such that no environment details are
>> exposed, i can probably handle this with sed/awk..
>>

[GitHub] cloudstack pull request: Addresses CLOUDSTACK-9300 where the MySQL...

2016-03-07 Thread dmabry

Github user dmabry commented on the pull request:

https://github.com/apache/cloudstack/pull/1428#issuecomment-193407327
  
@remibergsma , We loaded up the management server with this patch and it 
appears to work just fine on 4.7.1 with db.ha.enable=false and db.cloud.slaves 
left blank.  See logs below:

```
2016-03-07 13:09:47,721 INFO  [c.c.u.d.T.Transaction] 
(localhost-startStop-1:null) (logid:) Is Data Base High Availiability enabled? 
Ans : false
2016-03-07 13:09:47,867 DEBUG [c.c.u.d.ConnectionConcierge] 
(localhost-startStop-1:null) (logid:) Registering a database connection for 
LockMaster1
2016-03-07 13:09:47,867 INFO  [c.c.u.d.Merovingian2] 
(localhost-startStop-1:null) (logid:) Cleaning up locks for 233845178587501
2016-03-07 13:09:47,873 INFO  [c.c.u.d.Merovingian2] 
(localhost-startStop-1:null) (logid:) Released 0 locks for 233845178587501
2016-03-07 13:09:47,897 INFO  [o.a.c.s.l.CloudStackExtendedLifeCycle] 
(localhost-startStop-1:null) (logid:) Running system integrity checker 
com.cloud.upgrade.DatabaseUpgradeChecker@6fd77398
2016-03-07 13:09:47,898 INFO  [c.c.u.DatabaseUpgradeChecker] 
(localhost-startStop-1:null) (logid:) Grabbing lock to check for database 
upgrade.
2016-03-07 13:09:47,942 DEBUG [c.c.u.d.VersionDaoImpl] 
(localhost-startStop-1:null) (logid:) Checking to see if the database is at a 
version before it was the version table is created
2016-03-07 13:09:47,960 INFO  [c.c.u.DatabaseUpgradeChecker] 
(localhost-startStop-1:null) (logid:) DB version = 4.7.1 Code Version = 4.7.1
2016-03-07 13:09:47,961 INFO  [c.c.u.DatabaseUpgradeChecker] 
(localhost-startStop-1:null) (logid:) DB version and code version matches so no 
upgrade needed.
2016-03-07 13:09:47,961 INFO  [o.a.c.s.l.CloudStackExtendedLifeCycle] 
(localhost-startStop-1:null) (logid:) Configuring CloudStack Components
2016-03-07 13:09:47,963 INFO  [o.a.c.s.l.CloudStackExtendedLifeCycle] 
(localhost-startStop-1:null) (logid:) Done Configuring CloudStack Components
```


---
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: Addresses CLOUDSTACK-9300 where the MySQL...

2016-03-07 Thread kiwiflyer

Github user kiwiflyer commented on the pull request:

https://github.com/apache/cloudstack/pull/1428#issuecomment-193404245

Hi Remi,

Yes, we tested it with HA disabled. David is going to upload the logs for
reference.

The mysql-connector is also referenced in the catalina.properties
common.loader for tomcat.

-Si

On Mon, Mar 7, 2016, 10:29 AM Remi Bergsma  wrote:

> Hi @kiwiflyer , did you test this without
> MySQL HA as well? I doubt it will work without mysql-connector-java.
> Also, this most likely also needs to be fixed on other distributions?
>
> â
> 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.
---

[GitHub] cloudstack pull request: CLOUDSTACK-9285 - Agent throws an excepti...

2016-03-07 Thread remibergsma

Github user remibergsma commented on the pull request:

https://github.com/apache/cloudstack/pull/1429#issuecomment-193384072
  
@kiwiflyer Thanks, have seen this as well and will try your fix when I have 
some time :-)


---
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: Addresses CLOUDSTACK-9300 where the MySQL...

2016-03-07 Thread remibergsma

Github user remibergsma commented on the pull request:

https://github.com/apache/cloudstack/pull/1428#issuecomment-193383891
  
Hi @kiwiflyer, did you test this without MySQL HA as well? I doubt it will 
work without `mysql-connector-java`. Also, this most likely also needs to be 
fixed on other distributions?


---
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 #3409

2016-03-07 Thread jenkins

See 

--
[...truncated 28691 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.711s]
[INFO] Apache CloudStack . SUCCESS [2.059s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.769s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [18.619s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:30.237s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.103s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [53.637s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.821s]
[INFO] Apache CloudStack API . SUCCESS [1:48.614s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.498s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [30.047s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.084s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.246s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [25.391s]
[INFO] Apache CloudStack Core  SUCCESS [1:22.021s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.399s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.457s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.244s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:07.311s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.679s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [26.021s]
[INFO] Apache CloudStack Server .. SUCCESS [4:17.218s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.329s]
[INFO] Apache CloudStack Usage Server  SUCCESS [45.748s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:22.499s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.067s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.457s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.431s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [49.006s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [30.391s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.465s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [25.921s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [23.264s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.191s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.456s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [7.417s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.969s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.637s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.424s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[36.160s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.389s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.158s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [16.836s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[17.009s]
[INFO] Apache

Re: [PROPOSAL] Minimum Viable CI Integration

2016-03-07 Thread Will Stevens

Nice work Bharat.  I think the combination of our two tools gives us a
pretty complete solution to the problem.

I have renamed my project from notify_pr to upr, short for UpdatePR.

I have made an initial release available here: https://github.com/swill/upr

I did a complete rewrite of the tool over the weekend, so I currently only
support the updating of the 'Status' of a pull request.  I plan to add the
ability to programmatically add comments again, but I am going to get the
object storage integrations in place before I release the comments feature
again.  I may release the ability to just upload a title and body initially
and then build out the object store integration, but we will see.

The motivation for the complete rewrite was to make it easier to handle
different commands and the commands associated with each command.  It uses
the same mechanism as Docker, Hugo and a bunch of other major open source
softwares.

The main thing we have to sort out with this type of integration (as it is
today) is the distribution of access tokens with the correct permissions on
the apache/cloudstack github repo.  The required permissions are very
limited, but I don't know if we have access to create new tokens.  If we
don't then I will have to develop an application integration workaround to
make it easier for the people with access to the apache/cloudstack repo to
give the people running CI integrations access to update statuses (like the
current travis integration).

If you have questions or feedback, please don't be shy.

*Will STEVENS*
Lead Developer

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

On Mon, Mar 7, 2016 at 12:36 PM, Bharat Kumar 
wrote:

> Hi guys,
>
> I am also working on the similar reporting problem, here is what i did
>
> link to the report https://github.com/bvbharatk/cloud-stack/pull/1
>
> I am thinking this is good enough for now, I want to start posting the
> results on each pr as shown in the above link.
> please give me your comments or suggestions.
>
> Thanks,
> Bharat
> On 05-Mar-2016, at 7:02 PM, Will Stevens > wrote:
>
> Daan
>
> Regarding the obligatory provider id.  I agree, but I am still trying to
> figure out the details.  Creating distinct runs that have their own status
> is done by setting the 'context'.  I think we would need to have two pieces
> to this.  A provider id and an environment id.
>
> So for example.  Lets assume that my provider id is 'CloudOps' and I have
> two different environments, one for 'KVM' and one for 'Xen' (for example).
> I would then the tool would produce the following two independent CI
> statuses.
> 'CloudOps - KVM' : with a basic description of the environment.
> 'CloudOps - Xen' : again with a basic description of the env.
> ... and so on ...
>
> I am still sorting out the details here as well as making it easy for us to
> integrate this into the apache/cloudstack repo with the access we currently
> have.  Adding this is 'no biggy' for me because I am building this tool as
> we speak, and trying to tailor it to our (ACS) needs, so this type of
> feedback is perfect as it allows me to adapt the tool before I get too
> deep.
>
> *Will STEVENS*
> Lead Developer
>
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
>
> On Sat, Mar 5, 2016 at 4:17 AM, Daan Hoogland  >
> wrote:
>
> Will
>
> Gret work, especially the thing you are showing in link [4], I would like
> to make an enhancement request and that is a obligatory provider id. Only
> if it is no biggy for you!
> Several people may decide to do a XVM on ChildrensOS for instance and so we
> may be aware of an obscurity that is different. If one fails and the other
> succeeds it is easily identified.
>
> Ilya,
>
> I have been playing with go and it is a very nice language for such a
> simple script, though it wasn't exactly designed for it. So don't read my
> comment/question as an objection. But we do have
> bash,python,c#,java,javascript,xslt,sql at least. That is not counting the
> build system and I am sure the hyperv has some extra windows specific
> stuff.
> To me it is inherent to the nature of across platform orchestration and
> provisioning system so it is fine. It is something to consider. On the
> other hand when bringing in new tools we don't make the choice so I am
> ranting, I guess.
>
>
>
> On Sat, Mar 5, 2016 at 7:38 AM, ilya > wrote:
>
> I see where Daan is coming from :)  I thought this would be 4th, not
> exactly 7ths.
>
> I'm not against golang by any means (if anything - its my next "go" to
> language these days).
>
> Things to consider:
>
> Would notify-pr support proxy? I've been thinking on ways of
> contributing

Re: [PROPOSAL] Minimum Viable CI Integration

2016-03-07 Thread Bharat Kumar

Hi guys,

I am also working on the similar reporting problem, here is what i did

link to the report https://github.com/bvbharatk/cloud-stack/pull/1

I am thinking this is good enough for now, I want to start posting the results 
on each pr as shown in the above link.
please give me your comments or suggestions.

Thanks,
Bharat
On 05-Mar-2016, at 7:02 PM, Will Stevens 
> wrote:

Daan

Regarding the obligatory provider id.  I agree, but I am still trying to
figure out the details.  Creating distinct runs that have their own status
is done by setting the 'context'.  I think we would need to have two pieces
to this.  A provider id and an environment id.

So for example.  Lets assume that my provider id is 'CloudOps' and I have
two different environments, one for 'KVM' and one for 'Xen' (for example).
I would then the tool would produce the following two independent CI
statuses.
'CloudOps - KVM' : with a basic description of the environment.
'CloudOps - Xen' : again with a basic description of the env.
... and so on ...

I am still sorting out the details here as well as making it easy for us to
integrate this into the apache/cloudstack repo with the access we currently
have.  Adding this is 'no biggy' for me because I am building this tool as
we speak, and trying to tailor it to our (ACS) needs, so this type of
feedback is perfect as it allows me to adapt the tool before I get too deep.

*Will STEVENS*
Lead Developer

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

On Sat, Mar 5, 2016 at 4:17 AM, Daan Hoogland 
>
wrote:

Will

Gret work, especially the thing you are showing in link [4], I would like
to make an enhancement request and that is a obligatory provider id. Only
if it is no biggy for you!
Several people may decide to do a XVM on ChildrensOS for instance and so we
may be aware of an obscurity that is different. If one fails and the other
succeeds it is easily identified.

Ilya,

I have been playing with go and it is a very nice language for such a
simple script, though it wasn't exactly designed for it. So don't read my
comment/question as an objection. But we do have
bash,python,c#,java,javascript,xslt,sql at least. That is not counting the
build system and I am sure the hyperv has some extra windows specific
stuff.
To me it is inherent to the nature of across platform orchestration and
provisioning system so it is fine. It is something to consider. On the
other hand when bringing in new tools we don't make the choice so I am
ranting, I guess.

On Sat, Mar 5, 2016 at 7:38 AM, ilya 
> wrote:

I see where Daan is coming from :)  I thought this would be 4th, not
exactly 7ths.

I'm not against golang by any means (if anything - its my next "go" to
language these days).

Things to consider:

Would notify-pr support proxy? I've been thinking on ways of
contributing test runs, there would have to be few things i'd need to do.

1) massage the log content - such that no environment details are
exposed, i can probably handle this with sed/awk..

2) i'm behind multiple firewalls with no internet access. however, some
lab environments might have a proxy, so it would be nice to have a
support for it.

Thanks
ilya

On 3/4/16 6:56 AM, Will Stevens wrote:
Yes, I have most of it already built and will be releasing it later
today
or over the weekend.  The reason I chose Golang is because it can be
cross
compiled to be run on any system and distributed as a single binary
with
no
dependencies.  This means that no one will have to worry about building
it
or having to change their environment at all in order to use it.  I am
trying to lower the barrier to entry and make it as easy as possible
for
people to contribute back their CI execution details.

*Will STEVENS*
Lead Developer

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

On Fri, Mar 4, 2016 at 8:53 AM, Daan Hoogland 

wrote:

Will, Do you have an implementation of notify-pr? I am asking as you
specify it will be implemented in golang which seems odd. It is not
amongst
the 7 or so languages already in use.

On Fri, Mar 4, 2016 at 1:54 AM, Will Stevens <
williamstev...@gmail.com>
wrote:

Hey Everyone,
As I am sure most of you are aware, I have been focusing a lot on
ways
to
get CI integrated back into the community.

Today I build a little POC to validate some ideas and get a feel for
a
potential approach for getting CI integrated into the Github pull
request
workflow.

There are multiple individuals/companies focusing on CI right now
(which
is a good thing), but there has not really been much discussion
(that I

[GitHub] cloudstack pull request: CLOUDSTACK-9287 - Fix unique mac address ...

2016-03-07 Thread wilderrodrigues

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

https://github.com/apache/cloudstack/pull/1413#discussion_r55236035
  
--- Diff: server/src/com/cloud/network/element/VpcVirtualRouterElement.java 
---
@@ -559,9 +559,16 @@ public boolean applyACLItemsToPrivateGw(final 
PrivateGateway gateway, final List
 final DataCenterVO dcVO = 
_dcDao.findById(network.getDataCenterId());
 final NetworkTopology networkTopology = 
networkTopologyContext.retrieveNetworkTopology(dcVO);
 
+final Network privateNetwork = 
_networkModel.getNetwork(gateway.getNetworkId());
+
 boolean result = true;
 for (final DomainRouterVO domainRouterVO : routers) {
-result = result && networkTopology.applyNetworkACLs(network, 
rules, domainRouterVO, isPrivateGateway);
+final NicProfile nicProfile = 
_networkModel.getNicProfile(domainRouterVO, privateNetwork.getId(), null);
+if (nicProfile != null) {
+result = result && 
networkTopology.applyNetworkACLs(network, rules, domainRouterVO, 
isPrivateGateway);
--- End diff --

No worries, @GabrielBrascher 

:)


---
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] Request for comments: Out-of-band Management for CloudStack (new feature)

2016-03-07 Thread Rohit Yadav

Hi Hari,


[ShapeBlue]
Rohit Yadav
Software Architect  ,   ShapeBlue


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

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

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


[cid:imagee92091.png@0ce19fb7.479fbee5]


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 07-Mar-2016, at 10:51 AM, Harikrishna Patnala 
> 
wrote:

I have a little concern here regarding the baremetal deployment where we use 
ipmi as power management interface. Are you going to use the existing ipmi util 
we have or do you have a separate solution for this.

As noted in the FS, the feature is agnostic of a specific out-of-band 
technology and will by default ship with a ipmitool based driver to support 
hosts with IPMI 2.0 enabled interface.

The baremetal plugin uses Python based afaik, while the out-of-band ipmitool 
driver will be a Java wrapper around â€˜ipmitoolâ€™. The baremetal plugin 
maintainer in future can refactor their plugin to use the out-of-band 
management subsystem to manage machines without using a specific/hard-coded 
driver (ipmi util etc).

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-9270: UI alignment gone bad in...

2016-03-07 Thread glennwagner

Github user glennwagner commented on the pull request:

https://github.com/apache/cloudstack/pull/1398#issuecomment-193325954
  
LGTM no issues


---
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 #3408

2016-03-07 Thread jenkins

See 

--
[...truncated 28679 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.756s]
[INFO] Apache CloudStack . SUCCESS [2.103s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.859s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.166s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:30.820s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.109s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [52.668s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.618s]
[INFO] Apache CloudStack API . SUCCESS [1:50.137s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.382s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [30.110s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.089s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.136s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.966s]
[INFO] Apache CloudStack Core  SUCCESS [1:20.939s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.658s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.742s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.593s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:08.509s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [41.243s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.589s]
[INFO] Apache CloudStack Server .. SUCCESS [4:11.997s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.193s]
[INFO] Apache CloudStack Usage Server  SUCCESS [43.552s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:22.802s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.082s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.431s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [55.130s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.508s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [30.011s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.060s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [25.839s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [20.542s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.190s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.689s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [8.197s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.979s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.885s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.762s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[38.078s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.424s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.371s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [15.822s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[17.278s]
[INFO] Apache

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

2016-03-07 Thread jenkins

See 

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

[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @ 
cloud-quickcloud ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ cloud-quickcloud 
---
[INFO] 
[INFO] <<< cobertura-maven-plugin:2.6:cobertura (default-cli) @ 
cloud-quickcloud <<<
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:cobertura (default-cli) @ 
cloud-quickcloud ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache CloudStack Developer Tools - Checkstyle Configuration  SUCCESS 
[2.786s]
[INFO] Apache CloudStack . SUCCESS [3.119s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [1.067s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.612s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:30.603s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.119s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [52.946s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.240s]
[INFO] Apache CloudStack API . SUCCESS [1:49.050s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.089s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [31.546s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.097s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [27.909s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.384s]
[INFO] Apache CloudStack Core  SUCCESS [1:22.821s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.465s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.266s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.655s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:08.431s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [41.492s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.559s]
[INFO] Apache CloudStack Server .. SUCCESS [4:12.854s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.121s]
[INFO] Apache CloudStack Usage Server  SUCCESS [45.175s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:23.029s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.074s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.431s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.094s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [47.952s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [30.262s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [25.773s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [26.331s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [20.707s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.243s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.680s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [7.965s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.996s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.537s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.403s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[35.898s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.579s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.376s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [15.762s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[17.080s]
[INFO] Apache

[GitHub] cloudstack pull request: CLOUDSTACK-9285 - Agent throws an excepti...

2016-03-07 Thread DaanHoogland

Github user DaanHoogland commented on the pull request:

https://github.com/apache/cloudstack/pull/1429#issuecomment-193220496
  
@kiwiflyer Simon, I'm a nag but can you recreate this PR against 4.7? We've 
confirmed it on 4.7 s well. I think it was introduced in 4.6 even but that 
release is intermediate in our release process change so we might want to skip 
it.


---
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-8611. CS waits indefinitely fo...

2016-03-07 Thread GabrielBrascher

Github user GabrielBrascher commented on the pull request:

https://github.com/apache/cloudstack/pull/561#issuecomment-193216137
  
That's fair enough @DaanHoogland, I will see what I can do for this PR.


---
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] Request for comments: Out-of-band Management for CloudStack (new feature)

2016-03-07 Thread Rohit Yadav

Hi Ahmad,

Thanks. Good to see you again on the ML, after a long break.

The IPMI simulation is not tied with the ACS simulator (plugin) but it’s a 
separate Python based tool (also an importable library). Since it’s Python 
based, it would be difficult to tied it with the simulator plugin. Instead of 
using ipmisim or the default ipmitool driver that ships with this feature, the 
simulator plugin can have a separate dummy driver implementation.

The Marvin test will be Python based, so it will be easiest to tie ipmisim with 
it (no external setup needed for example); while to test this feature manually 
one can easily install ipmisim and run it separately.


[ShapeBlue]
Rohit Yadav
Software Architect  ,   ShapeBlue


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

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

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


[cid:image783119.png@1a865698.4eafe4a5]


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 05-Mar-2016, at 7:54 AM, Ahmad Emneina 
> wrote:

qq: is the ipmi simulation tied, or planned
to be tied to 'the simulator'? It would be interesting to see those tied
together. regardless... awesome work.

Regards.

Find out more about ShapeBlue and our range of CloudStack related services:
IaaS Cloud Design & Build | 
CSForge – rapid IaaS deployment framework
CloudStack Consulting | 
CloudStack Software 
Engineering
CloudStack Infrastructure 
Support | CloudStack 
Bootcamp Training Courses

Re: [DISCUSS] Request for comments: Out-of-band Management for CloudStack (new feature)

2016-03-07 Thread Harikrishna Patnala

Hi Rohit,

Thanks for the proposal and seems like a descent feature to have.

I have a little concern here regarding the baremetal deployment where we use 
ipmi as power management interface. Are you going to use the existing ipmi util 
we have or do you have a separate solution for this. If it is the latter case 
then you may need to consolidate everything to have one solution to avoid 
redundancy.

Regards,
Harikrishna


On 07-Mar-2016, at 2:51 pm, Rohit Yadav  wrote:

> Hi Ilya,
>
> Thanks for the suggestions.
>
> In the UI, we can easily have a warning statement on the pop up box if host 
> maintenance is enabled. We can also add mechanisms (for example specific APIs 
> or zone/cluster level settings) to allow admins to disable/enable the feature 
> at zone and cluster level without cascading it to the host enabled setting. 
> Will update the FS to reflect these additions.
>
> Regards.
>
>> On 05-Mar-2016, at 7:11 AM, ilya  wrote:
>>
>> Rohit,
>>
>> Great job!
>>
>> Not certain if this was mentioned, but premise behind IPMI integration
>> was partially driven by HA and being able to "fence" the host in
>> question to avoid split brain scenario - as well as other issues when
>> hypervisors malfunction.
>>
>> With that said, Will brings up a good point, what can we offer to avoid
>> accidental power down - while host is functional. I see plenty of
>> curious cloudstack admins who identify a function of a button by
>> pressing on it and saying "lets see what happens". Better yet, some
>> learn on the job on production environments.
>>
>> Do we give the end user a warning of any kind? If possible, i would
>> suggest we give a one line warning - something like "The host is not in
>> Maintenance Mode, proceed at your own risk!" or something to that effect.
>>
>> Obviously this would only be CloudStack UI safeguard and no such warning
>> would be shown when you use APIs directly.
>>
>> Lastly, please consider disable IPMI for Cluster and Zone level, i dont
>> believe we need it for pod. Please dont cascade over every host ipmi
>> object and change their state, instead, have a separate db entry (or
>> else) that tracks this selection for cluster or zone.
>>
>> It could be as simple as configuration setting for zone or cluster.
>>
>> thanks
>> ilya
>>
>>
>> On 3/4/16 1:20 AM, Rohit Yadav wrote:
>>>
>>>
>>> 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 03-Mar-2016, at 12:58 PM, Will Stevens > wrote:

 Maybe I am not understanding something here.

 Does this control the power cycle of the management server(s) or the
 hypervisor hosts?  The wording is throwing me off.
>>>
>>> Fixed. The feature applies for hypervisor hosts only, not management
>>> server hosts (unless of course, mgmt server host is hypervisor host as
>>> well for example running mgmt server + kvm agnet on a KVM host).
>>>
 I am guessing it is for managing the hypervisor hosts. If this is the
 case,
 does it also handle the "maintenance mode" for the host as well?
>>>
>>> Maintenance mode is a hypervisor semantic, this is not related to the
>>> out-of-band management interface (the BMC, such as iLO, iDRAC) available
>>> on the hypervisor host.
>>>
>>> Even when you enable/disable maintenance mode, you can use a tool like
>>> ‘ipmitool’ to do execute a power management operation such as
>>> on/off/reset etc, so you should be able to perform the same using this
>>> feature.

Build failed in Jenkins: build-systemvm64-master #770

2016-03-07 Thread jenkins

See 

--
[...truncated 3356 lines...]
  
Hit http://http.debian.net wheezy-backports/main Translation-en/DiffIndex

100% [Sources 25.4 MB]
  
100% [Working]
  
100% [Packages 1,795 kB]

100% [Working]
  
100% [Translation-en 1,219 kB]
  
100% [Working]
  
100% [Packages 28.5 MB]
100% [Packages 28.5 MB]
   
100% [Working]
  
100% [Packages 28.5 MB]
100% [Packages 28.5 MB]
   
100% [Working]
  
100% [Translation-en 18.5 MB]
100% [Translation-en 18.5 MB]
 
100% [Working]
  
100% [Sources 16.0 kB]
  
100% [Working]
  
Fetched 8,246 B in 3s (2,138 B/s)

Reading package lists... 0%

Reading package lists... 0%

Reading package lists... 1%

Reading package lists... 26%

Reading package lists... 31%

Reading package lists... 31%

Reading package lists... 50%

Reading package lists... 64%

Reading package lists... 64%

Reading package lists... 84%

Reading package lists... 84%

Reading package lists... 86%

Reading package lists... 86%

Reading package lists... 86%

Reading package lists... 88%

Reading package lists... 88%

Reading package lists... 90%

Reading package lists... 90%

Reading package lists... 90%

Reading package lists... 90%

Reading package lists... 90%

Reading package lists... 90%

Reading package lists... 90%

Reading package lists... 90%

Reading package lists... 93%

Reading package lists... 93%

Reading package lists... 97%

Reading package lists... 97%

Reading package lists... 99%

Reading package lists... 99%

Reading package lists... Done

+ apt-get -y --force-yes upgrade

Reading package lists... 0%

Reading package lists... 100%

Reading package lists... Done


Building dependency tree... 0%

Building dependency tree... 0%

Building dependency tree... 50%

Building dependency tree... 50%

Building dependency tree   


Reading state information... 0%

Reading state information... 0%

Reading state information... Done

The following packages have been kept back:
  openswan
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
+ '[' amd64 == amd64 ']'
+ wget http://people.apache.org/~rajeshbattala/hv-kvp-daemon_3.1_amd64.deb
--2016-03-07 09:34:03--  
http://people.apache.org/~rajeshbattala/hv-kvp-daemon_3.1_amd64.deb
Resolving people.apache.org (people.apache.org)... 163.172.16.173, 
2001:bc8:2142:100::
Connecting to people.apache.org (people.apache.org)|163.172.16.173|:80... 
connected.
HTTP request sent, awaiting response... 404 Not Found
2016-03-07 09:34:04 ERROR 404: Not Found.

ERROR: exit code 8
Error executing command ./install_systemvm_packages.sh : Exitcode was not what 
we expected
Exitcode was not what we expected
+ on_exit
+ (( i=5-1  ))
+ (( i>=0  ))
+ sleep 2
+ log DEBUG 'on_exit: veewee_destroy'
+ local level=DEBUG
+ shift
+ [[ 1 != \1 ]]
+ local code=
++ date '+%F %T'
+ local 'line=[2016-03-07 09:34:06] DEBUG: on_exit: veewee_destroy'
+ '[' -t 2 ']'
+ echo '[2016-03-07 09:34:06] DEBUG: on_exit: veewee_destroy'
[2016-03-07 09:34:06] DEBUG: on_exit: veewee_destroy
+ eval veewee_destroy
++ veewee_destroy
++ log INFO 'destroying existing veewee image, if any'
++ local level=INFO
++ shift
++ [[ 1 != \1 ]]
++ local code=
+++ date '+%F %T'
++ local 'line=[2016-03-07 09:34:06] INFO: destroying existing veewee image, if 
any'
++ '[' -t 2 ']'
++ echo '[2016-03-07 09:34:06] INFO: destroying existing veewee image, if any'
[2016-03-07 09:34:06] INFO: destroying existing veewee image, if any
++ set +e
++ bundle exec veewee vbox destroy systemvm64template-master-4.6.0
Shutting down vm systemvm64template-master-4.6.0
VBoxManage unregistervm  "systemvm64template-master-4.6.0" --delete
Deleting vm systemvm64template-master-4.6.0
++ set -e
+ (( i--  ))
+ (( i>=0  ))
+ sleep 2
+ log DEBUG 'on_exit: rm -f cloud_scripts_shar_archive.sh'
+ local level=DEBUG
+ shift
+ [[ 1 != \1 ]]
+ local code=
++ date '+%F %T'
+ local 'line=[2016-03-07 09:34:13] DEBUG: on_exit: rm -f 
cloud_scripts_shar_archive.sh'
+ '[' -t 2 ']'
+ echo '[2016-03-07 09:34:13] DEBUG: on_exit: rm -f 
cloud_scripts_shar_archive.sh'
[2016-03-07 09:34:13] DEBUG: on_exit: rm -f cloud_scripts_shar_archive.sh
+ eval rm -f cloud_scripts_shar_archive.sh
++ rm -f cloud_scripts_shar_archive.sh
+ (( i--  ))
+ (( i>=0  ))
+ sleep 2
+ log DEBUG 'on_exit: rm -rf definitions/systemvm64template-master-4.6.0'
+ local level=DEBUG
+ shift
+ [[ 1 != \1 ]]
+ local code=
++ date '+%F %T'
+ local 'line=[2016-03-07 09:34:15] DEBUG: on_exit: rm -rf 
definitions/systemvm64template-master-4.6.0'
+ '[' -t 2 ']'
+ echo '[2016-03-07 09:34:15] DEBUG: on_exit: rm -rf 
definitions/systemvm64template-master-4.6.0'
[2016-03-07 09:34:15] DEBUG: on_exit: rm -rf

Re: [DISCUSS] Request for comments: Out-of-band Management for CloudStack (new feature)

2016-03-07 Thread Rohit Yadav

Hi Ilya,

Thanks for the suggestions.

In the UI, we can easily have a warning statement on the pop up box if host 
maintenance is enabled. We can also add mechanisms (for example specific APIs 
or zone/cluster level settings) to allow admins to disable/enable the feature 
at zone and cluster level without cascading it to the host enabled setting. 
Will update the FS to reflect these additions.

Regards.

> On 05-Mar-2016, at 7:11 AM, ilya  wrote:
>
> Rohit,
>
> Great job!
>
> Not certain if this was mentioned, but premise behind IPMI integration
> was partially driven by HA and being able to "fence" the host in
> question to avoid split brain scenario - as well as other issues when
> hypervisors malfunction.
>
> With that said, Will brings up a good point, what can we offer to avoid
> accidental power down - while host is functional. I see plenty of
> curious cloudstack admins who identify a function of a button by
> pressing on it and saying "lets see what happens". Better yet, some
> learn on the job on production environments.
>
> Do we give the end user a warning of any kind? If possible, i would
> suggest we give a one line warning - something like "The host is not in
> Maintenance Mode, proceed at your own risk!" or something to that effect.
>
> Obviously this would only be CloudStack UI safeguard and no such warning
> would be shown when you use APIs directly.
>
> Lastly, please consider disable IPMI for Cluster and Zone level, i dont
> believe we need it for pod. Please dont cascade over every host ipmi
> object and change their state, instead, have a separate db entry (or
> else) that tracks this selection for cluster or zone.
>
> It could be as simple as configuration setting for zone or cluster.
>
> thanks
> ilya
>
>
> On 3/4/16 1:20 AM, Rohit Yadav wrote:
>>
>>
>> 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 03-Mar-2016, at 12:58 PM, Will Stevens >> > wrote:
>>>
>>> Maybe I am not understanding something here.
>>>
>>> Does this control the power cycle of the management server(s) or the
>>> hypervisor hosts?  The wording is throwing me off.
>>
>> Fixed. The feature applies for hypervisor hosts only, not management
>> server hosts (unless of course, mgmt server host is hypervisor host as
>> well for example running mgmt server + kvm agnet on a KVM host).
>>
>>> I am guessing it is for managing the hypervisor hosts. If this is the
>>> case,
>>> does it also handle the "maintenance mode" for the host as well?
>>
>> Maintenance mode is a hypervisor semantic, this is not related to the
>> out-of-band management interface (the BMC, such as iLO, iDRAC) available
>> on the hypervisor host.
>>
>> Even when you enable/disable maintenance mode, you can use a tool like
>> ‘ipmitool’ to do execute a power management operation such as
>> on/off/reset etc, so you should be able to perform the same using this
>> feature. Therefore, presently there is no such enforcement.
>>
>>> At least
>>> with XenServer, if you do a power cycle without putting the host into
>>> maintenance mode first, all the VRs will have to be restarted on that host
>>> once it is back up in order for their networking to work again.
>>
>> We can put in a rule to avoid executing any power operation when hosts
>> are put in maintenance mode, though some users may still want to be able
>> to execute power operations. Comments?
>>
>> Regards.
>>
>> Find out more about ShapeBlue and our range of CloudStack related services:
>> IaaS Cloud Design & Build
>>

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

2016-03-07 Thread jenkins

See 

--
[...truncated 28679 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.748s]
[INFO] Apache CloudStack . SUCCESS [2.062s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.792s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.418s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:30.109s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.104s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [54.036s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [28.478s]
[INFO] Apache CloudStack API . SUCCESS [1:49.170s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.223s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [29.899s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.089s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.192s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [25.004s]
[INFO] Apache CloudStack Core  SUCCESS [1:21.611s]
[INFO] Apache CloudStack Agents .. SUCCESS [35.641s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [37.831s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.184s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:07.096s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.418s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.582s]
[INFO] Apache CloudStack Server .. SUCCESS [4:14.883s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [36.656s]
[INFO] Apache CloudStack Usage Server  SUCCESS [45.715s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:20.903s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.066s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.427s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [53.777s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.428s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [29.991s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [25.739s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [31.013s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [21.075s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.860s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.810s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [8.265s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.986s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.939s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[24.098s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[37.622s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.370s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.434s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [15.033s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[17.375s]
[INFO] Apache

Re: Question on compatibility matrix

2016-03-07 Thread Rohit Yadav

Thanks Pierre-Luc, in that case anyone from Citrix has any idea?

On 05-Mar-2016, at 1:05 AM, Pierre-Luc Dion 
> wrote:

Hi Rohit,

I can't recall where that version specific come from for ACS 4.5 with VMware, I 
think it was from the CloudPlatform 4.5 release notes.
I never really tested  ACS with VMware so I cannot really comment on which 
version is required.

Anyone else would have an idea?

Thanks

On Fri, Mar 4, 2016 at 10:28 AM, Rohit Yadav 
> wrote:
Hi Pierre-Luc, (+dev@)

Hope you're doing great. I've a question around compatibility matrix and since 
you’ve been maintaining the docs I thought perhaps you may have an answer.

Refer: 
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.5.2/compat.html

I see that the VMware version supported is set to "5.0 update 3a". Any reason 
why we support only "3a" and not previous 5.0 updates such as update1 etc.? Or, 
maybe that was done because that specific version/patch was the latest 
available release at the time?

Appreciate if anyone can share if they are running VMware 5.0 with ACS 4.5.x. 
Thanks.

Regards.

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.

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: SystemVM cleanups

2016-03-07 Thread glennwagner

Github user glennwagner commented on the pull request:

https://github.com/apache/cloudstack/pull/1414#issuecomment-193156160
  
Had a look ta your changes, PR 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.
---

40 matches

Mail list logo