nova features do not respect which nova extensions are installed

[Eric Peterson]

Nova has (optional) extensions, some common ones are covered in the admin actions:

http://docs.openstack.org/developer/nova/api/nova.api.openstack.compute.contrib.admin_actions.html

The problem lies in that horizon always shows users features that may or may not be supported by the nova backend.

It would be more appropriate if horizon called the nova /extensions rest call and enabled the features that were supported by nova.

[OpenStack Infra (hudson-openstack)]

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

[justinsb (justin-fathomdb)]

I've found the same. I've been keeping a list:

* os-simple-tenant-usage (for the usage reports)
* os-availability-zone (when launching)
* os-keypairs (when launching, and on the keypairs tab)
* os-certificates (for downloading EC2 credentials; this shouldn't be the case)
* os-floatingip-pools
* os-volume_attachments (instance detail screen)
* OS-EXT-STS:task_state
* OS-FLV-EXT-DATA (When not present, cannot show instance launch dialog, because it assumes that OS-FLV-EXT-DATA:ephemeral is present - problem when calling humanize in client-side JS)

I take it anything with an os- extension is not part of core, right?

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/37584
Committed: http://github.com/openstack/horizon/commit/db9c08e1721710d3b8f866a47ec1034bf2cf7d9d
Submitter: Jenkins
Branch: master

commit db9c08e1721710d3b8f866a47ec1034bf2cf7d9d
Author: ericpeterson-l <email address hidden>
Date: Wed Jul 17 16:03:22 2013 -0600

    calling nova extensions api to enable certain nova features

    Fixes: bug #1202310

    Change-Id: I47365b0a89ab572f25cb71bfe17cae547261df9d

[Julie Pichon (jpichon)]

@justinsb: Could you file a new bug with that list of extensions? It would be good to track improvements in extensions handling, or at least documenting horizon requirements better.