Feature #44831
Updated by Sebastian Wagner about 4 years ago
ServiceSpec is the data structure used by Orchestrator to manage services.
The example below asks Orchestrator to create rgw services on host1, host2, and host3.
<pre>
service_type: rgw
service_id: realm.zone
placement:
hosts:
- host1
- host2
- host3
spec: ...
</pre>
For more information about ServiceSpec, see
* https://docs.ceph.com/ceph-prs/34290/mgr/orchestrator/#service-specification.
* https://github.com/ceph/ceph/blob/58cc88dd14e4279d63b9ffda12cd19843ed84cfd/src/pybind/mgr/dashboard/frontend/src/app/shared/models/service.interface.ts#L11-L17
We already use DriveGroup (which is actually a subclass of ServiceSpec) to create OSDs in octopus.
We should create various services in Ceph too.
Services to be created (captured from https://pad.ceph.com/p/ceph-dashboard-pacific-priorities)
* MON
* MGR
* RGW
* NFS
* MDS
* Samba/CIFS
* iSCSI
The service creation should support PlacementSpec for service daemon placement.
https://docs.ceph.com/docs/master/mgr/orchestrator/#placement-specification