openstack team mailing list archive

[Vishvananda Ishaya <vishvananda@xxxxxxxxx>]

We definitely wil need to be able to create volumes at the very least without using ec2.  Justinsb has some prototype code available for this.

Vish

On Feb 28, 2011, at 2:53 PM, John Purrier wrote:

> Hi Erik, today we have compute, block/volume, and network all encompassed in nova. Along with image and object storage these make the whole of OpenStack today. The goal is to see where we are at wrt the OpenStack API (compute/network/volume/image) and coverage of the underlying implementation as well as what is available through the EC2 API today.
>  
> I would propose that volume and network API’s be exposed not through the core compute API, but as extensions. Once we create separate services and factor network and volume services out of nova these API’s will form the core API’s for these services. We may also need to up-version these service API’s between Cactus and Diablo as they are currently under heavy discussion and design.
>  
> John
>  
> From: Erik Carlin [mailto:erik.carlin@xxxxxxxxxxxxx] 
> Sent: Monday, February 28, 2011 3:16 PM
> To: John Purrier; openstack@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Openstack] OpenStack Compute API for Cactus (critical!)
>  
> John -
>  
> Are we just talking about compute aspects?  IMO, we should NOT be exposing block functionality in the OS compute API.  In Diablo, we will break out block into a separate service with it's own OS block API.  That means for now, there may be functionality in nova that isn't exposed (an artifact of originally mimicing EC2) until we can fully decompose nova into independent services.
>  
> Erik   
>  
> From: John Purrier <john@xxxxxxxxxxxxx>
> Date: Mon, 28 Feb 2011 14:16:20 -0600
> To: <openstack@xxxxxxxxxxxxxxxxxxx>
> Subject: [Openstack] OpenStack Compute API for Cactus (critical!)
>  
> Has anyone done a gap analysis against the proposed OpenStack Compute API and a) the implemented code, and b) the EC2 API?
>  
> It looks like we have had a breakdown in process, as the community review process of the proposed spec has not generated discussion of the missing aspects of the proposed spec.
>  
> Here is what we said on Feb 3 as the goal for Cactus:
>  
> OpenStack Compute API completed. We need to complete a working set of API's that are consistent and inclusive of all the exposed functionality.
>  
> We need to *very* quickly identify the missing elements that are required in the OpenStack Compute API, and then discuss how we mobilize to get this work done for Cactus. As this is the #1 priority for this release there are implications on milestones dates depending on the results of this exercise. The 1.1 spec should be complete and expose all current Nova functionality (superset of EC2/RS).
>  
> Dendrobates, please take the lead on this, anyone who can help please coordinate with Rick. Can we get a fairly complete view by EOD tomorrow? Please set up a wiki page to identify the gaps, I suggest 3 columns (Actual code / EC2 / OpenStack Compute).
>  
> Thanks,
>  
> John
> _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@xxxxxxxxxxxxxxxxxxx Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
>  
> Confidentiality Notice: This e-mail message (including any attached or
> embedded documents) is intended for the exclusive and confidential use of the
> individual or entity to which this message is addressed, and unless otherwise
> expressly indicated, is confidential and privileged information of Rackspace.
> Any dissemination, distribution or copying of the enclosed material is prohibited.
> If you receive this transmission in error, please notify us immediately by e-mail
> at abuse@xxxxxxxxxxxxx, and delete the original message.
> Your cooperation is appreciated.
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp