Difference between revisions of "Obsolete:Api transition"
m (Fifieldt moved page Api transition to Obsolete:Api transition: outdated) |
|||
(3 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | + | ||
+ | |||
+ | <pre><nowiki>#!wiki caution | ||
+ | '''This page is outdated''' | ||
+ | |||
+ | The content of this page has not been updated for a very long time. The proposal mentioned below not implemented. | ||
+ | </nowiki></pre> | ||
+ | |||
+ | |||
Here are the current apis available in [[OpenStack]]: | Here are the current apis available in [[OpenStack]]: | ||
− | [[Image: | + | [[Image:os_current_apis.png]] |
Here are the proposed apis that could be available in [[OpenStack]]: | Here are the proposed apis that could be available in [[OpenStack]]: | ||
− | [[Image: | + | [[Image: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. | 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. | ||
Line 12: | Line 20: | ||
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: | + | [[Image:os_proposed_apis_with_proxy.png]] |
Latest revision as of 19:04, 25 July 2013
#!wiki caution '''This page is outdated''' The content of this page has not been updated for a very long time. The proposal mentioned below not implemented.
Here are the current apis available in OpenStack:
Here are the proposed apis that could be available in OpenStack:
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.