You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Ian Service <is...@ts2.ca> on 2013/12/10 12:35:18 UTC
Upgrade System VM Template
I'm having no end of NAT issues with the System VM template I installed
with 4.1 and I noticed there's a newer one available. Is there a
documented upgrade procedure somewhere or is it as simple as install the
new one and update a mysql table to point to the new template?
Thanks,
- Ian
Re: Upgrade System VM Template
Posted by Ian Service <is...@ts2.ca>.
Blogged for future generations...
http://www.weezey.com/2013/12/how-to-upgrade-the-cloudstack-systemvm-template/
- Ian
On Wed, Dec 11, 2013 at 12:04 PM, Ian Service <is...@ts2.ca> wrote:
> I've registered the new systemvm template and named it
> systemvm-xenserver-4.2 as per the documentation but vr/ssvm/console vms
> when destroyed come back as Cloudstack Release 3.0 instead of 4.2.
>
> So what hooks the system into knowing that that template is to be used as
> the systemvm?
>
> Dug into the source to find some schema updates from older versions to
> newer to trigger what I wanted and resolved what I needed with the
> following mySQL:
>
> UPDATE `cloud`.`vm_template` SET type='SYSTEM' WHERE
> name='systemvm-xenserver-4.2';
> UPDATE vm_instance SET vm_template_id=(SELECT id FROM vm_template WHERE
> name='systemvm-xenserver-4.2' AND removed IS NULL) WHERE vm_template_id=1;
>
> Then destroyed and respawned the ssvm and console vms and they all came up
> using the new template.
>
> root@s-300-VM:~# cat /etc/cloudstack-release
> Cloudstack Release 4.2.0 Sat Jul 13 04:17:59 UTC 2013
>
> Router did not...
>
> root@r-302-VM:~# cat /etc/cloudstack-release
> Cloudstack Release 3.0 Mon Feb 6 15:10:04 PST 2012
>
> After another hour of combing code (and doing real work) I found that the
> server/src/com/cloud/configuration/Config.java has a method called
> RouterTemplateXen which returns from the SQL with whatever has the name
> "SystemVM Template (XenServer)" so updating my new template accordingly...
>
> UPDATE `cloud`.`vm_template` SET name="SystemVM Template (XenServer)"
> where id=(SELECT id FROM vm_template WHERE name='systemvm-xenserver-4.2'
> AND removed IS NULL);
>
> And now the network spawns from the new system VM template.
>
> root@r-312-VM:~# cat /etc/cloudstack-release
> Cloudstack Release 4.2.0 Sat Jul 13 04:17:59 UTC 2013
> root@r-312-VM:~# uname -a
> Linux r-312-VM 3.2.0-4-686-pae #1 SMP Debian 3.2.41-2 i686 GNU/Linux
>
> All that's left now is to figure out if it solves all my NAT issues with
> it's fancy new kernel.
>
> - Ian
>
>
>
> On Tue, Dec 10, 2013 at 4:22 PM, Chiradeep Vittal <
> Chiradeep.Vittal@citrix.com> wrote:
>
>> You could use it, but with the caveat that no-one has tested this
>> extensively.
>> Upgrade instructions are generally included with the install guide.
>>
>> On 12/10/13 3:35 AM, "Ian Service" <is...@ts2.ca> wrote:
>>
>> >I'm having no end of NAT issues with the System VM template I installed
>> >with 4.1 and I noticed there's a newer one available. Is there a
>> >documented upgrade procedure somewhere or is it as simple as install the
>> >new one and update a mysql table to point to the new template?
>> >
>> >Thanks,
>> >
>> >- Ian
>>
>>
>
Re: Upgrade System VM Template
Posted by Ian Service <is...@ts2.ca>.
I've registered the new systemvm template and named it
systemvm-xenserver-4.2 as per the documentation but vr/ssvm/console vms
when destroyed come back as Cloudstack Release 3.0 instead of 4.2.
So what hooks the system into knowing that that template is to be used as
the systemvm?
Dug into the source to find some schema updates from older versions to
newer to trigger what I wanted and resolved what I needed with the
following mySQL:
UPDATE `cloud`.`vm_template` SET type='SYSTEM' WHERE
name='systemvm-xenserver-4.2';
UPDATE vm_instance SET vm_template_id=(SELECT id FROM vm_template WHERE
name='systemvm-xenserver-4.2' AND removed IS NULL) WHERE vm_template_id=1;
Then destroyed and respawned the ssvm and console vms and they all came up
using the new template.
root@s-300-VM:~# cat /etc/cloudstack-release
Cloudstack Release 4.2.0 Sat Jul 13 04:17:59 UTC 2013
Router did not...
root@r-302-VM:~# cat /etc/cloudstack-release
Cloudstack Release 3.0 Mon Feb 6 15:10:04 PST 2012
After another hour of combing code (and doing real work) I found that the
server/src/com/cloud/configuration/Config.java has a method called
RouterTemplateXen which returns from the SQL with whatever has the name
"SystemVM Template (XenServer)" so updating my new template accordingly...
UPDATE `cloud`.`vm_template` SET name="SystemVM Template (XenServer)" where
id=(SELECT id FROM vm_template WHERE name='systemvm-xenserver-4.2' AND
removed IS NULL);
And now the network spawns from the new system VM template.
root@r-312-VM:~# cat /etc/cloudstack-release
Cloudstack Release 4.2.0 Sat Jul 13 04:17:59 UTC 2013
root@r-312-VM:~# uname -a
Linux r-312-VM 3.2.0-4-686-pae #1 SMP Debian 3.2.41-2 i686 GNU/Linux
All that's left now is to figure out if it solves all my NAT issues with
it's fancy new kernel.
- Ian
On Tue, Dec 10, 2013 at 4:22 PM, Chiradeep Vittal <
Chiradeep.Vittal@citrix.com> wrote:
> You could use it, but with the caveat that no-one has tested this
> extensively.
> Upgrade instructions are generally included with the install guide.
>
> On 12/10/13 3:35 AM, "Ian Service" <is...@ts2.ca> wrote:
>
> >I'm having no end of NAT issues with the System VM template I installed
> >with 4.1 and I noticed there's a newer one available. Is there a
> >documented upgrade procedure somewhere or is it as simple as install the
> >new one and update a mysql table to point to the new template?
> >
> >Thanks,
> >
> >- Ian
>
>
Re: Upgrade System VM Template
Posted by Chiradeep Vittal <Ch...@citrix.com>.
You could use it, but with the caveat that no-one has tested this
extensively.
Upgrade instructions are generally included with the install guide.
On 12/10/13 3:35 AM, "Ian Service" <is...@ts2.ca> wrote:
>I'm having no end of NAT issues with the System VM template I installed
>with 4.1 and I noticed there's a newer one available. Is there a
>documented upgrade procedure somewhere or is it as simple as install the
>new one and update a mysql table to point to the new template?
>
>Thanks,
>
>- Ian