Re: [Xen-devel] OpenStack - Libvirt+Xen CI overview : anyone interested in a walk/through or presentation on how it works

[Lars Kurth <lars.kurth.xen@xxxxxxxxx>]

Bob,

adding the Test WG. 

As so far no-one has responded to your offer to organise an on-line meeting to 
walk interested parties the CI loop. If you are, please reply to this thread.

If no-one comes back, I am wondering whether it may not be better to put some 
wiki pages together explaining how the the CI loop works, how to read the 
results, what log files to get to investigate issues, etc. ... For someone 
unfamiliar with Jenkins, this is not entirely obvious.

And maybe have a separate status page. 

I could then take the material it and put a blog post together.

Regards
Lars

> On 10 Mar 2015, at 12:03, Bob Ball <bob.ball@xxxxxxxxxx> wrote:
> 
> For the last few weeks Anthony and I have been working on creating a CI 
> environment to run against all OpenStack jobs.  We're now in a position where 
> we can share the current status, overview of how it works and next steps.  We 
> actively want to support involvement in this effort from others with an 
> interest in libvirt+Xen's openstack integration.
> 
> The CI we have set up is follow the recommendations made by the OpenStack 
> official infrastructure maintainers, and reproduces a notable portion of the 
> official OpenStack CI environment to run these tests.  Namely this setup is 
> using:
> - Puppet to deploy the master node
> - Zuul to watch for code changes uploaded to review.openstack.org
> - Jenkins job builder to create Jenkins job definitions from a YAML file
> - Nodepool to automatically create single-use virtual machines in the 
> Rackspace public cloud 
> - Devstack-gate to run Tempest tests in serial
> 
> More information on Zuul, JJB, Nodepool and devstack-gate is available 
> through http://ci.openstack.org
> 
> The current status is that we have a zuul instance monitoring for jobs and 
> adding them to the queue of jobs to be run at 
> http://zuul.openstack.xenproject.org/
> 
> In the background Nodepool provisions virtual machines into a pool of nodes 
> ready to be used.  All ready nodes are automatically added to Jenkins 
> (https://jenkins.openstack.xenproject.org/), and then Zuul+Jenkins will 
> trigger a particular job on a node when one is available.
> 
> Logs are then uploaded to Rackspace's Cloud Files with sample logs for a 
> passing job at 
> http://logs.openstack.xenproject.org/52/162352/3/silent/dsvm-tempest-xen/da3ff30/index.html
> 
> I'd like to organise a meeting to walk through the various components of the 
> CI with those who are interested, so this is an initial call to find out who 
> is interested in finding out more!
> 
> Thanks,
> 
> Bob
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel