<div dir="ltr">There are two settings we've tweaked in the past in Nova.<div><br></div><div>shuffle_best_same_weighed_hosts --> Allow more spreading in the case of computes with the exact same specs/weights.<br>host_subset_size --> Helps with concurrent requests to get different hosts<br></div><div><br></div><div>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.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Feb 15, 2022 at 11:19 AM Franck VEDEL <<a href="mailto:franck.vedel@univ-grenoble-alpes.fr">franck.vedel@univ-grenoble-alpes.fr</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;">Hello,<div><div>I seem to have a problem that I hadn't seen. </div><div>I have 3 servers for my openstack, built with Kolla-ansible, I'm in Victoria version.</div><div>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.</div><div><br></div><div>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)</div><div><img id="gmail-m_6224011916695389525BEB96014-BA97-49F8-ADBA-62BECAD5491E" width="1213" height="213" src="cid:17eff2778356f37a4481"></div><div><img id="gmail-m_6224011916695389525A2066E35-A1A2-438D-8D6D-1CB5C455BD25" width="1242" height="254" src="cid:17eff277835e47aa83c2"></div><div><img id="gmail-m_6224011916695389525E04CD4E7-517C-462B-9D90-2176D33F927E" width="835" height="201" src="cid:17eff2778356f53d34a3"></div><div><br></div><div><br></div><div>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.</div><div>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?</div><div><br></div><div><br></div><div>Thanks in advance if you can help me.</div><div><br></div><div>
<div dir="auto" style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div dir="auto" style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div dir="auto" style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div dir="auto" style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div><span style="color:rgb(31,73,125);font-family:Arial,sans-serif;font-size:10pt">Franck VEDEL</span></div></div></div><div style="margin:0cm 0cm 0.0001pt"><br></div></div></div></div></div></div></blockquote></div>