<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">-1 on multi-distribution devstack. Being cross-platform is arguably a place where chef/puppet/cfengine automation comes into play, and that's not where devstack's self-declared mission lies.<div><br></div><div>+1 to continuing to have Ubuntu be the reference devstack target. Maintaining support for an apt-based distribution is much easier than the alternatives from a developer perspective.<br><div><br></div><div>Mind you, I don't think anybody would complain if Redhat et al wanted to maintain their own targeted version of devstack.</div><div><br></div><div>Thanks,</div><div><br></div><div><br></div><div>Maru</div></div><div><br></div><div><div>On 2012-02-06, at 5:22 PM, Joshua Harlow wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<title>Re: [Openstack] [DEVSTACK] officialize it!</title>
<div>
<font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size:11pt">+ There needs to be a way to install on multiple distributions (without saying go figure out the deps yourself).<br>
<br>
I know everyone is ubuntu, ubuntu, ubuntu, but this really needs to be fixed (process wise as well).<br>
<br>
:-/<br>
<br>
On 2/6/12 5:12 PM, "Jay Pipes" <<a href="x-msg://92/jaypipes@gmail.com">jaypipes@gmail.com</a>> wrote:<br>
<br>
</span></font><blockquote><font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size:11pt">cc'ing Matt Ray from OpsCode, since he and I discussed related topics<br>
this past Thursday during the bug squash day...<br>
<br>
On 02/06/2012 06:35 PM, Monty Taylor wrote:<br>
> I think the thing you are discussing already exists.<br>
><br>
> devstack is currently part of and managed by all of the normal OpenStack<br>
> development infrastructure. The canonical repository for it is<br>
> <a href="https://review.openstack.org/p/openstack-dev/devstack">https://review.openstack.org/p/openstack-dev/devstack</a> which is mirrored<br>
> to <a href="https://github.com/openstack-dev/devstack">https://github.com/openstack-dev/devstack</a>. Every change to OpenStack<br>
> is not only gated on devstack properly functioning, every change to<br>
> devstack is gated on OpenStack properly functioning.<br>
><br>
> Additionally, branches match up, so there is a stable/diablo that works<br>
> with stable/diablo of all of the OpenStack branches and is a part of<br>
> their trunk gating.<br>
<br>
This is a critical piece of the puzzle. If I want a Diablo install for<br>
testing, all I need to do is:<br>
<br>
cd $devstack_dir<br>
git checkout stable/diablo<br>
rm -rf /opt/stack<br>
./stack.sh<br>
<br>
And I get a Diablo installation of OpenStack. Likewise, if I want a<br>
development (Essex currently) version of OpenStack, I just do:<br>
<br>
cd $devstack_dir<br>
git checkout master<br>
rm -rf /opt/stack<br>
./stack.sh<br>
<br>
And I get a development installation of OpenStack.<br>
<br>
Now, I'm not entirely sure I even need to do the rm -rf /opt/stack part,<br>
but I do that for good measure, even if it does mean it takes a little<br>
longer... ;)<br>
<br>
This is not something I can do currently with the other deployment methods.<br>
<br>
> In that sense, it's actually the first "install OpenStack" method that<br>
> _is_ fully a part of OpenStack - even though there are also chef recipes<br>
> and puppet modules in OpenStack's gerrit as well. (although at some<br>
> point I wouldn't mind getting some installation testing and gating on<br>
> them as well)<br>
<br>
Yes, and getting those projects aligned with the core projects' branch<br>
layout would be good, too. Followup email on the Chef stuff coming<br>
shortly, as Matt ray and I discussed this last Thursday at length and I<br>
think there's a lot we can do to improve things.<br>
<br>
-jay<br>
<br>
> So it's pretty official already.<br>
><br>
> However, as to becoming an "official project" - it's a developer tool,<br>
> same as git-review or gerrit or the openstack nose-plugin. It's<br>
> something that's useful for developers for developing and testing<br>
> OpenStack. It is not, nor is it meant to be, part of the software we<br>
> "ship" -- which is the current definition of what it means to be a<br>
> "core" project. i.e. - If I'm a deployer and I want to "install<br>
> OpenStack" - is this one of the things I install? With devstack - the<br>
> answer is no.<br>
><br>
> Is is MASSIVELY helpful and a part of everyday life for all of us?<br>
> ABSOLUTELY (this is why we have to be careful with changes to it and run<br>
> them through the same process everything else gets)<br>
><br>
> All of that to say - I agree with you, and it's already done. :)<br>
><br>
> Monty<br>
><br>
> On 02/06/2012 01:43 PM, Joshua Harlow wrote:<br>
>> So the part that worries me about what u just said is the part about “it<br>
>> is already some kind of official project”.<br>
>> When you have to question whether a project is official or not, that<br>
>> seems to pretty make the whole point for making it official ;)<br>
>><br>
>> Overall though I think what u are saying is correct, but the overhead I<br>
>> don’t see as being a bad thing.<br>
>><br>
>> In my idea release management is good since it allows developers to be<br>
>> able to setup a development environment for a given openstack release<br>
>> (good for when you need to fix bugs against a given release as well as<br>
>> good for providing a stable point for other distributions to know what<br>
>> goes in a release and what configs need to be adjusted to make that<br>
>> release work for all the different components). So I don’t see that as a<br>
>> drawback (even though yes it does add work/overhead in, but I don’t see<br>
>> that as a valid point, in any case).<br>
>><br>
>> Downstream distribution, I am not exactly sure what you mean here?<br>
>><br>
>> A technical lead I think is something good to have, as this<br>
>> script/code/documentation is not as simple as you might think (and most<br>
>> likely won’t get any simpler).<br>
>><br>
>> Maybe the correct wording isn’t that this is a core project, but it<br>
>> seems like it is already a widely used project, so I don’t see the<br>
>> difference, either way it should become official and follow some of the<br>
>> same processes as the rest of openstack. Yes it might be developer<br>
>> oriented but if that doesn’t fit a definition of a core project (or<br>
>> whatever u want to call it), because of it being developer focused, then<br>
>> maybe the core project definition needs to be updated?<br>
>><br>
>> As for:<br>
>><br>
>> An other point is that the official CI systems (and I think<br>
>> everybody else, too) are using <a href="http://devstack.org">devstack.org</a> and and that the script<br>
>> is doing a well job.<br>
>><br>
>><br>
>> That’s the whole point, a un-official script shouldn’t be doing these<br>
>> tasks ;)<br>
>><br>
>> -Josh<br>
>><br>
>> On 2/6/12 12:36 PM, "Christian Berendt"<<a href="x-msg://92/berendt@b1-systems.de">berendt@b1-systems.de</a>> wrote:<br>
>><br>
>> Hello together.<br>
>><br>
>> > I was wondering if the community could elevate devstack to a<br>
>> > "official" openstack project, instead of being a "unofficial<br>
>> > project".<br>
>><br>
>> I think <a href="http://devstack.org">devstack.org</a> is already some kind of official project (provided<br>
>> by Rackspace Cloud Builders).<br>
>><br>
>> Where is the benefit of becoming a core project? At the moment I only<br>
>> see a lot of overhead (release management, downstream distribution,<br>
>> technical lead, feature frozen zones, ..) without any benefits.<br>
>><br>
>> Also it would take a lot of efforts (see [0] for details) to set up a<br>
>> new core project.<br>
>><br>
>> Devstack is an instrument to help and improve the development. I think<br>
>> a core component must have the opportunity to be used in a productive<br>
>> environment and should not "only" be used to support the development.<br>
>><br>
>> Can you please describe in more detail what are the benefits of<br>
>> becoming a core project?<br>
>><br>
>> An other point is that the official CI systems (and I think everybody<br>
>> else, too) are using <a href="http://devstack.org">devstack.org</a> and and that the script is doing a<br>
>> well job.<br>
>><br>
>> You're starting two discussions in this mail: Should devstack become a<br>
>> part of the core and should devstack be rewritten to Python. I think<br>
>> the discussions should be splitted and I don't see any motivation of<br>
>> the <a href="http://devstack.org">devstack.org</a> developers to join the discussion of a Python rewrite<br>
>> at the moment (maybe I'm wrong).<br>
>><br>
>> I don't find the definition and requirements of a core project at the<br>
>> moment, but I'm pretty sure that there exist some documents.<br>
>><br>
>> Maybe it makes sense to define some kind of requirements about OpenStack<br>
>> specific tools used by the official CI, but that's an other discussion.<br>
>><br>
>> [0] <a href="http://wiki.openstack.org/Governance/Approved/NewProjectProcess">http://wiki.openstack.org/Governance/Approved/NewProjectProcess</a><br>
>><br>
>> Bye, Christian.<br>
>><br>
>> --<br>
>> Christian Berendt<br>
>> Linux / Unix Consultant& Developer<br>
>> Mail: <a href="x-msg://92/berendt@b1-systems.de">berendt@b1-systems.de</a><br>
>><br>
>> B1 Systems GmbH<br>
>> Osterfeldstraße 7 / 85088 Vohburg / <a href="http://www.b1-systems.de/">http://www.b1-systems.de</a><br>
>> GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537<br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>
>> Post to : <a href="x-msg://92/openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
>> Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>
>> More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><br>
><br>
> _______________________________________________<br>
> Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>
> Post to : <a href="x-msg://92/openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
> Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>
> More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><br>
<br>
_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>
Post to : <a href="x-msg://92/openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><br>
<br>
</span></font></blockquote>
</div>
_______________________________________________<br>Mailing list: <a href="https://launchpad.net/~openstack">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">https://launchpad.net/~openstack</a><br>More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><br></blockquote></div><br></body></html>