How would Skytap be represented in the CMDB lining up with CSDM

[l337]

Skytap enables push button Test/Dev environments to be created.

I have the Skytap Prod application represented in the cmdb_ci_service_auto table.

I would like the Test/Dev environments created within Skytap as individual CIs related to Skytap Prod however I am unsure what class these should be created in according to CSDM.

I welcome all suggestions all your suggestions.

Thanks!

[mayabhai]

CMDB (Configuration Management Database) and CSDM (Common Service Data Model) are both concepts used in IT Service Management (ITSM) and ITIL (Information Technology Infrastructure Library) practices. The CMDB is a database that contains information about the configuration items (CIs) in an IT infrastructure, while CSDM is a framework for organizing and structuring the data within the CMDB. Skytap is a cloud service provider that offers virtualized environments. When representing Skytap in the CMDB in alignment with CSDM, you would consider the following:

1. Identification of Configuration Items (CIs):

• Identify the key configuration items related to Skytap in your IT environment. These might include virtual machines, networks, and configurations specific to Skytap.

2. Relationships:

• Define relationships between Skytap CIs and other CIs in the CMDB. For example, Skytap environments may have connections to databases, applications, or external services.

3. CSDM Alignment:

• Align Skytap configuration items with the CSDM framework. CSDM provides a standardized structure for organizing configuration items. For instance:
  • Service Offering: Skytap environments can be associated with a specific service offering or business service.
  • Service Instance: Each Skytap environment can be considered a service instance.
  • Application: If Skytap is used for hosting specific applications, associate the applications with the appropriate Skytap environment.

4. Attributes and Characteristics:

• Define attributes and characteristics for Skytap CIs based on CSDM. For example, capture information such as environment type, purpose, owner, and lifecycle status.

5. Lifecycle States:

• Define lifecycle states for Skytap CIs. This can include states like "Provisioning," "Active," "Suspended," or "Decommissioned" based on the stages in the lifecycle of a Skytap environment.

6. Impact and Dependencies:

• Identify the impact of Skytap environments on other CIs and vice versa. Understand the dependencies to ensure accurate representation in the CMDB.

7. Event Management:

• Implement event management processes to capture changes, incidents, and problems related to Skytap environments. This contributes to maintaining accurate and up-to-date information in the CMDB.

8. Integrate with Service Management Processes:

• Integrate Skytap CIs with incident, problem, change, and other service management processes. This ensures that the CMDB is part of broader ITSM practices.

9. Documentation:

• Document the Skytap-specific information in the CMDB, including configuration details, specifications, and any custom attributes relevant to your organization.

10. Automation and Discovery:

• Leverage automation and discovery tools to keep the CMDB updated with changes in the Skytap environment. Automated processes help maintain accuracy and consistency.

11. Continuous Improvement:

• Regularly review and update the CMDB to reflect changes in the Skytap environment. Continuous improvement ensures that the CMDB remains a reliable source of information.

By aligning the representation of Skytap in the CMDB with CSDM, you establish a structured and standardized approach to managing configuration data, enabling better IT service management and governance.