Prevent co-locating charms that may be conflicting with each other
Bug #2022057 reported by
Ponnuvel Palaniyappan
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceph Monitor Charm |
Triaged
|
Wishlist
|
Unassigned | ||
Ceph OSD Charm |
Triaged
|
Wishlist
|
Unassigned | ||
Kubernetes Control Plane Charm |
Triaged
|
Wishlist
|
Unassigned | ||
OpenStack Ceph-FS Charm |
Triaged
|
Wishlist
|
Unassigned | ||
OpenStack Compute (nova) |
New
|
Undecided
|
Unassigned |
Bug Description
Charms such as ceph-mon, ceph-osd, ceph-fs, kubernetes-
Can the charm be updated to refuse deployment if one of the other charms is already deployed or being deployed?
Peter Matulis is looking at updating the documentation.
Changed in charm-ceph-mon: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
Changed in charm-ceph-osd: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
Changed in charm-ceph-fs: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
Changed in cinder: | |
importance: | Undecided → Wishlist |
no longer affects: | cinder |
To post a comment you must log in.
I guess we could include some kind of deny list for this. Such a list would never be complete, of course, but we could raise warnings for the ones we know about.
Units would need to look for other units in /var/lib/ juju/agents and inspect their metadata.yaml to get the charm name to check against the deny list.