Auto-sync: 2026-04-24 04:02
This commit is contained in:
56
wiki/concepts/Standard-Change.md
Normal file
56
wiki/concepts/Standard-Change.md
Normal file
@@ -0,0 +1,56 @@
|
||||
---
|
||||
title: "Standard Change"
|
||||
type: concept
|
||||
tags: [Change-Management, ITSM, Automation, IaC, CI-CD]
|
||||
last_updated: 2026-04-14
|
||||
---
|
||||
|
||||
## Definition
|
||||
|
||||
Standard Change(标准变更)是一种预批准的变更类型,无需变更咨询委员会(CAB)的审批。在理想的 DevOps/SRE 实践中,标准变更应实现完全自动化,通过 IaC(基础设施即代码)+ CI/CD Pipeline 实现。
|
||||
|
||||
## Characteristics
|
||||
|
||||
|| Attribute | Value |
|
||||
|-----------|--------|
|
||||
| Approval Required | 否(预批准) |
|
||||
| CAB Involvement | 无需 |
|
||||
| Automation Level | 完全自动化(IaC + CI/CD) |
|
||||
| Risk Level | 低(已知变更,已评估) |
|
||||
| Change Window | 无限制 |
|
||||
|
||||
## Implementation
|
||||
|
||||
标准变更的实现依赖于以下技术栈:
|
||||
|
||||
1. **IaC(基础设施即代码)**:Terraform/Terragrunt 声明式定义基础设施
|
||||
2. **CI/CD Pipeline**:Jenkins/GitHub Actions 自动执行 plan/apply
|
||||
3. **Automated Testing**:在部署前自动验证基础设施变更
|
||||
4. **Tagging Standards**:符合 AWS 标签规范,确保 Checkpoint 防火墙正确放行
|
||||
|
||||
## Example Use Cases
|
||||
|
||||
- AWS 标签验证(Tag Validation Tool)自动扫描资源合规性
|
||||
- VPC 自动化供给(Topic 61):CIDR ≤ /22 自动审批
|
||||
- 标准 AMI 更新(Topic 50):自动构建和发布
|
||||
|
||||
## Relationship with Other Change Types
|
||||
|
||||
```
|
||||
Standard Change ──(通过自动化提升)──→ Normal Change
|
||||
↑
|
||||
CAB 审批
|
||||
有风险影响
|
||||
|
||||
Emergency Change ──(CAPA 修复根因)──→ Standard Change
|
||||
↓
|
||||
立即执行
|
||||
```
|
||||
|
||||
## Goal
|
||||
|
||||
将尽可能多的变更归类为标准变更,通过自动化减少人工审批负担,提高变更频率和可靠性。
|
||||
|
||||
## Sources
|
||||
|
||||
- [[ctp-topic-30-managing-change]]
|
||||
Reference in New Issue
Block a user