Difference between revisions of "GSP Virtualisation with Xen"
From PDP/Grid Wiki
Jump to navigationJump to search| Line 53: | Line 53: | ||
* NO need to change the version number of xapi | * NO need to change the version number of xapi | ||
* NO need to apply the security fix (obviously) | * NO need to apply the security fix (obviously) | ||
| + | |||
| + | == On the xapi version hack == | ||
| + | |||
| + | If you have applied the xapi version hack to 1.5beta (setting the xapi version to 6.0.99), you may run into limited trouble after the upgrade as the new master claims to be older than the slaves (and thus cannot control it or migrate VMs to it). Not being able to migrate VMs is a bummer, since then you cannot do a hitless rolling upgrade. So we need to fix it: download the [http://stal.nikhef.nl/cfg/XCP16up.sh post-install script from stal] (it writes out the two utility scripts) or do the manual process. Anyway, the solution is: | ||
| + | |||
| + | * COPY the original (XCP16) xapi file from <tt>/opt/xensource/bin/xapi</tt> to a safe place | ||
| + | * edit the version number to be 6.0.99 (like it was a hacked XCP15beta: | ||
| + | /etc/init.d/xapi stop | ||
| + | sed -i 's/1\.6\.10/6.0.99/g' xapi | ||
| + | /etc/init.d/xapi start | ||
| + | echo "Switched FROM original XCP16 1.6.10 TO XCP15-hack version 6.0.99" | ||
| + | * now you can control the slaves again. Upgrade the slaves, and then switch back by copying the saved xapi binary and restarting the service. | ||
| + | |||
| + | You can restart the service while VMs are running. You may also be able to switch back after upgrading just the master and migrate VMs from the target slaves to this master. | ||
= Networking = | = Networking = | ||
