<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 08.00.0681.000">
<TITLE>RE: [Openstack] Cactus Release Preparation</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">I</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">would suggest</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> that the theme(s) for the Cactus release be:</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">a.</FONT></SPAN><SPAN LANG="en-us"><U> <FONT FACE="Calibri">Deployability</FONT></U></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">. This includes</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> consistent packaging and deployment tools support; but also includes good</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> consistent documentation, approachability to the project (how quickly can a novice get a running system going for p</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">roof of concept), and deployability at larger scale (includes reference materials around hardware</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> and networking choices, operational concerns, and multi-machine deployment</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">orchestration).</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">b.</FONT></SPAN><SPAN LANG="en-us"><U> <FONT FACE="Calibri">Stability</FONT></U></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">. Agree with both Rick and Thierry, we need to get the existing feature</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">s stable and available for additional and larger scale testing environments. We will be</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">focusing</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> on providing additional test automation</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">, beyond testing into automated functional testing. Contributors such as Rackspace will be setting up larger testing environments (on the order of hundreds of machines</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">) to ensure that we are stable at scale, as well.</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">c.</FONT></SPAN><SPAN LANG="en-us"><U> <FONT FACE="Calibri">Reliability</FONT></U></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">.</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> Once a configuration is stood up and operational, it needs to run with only normal operational attention. This will mean additional attention</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">to operational concerns such as longer term test runs, memory leak detection, working set evaluation, etc.</FONT></SPAN><SPAN LANG="en-us"></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">d.</FONT></SPAN><SPAN LANG="en-us"><U> <FONT FACE="Calibri">Consistency</FONT></U></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">. Thierry is right on, we need to have OpenStack be consistent intra-project and across pr</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">ojects. This will include looking at scenarios that "break"</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> our goals of being hypervisor agnostic, API</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">definitions</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> and approach, developer documentation, a</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">nd other areas that teams might be optimizing locally but create a "not finished" view of the project.</FONT></SPAN><SPAN LANG="en-us"></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">e.</FONT></SPAN><SPAN LANG="en-us"><U> <FONT FACE="Calibri">OpenStack API completed</FONT></U></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">. We need to complete a working set of API's that are consistent</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> and inclusive of all the exposed functionality</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">. The OpenStack API will be an amalgam of the underlying services, we need to ensure</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">that the</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> application developer experience is smooth and logical. The DirectAPI calls wi</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">ll be exposed to project developers and committers, but the public</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">OpenStack</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">API</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">for application developers</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">will</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">need to be stable, repeatable, versioned, and extensible.</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> Developer documentation will need to address the fact that the OpenStack API will consist of fixed and well known core calls, plus additional calls that will be introduced by services</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">via the extension mechanisms.</FONT></SPAN><SPAN LANG="en-us"></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">Thoughts?</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">John</FONT></SPAN><SPAN LANG="en-us"></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">-----Original Message-----<BR>
From: openstack-bounces+john=openstack.org@lists.launchpad.net [<A HREF="mailto:openstack-bounces+john=openstack.org@lists.launchpad.net">mailto:openstack-bounces+john=openstack.org@lists.launchpad.net</A>] On Behalf Of Thierry Carrez<BR>
Sent: Monday, January 31, 2011 2:59 AM<BR>
To: openstack@lists.launchpad.net<BR>
Subject: Re: [Openstack] Cactus Release Preparation</FONT></SPAN><SPAN LANG="en-us"></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">Rick Clark wrote:</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">> In Bexar was a feature release. We pushed lots of new features. The</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">> focus of Nova development in Cactus is going to be testing and</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">> stabilization.</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">I wonder if we shouldn't say "consistency, testing and stabilization".</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">Feature work should be concentrated in areas where the resulting</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">software is not consistent, in covering the gaps left after a featureful</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">release. The different groups have been pursuing specific scenarios, but</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">as a project we want to make sure that the other combinations also work.</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">Support IPv6 on FlatManager, for example, is clearly part of that. A</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">complete toolset around the Openstack API, maybe have a plan to</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">deprecate the objectstore...</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">-- </FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">Thierry Carrez (ttx)</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">Release Manager, OpenStack</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">_______________________________________________</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">Mailing list: <A HREF="https://launchpad.net/~openstack">https://launchpad.net/~openstack</A></FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">Post to : openstack@lists.launchpad.net</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">Unsubscribe : <A HREF="https://launchpad.net/~openstack">https://launchpad.net/~openstack</A></FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">More help : <A HREF="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</A></FONT></SPAN></P>
</BODY>
</HTML>