Provide an option to specify creation of a new instance upon deployment

Bug #993288 reported by Robert Ayres
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Currently, if you destroy a deployed service, the machine instance is re-used when deploying a new charm. It'd be great if you could specify via a flag, maybe '--new-instance', that a new instance should be created and used for this deployment. This is particularly useful if you destroy a service but want to keep the instance dormant in the background for further tasks, e.g. data retrieval.

juju 0.5+bzr531-0ubuntu1

Revision history for this message
Clint Byrum (clint-fewbar) wrote :

Great idea Robert. I think the workaround right now is just to deploy something non-destructive to any instances you want to keep around, like a "null" charm or something.

Changed in juju:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Kapil Thangavelu (hazmat) wrote :

i think we need to stop reusing machines, and add a separate add-machine to account for this case.

Changed in juju:
milestone: none → 0.7
milestone: 0.7 → 0.8
Curtis Hovey (sinzui)
Changed in juju:
status: Confirmed → Triaged
Curtis Hovey (sinzui)
Changed in juju:
importance: Medium → Low
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.