<div style><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">Hi Michael,</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px"><br></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">
The reason why VMs have to be shut down is because the storage model has changed quite a bit in this last version, and we couldn't come up with a migration process that felt solid enough for any deployment.</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">
<br></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">But, since you said you are ready for lots of manual work, let's try this:</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">
<br></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">First, edit /usr/lib/one/ruby/onedb/3.3.0_to_3.3.80.rb and comment out lines 35 to 60 [1] to disable the VM status check.</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">
Then upgrade the opennebula DB with the onedb command [2]</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px"><br></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">
Before you start opennebula again, you need to adapt the previous VM storage directories to the new 3.4 hierarchy. Assuming you don't have VM_DIR nor DATASTORE_LOCATION defined in oned.conf, this is how the VM directories look in both versions:</div>
<div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px"><br></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">3.2:</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">
/var/lib/one/<vm_id>/images/disk.i</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">/var/lib/images/abcde</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">
<br></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">3.4:</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">/var/lib/one/datastores/0/<vm_id>/disk.i</div>
<div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">/var/lib/one/datastores/1/abcde</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px"><br></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">
So what you need to do in the front-end *and each host* is to individually link each existing VM dir:</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px"><br></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">
ln -s /var/lib/one/<vm_id>/images /var/lib/one/datastores/0/<vm_id></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px"><br></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">
Let me stress that this must be done in all the hosts.</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px"><br></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">
Please take into account that this is just the basic idea, and that *we haven't tested this*. You may run into problems depending on your infrastructure configuration. For instance, if you were using the tm_shared drivers, VMs containing persistent Images will have links like this one:</div>
<div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px"><br></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">/var/lib/one/7/images/disk.1 -> /var/lib/images/qwerty</div>
<div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px"><br></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">If you move the image files to their new destination in /var/lib/one/datastores/1, like the documentation says, you will break those VM disk links.</div>
<div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px"><br></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px"><br></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">
Another problem that may be important to you is that VMs over which you executed saveas [3] won't be able to save the changes back to the locked Image once the VM is shut down. In the best scenario, you will find the files inside /var/lib/one/<vm_id>/images/, but I'm not sure about this, you may lose your changes...</div>
<div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">You can locate these VMs looking for VM/DISK/SAVE_AS, and the Images all have "-" as the value of IMAGE/SOURCE.</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">
<br></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px"><br></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">As I said, this is not a tested or recommended procedure.</div>
<div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px"><br></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px"><br></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">
Good luck,</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">Carlos</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px"><br></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">
[1] <a href="http://dev.opennebula.org/projects/opennebula/repository/revisions/one-3.4/entry/src/onedb/3.3.0_to_3.3.80.rb" target="_blank" style="color:rgb(17,85,204)">http://dev.opennebula.org/projects/opennebula/repository/revisions/one-3.4/entry/src/onedb/3.3.0_to_3.3.80.rb</a></div>
<div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">[2] <a href="http://opennebula.org/documentation:rel3.4:upgrade" target="_blank" style="color:rgb(17,85,204)">http://opennebula.org/documentation:rel3.4:upgrade</a></div>
<div><font color="#222222" face="arial, sans-serif">[3] <a href="http://opennebula.org/documentation:archives:rel3.2:img_guide#save_changes">http://opennebula.org/documentation:archives:rel3.2:img_guide#save_changes</a></font></div>
<div><font color="#222222" face="arial, sans-serif"><br></font></div></div>--<br>Carlos Martín, MSc<br>Project Engineer<br>OpenNebula - The Open-source Solution for Data Center Virtualization<div><span style="border-collapse:collapse;color:rgb(136,136,136);font-family:arial,sans-serif;font-size:13px"><a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:cmartin@opennebula.org" target="_blank">cmartin@opennebula.org</a> | <a href="http://twitter.com/opennebula" target="_blank">@OpenNebula</a></span><span style="border-collapse:collapse;color:rgb(136,136,136);font-family:arial,sans-serif;font-size:13px"><a href="mailto:cmartin@opennebula.org" style="color:rgb(42,93,176)" target="_blank"></a></span></div>
<br>
<br><br><div class="gmail_quote">On Thu, Apr 12, 2012 at 2:41 PM, Michael Kutzner <span dir="ltr"><<a href="mailto:michael.kutzner@virtion.de">michael.kutzner@virtion.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello,<br>
<br>
first of all congratulations to the final 3.4 and many thanx for the hard work!<br>
<br>
I just wanted to upgrade to 3.4 and started reading.<br>
I noticed reading the upgrade guide that all active VMs have to be shut down.<br>
<br>
Is there any chance to upgrade without powering down all VMs? Even with lots of<br>
manual work?<br>
<br>
<br>
Many thanx,<br>
Michael<br>
<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
</blockquote></div><br>