<HTML>
<HEAD>
<TITLE>Re: [Openstack] [DEVSTACK] officialize it!</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Hmmm, that seems odd, and I guess I don’t understand your reasoning there.<BR>
<BR>
There are other developers that develop on more than just ubuntu X (where X is the latest ubuntu). Ie yahoo is on rhel, I’m pretty sure red hat is running rhel/fedora so the idea that because a “self-declared mission lies” is enough of a reason to not do something correctly seems pretty wrong. Rewrite the mission then imho. Having a separate devstack by rhel also seems wrong (yet another implementation). I know its possible to do this right, even if the “mission” was different before since me and my pep’s at yahoo + others have been writing <a href="https://github.com/yahoo/Openstack-DevstackPy">https://github.com/yahoo/Openstack-DevstackPy</a><BR>
Which guess what, has most of the features of devstack, written in python, but also can run in rhel 6.2, ubuntu 11 and work is being done for fedora 16.<BR>
<BR>
Josh<BR>
<BR>
On 2/6/12 9:51 PM, "Maru Newby" <<a href="mnewby@internap.com">mnewby@internap.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>-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.<BR>
<BR>
+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>
<BR>
Mind you, I don't think anybody would complain if Redhat et al wanted to maintain their own targeted version of devstack.<BR>
<BR>
Thanks,<BR>
<BR>
<BR>
Maru<BR>
<BR>
On 2012-02-06, at 5:22 PM, Joshua Harlow wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Re: [Openstack] [DEVSTACK] officialize it! <BR>
+ 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="jaypipes@gmail.com">jaypipes@gmail.com</a> <x-msg:<a href="//92/jaypipes@gmail.com">//92/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 devstack.org <<a href="http://devstack.org">http://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="berendt@b1-systems.de">berendt@b1-systems.de</a> <x-msg:<a href="//92/berendt@b1-systems.de">//92/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 devstack.org <<a href="http://devstack.org">http://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 devstack.org <<a href="http://devstack.org">http://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 devstack.org <<a href="http://devstack.org">http://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="berendt@b1-systems.de">berendt@b1-systems.de</a> <x-msg:<a href="//92/berendt@b1-systems.de">//92/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> <<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="openstack@lists.launchpad.net">openstack@lists.launchpad.net</a> <x-msg:<a href="//92/openstack@lists.launchpad.net">//92/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="openstack@lists.launchpad.net">openstack@lists.launchpad.net</a> <x-msg:<a href="//92/openstack@lists.launchpad.net">//92/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="openstack@lists.launchpad.net">openstack@lists.launchpad.net</a> <x-msg:<a href="//92/openstack@lists.launchpad.net">//92/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><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>_______________________________________________<BR>
Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><BR>
Post to : <a href="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>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>