Comment 6 for bug 1631480

The more I look at your service catalog, the less I feel like we can provide a solution that you can use. However, I'm looking at an actual real solution that turns out to be a joke from a Silicon Valley episode.

http://localhost:5000/v2/baremetal - Is this the root of the baremetal service or is that v2? Meaning, if I go to that URL, will it give me JSON showing all available baremetal versions (which is what I need)? What's going to happen if I hit http://localhost:5000/v2/?

http://localhost:5000/compute/v2/720429 -- This we could only figure out by going from the middle outward. From the left we'd get a Keystone version, from the right we'd get v2-only.

http://localhost:5000/network and http://localhost:5000/image -- These we can only figure out by going from the right, assuming that those /network and /image urls are returning version info for all available versions. At this point we probably can't assume anything reasonable ever again.

http://localhost:5000/volume/v1/720429 -- Same as compute.

Where does this cloud exist? Are there any rules or documentation for how these services can actually be installed and structured? Like everything else, this has mostly been a guess and trying it in real life, which only accounts for like 25% of what people can think up.