Side effects of resizing a juju machine

[Akshat Jiwan Sharma]

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?

Thanks,
Akshat

[Andrew Wilkins]

Post by Akshat Jiwan Sharma
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

Post by Akshat Jiwan Sharma
Thanks,
Akshat
--
Juju mailing list
https://lists.ubuntu.com/mailman/listinfo/juju

[Akshat Jiwan Sharma]

Just what I wanted to hear Andew, thanks!



On Thu, Nov 16, 2017 at 10:47 AM, Andrew Wilkins <

On Thu, Nov 16, 2017 at 11:38 AM Akshat Jiwan Sharma <

Post by Akshat Jiwan Sharma
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.
- 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

Post by Akshat Jiwan Sharma
Thanks,
Akshat
--
Juju mailing list
Modify settings or unsubscribe at: https://lists.ubuntu.com/
mailman/listinfo/juju

[Junien Fridrick]

This post might be inappropriate. Click to display it.

[Akshat Jiwan Sharma]

This post might be inappropriate. Click to display it.