Storage support for vSphere provider
Bug #1854122 reported by
Tim McNamara
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
As of Juju 2.6.10, Juju's vSphere provider lacks support for storage directives.
We're increasingly getting users deploying Kubernetes on vSphere. If they want to use a Juju-managed Ceph on their "undercloud", they're unable to do so.
https:/
Changed in juju: | |
importance: | High → Wishlist |
To post a comment you must log in.
Storage customization support would be beneficial for the on premises deployments as it would allow to utilize local storage of ESXi hosts via software SAN solution like Ceph.
At the moment Ceph silently installs itself onto loopback devices and this causes two issues:
1. performance is not optimal
2. loopback OSD devices can fill up / filesystem and crash the node.
BTW Issue No.2 I think also applicable to container runtime nodes. For the long running or runaway containers their logs can grow large in size and fill up the disk. If container runtime location is not separated from / this results in node crash (sometimes even root login does not work).