OpenStack Compute (nova)

Flavor disabled status should not be shown by default

Bug #1043585 reported by Vish Ishaya on 2012-08-30

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	OpenStack Compute (nova)	Fix Released	High	Vish Ishaya	OpenStack Compute (nova) 2012.2 "folsom"

Bug Description

We recently added the ability to turn off non-spec data in the api by moving it to an extension. The output for OS-FLV-DISABLED is not in an extension and cannot be disabled properly.

Vish Ishaya (vishvananda) on 2012-08-30

Changed in nova:
status:	New → In Progress
importance:	Undecided → High
milestone:	none → folsom-rc1
assignee:	nobody → Vish Ishaya (vishvananda)

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2012-08-30: Fix proposed to nova (master)

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

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2012-08-31: Fix merged to nova (master)

Reviewed: https://review.openstack.org/12165
Committed: http://github.com/openstack/nova/commit/f9fa7a68a368cefd79ccc6d5d2b91cbdb4d17be7
Submitter: Jenkins
Branch: master

commit f9fa7a68a368cefd79ccc6d5d2b91cbdb4d17be7
Author: Vishvananda Ishaya <email address hidden>
Date: Wed Aug 29 17:50:58 2012 -0700

Clean up non-spec output in flavor extensions

    Adds option to cache flavors in the request object like instances.
    Modifies the flavorextradata extension to use the cache and optimizes
    tests. Adds flavor_disabled extension to control the extra data and
    includes tests. Fixes api samples to show the new extension.

Fixes bug 1043585

Change-Id: Ie89df24a2891e3869d3fb604e07c79e8c913f290