Bug 1041201

Summary: [RFE][nova]: Move away from flavors to more dynamic instance specifications
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/nova/+spec/no-flavors
Whiteboard: upstream_milestone_none upstream_status_unknown upstream_definition_drafting
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 17:20:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-12 13:55:10 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/no-flavors.

Description:

Flavors present a somewhat administratively intensive approach to specifying an instance's technical specifications. I'd like to propose an alternative approach which no longer uses flavors and instead uses a predefined set of increments of each specification. In other words, instead of a list of options the user selects the specific vcpu, ram and storage amounts. In Horizon this can be presented on a sliding scale or as a set of drop-downs (one for vcpu's, one for ram amount, one for disk space). In the command-line the user can simply specify how much ram, disk and how many vcpu's are required. Instead of flavors the administrator then simply sets limits.

Specification URL (additional information):

https://wiki.openstack.org/wiki/DynamicFlavors