Go-Live War Room(上线作战室)
知识库位置:
FDE Knowledge Base/07 Playbooks/09-Go-Live-War-Room.md
Playbook Metadata(手册元数据)
Section titled “Playbook Metadata(手册元数据)”Playbook ID: PB-009
Stage(所属阶段):Production(生产)
Primary Goal(主要目标):Complete deployment, validation and incident handling under a clear command structure.(在清晰的指挥与沟通机制下完成部署、验证与故障处理。)
Typical Duration(典型时长):数小时(视发布窗口)
Primary Audience(主要使用者):FDE + Engineering + Customer IT
Difficulty(难度):Advanced(高级)
Status: CoreVersion: v0.1Objective(目标)
Section titled “Objective(目标)”Production(生产)上线是高风险事件。
War Room(作战室)的目标是:
在一个清晰的指挥和沟通机制下完成部署、验证和故障处理。
When to Use(适用场景)
Section titled “When to Use(适用场景)”适合:
- Major Production Launch(重大生产上线)
- Critical Customer Workflow(关键客户流程)
- Large User Rollout(大批用户放量)
- High-risk Migration(高风险迁移)
- Significant Integration Change(重大集成变更)
简单低风险 Release(发布)未必需要完整 War Room。
Roles(角色)
Section titled “Roles(角色)”必须明确:
Release Lead(发布负责人)
Section titled “Release Lead(发布负责人)”最终协调上线。
客户和技术之间协调。
Engineering Owner(工程负责人)
Section titled “Engineering Owner(工程负责人)”负责应用。
Infrastructure Owner(基础设施负责人)
Section titled “Infrastructure Owner(基础设施负责人)”负责环境。
Customer IT(客户信息技术部门)
Section titled “Customer IT(客户信息技术部门)”负责客户系统。
Security(安全团队)
Section titled “Security(安全团队)”如需要。
Business Validator(业务验证人)
Section titled “Business Validator(业务验证人)”验证业务流程。
Incident Commander(事故指挥官)
Section titled “Incident Commander(事故指挥官)”如上线出现重大问题,接管 Incident(事故)处理。
Pre-Go-Live Checklist(上线前检查)
Section titled “Pre-Go-Live Checklist(上线前检查)”至少确认:
Release approved(发布已批准)Backup complete(备份已完成)Rollback tested(回滚已演练)Monitoring ready(监控就绪)Alerts ready(告警就绪)Owners online(负责人在线)Dependencies healthy(依赖健康)Customer informed(客户已知情)War Room Timeline(作战室时间线)
Section titled “War Room Timeline(作战室时间线)”T-60 min
Section titled “T-60 min”- Attendance(人员就位)
- Final readiness(最终就绪确认)
- Dependency check(依赖检查)
- Freeze unrelated changes(冻结无关变更)
- Backup confirmation(备份确认)
- Monitoring opened(监控开启)
Deployment starts.(开始部署。)
执行:
Infrastructure Health(基础设施健康检查)↓Application Health(应用健康检查)↓Smoke Test(冒烟测试)↓Integration Test(集成测试)↓Critical Business Workflow(关键业务流程)↓Business Owner Validation(业务负责人验收)Status Communication(状态沟通)
Section titled “Status Communication(状态沟通)”固定状态:
Green(绿:正常)Amber(黄:有风险但可控)Red(红:受阻需决策)例如每 15 或 30 分钟更新一次,按项目风险决定。
Rollback Decision(回滚决策)
Section titled “Rollback Decision(回滚决策)”必须提前定义:
什么情况下回滚?
例如:
- Critical workflow unavailable(关键流程不可用)
- Data corruption(数据损坏)
- Severe security issue(严重安全问题)
- Error rate exceeds agreed threshold(错误率超过约定阈值)
- Dependency incompatible(依赖不兼容)
不要出问题后才讨论。
Incident During Go-Live(上线期间的事故)
Section titled “Incident During Go-Live(上线期间的事故)”如果出现重大问题:
Detect(发现)↓Assess Severity(评估严重度)↓Mitigate(缓解)↓Rollback if Needed(必要时回滚)↓Communicate(沟通)↓Root Cause Later(事后找根因)上线窗口内优先:
恢复业务。
不是马上进行完整 RCA(Root Cause Analysis,根本原因分析)。
End of War Room(作战室收尾)
Section titled “End of War Room(作战室收尾)”必须明确:
- Release status(发布状态)
- Known issues(已知问题)
- Open actions(未完行动)
- Hypercare plan(上线护航计划)
- Next update(下次更新时间)