Good idea, could you open a feature request?<div><br></div><div>BTW, would you mind sharing the libvirt hook you wrote?</div><div><br>Thanks!</div><div><div><br><div class="gmail_quote">On Thu, May 17, 2012 at 9:02 PM, fc lists <span dir="ltr"><<a href="mailto:fclists@pr-z.info" target="_blank">fclists@pr-z.info</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Brillant! , <br><br>that will perfectly work in my case. <br><br>I wrote the DS and TM drivers to work out of a single Target (per project more or less) with multiple LUNs ... that means that i only need 1 login (that i actually can perform outside of ONE as well as during the LN so to ensure that all hosts in the cluster are logged in to the ISCSI target) and then i can use a simple "iscsiadm -m session -R" to pick device for VM that is being live migrated.<br>
<br>The only thing that disappoint me a bit is that i will have to perform this configuration outside of openebula ... but i see your point about it.<br>I think it might be useful to have some kind of hook related to the live-migration command in opennebula, even if is just called when the live-migrate command is called. <br>
This way it would be possible to access the Image variables ...especially Source.<br><br>Thanks for pointing the link anyway, in my case will really do the trick.<span class="HOEnZb"><font color="#888888"><br><br>-FC</font></span><div class="HOEnZb">
<div class="h5"><br><br><br><br><div class="gmail_quote">On Wed, May 16, 2012 at 10:46 AM, Jaime Melis <span dir="ltr"><<a href="mailto:jmelis@opennebula.org" target="_blank">jmelis@opennebula.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<div><br></div><div>OpenNebula can't have control overt the internal live-migration process of the hypervisors. The iscsi actions should be perfectly synchronized with the live migration, otherwise an I/O error is likely to occur. That's the reason why this isn't out of the box supported with OpenNebula.</div>
<div><br>I believe the correct way to approach this is through hypervisor hooks:</div><div><a href="http://libvirt.org/hooks.html#qemu_migration" target="_blank">http://libvirt.org/hooks.html#qemu_migration</a></div><div>
<br></div><div>
cheers,</div>
<div>Jaime</div><div><br><div class="gmail_quote"><div><div>On Tue, May 15, 2012 at 8:56 PM, fc lists <span dir="ltr"><<a href="mailto:fclists@pr-z.info" target="_blank">fclists@pr-z.info</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>
Hi,<br><br>I am trying to hook up a NexentaStor ISCSI server with opennebula 3.4.1<br><br>I created a DS_MAD and TM_MAD out of the current "iscsi" ones and i got everything working fine ... other then live migration.<br>
<br>Things goes like this:<br><br>Create New Virtual Machine<br><br>oneadmin ssh to HOST1<br> - login into ISCSI<br> - LN the system datastore (NFS Shared) disk to the ISCSI device<br><br>live migrate from HOST1 to HOST2<br>
<br>At this point HOST 2 has no knowledge of ISCSI device ... because the FE never performed ISCSI login on host2.<br><br>"at first" i thought that the "MV" TM_MAD would be called for live-migration the same way it get executed for cold migration, but it does not seem so on my system.<br>
Cold migration works just fine because it actively login the ISCSI target in the HOST2 , with live-migration it seems like ONE does not really interact with the cluster other then performing the libvirt/kvm live migration.<br>
<br>As a proof of concept it was enough to manually login the ISCSI target on HOST2 and live-migration worked perfectly.<br><br>Is there any hook that i can use to manage this operation ? Ideally it would be enough to get the Image SOURCE available to get it to work.<br>
<br>Thanks<span><font color="#888888"><br>-FC<br>
</font></span><br></div></div>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org" target="_blank">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>
<br></blockquote></div><span><font color="#888888"><br></font></span></div><span><font color="#888888"><br clear="all"><div><br></div>-- <br>Jaime Melis<br>Project Engineer<br>OpenNebula - The Open Source Toolkit for Cloud Computing<br>
<a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:jmelis@opennebula.org" target="_blank">jmelis@opennebula.org</a><br>
</font></span></blockquote></div><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Jaime Melis<br>Project Engineer<br>OpenNebula - The Open Source Toolkit for Cloud Computing<br><a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:jmelis@opennebula.org" target="_blank">jmelis@opennebula.org</a><br>
</div></div>