[Openstack] [RFC] OpenStack API
sandy.walsh at RACKSPACE.COM
Sat Jan 8 15:47:02 UTC 2011
I just read the EasyAPI BP and, from a technical perspective, seems rational and sound. The challenge, of course, are the implications for the business side of the house. I realize it doesn't make sense to strive for backward compatibility to EC2/RS API's from EasyAPI, but perhaps the BP should discuss what an API Bridge might look like so we can pull out the existing API services and map them to EasyAPI?
Another point of consideration might be unimplemented features at the hypervisor level being reflected in the public API. For example, we have already added several features on the XenServer side that don't currently have sister operations on the KVM side. Should these operations appear in the public API? Or, should the choice of hypervisor cause the public API WADL to change? Perhaps it's fine to simply tell a "stack" user "<Blah> feature is not implemented for <Foo> hypervisor"?
Just some thoughts.
From: openstack-bounces+sandy.walsh=rackspace.com at lists.launchpad.net [openstack-bounces+sandy.walsh=rackspace.com at lists.launchpad.net] on behalf of Thierry Carrez [thierry at openstack.org]
Sent: Wednesday, January 05, 2011 4:38 AM
To: openstack at lists.launchpad.net
Subject: Re: [Openstack] [RFC] OpenStack API
ksankar at doubleclix.net wrote:
> I have added a new blue print
> https://blueprints.launchpad.net/nova/+spec/open-stack-api and
> associated wiki page to capture and make some progress.I have a
> launchpad account from my Ubuntu days.
We already have a blueprint to cover the Openstack API efforts for teh
Bexar release at:
See previous threads in that list: The Openstack API (1.0) support
already exists in the code, it is currently the Rackspace Cloud API.
Version 1.1 of that API (in Cactus) should have an Openstack namespace
> Developing an Open Stack Cloud System-level CLI might be a good start ...
As part of the above spec, Sandy Walsh has a new python-cloudservers
library (and accompanying cloudservers CLI tool) that, with adequate
rebranding, should just be what you're looking for.
Thierry Carrez (ttx)
Release Manager, OpenStack
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
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 at rackspace.com, and delete the original message.
Your cooperation is appreciated.
More information about the Openstack