<p dir="ltr">Cloud admin can add the necessary tags in the tenant flavors. </p>
<div class="gmail_extra"><br><div class="gmail_quote">On Aug 22, 2016 12:00 AM, "Jay Pipes" <<a href="mailto:jaypipes@gmail.com">jaypipes@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 08/21/2016 03:24 PM, Fawaz Mohammed wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I belive utilizing host aggregate is better than availability zone in<br>
this case.<br>
</blockquote>
<br>
Users don't know anything about host aggregates. They are a cloud-admin-only way of grouping like compute resources together and the end user doesn't have any way of specifying a particular host aggregate when launching an instance.<br>
<br>
Best,<br>
-jay<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Aug 19, 2016 8:33 PM, "Leehom Li (feli5)" <<a href="mailto:feli5@cisco.com" target="_blank">feli5@cisco.com</a><br>
<mailto:<a href="mailto:feli5@cisco.com" target="_blank">feli5@cisco.com</a>>> wrote:<br>
<br>
Hi, All<br>
<br>
I used to use below command to boot an instance with a specified IP<br>
address to a<br>
Specified compute node.<br>
<br>
nova boot<br>
--image <image-id> \<br>
--flavor <flavor-id> \<br>
--nic net-id=<network-id>,v4-fixed-i<wbr>p=<ip addr> \<br>
--availability-zone <AZ>:<host><br>
<Name><br>
<br>
<br>
<br>
May it helps.<br>
<br>
leehom<br>
<br>
On 8/17/16, 11:53 PM, "Géza Gémes" <<a href="mailto:geza.gemes@ericsson.com" target="_blank">geza.gemes@ericsson.com</a><br>
<mailto:<a href="mailto:geza.gemes@ericsson.com" target="_blank">geza.gemes@ericsson.co<wbr>m</a>>> wrote:<br>
<br>
>On 08/17/2016 05:38 PM, Rick Jones wrote:<br>
>> On 08/17/2016 08:25 AM, Kelam, Koteswara Rao wrote:<br>
>>> Hi All,<br>
>>><br>
>>> I have two computes<br>
>>><br>
>>> Compute node 1:<br>
>>> 1. physnet3:br-eth0<br>
>>><br>
>>> 2. physnet2: br-eth2<br>
>>><br>
>>> Compute node 2:<br>
>>> 1. physnet3:br-eth0<br>
>>> 2. physnet1:br-eth1<br>
>>> 3. physnet2:br-eth2<br>
>>><br>
>>> When I boot an instance with a network of provider-network physnet1,<br>
>>> nova is scheduling it on compute1 but there is no physnet1 on<br>
compute1<br>
>>> and it fails.<br>
>>><br>
>>> Is there any mechanism/way to choose correct compute with correct<br>
>>> provider-network?<br>
>><br>
>> Well, the --availability-zone option can be given a host name<br>
>> separated from an optional actual availability zone identifier by a<br>
>> colon:<br>
>><br>
>> nova boot .. --availability-zone :hostname ...<br>
>><br>
>> But specifying a specific host rather than just an availability zone<br>
>> requires the project to have forced_host (or is it force_host?)<br>
>> capabilities. You could, perhaps, define the two computes to be<br>
>> separate availability zones to work around that.<br>
>><br>
>> rick jones<br>
>><br>
>><br>
>><br>
>>____________________________<wbr>______________________________<wbr>_______________<br>
>>_<br>
>><br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe:<br>
>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@<wbr>lists.openstack.org?subject:un<wbr>subscribe</a>><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cg<wbr>i-bin/mailman/listinfo/opensta<wbr>ck-dev</a>><br>
><br>
>Hi,<br>
><br>
>Does it help if you boot your VMs, with pre-created neutron ports,<br>
>rather than a neutron network? I think nova is supposed to bind<br>
then and<br>
>failing that it shall rescedule the VM (up to the configured<br>
re-schedule<br>
>attempts (3 by default)). I think this is an area, where e.g. one<br>
of the<br>
>physnet would relate to an SRIOV PF the PciDeviceFilter would be<br>
able to<br>
>select the right host from beginning.<br>
><br>
>Cheers,<br>
><br>
>Geza<br>
><br>
><br>
>_____________________________<wbr>______________________________<wbr>_______________<br>
>OpenStack Development Mailing List (not for usage questions)<br>
>Unsubscribe:<br>
<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@<wbr>lists.openstack.org?subject:un<wbr>subscribe</a>><br>
><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cg<wbr>i-bin/mailman/listinfo/opensta<wbr>ck-dev</a><br>
<<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cg<wbr>i-bin/mailman/listinfo/opensta<wbr>ck-dev</a>><br>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe:<br>
<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@<wbr>lists.openstack.org?subject:un<wbr>subscribe</a>><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cg<wbr>i-bin/mailman/listinfo/opensta<wbr>ck-dev</a>><br>
<br>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br>
</blockquote>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</blockquote></div></div>