<HTML>
<HEAD>
<TITLE>Re: [Openstack] OpenStack immaturity</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>+ </SPAN><FONT COLOR="#222222"><FONT SIZE="2"><SPAN STYLE='font-size:10pt'>∞<BR>
</SPAN></FONT></FONT><SPAN STYLE='font-size:11pt'><BR>
On 4/5/12 9:43 AM, "Jay Pipes" <<a href="jaypipes@gmail.com">jaypipes@gmail.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>+10000.<BR>
<BR>
On 04/04/2012 04:20 PM, David Kranz wrote:<BR>
> +1000<BR>
><BR>
> I believe the nova team should make backporting essential bugs to a<BR>
> stable essex base and dealing with the upgrade issue the highest<BR>
> priority for the start (at least) of the Folsom cycle. We need people to<BR>
> deploy real systems using Essex. With regard to smooth upgrades, they<BR>
> won't happen if the issue is always punted to the end of a release<BR>
> cycle. The way to do this is to create a test very early in Folsom that<BR>
> demonstrates how a real large-scale style deployment can be upgraded to<BR>
> a new version containing no code changes. Any future change that breaks<BR>
> that test must be evaluated to compare the value of the change against<BR>
> whatever upgrade pain will be caused. In terms of real deployments, this<BR>
> issue scares me more than the fact that there are bugs. There will<BR>
> always be bugs. But we can't have it be tricky and risky to deploy the<BR>
> fixes.<BR>
><BR>
> -David<BR>
><BR>
> On 4/4/2012 2:30 PM, Tim Bell wrote:<BR>
>><BR>
>> Essex is a key release in this respect. With the excellent work done<BR>
>> by the developers, testers and packaging teams, OpenStack is much<BR>
>> better positioned than with Diablo.<BR>
>><BR>
>> As the work proceeds on Folsom, back porting critical bugs and<BR>
>> planning for a smooth migration path for production sites will become<BR>
>> factors in keeping the early adopters enthusiastic. These are the user<BR>
>> stories that will drive the next wave of OpenStack growth as much as<BR>
>> expanding the feature set.<BR>
>><BR>
>> Tim Bell<BR>
>><BR>
>> CERN<BR>
>><BR>
>><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><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><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>
</BODY>
</HTML>