Juju does not allocate swap for ubuntu on vmware

It seems that when we are defining images for ubuntu on vsphere we are missing something to configure swap.

Is this a Juju bug? IIANM we don't explicitly configure swap on images for other cloud providers.
Is there something bespoke Juju needs to do for vSphere? Are the upstream image files Juju consumes not configured correctly?

I'm not sure how the images get into vsphere for juju to consume. It is
possible that this isn't a juju bug at all, and instead there are missing
steps in the configuration of the images in vsphere itself.

On Tue, Apr 21, 2020 at 2:15 PM Ian Booth <email address hidden> wrote:

> Is this a Juju bug? IIANM we don't explicitly configure swap on images for
> other cloud providers.
> Is there something bespoke Juju needs to do for vSphere? Are the upstream
> image files Juju consumes not configured correctly?
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: Juju bugs
> https://bugs.launchpad.net/bugs/1873960
>
> Title:
> Juju does not allocate swap for ubuntu on vmware
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1873960/+subscriptions
>

I don't believe we set up Swap anywhere.:

juju bootstrap aws
juju ssh -m controller 0
free
ubuntu@ip-10-239-188-95:~$ free
              total used free shared buff/cache
available
Mem: 31391036 402104 28509584 788 2479348
 30594852
Swap: 0 0 0

I don't know if MAAS itself defaults to providing swap. And it would make
sense that it could be a machine constraint, but it isn't something that we
have special cased for VMWare, it just isn't something that we do generally.

On Tue, Apr 21, 2020 at 6:41 AM Tim Penhey <email address hidden> wrote:

> I'm not sure how the images get into vsphere for juju to consume. It is
> possible that this isn't a juju bug at all, and instead there are missing
> steps in the configuration of the images in vsphere itself.
>
> On Tue, Apr 21, 2020 at 2:15 PM Ian Booth <email address hidden>
> wrote:
>
> > Is this a Juju bug? IIANM we don't explicitly configure swap on images
> for
> > other cloud providers.
> > Is there something bespoke Juju needs to do for vSphere? Are the upstream
> > image files Juju consumes not configured correctly?
> >
> > --
> > You received this bug notification because you are subscribed to juju.
> > Matching subscriptions: Juju bugs
> > https://bugs.launchpad.net/bugs/1873960
> >
> > Title:
> > Juju does not allocate swap for ubuntu on vmware
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/juju/+bug/1873960/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1873960
>
> Title:
> Juju does not allocate swap for ubuntu on vmware
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1873960/+subscriptions
>

From what I understand, juju downloads a vmdk file from somewhere, which is then used to boot the vms in vmware. Shouldn't the swap be part of that template?

Juju does not set up swap on any cloud and at this time is not something currently under consideration.
There may be a way to do it using this cloud-init model-config attribute

https://discourse.juju.is/t/using-model-config-key-cloudinit-userdata/512

I am not sure if the vSphere images support cloud-init?

I used cloudinit to set the timezone for the vms in Vsphere, so yes, vSphere images support cloud-init.

So should this be a nagios bug then? It's not normal that upon deploy of our default template, we end up with red alerts in Nagios.

This is causing issues w/ CDK deployments, which do need swap.

(In other clouds, you'd specify a flavor, or instance type, and be off to the races -- we need to do something different in vSphere.)

I'd like to add this to the work we're doing on vSphere this cycle, if possible.

@freyes I ran this by the team in a hangout ... and got a little bit of pushback :-)

What charms, specifically, are failing in the absence of swap? Are they working on AWS? And what are/how terrible are the workarounds?

I know that there are some circumstances where, for example, a golang program will try to over commit on memory, and the kernel will refuse to do so if the machine doesn't have swap enabled. But it seems like this would be biting us on other clouds if there weren't already decent workarounds in the charms ...

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.