support vsphere disk.enableUUID model config

Bug #1751858 reported by Kevin W Monroe
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Christian Muirhead

Bug Description

Juju supports a few model config options for vsphere already ([external|primary]-network, datastore):

https://jujucharms.com/docs/2.3/help-vmware#bootstrapping

We should include disk.enableUUID in this list. Kubernetes can exploit vsphere storage features, but it requires all worker nodes to know the underlying disk uuid:

https://vmware.github.io/vsphere-storage-for-kubernetes/documentation/existing.html#step-3-enable-disk-uuid-on-node-virtual-machines

It feels like the right place to do this would be in createImportSpec so that all VMs created in a properly configured model would have it enabled:

https://github.com/juju/juju/blob/develop/provider/vsphere/internal/vsphereclient/createvm.go#L277

Users might set this like:

juju model-defaults vsphere disk-enable-uuid=1

Tim Penhey (thumper)
Changed in juju:
status: New → Triaged
importance: Undecided → Medium
tags: added: bitesize vsphere-provider
Revision history for this message
Kevin W Monroe (kwmonroe) wrote :

Any news on a release target for this?

Revision history for this message
John A Meinel (jameinel) wrote : Re: [Bug 1751858] Re: support vsphere disk.enableUUID model config

AFAIK nobody is looking at this, and it is triaged at Medium so it isn't
considered a priority. If there is reason to escalate the priority please
discuss. Probably directly with Tim, rather than via just the bug
conversation.

On Wed, Apr 11, 2018 at 10:02 PM, Kevin W Monroe <<email address hidden>
> wrote:

> Any news on a release target for this?
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1751858
>
> Title:
> support vsphere disk.enableUUID model config
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1751858/+subscriptions
>

Revision history for this message
John A Meinel (jameinel) wrote :

For my 2c, is there any reason *not* to always set disk.enableUUID always?
What is the reason you'd ever want disk.enableUUID to be 0 ?

On Thu, Apr 12, 2018 at 2:56 PM, John Meinel <email address hidden> wrote:

> AFAIK nobody is looking at this, and it is triaged at Medium so it isn't
> considered a priority. If there is reason to escalate the priority please
> discuss. Probably directly with Tim, rather than via just the bug
> conversation.
>
>
> On Wed, Apr 11, 2018 at 10:02 PM, Kevin W Monroe <
> <email address hidden>> wrote:
>
>> Any news on a release target for this?
>>
>> --
>> You received this bug notification because you are subscribed to juju.
>> Matching subscriptions: juju bugs
>> https://bugs.launchpad.net/bugs/1751858
>>
>> Title:
>> support vsphere disk.enableUUID model config
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/juju/+bug/1751858/+subscriptions
>>
>
>

Revision history for this message
Kevin W Monroe (kwmonroe) wrote :

@jam, i haven't found many use cases for wanting disk.EnableUUID to be 0. I found this:

https://blogs.vmware.com/kb/2013/03/setting-disk-enableuuidtrue-in-vmware-data-protection.html

That's pretty old, but basically, if the option was 0 (false) and an operator enabled it while the VM was running, snapshots would fail because the current config doesn't match the config from when the VM was started.

And also this:

https://kb.vmware.com/s/article/2146204

Apparently the Volume Snapshot Service (VSS) is tied to disk.EnableUUID; if you wanted a quiesced snapshot that doesn't interact with VSS, you might want to set the option to 0 (false).

The reason we want control over this setting is for persistent vsphere storage in kubernetes. You can't have it without disk.EnableUUID=true on the VMs:

https://vmware.github.io/vsphere-storage-for-kubernetes/documentation/existing.html#step-3-enable-disk-uuid-on-node-virtual-machines

So if we do end up supporting this with model config, perhaps the safe thing to do is default it to false to match current behavior, yet allow ops to turn it on when required.

Tim Penhey (thumper)
Changed in juju:
milestone: none → 2.5-beta1
Ian Booth (wallyworld)
Changed in juju:
importance: Medium → High
Revision history for this message
Ian Booth (wallyworld) wrote :

I think we make the setting true by default since that's what's needed 99% of the time.

Changed in juju:
assignee: nobody → Christian Muirhead (2-xtian)
Revision history for this message
Christian Muirhead (2-xtian) wrote :

Talking about this with Ian, we thought we could default it to true for new controllers but for existing controllers have an upgrade step that sets it to false (since that's effectively what they have).

Changed in juju:
status: Triaged → In Progress
Ian Booth (wallyworld)
Changed in juju:
milestone: 2.5-beta1 → 2.5-beta2
Ian Booth (wallyworld)
Changed in juju:
status: In Progress → Fix Committed
Ian Booth (wallyworld)
Changed in juju:
milestone: 2.5-beta2 → 2.5-beta3
Revision history for this message
Kevin W Monroe (kwmonroe) wrote :

Confirmed this is set in 2.5-b3!

$ ./govc_darwin_amd64 vm.info -e=true juju-fac896-0
Name: juju-fac896-0
...
  ExtraConfig:
...
    disk.EnableUUID: true
...

Big Thanks!

Changed in juju:
status: Fix Committed → Fix Released
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.