Nested Stack for LaunchConfig
Registered by
Kevin Fox
There seems to be no way to create a LaunchConfig that needs extra resources, like Volumes or Neutron ports. This means load ballancers can only use simple, compute only configs. It would be nice to be able to specify a LaunchConfig that uses a nested stack instead of instance details to allow much more configurable scaling.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Steve Baker
Related branches
Related bugs
Sprints
Whiteboard
(stevebaker) our AWS compatible autoscaling API can't be modified, but any collection of resources can be autoscaled with blueprint autoscaling-
(?)
