From: Anthony PERARD <anthony.perard@citrix.com>
To: xen-devel@lists.xen.org
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Request for a repo on xenbits for the XenProject Openstack CI Loop
Date: Thu, 17 Nov 2016 16:31:28 +0000 [thread overview]
Message-ID: <20161117163128.GD1717@perard.uk.xensource.com> (raw)
Hi,
I would like a new repo on xenbits to hold the configuration of our
OpenStack CI loop. Its name could be:
git://xenbits.xen.org/openstack-ci-loop-config.git
Right now, the repo is at
https://github.com/citrix-openstack/os-ext-testing
The repo contain everything needed if someone wanted to redeploy the ci
loop on rackspace (and might work elsewhere).
about the ci loop:
https://wiki.xen.org/wiki/OpenStack_CI_Loop_for_Xen-Libvirt
Thanks,
--
Anthony PERARD
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2016-11-17 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 16:31 Anthony PERARD [this message]
2016-11-17 16:34 ` Request for a repo on xenbits for the XenProject Openstack CI Loop Ian Jackson
2016-11-17 16:55 ` Anthony PERARD
2016-11-18 18:40 ` Ian Jackson
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=20161117163128.GD1717@perard.uk.xensource.com \
--to=anthony.perard@citrix.com \
--cc=Ian.Jackson@eu.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;
as well as URLs for NNTP newsgroup(s).