feat: add migration-architect POWERFUL-tier skill
This commit is contained in:
@@ -0,0 +1,161 @@
|
||||
================================================================================
|
||||
MIGRATION PLAN: 23a52ed1507f
|
||||
================================================================================
|
||||
Source System: PostgreSQL 13 Production Database
|
||||
Target System: PostgreSQL 15 Cloud Database
|
||||
Migration Type: DATABASE
|
||||
Complexity Level: CRITICAL
|
||||
Estimated Duration: 95 hours (4.0 days)
|
||||
Created: 2026-02-16T13:47:23.704502
|
||||
|
||||
MIGRATION PHASES
|
||||
----------------------------------------
|
||||
1. PREPARATION (19h)
|
||||
Description: Prepare systems and teams for migration
|
||||
Risk Level: MEDIUM
|
||||
Tasks:
|
||||
• Backup source system
|
||||
• Set up monitoring and alerting
|
||||
• Prepare rollback procedures
|
||||
• Communicate migration timeline
|
||||
• Validate prerequisites
|
||||
Success Criteria:
|
||||
✓ All backups completed successfully
|
||||
✓ Monitoring systems operational
|
||||
✓ Team members briefed and ready
|
||||
✓ Rollback procedures tested
|
||||
|
||||
2. EXPAND (19h)
|
||||
Description: Execute expand phase
|
||||
Risk Level: MEDIUM
|
||||
Dependencies: preparation
|
||||
Tasks:
|
||||
• Complete expand activities
|
||||
Success Criteria:
|
||||
✓ Expand phase completed successfully
|
||||
|
||||
3. MIGRATE (19h)
|
||||
Description: Execute migrate phase
|
||||
Risk Level: MEDIUM
|
||||
Dependencies: expand
|
||||
Tasks:
|
||||
• Complete migrate activities
|
||||
Success Criteria:
|
||||
✓ Migrate phase completed successfully
|
||||
|
||||
4. CONTRACT (19h)
|
||||
Description: Execute contract phase
|
||||
Risk Level: MEDIUM
|
||||
Dependencies: migrate
|
||||
Tasks:
|
||||
• Complete contract activities
|
||||
Success Criteria:
|
||||
✓ Contract phase completed successfully
|
||||
|
||||
5. CLEANUP (19h)
|
||||
Description: Execute cleanup phase
|
||||
Risk Level: MEDIUM
|
||||
Dependencies: contract
|
||||
Tasks:
|
||||
• Complete cleanup activities
|
||||
Success Criteria:
|
||||
✓ Cleanup phase completed successfully
|
||||
|
||||
RISK ASSESSMENT
|
||||
----------------------------------------
|
||||
CRITICAL SEVERITY RISKS:
|
||||
• Insufficient rollback testing
|
||||
Category: operational
|
||||
Probability: high | Impact: critical
|
||||
Mitigation: Execute full rollback procedures in staging environment
|
||||
Owner: QA Team
|
||||
|
||||
HIGH SEVERITY RISKS:
|
||||
• Data corruption during migration
|
||||
Category: technical
|
||||
Probability: low | Impact: critical
|
||||
Mitigation: Implement comprehensive backup and validation procedures
|
||||
Owner: DBA Team
|
||||
|
||||
• Extended downtime due to migration complexity
|
||||
Category: technical
|
||||
Probability: medium | Impact: high
|
||||
Mitigation: Use blue-green deployment and phased migration approach
|
||||
Owner: DevOps Team
|
||||
|
||||
• Business process disruption
|
||||
Category: business
|
||||
Probability: medium | Impact: high
|
||||
Mitigation: Communicate timeline and provide alternate workflows
|
||||
Owner: Business Owner
|
||||
|
||||
• Zero-downtime requirement increases complexity
|
||||
Category: business
|
||||
Probability: high | Impact: medium
|
||||
Mitigation: Implement blue-green deployment or rolling update strategy
|
||||
Owner: DevOps Team
|
||||
|
||||
• Regulatory compliance requirements
|
||||
Category: compliance
|
||||
Probability: medium | Impact: high
|
||||
Mitigation: Ensure all compliance checks are integrated into migration process
|
||||
Owner: Compliance Team
|
||||
|
||||
ROLLBACK STRATEGY
|
||||
----------------------------------------
|
||||
Rollback Triggers:
|
||||
• Critical system failure
|
||||
• Data corruption detected
|
||||
• Migration timeline exceeded by > 50%
|
||||
• Business-critical functionality unavailable
|
||||
• Security breach detected
|
||||
• Stakeholder decision to abort
|
||||
|
||||
Rollback Phases:
|
||||
CLEANUP:
|
||||
- Revert cleanup changes
|
||||
- Restore pre-cleanup state
|
||||
- Validate cleanup rollback success
|
||||
Estimated Time: 285 minutes
|
||||
|
||||
CONTRACT:
|
||||
- Revert contract changes
|
||||
- Restore pre-contract state
|
||||
- Validate contract rollback success
|
||||
Estimated Time: 285 minutes
|
||||
|
||||
MIGRATE:
|
||||
- Revert migrate changes
|
||||
- Restore pre-migrate state
|
||||
- Validate migrate rollback success
|
||||
Estimated Time: 285 minutes
|
||||
|
||||
EXPAND:
|
||||
- Revert expand changes
|
||||
- Restore pre-expand state
|
||||
- Validate expand rollback success
|
||||
Estimated Time: 285 minutes
|
||||
|
||||
PREPARATION:
|
||||
- Revert preparation changes
|
||||
- Restore pre-preparation state
|
||||
- Validate preparation rollback success
|
||||
Estimated Time: 285 minutes
|
||||
|
||||
SUCCESS CRITERIA
|
||||
----------------------------------------
|
||||
✓ All data successfully migrated with 100% integrity
|
||||
✓ System performance meets or exceeds baseline
|
||||
✓ All business processes functioning normally
|
||||
✓ No critical security vulnerabilities introduced
|
||||
✓ Stakeholder acceptance criteria met
|
||||
✓ Documentation and runbooks updated
|
||||
|
||||
STAKEHOLDERS
|
||||
----------------------------------------
|
||||
• Business Owner
|
||||
• Technical Lead
|
||||
• DevOps Team
|
||||
• QA Team
|
||||
• Security Team
|
||||
• End Users
|
||||
Reference in New Issue
Block a user