Workflow to manage unauthorised resizing

Registered by Jean-Daniel Bonnetot on 2015-05-11

There is some cases where switching from one flavor to an other is not possible. The reason could be technical (incompatibility between two computes) or strategy (strong separation between two offers).

This means that flavors are linked together. One flavor could have a list of compatible or incompatible flavors.

To solve this problem, a flavor could have a "type" and nova should allow resizing only between the same flavor types.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Jean-Daniel Bonnetot
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
Proposed for liberty
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:flavor-resize-restriction,n,z

Addressed by: https://review.openstack.org/182345
    Workflow to manage unauthorised resizing

Removing milestone as blueprint is not get complete. In fact the nova-spec is still being reviewed. --johnthetubaguy 22nd June 2015

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.