Difference between revisions of "Obsolete:Api transition"
Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
+ | |||
+ | <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]]: | ||
Revision as of 12:50, 8 January 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:
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.