On Fri, Mar 10, 2017 at 05:00:21PM -0000, John A Meinel wrote:
> The lifetimes of machines deployed by Juju are intentionally tied to the
> lifetime of the model. We don't support identifying already running
> machines which means that those machines would just become orphaned and it
> would not be possible to control them under Juju again.
Something that I found strange on this behavior is that after you ran
"juju remove-machine X" that machine won't be displayed to the user in
"juju status" which it's consistent with the operation remove-machine, so
if remove-machine did release the resource, why later (could be minutes,
days, months) juju will release the machine in maas during
destroy-model?.
> Harvest mode was never intended to support this. Is there a concrete reason
> why you want to deploy but never operate those machines afterward?
Hi John,
On Fri, Mar 10, 2017 at 05:00:21PM -0000, John A Meinel wrote:
> The lifetimes of machines deployed by Juju are intentionally tied to the
> lifetime of the model. We don't support identifying already running
> machines which means that those machines would just become orphaned and it
> would not be possible to control them under Juju again.
Something that I found strange on this behavior is that after you ran
"juju remove-machine X" that machine won't be displayed to the user in
"juju status" which it's consistent with the operation remove-machine, so
if remove-machine did release the resource, why later (could be minutes,
days, months) juju will release the machine in maas during
destroy-model?.
> Harvest mode was never intended to support this. Is there a concrete reason
> why you want to deploy but never operate those machines afterward?
Frode found this during the exploration of possible workarounds for the /bugs.launchpad .net/juju/ +bug/1671588
bug https:/
Best,