If you're using a fairly recent cephadm version, there is the ability to provide miscellaneous container arguments in the service spec https://docs.ceph.com/en/quincy/cephadm/services/#extra-container-arguments. This means you can have cephadm deploy each container in that service with, for example, --cpus and --memory flags podman/docker run command provides (or any other flags the podman/docker run commands take) which I think should allow you to accomplish the limiting. On Tue, Oct 25, 2022 at 8:39 AM Mikhail Sidorov <sidorov.ml99@xxxxxxxxx> wrote: > Hello! > > I am planning a ceph cluster and evaluating cephadm as an orchestration > tool > My cluster is going to be relatively small at the start, so I am planning > to run monitor daemons on the same node as osd. But I wanted to provide > some QoS on memory and cpu resources, so I am wondering if it is possible > to set the resource limits for containers via cephadm? And if not, wouldn't > they be overwritten, if I configure them some other way? What is the most > convenient way to do so? > Also I wanted to configure the containers to use jumbo frames and > preferably to use host networking to avoid additional overhead, is ithat > possible? > > Best regards, > Michael > _______________________________________________ > 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
 |