support vsphere disk.enableUUID model config
Bug #1751858 reported by
Kevin W Monroe
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|
https:/
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:
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:/
Users might set this like:
juju model-defaults vsphere disk-enable-uuid=1
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: bitesize vsphere-provider |
Changed in juju: | |
milestone: | none → 2.5-beta1 |
Changed in juju: | |
importance: | Medium → High |
Changed in juju: | |
milestone: | 2.5-beta1 → 2.5-beta2 |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
milestone: | 2.5-beta2 → 2.5-beta3 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Any news on a release target for this?