Problem

Today it is hard to understand what each service does and where it belongs, especially for users who are not deeply familiar with Ceph internals.

In the current UI:

• Services are listed with technical names that are not user-friendly
• There is no clear grouping to indicate which services belong together
• It is not obvious which services can have multiple instances and which cannot

This creates confusion and increases the learning curve for new and intermediate users.

What this PR improves / resolves

This PR focuses on improving in the services view:

• Added service labels with user-friendly names: Makes it easier to understand what each service does without requiring deep Ceph knowledge.
• Introduced service grouping aligned with the left navigation: Services are now grouped in a way that mirrors the Dashboard navigation, helping users quickly understand where a service logically belongs.
• Disabled services where multiple instances are not allowed: Prevents users from attempting unsupported configurations and aligns the UI with cephadm service constraints.

Before

After

Contribution Guidelines

• To sign and title your commits, please refer toSubmitting Patches to Ceph.

• If you are submitting a fix for a stable branch (e.g. "quincy"), please refer toSubmitting Patches to Ceph - Backports for the proper workflow.

• When filling out the below checklist, you may click boxes directly in the GitHub web UI. When entering or editing the entire PR message in the GitHub web UI editor, you may also select a checklist item by adding anx between the brackets:[x]. Spaces and capitalization matter when checking off items this way.

Checklist

• Tracker (select at least one)
  • References tracker ticket
  • Very recent bug; references commit where it was introduced
  • New feature (ticket optional)
  • Doc update (no ticket needed)
  • Code cleanup (no ticket needed)
• Component impact
  • AffectsDashboard, opened tracker ticket
  • AffectsOrchestrator, opened tracker ticket
  • No impact that needs to be tracked
• Documentation (select at least one)
  • Updates relevant documentation
  • No doc update is appropriate
• Tests (select at least one)
  • Includesunit test(s)
  • Includesintegration test(s)
  • Includes bug reproducer
  • No tests