Shared management
2 minute read
When adopting CMP, operations may keep working directly in vCenter or a cloud console while users order through CMP.
Two management models
CloudBolt exclusive
Operations teams have little or no access to change the services CMP provisions: every change goes through CMP. Only the changes a blueprint offers are possible; any configuration a team needs must be available as a resource action or a plugin on the blueprint’s Build tab. This suits production and tightly change-managed environments.
CloudBolt hybrid
Operations teams can make one-off or non-standard changes directly in the backend. Developers ask administrators to expose the configuration they need as actions or as parameters on the order form. This suits rapid testing of new capabilities, blueprint development, and environments that do not manage infrastructure as code.
Complex or highly procedural environments may arrive here, with both CMP and the operations team making changes. As a best practice, have CMP perform the operations it can, regardless of whether the operations team has backend access. Changes CMP makes are recorded, attributed, and repeatable.
Keeping CMP’s view current
When something other than CMP can change a resource, CMP’s copy of that resource can fall behind. Understand the sync process before designing for a hybrid model, since sync is what reconciles the two.
Copy as little backend state into the CMP database as you can. Anything you store there is only as current as the last sync. When users need live values, show them with a resource tab UI extension that reads from the provider.
Related
- Discovery/sync configuration: Reconciling CMP records with the provider’s.
- Develop blueprints: Building the actions that an exclusive model depends on.
- UI extensions: Showing live backend data on a resource tab.