Re: [PATCH] apparmor: ceph config file names

2021-10-13 Thread Jamie Strandboge
On Thu, 07 Oct 2021, christian.ehrha...@canonical.com wrote: > From: Christian Ehrhardt > > If running multiple [1] clusters (uncommon) the ceph config file will be > derived from the cluster name. Therefore the rule to allow to read ceph > config files need to be opened up slightly to allow for

Re: [PATCH] apparmor: ceph config file names

2021-10-10 Thread Christian Ehrhardt
On Sat, Oct 9, 2021 at 2:33 PM Jamie Strandboge wrote: > > On Thu, 07 Oct 2021, christian.ehrha...@canonical.com wrote: > > > From: Christian Ehrhardt > > > > If running multiple [1] clusters (uncommon) the ceph config file will be > > derived from the cluster name. Therefore the rule to allow to

Re: [PATCH] apparmor: ceph config file names

2021-10-07 Thread Michal Prívozník
On 10/7/21 1:32 PM, christian.ehrha...@canonical.com wrote: > From: Christian Ehrhardt > > If running multiple [1] clusters (uncommon) the ceph config file will be > derived from the cluster name. Therefore the rule to allow to read ceph > config files need to be opened up slightly to allow for t

[PATCH] apparmor: ceph config file names

2021-10-07 Thread christian . ehrhardt
From: Christian Ehrhardt If running multiple [1] clusters (uncommon) the ceph config file will be derived from the cluster name. Therefore the rule to allow to read ceph config files need to be opened up slightly to allow for that condition. [1]: https://docs.ceph.com/en/mimic/rados/configurati