Difference between revisions of "Obsolete:Api transition"
| Line 10: | Line 10: | ||
The customer could talk to each individual endpoint, but some operators would want to present a comprehensive api to the customer. This could be done by having a proxy layer above the service apis that would route the request to the appropriate api. | The customer could talk to each individual endpoint, but some operators would want to present a comprehensive api to the customer. This could be done by having a proxy layer above the service apis that would route the request to the appropriate api. | ||
| − | In our example below, if the customer was requesting /images, then proxy would receive the request then route it to the glance api. | + | In our example below, if the customer was requesting /images, then proxy would receive the request then route it to the glance api. |
| + | |||
| + | [[Image:api_transition$os_proposed_apis_with_proxy.png]] | ||
Revision as of 14:25, 18 February 2011
Here are the current apis available in OpenStack:
File:Api transition$os current apis.png
Here are the proposed apis that could be available in OpenStack:
File:Api transition$os proposed apis.png
The customer could talk to each individual endpoint, but some operators would want to present a comprehensive api to the customer. This could be done by having a proxy layer above the service apis that would route the request to the appropriate api.
In our example below, if the customer was requesting /images, then proxy would receive the request then route it to the glance api.
