standardize syntax in GET demonstrations when that matches standardization in api.rackspace.com

[rose-coste]

API requests asking different services to do similar things are shaped more similarly in reality than they appear to be if you compare API documentation for several services. If you want any Rackspace API to return a list of things, sending to its endpoint something shaped like "GET /release/tenant/things" is consistently a good guess as to how to ask for that list, though you might doubt that consistency based on what's described for each of the four core infrastructure services in its WADL as published in its Developer Guide and especially at api.rackspace.com:

• Cloud Servers, GET /v2/​{tenant_id}​/servers
  (described at http://api.rackspace.com/#compute_servers)
• Cloud Networks, GET v2.0/networks
  (described at http://api.rackspace.com/api-ref-networks.html)
• Cloud Images, GET images
  (described at http://api.rackspace.com/api-ref-images.html)
• Cloud Block Storage, GET v1/​{tenant_id}​/volumes
  (described at http://api.rackspace.com/api-ref-blockstorage.html)

The apparent inconsistencies will be reconciled as we develop and implement standards for how API operations are described in WADLs and then republish based on those standardized WADLs. Noting the issue here as a reminder to watch for change in what's published at api.rackspace.com and update each product's SDK+API introduction (text and screenshots) to match when change occurs.

Pages to update are:

• http://rackspace-core-infra-user-guide.readthedocs.org/en/latest/cloud-interfaces/API/cloudservers-API.html
• http://rackspace-core-infra-user-guide.readthedocs.org/en/latest/cloud-interfaces/API/cloudnetworks-API.html
• http://rackspace-core-infra-user-guide.readthedocs.org/en/latest/cloud-interfaces/API/cloudimages-API.html
• http://rackspace-core-infra-user-guide.readthedocs.org/en/latest/cloud-interfaces/API/cloudblockstorage-API.html

[rose-coste]

DevDoc team is developing a new standard now; will take a little longer to define the standard, then republish the API doc implementing the standard, then revise API doc in this guide to match the API doc

[rose-coste]

updating link to published draft, changed by #225

[stephamon]

talk to Cat about this one