Typically, an upgrade from within the 4.x stream *should* not be too painful. Obviously apply due diligence and read release notes, test in a lab when possible, etc to all the obvious pre-check/validation you would do for more other systems you upgrade.
An upgrade can potentially consist of making some DB changes/tweaks, upgrade existing packages installed on the managers, as well as the system ISO used for console, system, virtual routers. The VM's that are running at the time keep running and should only get grumpy when their virtual router disappears for a while. The more VR's you have, the longer this process takes. Anyhoot, this is a very brief response since I am as tired as a stinky rotten banana. Point being, create a similar environment, test the upgrade there. When ready for the real thing back everything up 9000 times, do one more backup, and then let 'er rip. HTH. Good luck. (I am sure that tones of people on this list can share their experiences too.. bribe them with Justin Bieber photo's or something...) On Tue, Feb 24, 2015 at 2:01 AM, Ahmad Emneina <aemne...@gmail.com> wrote: > There isn't much detail here but gues VM's shouldn't be impacted here. > There might be guest network interruptions when upgrading the routers > (assuming advanced zone here). Hope that helps... > > Ahmad E > > > On Feb 23, 2015, at 1:46 AM, kangkan mahanta <kangkan.maha...@gmail.com> > wrote: > > > > Hi, > > > > We are using cloudstack private cloud infra. We want to upgrade from > > version 4.2.1 to 4.4. Please let me know the impact on running virtual > > machines during the activity. > > > > Regards, > > Kangkan Mahanta Kashyap >
