On 10/30/24 14:58, Tim Holloway wrote:
Speaking abstractly, I can see 3 possible approaches.
...
2. You can create a Dockerfile based on the stock mgr but with your
extensions added. The main problem with this is that from what I can
see, the cephadm tool has the names and repositories of the stock
containers hard-wired in. Which ensures quality (getting the right
versions) and integrity (makes it hard for a bad agent to swap in a
malware module). So more information is needed at least.
...
... And, we have our answer, courtesy of John Mulligan! There are ways
to compact down layers in a container image, if that's a concern.
Tim
On Wed, 2024-10-30 at 18:00 +0000, Darrell Enns wrote:
Is there a simple way to deploy a custom (in-house) mgr module to an
orchestrator managed cluster? I assume the module code would need to
be included in the mgr container image. However, there doesn't seem
to be a straightforward way to do this without having the module
merged to upstream ceph (not possible for a custom/in-house solution)
or maintaining an in-house container repository and custom container
images (a lot of extra maintenance overhead).
Also, what's the best way to handle testing during development?
Custom scripts to push the code into to a mgr container in a dev
cluster?
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
