yahoo-eng-team team mailing list archive

Thread
Date

[Bug 2022057] Re: Prevent co-locating charms that may be conflicting with each other

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Sofia Enriquez <2022057@xxxxxxxxxxxxxxxxxx>
Date: Wed, 14 Jun 2023 10:17:52 -0000
Reply-to: Bug 2022057 <2022057@xxxxxxxxxxxxxxxxxx>
Sender: noreply@xxxxxxxxxxxxx

** Changed in: cinder
   Importance: Undecided => Wishlist

** No longer affects: cinder

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/2022057

Title:
  Prevent co-locating charms that may be conflicting with each other

Status in OpenStack Ceph-FS Charm:
  Triaged
Status in Ceph Monitor Charm:
  Triaged
Status in Ceph OSD Charm:
  Triaged
Status in Kubernetes Control Plane Charm:
  Triaged
Status in OpenStack Compute (nova):
  New

Bug description:
  Charms such as ceph-mon, ceph-osd, ceph-fs, kubernetes-control-plane,
  etc can interfere with each other if they're deployed on the same
  host. While this isn't a supported configuration, charms don't prevent
  from anyone deploying it and then end up with issues.

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-fs/+bug/2022057/+subscriptions