Difference between revisions of "OpenStackRESTAPI"
| Line 4: | Line 4: | ||
== Notes from e-mail chain == | == Notes from e-mail chain == | ||
| − | + | 1. [[OpenStack]] API is the Management & Control Plane for a Cloud Infrastructure built using [[OpenStack]] components. | |
| + | 1. It will be used by cloud service consumers & operators to build higher level systems. | ||
| + | 1. It is REST-ful | ||
| + | 1. It will have a programming model appropriate for the audience and their use cases | ||
| + | 1. It will be version-ed | ||
| + | 1. It is a lightweight framework and will have capabilities for service components to expose feature sets via declarative sets | ||
| + | 1. Hackability is important | ||
| + | 1. It will be JSON/HTTP | ||
| + | 1. We should have appropriate media types for the [[OpenStack]] API services (I have done it for CDMI, so have an idea how it could look like, if we decide to go this route) | ||
| + | 1. We could propose a first iteration at the next summit (April '11) | ||
| + | 1. A first client implementation could be a CLI for an [[OpenStack]] Cloud system | ||
== Design Notes == | == Design Notes == | ||
| − | + | 1. Should be a superset of Rackspace APIs | |
| + | 1. Need higher levels abstractions for datacenter/Cloud System, composite application and so forth | ||
| + | 1. Storage and Network layer abstractions | ||
Related Blueprint : https://blueprints.launchpad.net/nova/+spec/easy-api | Related Blueprint : https://blueprints.launchpad.net/nova/+spec/easy-api | ||
Revision as of 05:25, 5 January 2011
OpenStack REST API
Wiki Page for the blue print https://blueprints.launchpad.net/nova/+spec/open-stack-api
Notes from e-mail chain
1. OpenStack API is the Management & Control Plane for a Cloud Infrastructure built using OpenStack components. 1. It will be used by cloud service consumers & operators to build higher level systems. 1. It is REST-ful 1. It will have a programming model appropriate for the audience and their use cases 1. It will be version-ed 1. It is a lightweight framework and will have capabilities for service components to expose feature sets via declarative sets 1. Hackability is important 1. It will be JSON/HTTP 1. We should have appropriate media types for the OpenStack API services (I have done it for CDMI, so have an idea how it could look like, if we decide to go this route) 1. We could propose a first iteration at the next summit (April '11) 1. A first client implementation could be a CLI for an OpenStack Cloud system
Design Notes
1. Should be a superset of Rackspace APIs 1. Need higher levels abstractions for datacenter/Cloud System, composite application and so forth 1. Storage and Network layer abstractions
Related Blueprint : https://blueprints.launchpad.net/nova/+spec/easy-api
