openstack team mailing list archive

[Devin Carlen <devin.carlen@xxxxxxxxx>]

Erik,

Thanks for the clarification.  I'd just like to reiterate that official support for the EC2 API is something that needs to be handled in parallel, since we've committed to supporting it in the past.  


Best,


Devin

On Feb 28, 2011, at 7:53 PM, Erik Carlin wrote:

> Devin -
> 
> In a decomposed service model, OS APIs are per service, so the routing is straightforward.  For services that need to consume other services (e.g. The compute service needs an IP from the network service), the queueing and worker model remains the same, it's just that the network worker calls out to the RESTful network service API (likely the admin API).
> 
> For EC2 (and any other 3rd party API), the community is welcome to support them, although I see them as secondary to the canonical OS APIs themselves.  Since the EC2 API combines a number of services, it is essentially a composition API.  It probably makes sense to keep in nova (i.e. compute) but you are right, it would need to call out to glance, block, and network in the diablo timeframe.
> 
> What was attached was intended simply to show the general approach, not be a detailed diagram of the API flows.  Once we complete the gap analysis John has requested, these connections should become more clear.
> 
> Erik
> 
> From: Devin Carlen <devin.carlen@xxxxxxxxx>
> Date: Mon, 28 Feb 2011 17:44:03 -0800
> To: Erik Carlin <erik.carlin@xxxxxxxxxxxxx>
> Cc: John Purrier <john@xxxxxxxxxxxxx>, "openstack@xxxxxxxxxxxxxxxxxxx" <openstack@xxxxxxxxxxxxxxxxxxx>
> Subject: Re: [Openstack] OpenStack Compute API for Cactus (critical!)
> 
> Your diagram is deceptively simple because it makes no distinction about how block API would be handled in the EC2 API, where compute and block operations are very closely coupled.  In order for the diagram to convey the requirements properly, it needs to show how compute/network/volume API requests are routed by both the EC2 and OpenStack API.
> 
> 
> Devin
> 
> 
> On Feb 28, 2011, at 3:52 PM, Erik Carlin wrote:
> 
>> I was talking with Will Reese about this more.  If we are eventually going to decompose into independent services with separate endpoints, he thought we should do that now.  I like that idea better.  For cactus, we still have a single nova service "black box" but we put multiple OpenStack API endpoints on the front side, one for each future service.  In other words, use separate endpoints instead of extensions in a single endpoint to expose the current capabilities.  That way, it sets us on the right path and consumers don't have to refactor to support between cactus and diable.  In diablo, we decompose into separate services and the endpoints move with them.  It's a bit hard to visualize so I put together the attached pdf.  I'm assuming glance is a separate service and endpoint for cactus (still need to figure out per my message below) and swift already is.
>> 
>> Erik 
>> 
>> From: Erik Carlin <erik.carlin@xxxxxxxxxxxxx>
>> Date: Mon, 28 Feb 2011 17:07:22 -0600
>> To: John Purrier <john@xxxxxxxxxxxxx>, <openstack@xxxxxxxxxxxxxxxxxxx>
>> Subject: Re: [Openstack] OpenStack Compute API for Cactus (critical!)
>> 
>> That all sounds good.  My only question is around images.  Is glance ready to be an independent service (and thus have a separate API) in Cactus?
>> 
>> Erik
>> 
>> From: John Purrier <john@xxxxxxxxxxxxx>
>> Date: Mon, 28 Feb 2011 16:53:53 -0600
>> To: Erik Carlin <erik.carlin@xxxxxxxxxxxxx>, <openstack@xxxxxxxxxxxxxxxxxxx>
>> Subject: RE: [Openstack] OpenStack Compute API for Cactus (critical!)
>> 
>> 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.
>>  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.
>> <Cactus-Diablo APIs.pdf>_______________________________________________
>> 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.