Description of problem:
Hello, OpenStack API documentation is confusing for me as a user and causes wastes much more time than reasonable when I try to use it.
For example http://developer.openstack.org/api-ref/compute/?expanded=create-server-detail
There is no indication I can see about API call structure. From the table representation I see `server object` with no link to actual server object structure. Then I see for example `networks` parameter. From table it looks like being specified as a standalone param but in fact it needs to be specified under `server`. There is one exmple which shows where `networks` is to be set, but there is no example about `block_device_mapping_v2`.
I think that for a reasonable user experience, the tables describing call parameters in documentation need to show the proper structure of those params.
As an example I'd provide the OpenShift API  where each `object` has a link to its structure instead of a flat parameter list in the request table. You can see how table links to `v1.BuildConfig` and then the table for `v1.BuildConfig` links to other structures.
Bugs against upstream documentation can be reported here:
It seems like we don't maintain an API documentation. I think we should do that, as well fix issues inside it as the one described above.
Please report the issue to the link provided above in comment 1. The Red Hat documentation group does not work on the upstream docs. Closing this bug.