Start/Stop operations for Juju units/machines
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Won't Fix
|
Low
|
Unassigned |
Bug Description
Could juju support start/stop operations for units/machines in the future?
The use case I am thinking of is when an application setup takes such a long time that it is not feasible to create new units from scratch to handle additional load. Being able to initially add lots of units and keep them in a shutdown state would allow very fast scaling up and down - decreasing the costs from the cloud service.
I realize a machine can have many units, so of course there would have to be good intelligence behind so that juju would when needed first stop those units that are alone on machines - and if no units can be stopped without stopping any other services, the command would not process.
I had a look in blueprints and bugs and could not find something relating to this so raising a feature request here.
tags: | added: add-unit feature |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → Low |
Changed in juju-core: | |
status: | Triaged → Won't Fix |