Closed mnaser closed 1 month ago
FTR, right now it takes around 12 minutes for cephadm
to deploy a cluster, potentially maybe at the speedups we see above it can go down to a few minutes (like it was before?) and the HA is taking almost 50 minutes should be cut down significnatly.
Hello @mnaser X stray daemon(s) not managed by cephadm We are having this on our sandbox env, do you have any insights about it? We know the issue/bug is superficial and it looks like a bug
Hello @mnaser
X stray daemon(s) not managed by cephadm
We are having this on our sandbox env, do you have any insights about it?
We know the issue/bug is superficial and it looks like a bug
This is not a bug but a result of how things run inside Atmosphere.
Hello @mnaser X stray daemon(s) not managed by cephadm We are having this on our sandbox env, do you have any insights about it? We know the issue/bug is superficial and it looks like a bug
This is not a bug but a result of how things run inside Atmosphere.
Do you have an open issue about it? or a way to solve this?
Hello @mnaser
X stray daemon(s) not managed by cephadm
We are having this on our sandbox env, do you have any insights about it?
We know the issue/bug is superficial and it looks like a bug
This is not a bug but a result of how things run inside Atmosphere.
Do you have an open issue about it?
or a way to solve this?
It's not a bug so there's no point in solving this. It's silenced by our deployment tooling.
Please let's keep this issue on topic.
Thanks
We already have this issue targeted with https://github.com/vexxhost/ansible-collection-ceph/commit/32bb44d26570eedc11ea5adca09791deff312bff so let's close this issue
vs
almost 15x faster, we gotta do this, it'll speed up the CI tremendously.