Hey Radek - You are referring to the systemvm template upgrade. I was
asking for systemvm.iso (it has all the agent code) upgrade.
On 19/05/14 11:42 PM, "Radek Smigielski"
wrote:
>"CloudStack 4.2 (KVM) System Vm Upgrade"
>https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.2+(KVM
That is correct Mike. Thanks to you and Marcus for confirming this.
On 13/05/14 8:59 PM, "Mike Tutkowski" wrote:
>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 duri
"CloudStack 4.2 (KVM) System Vm Upgrade"
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.2+(KVM)+System+Vm+Upgrade
isn't what you looking for?
- Radoslaw Smigielski
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" 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
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 wrote:
> It is in the RPM/DEB. One installs the age
Hey Marcus,
I wonder if you might be familiar with this process?
Thanks!
On Mon, Apr 14, 2014 at 5:16 PM, Nitin Mehta 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 wo
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
