people.apache.org

[Sebastien Goasguen]

Not sure if you got that

——
Hi folks,
As we said back in November, we have now moved the people.apache.org DNS
entry to home.apache.org, the new home for your web stuff.

If you forgot to move over your old content, or if you need to perform
LDAP operations, you can still gain access to the old box by using it's
machine name, minotaur.apache.org. The minotaur box is scheduled to be
decommissioned within a few months, so act fast :)

We advise you to copy over any content you wish to still display at
people.apache.org.

Do note that the new box, home.apache.org, ONLY allows SFTP operations,
you do not have shell access to it.

With regards,
Daniel on behalf of the Apache Infrastructure Team.

[GitHub] cloudstack pull request: Improve ordering of fields of VPC router ...

[glennwagner]

Github user glennwagner commented on the pull request:

https://github.com/apache/cloudstack/pull/1422#issuecomment-193666093
  
Made Simple - LGTM - Can we look at making these Fields configurable? 


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

[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.717s]
[INFO] Apache CloudStack . SUCCESS [2.060s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.767s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [20.013s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:30.460s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.113s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [53.515s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.307s]
[INFO] Apache CloudStack API . SUCCESS [1:50.268s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [15.901s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [30.100s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.090s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.055s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.438s]
[INFO] Apache CloudStack Core  SUCCESS [1:22.313s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.553s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.630s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [13.987s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:08.351s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [41.386s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [26.318s]
[INFO] Apache CloudStack Server .. SUCCESS [4:15.078s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [36.393s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.179s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:23.861s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.073s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.462s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [53.740s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.443s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [31.560s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [27.260s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [22.549s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [20.649s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.855s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.653s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [7.498s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.979s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [27.694s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.695s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[37.850s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.793s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.729s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [16.042s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[17.422s]
[INFO] Apache Cloud

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

[jenkins]

See 

--
[...truncated 3386 lines...]
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]
  
100% [Sources 1,127 kB]
   
100% [Working]
  
100% [Packages 1,782 kB]

100% [Working]
  
100% [Packages 1,795 kB]

100% [Working]
  
100% [Translation-en 1,219 kB]
  
100% [Working]
  
Fetched 8,246 B in 3s (2,173 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... 51%

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

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-08 09:30:17--  
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-08 09:30:18 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-08 09:30:20] DEBUG: on_exit: veewee_destroy'
+ '[' -t 2 ']'
+ echo '[2016-03-08 09:30:20] DEBUG: on_exit: veewee_destroy'
[2016-03-08 09:30:20] 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-08 09:30:20] INFO: destroying existing veewee image, if 
any'
++ '[' -t 2 ']'
++ echo '[2016-03-08 09:30:20] INFO: destroying existing veewee image, if any'
[2016-03-08 09:30:20] 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-08 09:30:27] DEBUG: on_exit: rm -f 
cloud_scripts_shar_archive.sh'
+ '[' -t 2 ']'
+ echo '[2016-03-08 09:30:27] DEBUG: on_exit: rm -f 
cloud_scripts_shar_archive.sh'
[2016-03-08 09:30:27] 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-08 09:30:29] DEBUG: on_exit: rm -rf 
definitions/systemvm64template-master-4.6.0'
+ '[' -t 2 ']'
+ echo '[2016-03-08 09:30:29] DEBUG: on_exit: rm -rf 
definitions/systemvm64template-master-4.6.0'
[2016-03-08 09:30:29] DEBUG: on_exit: rm -rf 
definitions/systemvm64template-master-4.6.0
+ eval rm -rf definitions

Re: [PROPOSAL] Minimum Viable CI Integration

[Suresh Anaparti]

Ok Bharat. That sounds good.

Can you add the details like hardware requirements not satisfied, etc as you 
said in earlier email.

Thanks,
Suresh



On 08/03/16 12:21 pm, "Bharat Kumar"  wrote:

>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 
>>> mailto:gandikota.srini...@gmail.com>> 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 
>>> mailto: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 
>>> mailto: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 
>>> mailto:daan.hoogl...@gmail.com>>>
>>> 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 
>>> mailto:ilya.mai

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

[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.800s]
[INFO] Apache CloudStack . SUCCESS [2.079s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.762s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.417s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:31.893s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.101s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [54.123s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.032s]
[INFO] Apache CloudStack API . SUCCESS [1:49.345s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.324s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [30.809s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.090s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [27.981s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.699s]
[INFO] Apache CloudStack Core  SUCCESS [1:20.465s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.688s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [37.355s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [13.984s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:07.515s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [41.238s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.766s]
[INFO] Apache CloudStack Server .. SUCCESS [4:17.380s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [36.822s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.462s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:23.134s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.076s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.431s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.767s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.108s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [29.880s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [25.585s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [25.681s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [22.736s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.079s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.701s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [7.921s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.930s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.624s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.849s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[35.713s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.672s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.722s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [16.841s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.747s]
[INFO] Apache Cloud

Re: VR metadata unreachable from VPC tier

[Pierre-Luc Dion]

Hi nux,

Does the VM got is hostname and ip?  Would it be just the password set that
is not working?
On Feb 25, 2016 14:45, "Syed Mushtaq"  wrote:

> http://fpaste.org/329431/42948514/raw/
>
> On Thu, Feb 25, 2016 at 2:36 PM, Nux!  wrote:
>
> > Anywho, a VR reboot has not done anything. I continue to have the same
> > issue.
> > Here's the VR's iptables config, something is wrong with it, haven't
> found
> > what, once I flush the rules I can get to VRIP:8080
> > http://fpaste.org/329413/45642787/raw/
> >
> > Can you give your VR's ruleset, for comparison?
> >
> > --
> > Sent from the Delta quadrant using Borg technology!
> >
> > Nux!
> > www.nux.ro
> >
> > - Original Message -
> > > From: "Nux!" 
> > > To: dev@cloudstack.apache.org
> > > Sent: Thursday, 25 February, 2016 19:04:13
> > > Subject: Re: VR metadata unreachable from VPC tier
> >
> > > Thanks, I'll investigate some more.
> > >
> > > In the meanwhile I have tried to restart the VPC network, but nothing
> > happened
> > > when I clicked the restart button, the network is now listed with
> > "restart
> > > required Yes". What does that mean?
> > >
> > > --
> > > Sent from the Delta quadrant using Borg technology!
> > >
> > > Nux!
> > > www.nux.ro
> > >
> > > - Original Message -
> > >> From: "Syed Mushtaq" 
> > >> To: dev@cloudstack.apache.org
> > >> Sent: Thursday, 25 February, 2016 17:33:02
> > >> Subject: Re: VR metadata unreachable from VPC tier
> > >
> > >> It works in my local setup Nux. A VPC with one tier and a password
> > enabled
> > >> template. I am working on the master though. The flow to set password
> > on a
> > >> VM is the same for a normal VR and a VPC VR. The problem maybe that
> the
> > VPC
> > >> VR is not being sleected by the management server somehow. So there
> > must be
> > >> some problem with the VPC VR <=> CS management server.
> > >>
> > >> -Syed
> > >>
> > >>
> > >> On Thu, Feb 25, 2016 at 10:38 AM, Nux!  wrote:
> > >>
> > >>> Deploy new VM.
> > >>>
> > >>> --
> > >>> Sent from the Delta quadrant using Borg technology!
> > >>>
> > >>> Nux!
> > >>> www.nux.ro
> > >>>
> > >>> - Original Message -
> > >>> > From: "Syed Mushtaq" 
> > >>> > To: dev@cloudstack.apache.org
> > >>> > Sent: Thursday, 25 February, 2016 15:35:04
> > >>> > Subject: Re: VR metadata unreachable from VPC tier
> > >>>
> > >>> > I see thanks. So this happens when you create a new VM or when you
> > try to
> > >>> > reset password of an already existing VM?
> > >>> >
> > >>> > On Thu, Feb 25, 2016 at 9:49 AM, Nux!  wrote:
> > >>> >
> > >>> >> Hi,
> > >>> >>
> > >>> >> I am yet to restart the VR, will do this a bit later on to see if
> > the
> > >>> >> problems gets fixed.
> > >>> >>
> > >>> >> Syed, the VM is trying to get the root password from the VR, but
> it
> > >>> can't
> > >>> >> connect to it.
> > >>> >>
> > >>> >> --
> > >>> >> Sent from the Delta quadrant using Borg technology!
> > >>> >>
> > >>> >> Nux!
> > >>> >> www.nux.ro
> > >>> >>
> > >>> >> - Original Message -
> > >>> >> > From: "Syed Mushtaq" 
> > >>> >> > To: dev@cloudstack.apache.org
> > >>> >> > Sent: Thursday, 25 February, 2016 14:47:17
> > >>> >> > Subject: Re: VR metadata unreachable from VPC tier
> > >>> >>
> > >>> >> > Hi nux,
> > >>> >> >
> > >>> >> > Just so I understand, what is the metadata that VR sends to a
> VM?
> > >>> >> >
> > >>> >> > On Thu, Feb 25, 2016, 9:44 AM Pierre-Luc Dion <
> pd...@cloudops.com
> > >
> > >>> >> wrote:
> > >>> >> >
> > >>> >> >> When you have this issue, if you setup a Portforwarding for ssh
> > for
> > >>> the
> > >>> >> VM,
> > >>> >> >> does the PF rule work?
> > >>> >> >>
> > >>> >> >> We observed similar issue where VR does not apply or receive
> > configs
> > >>> >> pushed
> > >>> >> >> by the management-server. I haven't really start investigate
> > that but
> > >>> >> >> wondering if you have similar issue. and usually a restart of
> > the VR
> > >>> or
> > >>> >> >> reset of the VPC fixe the issue.
> > >>> >> >>
> > >>> >> >>
> > >>> >> >> PL
> > >>> >> >>
> > >>> >> >>
> > >>> >> >>
> > >>> >> >> On Thu, Feb 25, 2016 at 6:51 AM, Nux!  wrote:
> > >>> >> >>
> > >>> >> >> > Hi,
> > >>> >> >> >
> > >>> >> >> > Just a quick one, before I go on submitting a bug, apparently
> > my
> > >>> VMs
> > >>> >> >> > connected in a VPC tier ("allow" acl) cannot get the metadata
> > >>> password
> > >>> >> >> from
> > >>> >> >> > the VR.
> > >>> >> >> > It works from normal isolated networks.
> > >>> >> >> >
> > >>> >> >> > Tested on ACS 4.8, Xen & KVM.
> > >>> >> >> >
> > >>> >> >> > Has anyone seen this?
> > >>> >> >> >
> > >>> >> >> >
> > >>> >> >> > --
> > >>> >> >> > Sent from the Delta quadrant using Borg technology!
> > >>> >> >> >
> > >>> >> >> > Nux!
> > >>> >> >> > www.nux.ro
> >
>

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

[kiwiflyer]

Github user kiwiflyer commented on the pull request:

https://github.com/apache/cloudstack/pull/1430#issuecomment-193796033
  
@ustcweizhou 
So after looking at our issue and the one reported originally in 9285, I 
think they're two different issues. One related to initial connection on agent 
startup and our one, related to a re-connection event where the connection is 
terminated unexpectedly.


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

[ustcweizhou]

Github user ustcweizhou commented on the pull request:

https://github.com/apache/cloudstack/pull/1430#issuecomment-193813489
  
@kiwiflyer Simon, I agree with you. Besides your change,  we also need to 
fix similar issue in line 230/238.
Actually line 230 caused the issue described in the ticket.




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

[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.726s]
[INFO] Apache CloudStack . SUCCESS [2.103s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.797s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.184s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:32.255s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.101s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [53.707s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.782s]
[INFO] Apache CloudStack API . SUCCESS [1:48.884s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.719s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [31.344s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.100s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [27.681s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.727s]
[INFO] Apache CloudStack Core  SUCCESS [1:22.666s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.596s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [37.183s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [15.541s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:07.971s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [41.200s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [26.885s]
[INFO] Apache CloudStack Server .. SUCCESS [4:15.722s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.566s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.442s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:21.155s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.071s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.509s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.813s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.362s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [29.731s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.281s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [26.155s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [20.383s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.360s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.594s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [8.273s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.983s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.589s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.501s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[36.500s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [18.045s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.335s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [15.850s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.709s]
[INFO] Apache Cloud

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

[kiwiflyer]

Github user kiwiflyer commented on the pull request:

https://github.com/apache/cloudstack/pull/1430#issuecomment-193820061
  
@ustcweizhou I've cleaned up the other 2 exceptions and also removed the 
newline you pointed out eariler.


---
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: VR metadata unreachable from VPC tier

[Nux!]

Pierre-Luc,

DHCP works, metadata does not.
I restarted the VPC and it started to work, it happened one more time after 
that; somewhat related to setting up a 1:1 NAT to the only VM in the VPC, 
however I did not have time to look into it more thoroughly. Hopefully next 
time.

Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Pierre-Luc Dion" 
> To: dev@cloudstack.apache.org
> Sent: Tuesday, 8 March, 2016 12:50:52
> Subject: Re: VR metadata unreachable from VPC tier

> Hi nux,
> 
> Does the VM got is hostname and ip?  Would it be just the password set that
> is not working?
> On Feb 25, 2016 14:45, "Syed Mushtaq"  wrote:
> 
>> http://fpaste.org/329431/42948514/raw/
>>
>> On Thu, Feb 25, 2016 at 2:36 PM, Nux!  wrote:
>>
>> > Anywho, a VR reboot has not done anything. I continue to have the same
>> > issue.
>> > Here's the VR's iptables config, something is wrong with it, haven't
>> found
>> > what, once I flush the rules I can get to VRIP:8080
>> > http://fpaste.org/329413/45642787/raw/
>> >
>> > Can you give your VR's ruleset, for comparison?
>> >
>> > --
>> > Sent from the Delta quadrant using Borg technology!
>> >
>> > Nux!
>> > www.nux.ro
>> >
>> > - Original Message -
>> > > From: "Nux!" 
>> > > To: dev@cloudstack.apache.org
>> > > Sent: Thursday, 25 February, 2016 19:04:13
>> > > Subject: Re: VR metadata unreachable from VPC tier
>> >
>> > > Thanks, I'll investigate some more.
>> > >
>> > > In the meanwhile I have tried to restart the VPC network, but nothing
>> > happened
>> > > when I clicked the restart button, the network is now listed with
>> > "restart
>> > > required Yes". What does that mean?
>> > >
>> > > --
>> > > Sent from the Delta quadrant using Borg technology!
>> > >
>> > > Nux!
>> > > www.nux.ro
>> > >
>> > > - Original Message -
>> > >> From: "Syed Mushtaq" 
>> > >> To: dev@cloudstack.apache.org
>> > >> Sent: Thursday, 25 February, 2016 17:33:02
>> > >> Subject: Re: VR metadata unreachable from VPC tier
>> > >
>> > >> It works in my local setup Nux. A VPC with one tier and a password
>> > enabled
>> > >> template. I am working on the master though. The flow to set password
>> > on a
>> > >> VM is the same for a normal VR and a VPC VR. The problem maybe that
>> the
>> > VPC
>> > >> VR is not being sleected by the management server somehow. So there
>> > must be
>> > >> some problem with the VPC VR <=> CS management server.
>> > >>
>> > >> -Syed
>> > >>
>> > >>
>> > >> On Thu, Feb 25, 2016 at 10:38 AM, Nux!  wrote:
>> > >>
>> > >>> Deploy new VM.
>> > >>>
>> > >>> --
>> > >>> Sent from the Delta quadrant using Borg technology!
>> > >>>
>> > >>> Nux!
>> > >>> www.nux.ro
>> > >>>
>> > >>> - Original Message -
>> > >>> > From: "Syed Mushtaq" 
>> > >>> > To: dev@cloudstack.apache.org
>> > >>> > Sent: Thursday, 25 February, 2016 15:35:04
>> > >>> > Subject: Re: VR metadata unreachable from VPC tier
>> > >>>
>> > >>> > I see thanks. So this happens when you create a new VM or when you
>> > try to
>> > >>> > reset password of an already existing VM?
>> > >>> >
>> > >>> > On Thu, Feb 25, 2016 at 9:49 AM, Nux!  wrote:
>> > >>> >
>> > >>> >> Hi,
>> > >>> >>
>> > >>> >> I am yet to restart the VR, will do this a bit later on to see if
>> > the
>> > >>> >> problems gets fixed.
>> > >>> >>
>> > >>> >> Syed, the VM is trying to get the root password from the VR, but
>> it
>> > >>> can't
>> > >>> >> connect to it.
>> > >>> >>
>> > >>> >> --
>> > >>> >> Sent from the Delta quadrant using Borg technology!
>> > >>> >>
>> > >>> >> Nux!
>> > >>> >> www.nux.ro
>> > >>> >>
>> > >>> >> - Original Message -
>> > >>> >> > From: "Syed Mushtaq" 
>> > >>> >> > To: dev@cloudstack.apache.org
>> > >>> >> > Sent: Thursday, 25 February, 2016 14:47:17
>> > >>> >> > Subject: Re: VR metadata unreachable from VPC tier
>> > >>> >>
>> > >>> >> > Hi nux,
>> > >>> >> >
>> > >>> >> > Just so I understand, what is the metadata that VR sends to a
>> VM?
>> > >>> >> >
>> > >>> >> > On Thu, Feb 25, 2016, 9:44 AM Pierre-Luc Dion <
>> pd...@cloudops.com
>> > >
>> > >>> >> wrote:
>> > >>> >> >
>> > >>> >> >> When you have this issue, if you setup a Portforwarding for ssh
>> > for
>> > >>> the
>> > >>> >> VM,
>> > >>> >> >> does the PF rule work?
>> > >>> >> >>
>> > >>> >> >> We observed similar issue where VR does not apply or receive
>> > configs
>> > >>> >> pushed
>> > >>> >> >> by the management-server. I haven't really start investigate
>> > that but
>> > >>> >> >> wondering if you have similar issue. and usually a restart of
>> > the VR
>> > >>> or
>> > >>> >> >> reset of the VPC fixe the issue.
>> > >>> >> >>
>> > >>> >> >>
>> > >>> >> >> PL
>> > >>> >> >>
>> > >>> >> >>
>> > >>> >> >>
>> > >>> >> >> On Thu, Feb 25, 2016 at 6:51 AM, Nux!  wrote:
>> > >>> >> >>
>> > >>> >> >> > Hi,
>> > >>> >> >> >
>> > >>> >> >> > Just a quick one, before I go on submitting a bug, apparently
>> > my
>> > >>> VMs
>> > >>> >> >> > connected in a 

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

[ustcweizhou]

Github user ustcweizhou commented on the pull request:

https://github.com/apache/cloudstack/pull/1430#issuecomment-193827846
  
@kiwiflyer code LGTM. 
can you 
(1) squash the commits,
(2) add a space before s_logger.info ? We use 4 space indentation in java.


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

[kiwiflyer]

Github user kiwiflyer commented on the pull request:

https://github.com/apache/cloudstack/pull/1430#issuecomment-193851127
  
@ustcweizhou  Does 3683dff work?


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

[GitHub] cloudstack pull request: ADD be explicit about the underlying limi...

[kiwiflyer]

Github user kiwiflyer commented on the pull request:

https://github.com/apache/cloudstack/pull/1426#issuecomment-193861558
  
LGTM


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

[GitHub] cloudstack pull request: [CLOUDSTACK-9296] Start ipsec for client ...

[kiwiflyer]

Github user kiwiflyer commented on the pull request:

https://github.com/apache/cloudstack/pull/1423#issuecomment-193864782
  
@syed Can you squash the 2 commits please?
Can you provide some logs showing the fix works?


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

[kiwiflyer]

Github user kiwiflyer commented on the pull request:

https://github.com/apache/cloudstack/pull/1414#issuecomment-193866958
  
Makes sense. LGTM.


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

[GitHub] cloudstack pull request: Check the existence of 'forceencap' param...

[kiwiflyer]

Github user kiwiflyer commented on the pull request:

https://github.com/apache/cloudstack/pull/1402#issuecomment-193872249
  
Since forceencaps is no by default, I think this is a fair change. LGTM.


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

[GitHub] cloudstack pull request: Improve ordering of fields of VPC router ...

[kiwiflyer]

Github user kiwiflyer commented on the pull request:

https://github.com/apache/cloudstack/pull/1422#issuecomment-193873854
  
I agree that it would be nice for this to be configurable (in the future). 
But I will say that those 5 fields are also the ones we use religiously when in 
VR Hell ;-)

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

Re: [PROPOSAL] Minimum Viable CI Integration

[Will Stevens]

I am going to open a ticket with the infra team to request access tokens
for each of the organizations who are putting up hardware for the CI cause.

The reason I am planning to request a token for each organization
individually is because I want to make a point about our need for CI and
the need for many groups to be doing CI in order for us to get full
hardware coverage of the different features we support.  The token is
needed in order for the different CI implementations to be able to simply
post back a 'red light', 'green light' status of the pull request in
github.  More details can be added in comments using an implementation like
what Bharat is working on, but the focus of this request will be to enable
us to have the ability for the different CI environments to get at least
'red light', 'green light' functionality for pull requests.

I will be requesting a token with the following basic permissions:
- public_repo - the same as an anonymous user
- repo:status - this allows for the status of a PR to be changed to one of
the following 4 states; pending, success, failure, error, with some
additional information such as; context, description, and a public url for
more details of the status.

I am going to associate people with each token request and ask that each
person be sent their own token since they are providing infrastructure to
operate a CI environment and the community would like visibility into their
results.

The people I am going to ask for a token for are as follows:

Will Stevens 
Paul Angus 
Bharat Kumar 
Remi Bergsma 

If you would also like to be included in this request and get your own
token in order to be able to contribute back the status of your CI runs,
please let me know so I can request a token for you as well.  Ilya, you had
shown some interest in this as well, would you like me to include you?  If
so which email address should I use?

Anyone else who is planning to contribute an environment to the CI process
in the near to medium future?

Cheers,

*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 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 the

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

[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.726s]
[INFO] Apache CloudStack . SUCCESS [2.090s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.772s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.018s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:32.236s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.105s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [52.625s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [26.719s]
[INFO] Apache CloudStack API . SUCCESS [1:57.468s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.011s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [30.195s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.091s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.725s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [25.480s]
[INFO] Apache CloudStack Core  SUCCESS [1:21.817s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.542s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.968s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.069s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:09.379s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [41.832s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [26.030s]
[INFO] Apache CloudStack Server .. SUCCESS [4:12.189s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.615s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.154s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:22.503s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.068s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.432s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [54.546s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.619s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [30.449s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.655s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [22.298s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [21.519s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [34.605s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.502s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [7.857s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.972s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.353s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.424s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[35.614s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.558s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.617s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [14.637s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.724s]
[INFO] Apache Cloud

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

[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.968s]
[INFO] Apache CloudStack . SUCCESS [3.305s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [1.131s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.638s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:30.324s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.104s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [54.885s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.713s]
[INFO] Apache CloudStack API . SUCCESS [1:48.912s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.786s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [29.837s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.098s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.589s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.909s]
[INFO] Apache CloudStack Core  SUCCESS [1:22.396s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.500s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.058s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [14.174s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:07.790s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.946s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.801s]
[INFO] Apache CloudStack Server .. SUCCESS [4:14.746s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.991s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.880s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:22.355s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.066s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.445s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [53.913s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.263s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [29.798s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.821s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [25.745s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [23.403s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.401s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.122s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [7.851s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.999s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.667s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.404s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[35.545s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.140s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.570s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [15.885s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.728s]
[INFO] Apache Cloud

Re: LDAP auth failures

[ilya]

I could not get LDAP to work as well in 4.5.x, i could get it to work in 4.3

I also get no stacktrace as to what could be wrong.



On 3/3/16 4:53 AM, Rene Moser wrote:
> We are experiencing authentication issues with LDAP since upgrade to 4.5.1.
> 
> After some time (...), users can not authenticate anymore, however,
> authentication in other services using ldap works during this time. The
> issue is only related to cloudstack login it seems.
> 
> We haven't found the root cause yet, a network setup issue or openldap
> config issue can not be excluded.
> 
> Stacktrace:
> 
> 2016-02-29 10:05:36,375 DEBUG [cloudstack.ldap.LdapContextFactory]
> (catalina-exec-4:ctx-9ffa7c60) initializing ldap with provider url:
> ldap://ldap.example.com:389
> 2016-02-29 10:05:42,382 DEBUG [cloudstack.ldap.LdapManagerImpl]
> (catalina-exec-4:ctx-9ffa7c60) ldap Exception:
> javax.naming.NamingException: LDAP response read timed out, timeout
> used:6000ms.; remaining name 'dc=foo,dc=bar'
>   at com.sun.jndi.ldap.Connection.readReply(Connection.java:485)
>   at com.sun.jndi.ldap.LdapClient.getSearchReply(LdapClient.java:639)
>   at com.sun.jndi.ldap.LdapClient.search(LdapClient.java:562)
>   at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:1985)
>   at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1847)
>   at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1772)
>   at
> org.apache.cloudstack.ldap.LdapUserManager.searchUsers(LdapUserManager.java:206)
>   at
> org.apache.cloudstack.ldap.LdapUserManager.getUser(LdapUserManager.java:122)
>   at
> org.apache.cloudstack.ldap.LdapManagerImpl.getUser(LdapManagerImpl.java:173)
>   at
> org.apache.cloudstack.ldap.LdapManagerImpl.canAuthenticate(LdapManagerImpl.java:97)
>   at
> org.apache.cloudstack.ldap.LdapAuthenticator.authenticate(LdapAuthenticator.java:61)
> 2016-02-29 10:05:42,383 DEBUG [cloudstack.ldap.LdapManagerImpl]
> (catalina-exec-4:ctx-9ffa7c60) Exception while doing an LDAP bind for
> user  johndoe
> org.apache.cloudstack.ldap.NoLdapUserMatchingQueryException: No users
> matching: No Ldap User found for username: johndoe
> 
> As I understand there is a username lookup (bind with top reader
> credentials) to see if a user exists in the ldap. if found a new
> connection will be etablished for auth. In the above stacktrace it seem
> that the username lookup fails.
> 
> Further we see on the ACS management server however, is that LDAP
> connection are not going to be closed at any time.
> 
> For _every_ successful auth, the tcp connection remains established forever.
> 
> In my understanding of
> http://docs.oracle.com/javase/jndi/tutorial/ldap/connect/config.html
> these connections will become idle after successful authentication and
> reused for new authentication.
> 
> However, the reuse for the auth doesn't seem to work. _Every_ new
> successful auth of a user _creates_ a new ldap connection. We don't know
> if this is related to our problem, but at least it doesn't look like a
> wanted behavior.
> 
> In the docs we read: "By default, idle connections remain in the pool
> indefinitely until they are garbage-collected"
> 
> But as said, they seem never be gc-ed. After we added
> -Dcom.sun.jndi.ldap.connect.pool.timeout=6 to the
> /etc/cloudstack/management/tomcat6.conf which resulted in the
> connections beeing gc-ed and we didn't have any report about missing
> login since then.
> 
> Has anyone also see such an issue? Any thoughts?
> 
> René
> 

Re: 4.9 Release Management

[ilya]

Will, Samir, Koushik and Patrick,

Thanks for your commitment and energy.

Regards
ilya

On 3/2/16 11:43 AM, Samir Agarwal wrote:
> Kudos Will!
> 
> I had received many private notes wondering if Accelerite will continue to 
> play a strong role in contributions to the community; here is your proof!
> 
> We wanted to take on the biggest pain points in the community, and see how we 
> can make positive contributions. Koushik Das will work alongside Will and 
> Patrick to address both of these problem areas. I believe that this will put 
> the community on a path to more manageable releases going forward.
> 
> Best
> 
> Samir
> 
>   
> 
> 
> -Original Message-
> From: Will Stevens [mailto:williamstev...@gmail.com] 
> Sent: Wednesday, March 02, 2016 9:15 AM
> To: dev@cloudstack.apache.org
> Subject: 4.9 Release Management
> 
> Hello Everyone,
> I have mentioned this in other related threads, but I wanted to make an 
> official thread on the topic.
> 
> I am nominating myself as the release manager for 4.9.  Please feel free to 
> discuss if you have comments or concerns.
> 
> I will not be working alone, I will be assisted by Koushik Das and Patrick 
> Dube.  I will be running point, but all three of us will be working together 
> as a unit for this release.
> 
> Our main focus for this release is the integration of hardware Continuous 
> Integration (CI) into the PR flow.  Koushik and his team will be setting up a 
> CI environment which will be used for testing PRs and I will also be setting 
> up a CI environment for testing PRs.
> 
> The details of the CI integration will be handled publicly, but we will 
> likely have to work with a minimum viable implementation initially and move 
> forward from there.  Here are some of the key aspects of the CI which are top 
> of mind for me.
> 
> - Standardize a feedback mechanism to post the result of CI runs back to the 
> relevant PR.  I believe the best way to do this would be to post a summary of 
> the CI run in the PR thread on Github.  With the existing integration, this 
> will then get pushed to the mailing list (since all comments on a PR are 
> pushed to the mailing list).
> - Ideally, we will also make the CI logs available for the run.  We are still 
> working out the details of how we do this, but we will likely be pushing the 
> logs to an object store with a cleanup window to remove the logs after a set 
> period of time (probably a week).  This should give people the opportunity to 
> pull the logs if they are interested in the test results, but will reduce the 
> need for ever growing storage.
> - In order to parallelize the CI operations, we will not be automatically 
> kicking off a CI run for every PR for now.  Instead, we will communicate 
> between us and each run distinct PRs so we can maximize the utilization of 
> our hardware.
> 
> Some longer term goals of the CI in my mind are as follows:
> 
> - I would like the core CI framework to be easily distributed and accessible 
> to anyone who has hardware available.  This would enable anyone to setup a CI 
> on their hardware and it would automatically be hooked up to feedback the 
> results to the Github PRs.  I feel this is very important long term because 
> every individual or organization depends on a different configuration and 
> hardware setup, so it empowers them to validate their own use case while 
> adding value back to the community.
> 
> Additional details will follow, namely the release schedule etc.
> 
> Please contribute your ideas and feedback.
> 
> Cheers,
> 
> Will
> 
> 
> 
> 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 #3419

[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.722s]
[INFO] Apache CloudStack . SUCCESS [2.089s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.794s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.925s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:30.643s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.102s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [54.222s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.298s]
[INFO] Apache CloudStack API . SUCCESS [1:56.272s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [15.974s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [30.193s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.087s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.148s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [26.037s]
[INFO] Apache CloudStack Core  SUCCESS [1:21.871s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.683s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [36.623s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [13.759s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:08.468s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.877s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [26.011s]
[INFO] Apache CloudStack Server .. SUCCESS [4:13.302s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.054s]
[INFO] Apache CloudStack Usage Server  SUCCESS [43.802s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:21.112s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.066s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.426s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [53.207s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.114s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [29.853s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.009s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [22.912s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [20.566s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [34.996s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.388s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [8.221s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [1.007s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.441s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.824s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[36.129s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.312s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.217s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [16.854s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.623s]
[INFO] Apache Cloud

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

[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.788s]
[INFO] Apache CloudStack . SUCCESS [2.078s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.797s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [19.199s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:30.969s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.105s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [53.622s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.529s]
[INFO] Apache CloudStack API . SUCCESS [1:48.100s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.060s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [30.080s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.091s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.516s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [25.899s]
[INFO] Apache CloudStack Core  SUCCESS [1:21.775s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.848s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [37.122s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [15.562s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:09.207s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [40.796s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [26.092s]
[INFO] Apache CloudStack Server .. SUCCESS [4:11.905s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.829s]
[INFO] Apache CloudStack Usage Server  SUCCESS [44.232s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:21.976s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.070s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.433s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [53.889s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [47.582s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [29.924s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [26.250s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [25.643s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [22.913s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.494s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.453s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [8.412s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.960s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.299s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.317s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[35.593s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.333s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.227s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [14.833s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.793s]
[INFO] Apache Cloud

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

[Slair1]

Github user Slair1 commented on the pull request:

https://github.com/apache/cloudstack/pull/1428#issuecomment-194096939
  
Thanks guys, FYI i applied these change to my 4.8 source, running on 
Centos7 and it fixed the problem for me also. Thanks again!!


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

[GitHub] cloudstack pull request: CLOUDSTACK-9304: Add nuagevsp userdata te...

[sneeladh]

GitHub user sneeladh opened a pull request:

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

CLOUDSTACK-9304: Add nuagevsp userdata testcase (Cloudstack-9095) & 
Refactor existing testcases

https://issues.apache.org/jira/browse/CLOUDSTACK-9304

1. Created folder / test / integration / plugins / nuagevsp 
 2. Moved test_nuage_vpc_network.py , test_nuage_vsp.py from / test / 
integration / component / – to---> / test / integration / plugins / nuagevsp/ 
 3. Added new testcase test_nuage_password_reset.py (Cloudstack-9095) 
 4. Added Nuage class in / tools / marvin / marvin / lib / base.py 
 5. Added services in / tools / marvin / marvin / config / test_data.py

results: 
 test_01_UserDataPasswordReset 
(nuagevsp.test_nuage_password_reset.TestNuagePasswordReset) ... === TestName: 
test_01_UserDataPasswordReset | Status : SUCCESS ===
 ok
 Test Basic VPC Network Functionality with NuageVsp network Plugin ... === 
TestName: test_nuage_vpc_network | Status : SUCCESS ===
 ok
 Test NuageVsp network plugin with basic Isolated Network functionality ... 
=== TestName: test_nuage_vsp | Status : SUCCESS ===
 ok

--
 XML: /root/report_xunit.xml
 --

[PassLogs.zip](https://github.com/apache/cloudstack/files/164368/PassLogs.zip)

 Ran 3 tests in 2406.256s

OK


#CLOUDSTACK-9304 





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

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

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

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


commit 3c8d3d0ee1288931369650195c8c316508483757
Author: Sowmya 
Date:   2016-03-09T02:13:24Z

Add nuagevsp userdata testcase (Cloudstack-9095) & Refactor existing 
testcases

commit 226026342581eb07b0de9718fa207f6cd8299732
Author: Sowmya 
Date:   2016-03-09T02:57:24Z

deleted:test_vpcnetwork_nuage.py
new file:   ../plugins/nuagevsp/__init__.py

commit 255b7464b0ebe869a463534107142eedc8ca2bf4
Author: Sowmya 
Date:   2016-03-09T03:40:43Z

CLOUDSTACK-9304 - Modified Description




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

Re: 4.9 Release Management

[Abhinandan Prateek]

[ShapeBlue]
Abhinandan Prateek
Software Architect  ,   ShapeBlue


d:   | s: +44 203 603 0540  |  
m:  +91 970 11 99011

e:  abhinandan.prat...@shapeblue.com | t: 
 |  w:  
www.shapeblue.com

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


[cid:image0d9449.png@84acf60b.4ab55f1a]


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/03/16, 9:20 AM, "Koushik Das"  wrote:


>Thanks Will for initiating the discussion on 4.9 release management. As 
>already mentioned, I along with Patrick will be helping out Will with the 
>release process.
>
>Having a reliable CI system is very important going forward. There are 
>discussions already happening in the list related to it. I agree that CI 
>should be the top priority for 4.9 release.
>
>The initial idea is to run the CI manually against each PR and publish the 
>results in github itself. The details of the CI environment, test scenarios 
>and configurations will be published as well. Simulator based tests are 
>already running as part of Travis, if required some more tests scenarios can 
>be added there.

Good to see you taking up CI implementation for cloudstack with others. Do you 
yet have timeline to publish a roadmap or a plan for this effort ?

>
>In the longer run, if more contributors/organizations come up with their own 
>CI environment and help test PRs then it will be even better.
>
>-Koushik
>
>From: Will Stevens 
>Sent: Wednesday, March 2, 2016 10:44 PM
>To: dev@cloudstack.apache.org
>Subject: 4.9 Release Management
>
>Hello Everyone,
>I have mentioned this in other related threads, but I wanted to make an
>official thread on the topic.
>
>I am nominating myself as the release manager for 4.9. Please feel free to
>discuss if you have comments or concerns.
>
>I will not be working alone, I will be assisted by Koushik Das and Patrick
>Dube. I will be running point, but all three of us will be working
>together as a unit for this release.
>
>Our main focus for this release is the integration of hardware Continuous
>Integration (CI) into the PR flow. Koushik and his team will be setting up
>a CI environment which will be used for testing PRs and I will also be
>setting up a CI environment for testing PRs.
>
>The details of the CI integration will be handled publicly, but we will
>likely have to work with a minimum viable implementation initially and move
>forward from there. Here are some of the key aspects of the CI which are
>top of mind for me.
>
>- Standardize a feedback mechanism to post the result of CI runs back to
>the relevant PR. I believe the best way to do this would be to post a
>summary of the CI run in the PR thread on Github. With the existing
>integration, this will then get pushed to the mailing list (since all
>comments on a PR are pushed to the mailing list).
>- Ideally, we will also make the CI logs available for the run. We are
>still working out the details of how we do this, but we will likely be
>pushing the logs to an object store with a cleanup window to remove the
>logs after a set period of time (probably a week). This should give people
>the opportunity to pull the logs if they are interested in the test
>results, but will reduce the need for ever growing storage.
>- In order to parallelize the CI operations, we will not be automatically
>kicking off a CI run for every PR for now. Instead, we will communicate
>between us and each run distinct PRs so we can maximize the utilization of
>our hardware.
>
>Some longer term goals of the CI in my mind are as follows:
>
>- I would like the core CI framework to be easily distributed and
>accessible to anyone who has hardware available. This would enable anyone
>to setup a CI on their hardware and it would automatically be hooked up to
>feedback the results to the Github PRs. I feel this is very important long
>term because every individual or organization depends on a differe

Re: 4.9 Release Management

[Will Stevens]

I need to talk to the other guys and start to work that out.  We have to
have at least one CI environment up and running that we can validate
against before we will be able to have a clear timeline.  This is a work in
progress as we speak...

*Will STEVENS*
Lead Developer

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

On Wed, Mar 9, 2016 at 12:29 AM, Abhinandan Prateek <
abhinandan.prat...@shapeblue.com> wrote:

>
> [image: ShapeBlue] 
> Abhinandan Prateek
> Software Architect ,  ShapeBlue
> d:  * | s: +44 203 603 0540* <%7C%20s:%20+44%20203%20603%200540>  |  m:
> *+91 970 11 99011* <+91%20970%2011%2099011>
> e:  *abhinandan.prat...@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/03/16, 9:20 AM, "Koushik Das"  wrote:
>
>
> >Thanks Will for initiating the discussion on 4.9 release management. As
> already mentioned, I along with Patrick will be helping out Will with the
> release process.
> >
> >Having a reliable CI system is very important going forward. There are
> discussions already happening in the list related to it. I agree that CI
> should be the top priority for 4.9 release.
> >
> >The initial idea is to run the CI manually against each PR and publish
> the results in github itself. The details of the CI environment, test
> scenarios and configurations will be published as well. Simulator based
> tests are already running as part of Travis, if required some more tests
> scenarios can be added there.
>
> Good to see you taking up CI implementation for cloudstack with others. Do
> you yet have timeline to publish a roadmap or a plan for this effort ?
>
>
> >
> >In the longer run, if more contributors/organizations come up with their
> own CI environment and help test PRs then it will be even better.
> >
> >-Koushik
> >
> >From: Will Stevens 
> >Sent: Wednesday, March 2, 2016 10:44 PM
> >To: dev@cloudstack.apache.org
> >Subject: 4.9 Release Management
> >
> >Hello Everyone,
> >I have mentioned this in other related threads, but I wanted to make an
> >official thread on the topic.
> >
> >I am nominating myself as the release manager for 4.9. Please feel free to
> >discuss if you have comments or concerns.
> >
> >I will not be working alone, I will be assisted by Koushik Das and Patrick
> >Dube. I will be running point, but all three of us will be working
> >together as a unit for this release.
> >
> >Our main focus for this release is the integration of hardware Continuous
> >Integration (CI) into the PR flow. Koushik and his team will be setting up
> >a CI environment which will be used for testing PRs and I will also be
> >setting up a CI environment for testing PRs.
> >
> >The details of the CI integration will be handled publicly, but we will
> >likely have to work with a minimum viable implementation initially and
> move
> >forward from there. Here are some of the key aspects of the CI which are
> >top of mind for me.
> >
> >- Standardize a feedback mechanism to post the result of CI runs back to
> >the relevant PR. I believe the best way to do this would be to post a
> >summary of the CI run in the PR thread on Github. With the existing
> >integration, this will then get pushed to the mailing list (since all
> >comments on a PR are pushed to the mailing list).
> >- Ideally, we will also make the CI logs available for the run. We are
> >still working out the details of how we do this, but we will likely be
> >pushing the logs to an object store with a cleanup window to remove the
> >logs after a set period of time (probably a week). This should give people
> >the opportunity to pull the logs if they are interested in the test
> >results, but will reduce the need for ever growing storage.
> >- In order to parallelize the CI operations, we will not be automatically
> >kicking off a CI run fo

Re: LDAP auth failures

[Abhinandan Prateek]

In 4.5 there is a timeout param that was added ‘ldap.read.timeout’ that 
defaults to 1000,
It should be set to about 6000 and that should resolve the read timeout that 
you guys see.




[ShapeBlue]
Abhinandan Prateek
Software Architect  ,   ShapeBlue


d:   | s: +44 203 603 0540  |  
m:  +91 970 11 99011

e:  abhinandan.prat...@shapeblue.com | t: 
 |  w:  
www.shapeblue.com

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


[cid:image631b15.png@e7854a64.46aae3f8]


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 09/03/16, 3:19 AM, "ilya"  wrote:

>I could not get LDAP to work as well in 4.5.x, i could get it to work in 4.3
>
>I also get no stacktrace as to what could be wrong.
>
>
>
>On 3/3/16 4:53 AM, Rene Moser wrote:
>> We are experiencing authentication issues with LDAP since upgrade to 4.5.1.
>>
>> After some time (...), users can not authenticate anymore, however,
>> authentication in other services using ldap works during this time. The
>> issue is only related to cloudstack login it seems.
>>
>> We haven't found the root cause yet, a network setup issue or openldap
>> config issue can not be excluded.
>>
>> Stacktrace:
>>
>> 2016-02-29 10:05:36,375 DEBUG [cloudstack.ldap.LdapContextFactory]
>> (catalina-exec-4:ctx-9ffa7c60) initializing ldap with provider url:
>> ldap://ldap.example.com:389
>> 2016-02-29 10:05:42,382 DEBUG [cloudstack.ldap.LdapManagerImpl]
>> (catalina-exec-4:ctx-9ffa7c60) ldap Exception:
>> javax.naming.NamingException: LDAP response read timed out, timeout
>> used:6000ms.; remaining name 'dc=foo,dc=bar'
>> at com.sun.jndi.ldap.Connection.readReply(Connection.java:485)
>> at com.sun.jndi.ldap.LdapClient.getSearchReply(LdapClient.java:639)
>> at com.sun.jndi.ldap.LdapClient.search(LdapClient.java:562)
>> at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:1985)
>> at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1847)
>> at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1772)
>> at
>> org.apache.cloudstack.ldap.LdapUserManager.searchUsers(LdapUserManager.java:206)
>> at
>> org.apache.cloudstack.ldap.LdapUserManager.getUser(LdapUserManager.java:122)
>> at
>> org.apache.cloudstack.ldap.LdapManagerImpl.getUser(LdapManagerImpl.java:173)
>> at
>> org.apache.cloudstack.ldap.LdapManagerImpl.canAuthenticate(LdapManagerImpl.java:97)
>> at
>> org.apache.cloudstack.ldap.LdapAuthenticator.authenticate(LdapAuthenticator.java:61)
>> 2016-02-29 10:05:42,383 DEBUG [cloudstack.ldap.LdapManagerImpl]
>> (catalina-exec-4:ctx-9ffa7c60) Exception while doing an LDAP bind for
>> user johndoe
>> org.apache.cloudstack.ldap.NoLdapUserMatchingQueryException: No users
>> matching: No Ldap User found for username: johndoe
>>
>> As I understand there is a username lookup (bind with top reader
>> credentials) to see if a user exists in the ldap. if found a new
>> connection will be etablished for auth. In the above stacktrace it seem
>> that the username lookup fails.
>>
>> Further we see on the ACS management server however, is that LDAP
>> connection are not going to be closed at any time.
>>
>> For _every_ successful auth, the tcp connection remains established forever.
>>
>> In my understanding of
>> http://docs.oracle.com/javase/jndi/tutorial/ldap/connect/config.html
>> these connections will become idle after successful authentication and
>> reused for new authentication.
>>
>> However, the reuse for the auth doesn't seem to work. _Every_ new
>> successful auth of a user _creates_ a new ldap connection. We don't know
>> if this is related to our problem, but at least it doesn't look like a
>> wanted behavior.
>>
>> In the docs we read: "By default, idle connections remain in the pool
>> indefinitely until they are garbage-collected"
>>
>> But as said, they seem never be gc-ed. After we added
>> -Dcom.sun.jndi.ldap.connect.pool.timeout=6 to the
>> /etc/cloudstack/management/tomcat6.conf which resulted in the
>> connections beeing gc

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

[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.864s]
[INFO] Apache CloudStack . SUCCESS [2.168s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.790s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [18.907s]
[INFO] Apache CloudStack Utils ... SUCCESS [1:28.974s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.101s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [53.521s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [27.668s]
[INFO] Apache CloudStack API . SUCCESS [1:47.149s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [16.037s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [31.591s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.087s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [28.251s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [24.215s]
[INFO] Apache CloudStack Core  SUCCESS [1:21.731s]
[INFO] Apache CloudStack Agents .. SUCCESS [36.513s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [37.239s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [13.842s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [2:09.374s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [41.313s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [25.411s]
[INFO] Apache CloudStack Server .. SUCCESS [4:13.274s]
[INFO] Apache CloudStack Framework - Quota ... SUCCESS [37.221s]
[INFO] Apache CloudStack Usage Server  SUCCESS [43.468s]
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SUCCESS 
[1:20.633s]
[INFO] Apache CloudStack Cloud Services .. SUCCESS [0.068s]
[INFO] Apache CloudStack Secondary Storage ... SUCCESS [0.480s]
[INFO] Apache CloudStack Secondary Storage Service ... SUCCESS [53.449s]
[INFO] Apache CloudStack Engine Storage Component  SUCCESS [48.061s]
[INFO] Apache CloudStack Engine Storage Volume Component . SUCCESS [29.914s]
[INFO] Apache CloudStack Engine Storage Image Component .. SUCCESS [25.745s]
[INFO] Apache CloudStack Engine Storage Data Motion Component  SUCCESS [25.582s]
[INFO] Apache CloudStack Engine Storage Cache Component .. SUCCESS [22.712s]
[INFO] Apache CloudStack Engine Storage Snapshot Component  SUCCESS [35.184s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [12.380s]
[INFO] Apache CloudStack Cloud Engine Service  SUCCESS [8.376s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.993s]
[INFO] Apache CloudStack Plugin - API Rate Limit . SUCCESS [26.447s]
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SUCCESS 
[23.643s]
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SUCCESS 
[36.152s]
[INFO] Apache CloudStack Plugin - API SolidFire .. SUCCESS [17.083s]
[INFO] Apache CloudStack Plugin - API Discovery .. SUCCESS [23.404s]
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SUCCESS [15.782s]
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SUCCESS 
[16.794s]
[INFO] Apache Cloud

[GitHub] cloudstack pull request: CLOUDSTACK-7985: assignVM in Advanced zon...

[ustcweizhou]

Github user ustcweizhou commented on the pull request:

https://github.com/apache/cloudstack/pull/844#issuecomment-194147680
  
rebased, and fixed an issue in assignvm to project.


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