Thanks a lot Marcus, will probably activate the recreate on reboot stuff.
You said you manually reboot/recreate VRs after upgrade, instead of using
the script - you finish all VRs upgrade/recreate before actually giving
client access to cloudstack again?
I mean - there is operational risk as you
I've never used the official script to upgrade. I always set to the
global setting to recreate on reboot of systemvms, it has been more
robust for me to do it the cloudy way and get a fresh vm on every
boot. With various issues that have arisen in the past (file system
filling up, fsck required on
Thanks Markus.
So anyway, I need to make some time to upgrade to 4.3.2.
Can I manually reboot VR/s one by one after the upgrade is done (instead of
using the script for rebooting ssvm, cpvm, and 66 VRs...)
And is this reallt reboot inside OS - not destroying and recreating VRs ???
Or would you s
Hi,
It's impossible to know without looking at the changes in 4.3.1,
4.3.2. Your routers will be running old code, and will probably work,
but might not, e.g. if a router script is called with parameters that
don't exist in the version of the script that the router runs. If you
don't plan on mak
Hi,
I was wondering is it possibe to update/replace the VR template somehow
without actually updating the ACS.
I'm running ACS 4.3.0, and having some issues with remote IP not being
really shown during Port Forwarding and Static NAT (VR also does SNAT
beside the DNAT)
I know question is a little
