<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Thank’s a lot ! <div class=""><div class="">I changed the settings and indeed, it seems to work. This distribution of instances is really interesting. I learn a lot.</div><div class="">Question: is it possible to view the calculated weight when choosing a server?</div><div class="">Otherwise, thanks again, really</div><div class=""><br class=""></div><div class="">
<meta charset="UTF-8" class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div><span style="color: rgb(31, 73, 125); font-family: Arial, sans-serif; font-size: 10pt; orphans: 2; widows: 2;" class="">Franck</span></div></div></div><div class="" style="orphans: 2; widows: 2; margin: 0cm 0cm 0.0001pt;"><br class=""></div></div></div></div><div><blockquote type="cite" class=""><div class="">Le 16 févr. 2022 à 03:35, Tony Liu <<a href="mailto:tonyliu0592@hotmail.com" class="">tonyliu0592@hotmail.com</a>> a écrit :</div><br class="Apple-interchange-newline"><div class=""><div class="">Build failure could be caused by different things, networking, storage, hypervisor, etc.<br class="">For example, failure caused by Neutron service, that doesn't mean this hypervisor is<br class="">not healthy, but because of that weigher, even Neutron service is recovered, this<br class="">hypervisor is still excluded from holding instance. This doesn't make sense.<br class="">I wouldn't enable this weigher until it's smart enough to know the failure is caused<br class="">by hypervisor itself, but not anywhere else.<br class=""><br class="">Tony<br class="">________________________________________<br class="">From: Laurent Dumont <<a href="mailto:laurentfdumont@gmail.com" class="">laurentfdumont@gmail.com</a>><br class="">Sent: February 15, 2022 05:00 PM<br class="">To: Tony Liu<br class="">Cc: Franck VEDEL; openstack-discuss<br class="">Subject: Re: [kolla-ansible][nova]Problem with distribution of instance on servers<br class=""><br class="">In a healthy setup, should build_failure_weight_multiplier be triggered?<br class=""><br class="">From the doc, tweaking this might mean you try to schedule and built instances on computes that are not healthy.<br class=""><br class="">On Tue, Feb 15, 2022 at 6:38 PM Tony Liu <<a href="mailto:tonyliu0592@hotmail.com" class="">tonyliu0592@hotmail.com</a><<a href="mailto:tonyliu0592@hotmail.com" class="">mailto:tonyliu0592@hotmail.com</a>>> wrote:<br class="">Enable debug logging on nova-scheduler, you will see how the winner is picked.<br class="">I had the same issue before, caused by the build-failure weigher enabled by default.<br class="">setting build_failure_weight_multiplier to 0 resolved issue for me. Instances are<br class="">balanced by weighers (compute and memory) as expected.<br class="">shuffle_best_same_weighed_hosts and host_subset_size are not necessary, unless<br class="">it's required by certain cases.<br class=""><br class="">Tony<br class="">________________________________________<br class="">From: Laurent Dumont <<a href="mailto:laurentfdumont@gmail.com" class="">laurentfdumont@gmail.com</a><<a href="mailto:laurentfdumont@gmail.com" class="">mailto:laurentfdumont@gmail.com</a>>><br class="">Sent: February 15, 2022 12:54 PM<br class="">To: Franck VEDEL<br class="">Cc: openstack-discuss<br class="">Subject: Re: [kolla-ansible][nova]Problem with distribution of instance on servers<br class=""><br class="">There are two settings we've tweaked in the past in Nova.<br class=""><br class="">shuffle_best_same_weighed_hosts --> Allow more spreading in the case of computes with the exact same specs/weights.<br class="">host_subset_size --> Helps with concurrent requests to get different hosts<br class=""><br class="">Before that, we saw the same behavior with Openstack stacking VM on single computes. It still respects anti-affinity, but I don't see a good reason to not spread as a default. Changing these two was enough to allow our spread to get a little better.<br class=""><br class="">On Tue, Feb 15, 2022 at 11:19 AM Franck VEDEL <<a href="mailto:franck.vedel@univ-grenoble-alpes.fr" class="">franck.vedel@univ-grenoble-alpes.fr</a><<a href="mailto:franck.vedel@univ-grenoble-alpes.fr" class="">mailto:franck.vedel@univ-grenoble-alpes.fr</a>><<a href="mailto:franck.vedel@univ-grenoble-alpes.fr" class="">mailto:franck.vedel@univ-grenoble-alpes.fr</a><<a href="mailto:franck.vedel@univ-grenoble-alpes.fr" class="">mailto:franck.vedel@univ-grenoble-alpes.fr</a>>>> wrote:<br class="">Hello,<br class="">I seem to have a problem that I hadn't seen.<br class="">I have 3 servers for my openstack, built with Kolla-ansible, I'm in Victoria version.<br class="">I had simply put the 3 servers in the [compute] part of the multinode file, at first it worked, but for some time all the VMs are placed on server 1.<br class=""><br class="">The 3 servers are operational, identical. here are 3 screenshots to show it. (on the images, the instances on servers 2 and 3 are present because it worked correctly, but no more instances are created on these servers now)<br class="">[<a href="cid:17eff2778356f37a4481" class="">cid:17eff2778356f37a4481</a>]<br class="">[<a href="cid:17eff277835e47aa83c2" class="">cid:17eff277835e47aa83c2</a>]<br class="">[<a href="cid:17eff2778356f53d34a3" class="">cid:17eff2778356f53d34a3</a>]<br class=""><br class=""><br class="">I tried to understand how the instances are distributed on the servers, but in my case, I don't understand why none are assigned to the 2nd and 3rd server.<br class="">How to find the problem? It should be nova-scheduler . Do you have to do anything special? Go see if a parameter has a bad value?<br class=""><br class=""><br class="">Thanks in advance if you can help me.<br class=""><br class="">Franck VEDEL<br class=""><br class=""></div></div></blockquote></div><br class=""></div></body></html>