Allow admins to set instance defaults per image
Launching an instance can be a complicated process for an end user. There are many options and not all of them may be known. In addition, an admin may want to enforce certain values for certain properties. For example, an admin may want to force all instances based on image "foo" to use the "m1.tiny" flavor. This blueprint adds changes that allow an admin to specify default deployment properties for an image. In other words, an admin can set default values for the properties that are requested when launching an instance. For each property, the admin can also specify whether or not a user is able to supply their own value.
The instance default values will be stored as metadata on the image. When a user launches an instance based on this image, the fields presented in the UI will be tailored based on the value of this metadata property.
Blueprint information
- Status:
- Complete
- Approver:
- David Lyle
- Priority:
- Low
- Drafter:
- Justin Pomeroy
- Direction:
- Needs approval
- Assignee:
- Justin Pomeroy
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Slow progress
- Milestone target:
- None
- Started by
- Justin Pomeroy
- Completed by
- Justin Pomeroy
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Allow admin to set instance defaults per image
[jpich 2014.06.10] Moving milestone to j-2. Could you set the status to "Code Needs Review" is that is the correct status? Thank you.
[david-lyle | 2014.07.23] Moving to Juno-3.
[david-lyle | 2014.08.28] Moving out of Juno.
[jpomero 2014-09-10] This hasn't been going anywhere because I know there is desire to make significant usability improvements to the launch instance workflow, which would have impact on this. There is also some debate whether heat templates would be a better approach to solving this problem. Ultimately this is a somewhat messy solution that I'm not all that happy with, so I'm just sitting on it for now.
