GitHub user shakibshalim74 created a discussion: Best Practices for CloudStack Upgrade (Current Version: 4.19.3.0) – Request for Recommendations
Hello, We are planning to upgrade our CloudStack environment and would appreciate guidance on best practices and rollback strategies. Current Setup: CloudStack: 4.19.3.0 Number of Management Servers: 3 Number of Database Server: 1 KVM Hosts: 30 Number of running instances : 400 Looking for recommendations on: Best-practice upgrade sequence (Management, Data Base, KVM hosts) Known issues when upgrading from 4.19.3.0 Key validation checks post-upgrade Reliable rollback methods (DB backup/restore, KVM agent rollback, System VM/VR template rollback, config and certificate backups) Some question regarding the upgrade process: We plan to upgrade the Management and DB servers first according to the official upgrade documentation. If we start upgraded management service first, and then upgrade KVM hosts one by one, are there any caveats? We are asking this question as the official upgrade documentation suggests starting the management server at the very end of the upgradation process after all agents are being upgraded. Is it safe to run upgraded Management+DB services with hypervisors still on the older version? or should we need all Hypervisor Agents to be upgraded before starting Management services? Any best-practice recommendations or real-world feedback would be highly appreciated. GitHub link: https://github.com/apache/cloudstack/discussions/12377 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
