Thanks, Marcus So, it sounds like when you upgrade your CloudStack Management Server(s), you need to update all of your KVM hosts anyways, so you get the new System VM ISO during that agent-side update.
On Tue, May 13, 2014 at 9:14 PM, Marcus <shadow...@gmail.com> wrote: > It is in the RPM/DEB. One installs the agent and common packages on a KVM > host. > On Apr 14, 2014 7:16 PM, "Nitin Mehta" <nitin.me...@citrix.com> wrote: > > > I am curious as to how does the systemvm.iso gets pushed onto the KVM > host > > ? > > Lets say I upgrade from 4.2.1 to 4.3 and there is some ssvm agent code > > change, I would expect the new systemvm.iso getting pushed from MS to the > > KVM host and stop/start ssvm would have the new code into affect. > > I want to know the mechanism which detects the version change and does > > this magic. > > > > Thanks, > > -Nitin > > > -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play> *™*
