Key concepts

Mon, 01 Jan 0001 00:00:00 +0000

Core concepts

Concept	Description
Resource handlers	A resource handler is a connection to a cloud platform or virtualization technology, such as AWS, Azure, GCP, or VMware. Each resource handler provides CMP with visibility and control over resources on that platform.
Environments	An environment is a logical grouping of resources within a resource handler, such as an AWS region or a VMware cluster. Environments define which VM images, networks, and configuration options are available when users place orders.
Servers	A server is CMP’s record of a compute resource, either a virtual machine or a physical server. Servers can be provisioned through CMP or discovered automatically by scanning a connected resource handler. Each server belongs to one environment and one group, and can be managed, tracked, and acted on throughout its lifecycle.
Groups	Groups organize users and facilitate access to environments, blueprints, and resources. Roles and quotas are applied at the group level to control what members can see, use, and request.
Catalog	The catalog is the self-service portal where users browse and order blueprints. Administrators can control which blueprints appear in the catalog.
Blueprints	A blueprint defines a repeatable, orderable service. Blueprints include build steps, management actions, and teardown logic, and are ordered by users through the catalog.
Orchestration	Orchestration allows administrators to automate actions at defined trigger points, such as during provisioning, on a schedule, or in response to an event. Actions can run plugins, remote scripts, webhooks, or integrate with external systems.
Networks	Networks define the subnets and VLANs available to servers in CMP, derived from your resource handlers. They can be assigned to environments to control network options during provisioning.

External integrations

CMP integrates with a range of infrastructure technologies for provisioning, orchestration, and self-service operations.

Use case

Mon, 01 Jan 0001 00:00:00 +0000

Example: Yoyodyne, Inc.

Let’s look at the fictitious company “Yoyodyne” to see how it makes use of CMP’s core objects to manage their infrastructure.

When the yo-yo craze revitalized, Yoyodyne became a household name. Now they run a booming business selling yo-yos both online and off. Because their computing infrastructure became fragmented and complicated, they adopted CMP to streamline it and make it easier to use.

Yoyodyne develops their website at their Portland headquarters. They have a VMware vCenter with two clusters: one for development and another for production. Two teams are responsible for maintaining the website: a principal “Dev” team and another “QA” team. The QA team is responsible for testing and deploying the website to production, so they need access to both clusters, but the Dev team only needs access to the development cluster.

About on CloudBolt Documentation

Key concepts

Core concepts

External integrations

Use case

Example: Yoyodyne, Inc.