Nova os-volume-types endpoint doesn't exist

[Carolyn Van Slyck]

The Nova v2.1 documentation shows an endpoint "os-volume-types" which lists the available volume types. http://developer.openstack.org/api-ref-compute-v2.1.html#listVolumeTypes

I am using OpenStack Liberty and that endpoint doesn't appear to exist anymore. GET requests sent to /v2.1/​{tenant_id}​/os-volume-types return 404 not found. When I searched the Nova codebase on GitHub, I could only find a reference to volume types in the policy.json but not implemented anywhere.

Does this endpoint still exist, and if so what is the appropriate documentation?

[Anne Gentle (annegentle)]

Good catch, this resource/extension definitely no longer exists. You can use the Block Storage API and endpoint to list volume types, see http://developer.openstack.org/api-ref-blockstorage-v2.html#volumes-v2-types.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/278047

[Anne Gentle (annegentle)]

As it turns out, no calls should be removed.

[Anne Gentle (annegentle)]

Carolyn, do you have a list of operations that have been removed from v2 to v2.1?

[Carolyn Van Slyck (carolynvs)]

Not really. I've covered about 95% of the (non-operator) endpoints at this point and this is the only one that just plain wasn't there anymore. If I run into any more, I'll let y'all know. :-)

[OpenStack Infra (hudson-openstack)]

Change abandoned by Anne Gentle (<email address hidden>) on branch: master
Review: https://review.openstack.org/278047
Reason: This operation should be added back to the nova code base. Moving bug from openstack-api-site to nova.

[Sean Dague (sdague)]

It's not there in 2.0 either. The help text is super out of whack saying that volumes have 'gpu' associated with them.

I just don't think this ever existed.

[Sean Dague (sdague)]

I went back to juno code, couldn't find any reference to any of this. I think we just delete it from docs. It's not a thing.

[Anne Gentle (annegentle)]

Sean, this extension has been documented for a long time and in 2012 it was an alias returned when listing /extensions:

https://answers.launchpad.net/nova/+question/213261

How would you like to handle this? It was definitely removed from the nova codebase. Sure, it was an alias, but if SDK authors are finding this we need to handle. Ideas?

$ git log | grep -C 5 "os-volume-types"

    * SecurityGroups (security_groups)
    * SimpleTenantUsage (os-simple-tenant-usage)
    * VirtualInterfaces (virtual_interfaces)
    * Volumes (os-volumes)
    * VolumeTypes (os-volume-types)

    Change-Id: Ia3aef79c1912d3df14ab72bbdda3768ae131a19e

commit 8920181a0d8cfb4f78af0fa0b868e864d8971744
Author: Brian Waldon <email address hidden>

[Carolyn Van Slyck (carolynvs)]

In principle, I lean towards not adding back this alias. It's confusing to have block storage functionality aliased and slightly different in the compute service. To me, it is more straightforward to not uses aliases like this, and as a SDK writer, I avoid them. When I can, I use the original service directly instead of the alias.

I am guessing the only reason the alias existed in the first place was nova was a dumping ground for a while until the other solutions and API strategy matured?

[Sharat Sharma (sharat-sharma)]

Nova api has moved to nova code base.

[Anusha Unnam (anusha-unnam)]

Changing the status from new to Invalid, as this bug is marked as invalid by sean dague before it was changed to confirmed by sharat sharma.
Carolyn, Please feel free to mark it as new if you still feel this bug is valid.