Hi,<br><br>So I tried this - but doesn't seem to work - I still get the "unable to find host" for the instance :| when specifying a flavour to use a specific zone..<div><br></div><div>so I create a new aggregate and zone : </div><div><br></div><div>nova aggregate-create C3 C3<br></div><div><div>+----+------+-------------------+-------+-------------------------+</div><div>| Id | Name | Availability Zone | Hosts | Metadata |</div><div>+----+------+-------------------+-------+-------------------------+</div><div>| 5 | C3 | C3 | | 'availability_zone=C3' |</div><div>+----+------+-------------------+-------+-------------------------+</div></div><div><br></div><div>then I add a host to that aggregate : </div><div><br></div><div>nova aggregate-add-host C3 stack24.internal<br></div><div><div>+----+------+-------------------+------------------+-------------------------+</div><div>| Id | Name | Availability Zone | Hosts | Metadata |</div><div>+----+------+-------------------+------------------+-------------------------+</div><div>| 5 | C3 | C3 | 'stack24.internal' | 'availability_zone=C3' |</div><div>+----+------+-------------------+------------------+-------------------------+</div></div><div><br></div><div>then I set the metadata for the aggregate : </div><div><br></div><div>nova aggregate-set-metadata C3 not-controller=true<br></div><div><div>+----+------+-------------------+------------------+------------------------------------------------+</div><div>| Id | Name | Availability Zone | Hosts | Metadata |</div><div>+----+------+-------------------+------------------+------------------------------------------------+</div><div>| 5 | C3 | C3 | 'stack24.internal' | 'availability_zone=C3', 'not-controller=true' |</div><div>+----+------+-------------------+------------------+------------------------------------------------+</div></div><div><br></div><div>then I set the flavour to be locked to that zone/aggregate : </div><div><br></div><div>nova flavor-key 558213d9-7641-4f9a-a9c4-2685e75f268d set not-controller=true<br></div><div><div>nova flavor-show 558213d9-7641-4f9a-a9c4-2685e75f268d </div><div>+----------------------------+--------------------------------------+</div><div>| Property | Value |</div><div>+----------------------------+--------------------------------------+</div><div>| OS-FLV-DISABLED:disabled | False |</div><div>| OS-FLV-EXT-DATA:ephemeral | 0 |</div><div>| disk | 10 |</div><div>| extra_specs | {"not-controller": "true"} |</div><div>| id | 558213d9-7641-4f9a-a9c4-2685e75f268d |</div><div>| name | t1.micro |</div><div>| os-flavor-access:is_public | True |</div><div>| ram | 768 |</div><div>| rxtx_factor | 1.0 |</div><div>| swap | |</div><div>| vcpus | 1 |</div><div>+----------------------------+--------------------------------------+</div></div><div><br></div><div>And when I try to create a Instance, all I can get into the logs (debug is disabled):</div><div><br></div><div><div>2015-01-09 15:26:39.149 28901 WARNING nova.scheduler.driver [req-8d50f7ab-9f0c-4ac9-b218-c95450d46895 Alex Leonhardt 5cec227f266b4e3d85b106daae5deed8] [instance: 3b300f3a-2b04-4063-9bbb-b8295c8729b8] Setting instance to ERROR state.</div></div><div><br></div><div>The HV I expected this to be scheduled for (stack24.internal) does not have any of the UUIDs in its logs. </div><div><br></div><div>FWIW - am running Icehouse on CentOS 6.5 : </div><div><br></div><div><div>openstack-neutron-2014.1.1-3.el6.noarch</div><div>openstack-nova-conductor-2014.1.1-2.el6.noarch</div><div>openstack-dashboard-2014.1.1-1.el6.noarch</div><div>openstack-nova-api-2014.1.1-2.el6.noarch</div><div>openstack-utils-2014.1-3.el6.noarch</div><div>openstack-neutron-openvswitch-2014.1.1-3.el6.noarch</div><div>openstack-nova-compute-2014.1.1-2.el6.noarch</div><div>openstack-nova-console-2014.1.1-2.el6.noarch</div><div>python-django-openstack-auth-1.1.5-1.el6.noarch</div><div>openstack-keystone-2014.1.1-1.el6.noarch</div><div>openstack-nova-cert-2014.1.1-2.el6.noarch</div><div>openstack-glance-2014.1.1-1.el6.noarch</div><div>openstack-nova-common-2014.1.1-2.el6.noarch</div><div>openstack-nova-novncproxy-2014.1.1-2.el6.noarch</div><div>openstack-nova-scheduler-2014.1.1-2.el6.noarch</div></div><div><br></div><div>Any ideas ? </div><div><br></div><div>Thanks!<br>Alex</div><div><br></div><div><br></div><div><br></div><div><br></div><br><div class="gmail_quote">On Fri Jan 09 2015 at 11:06:26 Alex Leonhardt <<a href="mailto:aleonhardt.py@gmail.com">aleonhardt.py@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Ah, the link helped - I was trying to get the extra spec filter to work the other day but messed it up - i think i forgot a nova config option : <br>scheduler_default_filters=AggregateInstanceExtraSpecsFilter,AvailabilityZoneFilter,RamFilter,ComputeFilter<br><div><br></div><div>So I'll try that now that should help me prevent things going onto that zone / host / aggregate. </div><div><br></div><div>Thanks!</div><div><br>Alex</div><div><br></div><br><div class="gmail_quote">On Fri Jan 09 2015 at 11:02:45 Alex Leonhardt <<a href="mailto:aleonhardt.py@gmail.com" target="_blank">aleonhardt.py@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Belmiro,<br><br>Thanks that helps - where is that config option to be set ? <br><div><br></div><div>We do have 2 new aggregates which are zoneA and zoneB, both with 4-6 hypervisors at the moment. But somehow the default "nova" zone still exists with a host that I want to keep "private" (or unused for now). Any ideas ? </div><div><br></div><div>Thanks!</div><div><br>Alex</div><div><br></div><br><div class="gmail_quote">On Fri Jan 09 2015 at 10:38:42 Belmiro Moreira <<a href="mailto:moreira.belmiro.email.lists@gmail.com" target="_blank">moreira.belmiro.email.lists@<u></u>gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Alex,<div>you need to create "host aggregates" to define other availability zones.</div><div>For more info see: <a href="http://docs.openstack.org/havana/config-reference/content/host-aggregates.html" target="_blank">http://docs.openstack.org/<u></u>hava<u></u>na/config-reference/<u></u>content/<u></u>host-aggregates.html</a></div><div><br></div><div>The default availability zone can be changed with the configuration option:</div><div><span style="color:rgb(0,0,0);font-family:Verdana,Geneva,sans-serif;font-size:13px">default_availability_zone</span><br></div><div><span style="color:rgb(0,0,0);font-family:Verdana,Geneva,sans-serif;font-size:13px"><br></span></div><div><span style="color:rgb(0,0,0);font-family:Verdana,Geneva,sans-serif;font-size:13px">Belmiro</span></div></div><div class="gmail_extra"><br><div class="gmail_quote"></div></div><div class="gmail_extra"><div class="gmail_quote">On Fri, Jan 9, 2015 at 10:38 AM, Alex Leonhardt <span dir="ltr"><<a href="mailto:aleonhardt.py@gmail.com" target="_blank">aleonhardt.py@gmail.com</a>></span> wrote:<br></div></div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<div><br></div><div>we seem to get a default "nova" zone which is available to all users to create VMs on - that by itself is fine - but I want the users limited to use other zones only, and not the default nova zone. Is it possible to do that ? If so, where do I do that and how ? </div><div><br></div><div>Any links / docs would be much appreciated!</div><div><br></div><div>Thanks!<span><font color="#888888"><br>Alex</font></span></div>
<br></blockquote></div></div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">______________________________<u></u><u></u>_________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.<u></u>open<u></u>stack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/<u></u>cgi<u></u>-bin/mailman/listinfo/<u></u>openstac<u></u>k-operators</a><br>
<br></blockquote></div><br></div>
</blockquote></div></blockquote></div></blockquote></div>