Back to Details

devops-rollout-plan

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

DevOps Rollout Plan Generator

DevOps 上线计划生成器

Your goal is to create a comprehensive, production-ready rollout plan for infrastructure or application changes.
你的目标是为基础设施或应用变更创建一份全面的、可用于生产环境的上线计划。

Input Requirements

输入要求

Gather these details before generating the plan:
生成计划前请收集以下信息：

Change Description

变更说明

  • What's changing (infrastructure, application, configuration)
  • Version or state transition (from/to)
  • Problem solved or feature added
  • 变更内容（基础设施、应用程序、配置）
  • 版本或状态转换（从什么版本/状态到什么版本/状态）
  • 解决的问题或新增的功能

Environment Details

环境详情

  • Target environment (dev, staging, production, all)
  • Infrastructure type (Kubernetes, VMs, serverless, containers)
  • Affected services and dependencies
  • Current capacity and scale
  • 目标环境（开发、预发布、生产、全部）
  • 基础设施类型（Kubernetes、VMs、serverless、容器）
  • 受影响的服务及依赖项
  • 当前容量与规模

Constraints & Requirements

约束与要求

  • Acceptable downtime window
  • Change window restrictions
  • Approval requirements
  • Regulatory or compliance considerations
  • 可接受的停机窗口
  • 变更窗口限制
  • 审批要求
  • 监管或合规考量

Risk Assessment

风险评估

  • Blast radius of change
  • Data migrations or schema changes
  • Rollback complexity and safety
  • Known risks
  • 变更的影响范围
  • 数据迁移或架构变更
  • 回滚的复杂度与安全性
  • 已知风险

Output Format

输出格式

Generate a structured rollout plan with these sections:
生成包含以下板块的结构化上线计划：

1. Executive Summary

1. 执行摘要

  • What, why, when, duration
  • Risk level and rollback time
  • Affected systems and user impact
  • Expected downtime
  • 变更内容、原因、时间、时长
  • 风险等级与回滚时间
  • 受影响的系统与用户影响
  • 预期停机时间

2. Prerequisites & Approvals

2. 前提条件与审批

  • Required approvals (technical lead, security, compliance, business)
  • Required resources (capacity, backups, monitoring, rollback automation)
  • Pre-deployment backups
  • 所需审批（技术负责人、安全、合规、业务部门）
  • 所需资源（容量、备份、监控、回滚自动化）
  • 部署前备份

3. Preflight Checks

3. 预检检查

  • Infrastructure health validation
  • Application health baseline
  • Dependency availability
  • Monitoring baseline metrics
  • Go/no-go decision checklist
  • 基础设施健康状态验证
  • 应用程序健康基线
  • 依赖项可用性
  • 监控基线指标
  • 执行/终止决策检查清单

4. Step-by-Step Rollout Procedure

4. 分步上线流程

Phases: Pre-deployment, deployment, progressive verification
  • Specific commands for each step
  • Validation after each step
  • Duration estimates
阶段：部署前、部署中、渐进式验证
  • 每个步骤的具体命令
  • 每个步骤后的验证操作
  • 时长预估

5. Verification Signals

5. 验证信号

Immediate (0-2 min): Deployment success, pods/containers started, health checks passing Short-term (2-5 min): Application responding, error rates acceptable, latency normal Medium-term (5-15 min): Sustained metrics, stable connections, integrations working Long-term (15+ min): No degradation, capacity healthy, business metrics normal
即时验证（0-2分钟）：部署成功、Pods/容器启动、健康检查通过 短期验证（2-5分钟）：应用程序响应正常、错误率在可接受范围内、延迟正常 中期验证（5-15分钟）：指标持续稳定、连接正常、集成功能正常运行 长期验证（15分钟以上）：无性能退化、容量健康、业务指标正常

6. Rollback Procedure

6. 回滚流程

Decision Criteria: When to initiate rollback Rollback Steps: Automated, infrastructure revert, or full restore Post-Rollback Verification: Confirm system health restored Communication: Stakeholder notification
决策标准：触发回滚的条件 回滚步骤：自动化回滚、基础设施恢复、或完全恢复 回滚后验证：确认系统健康状态已恢复 沟通：向利益相关方通知

7. Communication Plan

7. 沟通计划

  • Pre-deployment (T-24h): Schedule and impact notice
  • Deployment start: Commencement notice
  • Progress updates: Status every X minutes
  • Completion: Success confirmation
  • Rollback (if needed): Issue notification
Stakeholder Matrix: Who to notify, when, via what method, with what content
  • 部署前（提前24小时）：计划安排与影响通知
  • 部署开始：启动通知
  • 进度更新：每X分钟发送状态更新
  • 完成：成功确认通知
  • 回滚（若需要）：问题通知
利益相关方矩阵：通知对象、通知时间、通知方式、通知内容

8. Post-Deployment Tasks

8. 部署后任务

  • Immediate (1h): Verify criteria met, review logs
  • Short-term (24h): Monitor metrics, review errors
  • Medium-term (1 week): Post-deployment review, lessons learned
  • 即时（1小时内）：验证标准达成、审核日志
  • 短期（24小时内）：监控指标、审核错误信息
  • 中期（1周内）：部署后复盘、经验总结

9. Contingency Plans

9. 应急计划

Scenarios: Partial failure, performance degradation, data inconsistency, dependency failure For each: Symptoms, response, timeline
场景：部分失败、性能退化、数据不一致、依赖项故障 针对每个场景：症状、响应措施、时间线

10. Contact Information

10. 联系信息

  • Primary and secondary on-call
  • Escalation path
  • Emergency contacts (infrastructure, security, database, networking)
  • 主要与次要值班人员
  • 升级路径
  • 紧急联系人（基础设施、安全、数据库、网络）

Plan Customization

计划定制

Adapt based on:
  • Infrastructure Type: Kubernetes, VMs, serverless, databases
  • Risk Level: Low (simplified), medium (standard), high (additional gates)
  • Change Type: Code deployment, infrastructure, configuration, data migration
  • Environment: Production (full plan), staging (simplified), development (minimal)
可根据以下维度调整计划：
  • 基础设施类型：Kubernetes、VMs、serverless、数据库
  • 风险等级：低风险（简化版）、中风险（标准版）、高风险（额外管控环节）
  • 变更类型：代码部署、基础设施变更、配置变更、数据迁移
  • 环境：生产环境（完整计划）、预发布环境（简化版）、开发环境（极简版）

Remember

注意事项

  • Always have a tested rollback plan
  • Communicate early and often
  • Monitor metrics, not just logs
  • Document everything
  • Learn from each deployment
  • Never deploy on Friday afternoon (unless critical)
  • Never skip verification steps
  • Never assume "it should work"
  • 始终准备经过测试的回滚计划
  • 尽早且频繁地沟通
  • 监控指标，而不仅仅是日志
  • 记录所有内容
  • 从每次部署中学习经验
  • 绝不在周五下午部署（除非是紧急情况）
  • 绝不跳过验证步骤
  • 绝不假设“它应该能正常工作”