openstack team mailing list archive
Mailing list archive
Re: Steps that can help stabilize Nova's trunk
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
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.
Soren, based on your blog post I suspect you have a bunch of this material
already, could you add it to that wiki?
Brian Schott, could you add your deployment and existing testing strategy to
I'll take care of getting the Anso/NASA pieces (we have a bunch of
vagrant-based stuff) in there.
On Fri, Feb 18, 2011 at 8:40 AM, Trey Morris <trey.morris@xxxxxxxxxxxxx>wrote:
> yeah I agree with jay, makes me feel more comfortable with this process.
> also, re jay: guess i had better get to work on that bug
> On Fri, Feb 18, 2011 at 7:29 AM, Jay Pipes <jaypipes@xxxxxxxxx> wrote:
>> This was an excellent explanation. Thank you, Thierry.
>> On Fri, Feb 18, 2011 at 2:55 AM, Thierry Carrez <thierry@xxxxxxxxxxxxx>
>> > Trey Morris wrote:
>> >> I don't like that it currently only runs on ubuntu + the ppa. If it
>> >> doesn't work with existing versions I think we're doing something
>> >> Even when natty comes out, I don't like the idea of having to ensure I
>> >> have latest ubuntu for openstack to run.
>> > Maybe with my Ubuntu core developer hat on, I can try to clarify.
>> > Once an Ubuntu version is released, you can't push new versions of
>> > libraries or new features in it, only critical bugfixes.
>> > So when for openstack we happen to need to new version of a library, it
>> > won't run on the current stable version. We have a choice between
>> > avoiding new versions of libraries altogether, or use a PPA to add the
>> > required version.
>> > The route we follow is to provide the new version of the library in a
>> > PPA for the current stable releases (Lucid/Maverick), and update the
>> > development release (Natty) proper.
>> > The end goal being, when Natty goes out, the corresponding Openstack
>> > release (Cactus) runs on it without the need for a PPA. For those that
>> > prefer to run it on an older stable release (or an LTS), the "release"
>> > PPA can be used.
>> > Regards,
>> > --
>> > Thierry Carrez (ttx)
>> > Release Manager, OpenStack
>> > Core developer, Ubuntu
>> > _______________________________________________
>> > Mailing list: https://launchpad.net/~openstack
>> > Post to : openstack@xxxxxxxxxxxxxxxxxxx
>> > Unsubscribe : https://launchpad.net/~openstack
>> > More help : https://help.launchpad.net/ListHelp
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help : https://help.launchpad.net/ListHelp
> 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 abuse@xxxxxxxxxxxxx, and delete the original message.
> Your cooperation is appreciated.
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp