<div dir="ltr">Hi,<div><br></div><div class="gmail_extra">On Wed, Sep 4, 2013 at 12:03 PM, Igor Laskovy <span dir="ltr"><<a href="mailto:igor.laskovy@gmail.com" target="_blank">igor.laskovy@gmail.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div>One further question - how Fault Tolerance mechanism (via HOST_HOOK) deal with this reservations? Does it reserved some "slots" for VMs recovery?</div></div></blockquote><div><br></div><div>
OpenNebula does not have any kind of reservation scheduling.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div> If not and if I at every turn manually don't control available resources on hosts those may cause to situation when my automatically recreated VMs will stuck in placement state.</div>
</div></blockquote><div><br></div><div>Yes, that may happen. But you still can implement a reservation mechanism.</div><div>I'm sure there are better alternatives, but this is a quick idea:</div><div><br></div><div>- Disable half of your hosts.</div>
<div>- For each enabled host, define a failover_host = <id> attribute in its template, pointing to one of the disabled hosts</div><div>- Modify the fault tolerance hook to make it enable the defined failover host.</div>
<div><br></div><div>Another quick hack is to create a dummy VM for each VM that you need to guarantee that reserved slot, using the requirements and current_vms features to deploy it in a host different from the original VM. Then delete that VM when the hook recreates the original VM...</div>
<div><br></div><div><br></div><div>Regards.</div><div><br></div><div><div dir="ltr">--<br>Join us at <a href="http://opennebulaconf.com" target="_blank">OpenNebulaConf2013</a> in Berlin, 24-26 September, 2013<br>--<div>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>
</div></div></div>
<br><br><div class="gmail_quote">On Wed, Sep 4, 2013 at 12:03 PM, Igor Laskovy <span dir="ltr"><<a href="mailto:igor.laskovy@gmail.com" target="_blank">igor.laskovy@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">Thank you for reply!<div><br></div><div>One further question - how Fault Tolerance mechanism (via HOST_HOOK) deal with this reservations? Does it reserved some "slots" for VMs recovery? If not and if I at every turn manually don't control available resources on hosts those may cause to situation when my automatically recreated VMs will stuck in placement state.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote"><div class="im">On Wed, Sep 4, 2013 at 12:23 PM, Carlos Martín Sánchez <span dir="ltr"><<a href="mailto:cmartin@opennebula.org" target="_blank">cmartin@opennebula.org</a>></span> wrote:<br>
</div><div><div class="h5"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div>
<div class="gmail_extra"><div class="gmail_quote"><div>On Tue, Sep 3, 2013 at 1:32 PM, Igor Laskovy <span dir="ltr"><<a href="mailto:igor.laskovy@gmail.com" target="_blank">igor.laskovy@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Hello all!<div><br></div><div>I found that this already have discussed not so far from now - <a href="http://comments.gmane.org/gmane.comp.distributed.opennebula.user/10568" target="_blank">http://comments.gmane.org/gmane.comp.distributed.opennebula.user/10568</a></div>
<div><br></div><div>As understand for now about Memory over-commitment for production I can forget ;)</div><div><br></div><div>For CPU over-commitment I can only use CPU & VCPU attributes, right?</div></div></blockquote>
<div><br></div></div><div>That's right</div><div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">
<div>If I will, for example, set CPU to 0.2, than host will do only reservation of processor time for that VM OR do limit ether, so this VM will limited of 1/5 of one physical/logical hardware core?</div></div></blockquote>
<div><br></div></div><div><div style="font-family:arial,sans-serif;font-size:13px">We enforce the CPU reserved at hypervisor level with <span>cgroups</span> for kvm, credit scheduler for xen, and the esx cpu scheduler for vmware</div>
<div style="font-family:arial,sans-serif;font-size:13px"></div></div><div><br></div><div><div><div dir="ltr">Regards</div><div dir="ltr"><br>--<br>Join us at <a href="http://opennebulaconf.com/" target="_blank">OpenNebulaConf2013</a> in Berlin, 24-26 September, 2013<br>
--<div>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></div>
</div></div></div></div></div></div></div>
</blockquote></div></div></div><br><br clear="all"><div class="im"><div><br></div>-- <br><div dir="ltr">Igor Laskovy<br><a href="http://facebook.com/igor.laskovy" target="_blank">facebook.com/igor.laskovy</a><br><div><a href="http://studiogrizzly.com" target="_blank">studiogrizzly.com</a></div>
</div>
</div></div>
</blockquote></div><br></div></div>