Open Stack

I have an api, diablo nova v1.1.

What we are talking about is if it covers 100% functionality.

I can start my deployment testing with v1.1.  The limiting factor is not v1.1 vs v1.x for most sites. It is packaging, user exits and integration, not whether feature X is in the latest API.

Tim.

----- Reply message -----
From: "George Reese" <george.reese at enstratus.com>
To: "Tim Bell" <Tim.Bell at cern.ch>
Cc: "openstack at lists.launchpad.net" <openstack at lists.launchpad.net>
Subject: [Openstack] API Spec
Date: Sat, Aug 27, 2011 20:47



A cloud platform simply isn't functional without an API. It is a core requirement.

No API, no cloud.

-George

On Aug 27, 2011, at 7:04 PM, Tim Bell wrote:

> I'm also a non-API expert but getting a stable open cloud engine with a reasonable API would seem to be a good target before we look to enhance it.
>
> There are lots of potential users of Nova (including Rackspace) who would like to get Nova into production.  An API will fully exploits all of the underlying functionality should be discussed/planned in the longer term but let's get Diablo out and deployable first.
>
> Tim Bell
> CERN
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

--
George Reese - Chief Technology Officer, enStratus
e: george.reese at enstratus.com    t: @GeorgeReese    p: +1.207.956.0217    f: +1.612.338.5041
enStratus: Governance for Public, Private, and Hybrid Clouds - @enStratus - http://www.enstratus.com
To schedule a meeting with me: http://tungle.me/GeorgeReese

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20110827/57ebf7ba/attachment.html>