Difference between revisions of "URLs"
| Line 62: | Line 62: | ||
== Conclusion == | == Conclusion == | ||
The pattern here should be clear enough to extend to integrating projects not listed above. | The pattern here should be clear enough to extend to integrating projects not listed above. | ||
| + | Last added page: [http://wiki.openstack.org/How_to_create_a_Wiki How to create a Wiki] | ||
Revision as of 14:05, 9 January 2013
Proposal:
A production configuration of Openstack should be able to run in HTTPD using SSL. The following URL scheme deconflicts the HTTP based applications so that the various pieces can be installed on a single port on a single machine using the https protocol.
The URLS are descriptive of their functionality. Thus, the project names have been replaced with the names from the openstack.com website.
Components
Horizon Web UI
if and only if this is installed, we should put in a forward from / to /dashboard for browser clients.
Keystone
https://hostname/identity/main
https://hostname/identity/admin
Glance
https://hostname/image/registry
Nova.
Not all of these may be required.
https://hostname/compute/object
https://hostname/compute/network
https://hostname/compute/volume
https://hostname/compute/schedule
https://hostname/compute/novnc
https://hostname/compute/cauth
Quantum
if we get an API for the agent it will be
https://hostname/network/agent
Swift
There was an attempt to make Swift also fit into this scheme. However, Swift URLs fall into a scheme of their own, and won't likely be colocated with the admin pieces outside of development. Here they are for completeness.
https://hostname/storage/account
https://hostname/storage/object
https://hostname/storage/container
Conclusion
The pattern here should be clear enough to extend to integrating projects not listed above. Last added page: How to create a Wiki
