Feature #44831
closedTasks #46756: mgr/dashboard: orchestration workflows & enhancements
mgr/dashboard: Create Ceph services via Orchestrator by using ServiceSpec
100%
Description
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.
service_type: rgw service_id: realm.zone placement: hosts: - host1 - host2 - host3 spec: ...
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
Updated by Kiefer Chang about 4 years ago
- Related to Feature #36596: Integrate the Orchestrator interface into the dashboard added
Updated by Kiefer Chang almost 4 years ago
- Related to Feature #45897: mgr/dashboard: Add host labels in UI added
Updated by Volker Theile almost 4 years ago
- Assignee set to Volker Theile
- Target version set to v16.0.0
Updated by Volker Theile almost 4 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 36119
Updated by Lenz Grimmer over 3 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler over 3 years ago
- Copied to Backport #46963: octopus: mgr/dashboard: Create Ceph services via Orchestrator by using ServiceSpec added
Updated by Nathan Cutler about 3 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".