A few emails back (I have been in meetings and travel for the past two weeks so I am just catching up on email now), Jay pretty much described our plan of setting up a bunch of machines in multiple configurations for use as a test cluster.<div>
<br></div><div>Towards that goal I'd love to start compiling the various systems mentioned in this thread so far into a place so that we can look at the configurations people are already using. My vote is just a wiki page linking to Jenkins deployments and tarballs of Jenkins build configurations and so forth.</div>
<div><br></div><div><a href="http://wiki.openstack.org/TestingBrainstorm">http://wiki.openstack.org/TestingBrainstorm</a><br><br></div><div>Soren, based on your blog post I suspect you have a bunch of this material already, could you add it to that wiki?</div>
<div><br></div><div>Brian Schott, could you add your deployment and existing testing strategy to that wiki?</div><div><br></div><div>I'll take care of getting the Anso/NASA pieces (we have a bunch of vagrant-based stuff) in there.</div>
<div><br></div><div>--andy</div><div><br><div class="gmail_quote">On Fri, Feb 18, 2011 at 8:40 AM, Trey Morris <span dir="ltr"><<a href="mailto:trey.morris@rackspace.com">trey.morris@rackspace.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">yeah I agree with jay, makes me feel more comfortable with this process.<div>also, re jay: guess i had better get to work on that bug</div>
<div><br></div><div>-tr3buchet<div><div></div><div class="h5"><br><br><div class="gmail_quote">On Fri, Feb 18, 2011 at 7:29 AM, Jay Pipes <span dir="ltr"><<a href="mailto:jaypipes@gmail.com" target="_blank">jaypipes@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This was an excellent explanation. Thank you, Thierry.<br>
<font color="#888888"><br>
-jay<br>
</font><div><div></div><div><br>
On Fri, Feb 18, 2011 at 2:55 AM, Thierry Carrez <<a href="mailto:thierry@openstack.org" target="_blank">thierry@openstack.org</a>> wrote:<br>
> Trey Morris wrote:<br>
>> I don't like that it currently only runs on ubuntu + the ppa. If it<br>
>> doesn't work with existing versions I think we're doing something wrong.<br>
>> Even when natty comes out, I don't like the idea of having to ensure I<br>
>> have latest ubuntu for openstack to run.<br>
><br>
> Maybe with my Ubuntu core developer hat on, I can try to clarify.<br>
><br>
> Once an Ubuntu version is released, you can't push new versions of<br>
> libraries or new features in it, only critical bugfixes.<br>
><br>
> So when for openstack we happen to need to new version of a library, it<br>
> won't run on the current stable version. We have a choice between<br>
> avoiding new versions of libraries altogether, or use a PPA to add the<br>
> required version.<br>
><br>
> The route we follow is to provide the new version of the library in a<br>
> PPA for the current stable releases (Lucid/Maverick), and update the<br>
> development release (Natty) proper.<br>
><br>
> The end goal being, when Natty goes out, the corresponding Openstack<br>
> release (Cactus) runs on it without the need for a PPA. For those that<br>
> prefer to run it on an older stable release (or an LTS), the "release"<br>
> PPA can be used.<br>
><br>
> Regards,<br>
><br>
> --<br>
> Thierry Carrez (ttx)<br>
> Release Manager, OpenStack<br>
> Core developer, Ubuntu<br>
><br>
> _______________________________________________<br>
> Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> Post to : <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br>
> Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
><br>
<br>
_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
</div></div></blockquote></div><br></div></div></div><div><div></div><div class="h5"><pre>Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
individual or entity to which this message is addressed, and unless otherwise
expressly indicated, is confidential and privileged information of Rackspace.
Any dissemination, distribution or copying of the enclosed material is prohibited.
If you receive this transmission in error, please notify us immediately by e-mail
at <a href="mailto:abuse@rackspace.com" target="_blank">abuse@rackspace.com</a>, and delete the original message.
Your cooperation is appreciated.
</pre>
</div></div><br>_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
<br></blockquote></div><br></div>