Xen-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Fehlig <jfehlig@suse.com>
To: Bob Ball <bob.ball@citrix.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: OpenStack - Libvirt+Xen CI overview
Date: Tue, 17 Mar 2015 08:22:09 -0600	[thread overview]
Message-ID: <55083891.3050002@suse.com> (raw)
In-Reply-To: <BB824EA959B82F43820FFEE5E6B00AA625B521E0@AMSPEX01CL01.citrite.net>

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

Thanks for the info!

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

I'd like to know more.

Regards,
Jim

  parent reply	other threads:[~2015-03-17 14:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10 12:03 OpenStack - Libvirt+Xen CI overview Bob Ball
2015-03-16 15:09 ` OpenStack - Libvirt+Xen CI overview : anyone interested in a walk/through or presentation on how it works Lars Kurth
2015-03-16 18:00 ` OpenStack - Libvirt+Xen CI overview Konrad Rzeszutek Wilk
2015-03-17 12:52   ` Dario Faggioli
2015-03-17 11:14 ` George Dunlap
2015-03-17 14:22 ` Jim Fehlig [this message]
2015-03-17 15:51 ` Alvin Starr
2015-03-18 13:12   ` OpenStack - Libvirt+Xen CI overview : anyone interested in a walk/through or presentation on how it works Lars Kurth
2015-03-18 14:37     ` Wei Liu
2015-03-24 18:17       ` Lars Kurth
2015-03-25 10:08         ` Ian Campbell
2015-03-25 10:09           ` Bob Ball
2015-03-25 12:26             ` Alvin Starr
2015-04-22 10:03               ` Lars Kurth
2015-06-04 17:12             ` Bob Ball
2015-06-05 11:47               ` Lars Kurth
2015-06-08 12:52             ` Bob Ball
2015-06-10 14:25             ` Bob Ball
2015-06-15 16:26             ` Bob Ball

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55083891.3050002@suse.com \
    --to=jfehlig@suse.com \
    --cc=anthony.perard@citrix.com \
    --cc=bob.ball@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox