CCloudNexaCloud FinOps learning · cloudnexa.viswanext.com
Vendor-neutral guide

Cloud Management Platform (CMP) — End-to-End Guide

End-to-End Implementation Guide — From Fundamentals to Advanced Operations
Day 0 • Day 1 • Day 2+

1. Introduction to a CMP

What is a CMP?

A CMP is a Cloud Management Platform (CMP) that provides a single control plane to manage, govern, and automate infrastructure and applications across public cloud, private cloud, and on-premises environments.

  • Multi-cloud provisioning (public clouds and on-prem virtualization)
  • Multi-tenancy and isolation
  • Self-service catalogs
  • Governance, security, and cost control
  • Day-2 operations and lifecycle automation

A CMP does not replace cloud providers or hypervisors. It orchestrates, governs, and standardizes them.

2. CMP Architecture (Conceptual)

Core Components

  • CMP appliance – Central control plane
  • Cloud Integrations – API connections to clouds and hypervisors
  • Tenants & Groups – Isolation and access boundaries
  • Library & Catalog – Blueprint factory and self-service
  • Operations & Governance – Cost, policies, lifecycle
A CMP is usually deployed as a software appliance (on a VM, on-prem or in the cloud). It is not hardware and is not tied to any specific vendor.

3. Day 0 – Installation & Foundation

Deployment example: public cloud

  • Launch the CMP image from a cloud marketplace
  • Recommended production sizing:
    • 4–8 vCPU
    • 16–32 GB RAM
    • 100–200 GB EBS

Network, DNS & Bootstrap

  • Management VPC
  • Security Groups: 443, 22
  • Customer-managed DNS (e.g. cmp.example.com)
  • Initial setup wizard and license upload

4–6. Day 1 – Cloud Onboarding, Tenancy & Catalog

Cloud Connectivity

  • Public cloud A – IAM role, regions, VPCs
  • Public cloud B – service principal, subscription
  • Public cloud C – service account, project
  • Private virtualization – management server, clusters, datastores

Tenants, Groups & Isolation

  • Master Tenant (platform owner)
  • Sub-tenants (customers or business units)
  • Groups define where workloads can run
  • RBAC enforces isolation

Library & Service Catalog

  • Instance Types, Layouts, Node Types
  • Blueprints define application topology
  • Catalog exposes approved services

7–8. Day 2+ – Governance, Cost & Operations

Governance & Cost Control

  • Approval workflows
  • Quota and policy enforcement
  • Showback, chargeback, budgets
  • vCPU-based licensing model

Lifecycle, Monitoring & Backups

  • Power schedules and lease expiration
  • Monitoring and alerts
  • Integration with open-source and commercial observability tools
  • Backup orchestration (snapshots, Veeam, Rubrik)

9. Troubleshooting – Common Issues

  • Cloud discovery issues → Check IAM/RBAC and network
  • Catalog failures → Validate blueprint and quotas
  • License exceeded → Review managed vCPU
  • Hypervisor unreachable → Check firewall, DNS, credentials
Day 0 → Platform Foundation
Day 1 → Access & Enablement
Day 2 → Control & Optimization