Feature #46666: cephadm: Introduce 'container' specification to deploy custom containers - Orchestrator - Ceph

Feature #46666

cephadm: Introduce 'container' specification to deploy custom containers

Added by Volker Theile 6 months ago. Updated 2 months ago.

Status:

Resolved

Priority:

Normal

Assignee:

Volker Theile

Category:

cephadm/services

Target version:

Ceph - v16.0.0

% Done:

Source:

Development

Tags:

Backport:

octopus

Reviewed:

Affected Versions:

Pull request ID:

36969

Description

By introducing a 'ContainerSpec' it is possible to deploy custom containers and configurations using cephadm without poluting the code base with things that are not related to Ceph.

E.g. there are plans to deploy a container containing a Prometheus Alertmanager SNMP webhook via cephadm which has absolute no relation to Ceph, but cephadm is needed downstream to deploy that container.
This example is surely the first but not the last potential scenario where such a 'Custom' specification makes sense.

A specification may look like

service_type: container
service_id: snmp-reciever
placement:
  hosts:
  - myhost
spec:
  image: registry.suse.com...
  config_files:
    config.yaml: |
      foobarbaz

Related issues

History

#1 Updated by Sebastian Wagner 6 months ago

Description updated (diff)

#2 Updated by Sebastian Wagner 6 months ago

Description updated (diff)

#3 Updated by Sebastian Wagner 6 months ago

https://github.com/ceph/ceph/blob/12a5c4669828a65ef23d87d22e9a6bfaad68691e/src/cephadm/cephadm#L3047
Needs a new case

src/python-common/ceph.deployment.service_spec needs a new sub class of ServiceSpec

mgr/cephadm.services.cephadmservice needs a new sub class of CephadmService

and the container should have a daemon_id similar to

custom.snmp-reciever.hostname.hsdfjksd

#4 Updated by Volker Theile 6 months ago

Subject changed from cephadm: Introduce 'Custom' specification to deploy custom containers to cephadm: Introduce 'container' specification to deploy custom containers
Description updated (diff)