juju terminate-machine should have an --all-unused option

Bug #719685 reported by Kapil Thangavelu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pyjuju
Triaged
Low
Unassigned

Bug Description

<SpamapS> oh and terminate-machine is nice too. :)
<SpamapS> I'd love a terminate-machines --all-unused
<kapil> SpamapS, me too..
<kapil> SpamapS, i argued for and got shot down a couple of times
<kapil> easy to enough implement though
<SpamapS> yeah its quite obvious when looking at status which ones are unneeded
<kapil> SpamapS, the reason against, was to keep the command simple, as it might not be there long term, and its nice to have unused machines when deploy recycles unused ones for new deployments
<kapil> s/command/implementation
<SpamapS> I think there's an opportunity for a sophisticated secondary set of tools to manage service units and machines based on business logic.. but its good to have low level tools capable of working in broad strokes.. killall comes in handy sometimes. ;)

Changed in ensemble:
importance: Undecided → Low
milestone: none → budapest
Changed in ensemble:
milestone: budapest → dublin
Changed in ensemble:
milestone: dublin → none
Revision history for this message
Clint Byrum (clint-fewbar) wrote :

Seems like as long as we have a terminate-machine command, we should allow terminating all of the obviously unused machines.

Changed in juju:
status: New → Triaged
summary: - ensemble terminate-machines should have an --all-unused option
+ juju terminate-machines should have an --all-unused option
summary: - juju terminate-machines should have an --all-unused option
+ juju terminate-machine should have an --all-unused option
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.