Hi,

I am planning to upgrade cloudstack from 4.11.3 to 4.15.2. I am planning to
create a parallel build i.e will create a new VM of 4.11.3 and restore the
DB and upgrade the management server to 4.15.2 and start the management
server to perform DB upgrade. Will this process be ok ?

OR should I directly install 4.15.2 on a new VM and DB upgrades can be
handled by 4.15.2 management server from 4.11.3 to 4.15.2 ?

Is it ok to upload system vm template 4.15.1 to my production 4.11.3
environment and restarting the MS host won't make any issue because of
newer systemVM template uploaded ?

Also I want to purge all my cloud_usage DB data before upgrading to a new
system. Is it ok that I can only restore the schema of cloud_usage database
to a new system and upgraded cloudstack usage service can upgrade
its tables and put the data in there ?
- Ammad Ali

Reply via email to