openstack team mailing list archive

[Brian Schott <brian.schott@xxxxxxxxxxxxxxxxxx>]

+ 1

If the nova-* service APIs are all talking UUIDs, then there could be an OS-API 1.0 endpoint and an OS-API 2.0 endpoint coexisting on the same zone.  Much of the UUID disagreements are around exposing them to clients.  So, support  OS API 1.0 interfaces that don't use UUID the same way as EC2 will do it.

-------------------------------------------------
Brian Schott, CTO
Nimbis Services, Inc.
brian.schott@xxxxxxxxxxxxxxxxxx
ph: 443-274-6064  fx: 443-274-6060







On Jul 8, 2011, at 1:29 PM, Lorin Hochstein wrote:

> 
> I think it actually looks more like this right now: 
> 
> 
> EC2 Client   OS Client
>   |             |
> EC2 API        OS API
>    \           /
>   [nova-*] service APIs
> 
> There isn't really a single back-end API for the front-end APIs to call into. Instead, each of them makes calls to the multiple service APIs (e.g., scheduler, network, compute). 
> 
> I would advocate for something more like this:
> 
> 
> EC2 Client   OS Client
>   |             |
> EC2 API        OS API
>    \           /
>   internal nova API
>           |
>   [nova-*] service APIs
> 
> 
> This is a single, unified API that is meant only for internal use. This would reduce the coupling between front-end and back-end. It would make it easier for someone with less expertise in the code (hello!) to find the location in the code that answers questions like: "What does nova do when a user requests that an instance is launched?"   They would just look at the internal API and find the appropriate method. It would also make it easier to add additional front-ends, if there's ever any interest in that.
> 
> 
> Lorin
> --
> Lorin Hochstein, Computer Scientist
> USC Information Sciences Institute
> 703.812.3710
> http://www.east.isi.edu/~lorin
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

Attachment: smime.p7s
Description: S/MIME cryptographic signature