<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-text-flowed" style="font-family: -moz-fixed;
font-size: 12px;" lang="x-unicode">A production configuration of
Openstack should be able to run in HTTPD using SSL. I'd like to
propose the following URL scheme for the web Apps so that the
various pieces can be installed on a single machine without
conflict.
<br>
<br>
All pieces will be served on port 443 using the https protocol.
<br>
<br>
<br>
I've written these up to use the project names. Enough
documentation and information around the projects has circulated
such that replacing, say, Keystone with identity would cause more
confusion than it would remove.<br>
<br>
<br>
#Web UI<br>
#If and only if this is installed, we should put in a forward
from / to /dashboard
for browser clients.<br>
<a class="moz-txt-link-freetext" href="https://hostname/dashboard">https://hostname/dashboard</a>
<br>
<br>
<br>
#identity<br>
<a class="moz-txt-link-freetext"
href="https://hostname/keystone/main">https://hostname/keystone/main</a>
<br>
<a class="moz-txt-link-freetext"
href="https://hostname/keystone/admin">https://hostname/keystone/admin</a>
<br>
<br>
#image<br>
<a class="moz-txt-link-freetext"
href="https://hostname/glance/api">https://hostname/glance/api</a>
<br>
<a class="moz-txt-link-freetext"
href="https://hostname/glance/registry">https://hostname/glance/registry</a>
<br>
<br>
#compute. Not sure if all of these are required<br>
<a class="moz-txt-link-freetext" href="https://hostname/nova/api">https://hostname/nova/api</a>
<br>
<a class="moz-txt-link-freetext" href="https://hostname/nova/crt">https://hostname/nova/crt</a>
<br>
<a class="moz-txt-link-freetext"
href="https://hostname/nova/object">https://hostname/nova/object</a>
<br>
<a class="moz-txt-link-freetext" href="https://hostname/nova/cpu">https://hostname/nova/cpu</a>
<br>
<a class="moz-txt-link-freetext"
href="https://hostname/nova/network">https://hostname/nova/network</a>
<br>
<a class="moz-txt-link-freetext"
href="https://hostname/nova/volume">https://hostname/nova/volume</a>
<br>
<a class="moz-txt-link-freetext"
href="https://hostname/nova/schedule">https://hostname/nova/schedule</a>
<br>
<a class="moz-txt-link-freetext"
href="https://hostname/nova/novnc">https://hostname/nova/novnc</a>
<br>
<a class="moz-txt-link-freetext" href="https://hostname/nova/vncx">https://hostname/nova/vncx</a>
<br>
<a class="moz-txt-link-freetext"
href="https://hostname/nova/cauth">https://hostname/nova/cauth</a>
<br>
<br>
#network<br>
<a class="moz-txt-link-freetext"
href="https://hostname/quantum/service">https://hostname/quantum/api</a><br>
#if we had an API for the agent it would be<br>
<a class="moz-txt-link-freetext"
href="https://hostname/quantum/service">https://hostname/quantum/agent</a><br>
<br>
<br>
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.<br>
<br>
#storage<br>
<a class="moz-txt-link-freetext"
href="https://hostname/swift/account">https://hostname/swift/account</a>
<br>
<a class="moz-txt-link-freetext"
href="https://hostname/swift/object">https://hostname/swift/object</a>
<br>
<a class="moz-txt-link-freetext"
href="https://hostname/swift/container">https://hostname/swift/container</a>
<br>
<br>
<br>
The pattern here should be clear enough to extend to integrating
projects not listed above.<br>
<br>
<br>
</div>
</body>
</html>