ashutoshsrivastava17/skill-library/configuration-management

Configuration Management

Process

Step 1: Define CMDB Scope

Step 2: Design CI Schema

Step 3: Map Relationships

Step 4: Automate Discovery

Step 5: Enable Impact Analysis

When a change is proposed:

1. Identify affected CI
2. Traverse dependency graph
3. List all downstream services/users impacted
4. Calculate risk score based on CI criticality

Step 6: Maintain Data Quality

Output Format

## CMDB Design: [Scope]
### CI Types: [table with schema]
### Relationships: [dependency model]
### Discovery: [automation approach]
### Quality: [metrics and targets]

Quality Checklist

• [ ] CI types cover critical infrastructure and applications
• [ ] Relationships enable impact analysis
• [ ] Discovery automation reduces manual maintenance
• [ ] Data quality metrics are tracked
• [ ] Change management integrates with CMDB

Edge Cases

• For cloud-native environments, treat infrastructure as ephemeral
• If starting from scratch, focus on critical services first
• For hybrid environments, ensure cross-platform visibility