Skip to main content

CEPH Requirements

This page is the CEPH onboarding checklist for StackConsole / CMP. Complete the common prerequisites and confirm hosting topology as well.

Standalone object storage

CEPH is independent of compute orchestrators (CloudStack, VMware, and others). You can run it alongside any compute setup so customers can provision buckets, credentials, and object storage plans through CMP. See also ceph.io.

Bare minimum

Items marked as required to begin in the checklist must be ready before setup can start. Without those prerequisites, installation cannot proceed.

1. Access for StackConsole Team​

To access the CEPH Dashboard UI, use one of:

Option A — VPN access (preferred)

NameEmail
Satish Londhesatish.londhe@stackconsole.io
Ganesh Kanadeganesh.kanade@stackconsole.io

Option B — IP whitelist

If VPN is not feasible, whitelist the StackConsole jump server:

14.192.19.227

2. CEPH Dashboard Credentials​

CMP needs a CEPH user with at least the Admin role (for RGW users, buckets, and related S3 operations).

FieldValue
CEPH URL(for example https://ceph.example.com:8443)
Username(minimum Admin role)
Password

3. S3 Endpoint​

CMP exposes CEPH as S3-compatible object storage. The S3 endpoint must have public access because:

  • Large file transfers (ISO uploads, backups) use S3 presigned URLs
  • Customers may access storage via S3 CLI tools
FieldValue
S3 Endpoint URL (public access)(for example https://s3.example.com)
Public S3 required

Private-only S3 endpoints prevent customers from uploading/downloading large files and using S3-compatible clients.

4. CMP VM → CEPH connectivity​

From all CMP VMs, the CEPH API must be reachable. Private access is recommended for the CEPH dashboard; the S3 endpoint requires public access.

Communication between the CMP VM and CEPH must be allowed on the configured ports.

# CEPH Dashboard API — replace with your URL
curl https://ceph.example.com:8443/api/health/minimal

# S3 Endpoint
curl https://s3.example.com

5. CMP VM configuration​

Shared install inputs:

6. Domain, SSL, SMTP, and app logos​

Shared install inputs:

7. Checklist​

Items needed to begin setup (without these, setup cannot proceed):

Access and CEPH​

  • VPN access to StackConsole team provided or jump server IP whitelisted
  • CEPH access — at least Admin user credentials (URL, username, password)
  • S3 endpoint URL provided and publicly accessible

Staging VM​

  • Staging VM and credentials provided
  • Staging URL provided
  • Staging SSL certificates provided

Production VM​

  • Frontend VM and credentials provided
  • Backend VM and credentials provided
  • Database VM and credentials provided

Production URL and SSL​

  • Frontend URL provided
  • Backend URL provided
  • Frontend VM can reach backend API URL (curl / connectivity tested)
  • Production SSL certificates provided

Other​

  • SMTP details provided
  • App logos (light + dark) provided when branding is required

8. CEPH setup checkpoints​

CheckNotes
At least one zone configured and activeZone associated with a realm and zone group
S3 endpoint publicly accessibleTest with an S3 client or curl
CEPH Dashboard accessibleVia VPN or whitelisted jump IP
Admin credentials can manage pools, users, and object storage