Side effects of resizing a juju machine

[Andrew Wilkins]

On Thu, Nov 16, 2017 at 11:38 AM Akshat Jiwan Sharma <akshatjiwan at gmail.com>
wrote:

> Hi everyone,
>
> A couple of times I've noticed that the capacity of a machine provisioned
> by juju is much more than what I require for my workload. I was wondering
> that  if I were to manually resize the machine would it break any of juju
> services?
>

Juju won't care, you will just have some incorrect information in "juju
status". We record hardware characteristics for each machine, but it's used
only for describing machines to the user.

FWIW, I've just tested this:
 - juju bootstrap azure --bootstrap-constraints
instance-type=instance-type=Standard_DS12_v2
 - juju switch controller && juju deploy ubuntu --to 0
Then resized the machine to Standard_D4s_v3 via the Azure Portal. Juju came
back up fine, as did the unit.

Some charms might take a snapshot of hardware details when they're
installed, but I'm not aware of which if any would do that. But Juju itself
doesn't care.

Cheers,
Andrew


> Thanks,
> Akshat
> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20171116/df660554/attachment.html>