With tags we can boot instances to a specified host aggregate.
But in case when we need boot instances to a specified host, available zone is
a good approach.
Otherwise, we need to provide tagged flavors for each host. In real use I think
it's quite impossible.
Best regards,
Leehom Li
From:
Cloud admin can add the necessary tags in the tenant flavors.
On Aug 22, 2016 12:00 AM, "Jay Pipes" wrote:
> On 08/21/2016 03:24 PM, Fawaz Mohammed wrote:
>
>> I belive utilizing host aggregate is better than availability zone in
>> this case.
>>
>
> Users don't know
On 08/21/2016 03:24 PM, Fawaz Mohammed wrote:
I belive utilizing host aggregate is better than availability zone in
this case.
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
I belive utilizing host aggregate is better than availability zone in this
case.
On Aug 19, 2016 8:33 PM, "Leehom Li (feli5)" wrote:
> Hi, All
>
> I used to use below command to boot an instance with a specified IP
> address to a
> Specified compute node.
>
> nova boot
>
Hi, All
I used to use below command to boot an instance with a specified IP
address to a
Specified compute node.
nova boot
--image \
--flavor \
--nic net-id=,v4-fixed-ip= \
--availability-zone :
May it helps.
leehom
On 8/17/16, 11:53 PM, "Géza Gémes" wrote:
On 08/17/2016 05:38 PM, Rick Jones wrote:
On 08/17/2016 08:25 AM, Kelam, Koteswara Rao wrote:
Hi All,
I have two computes
Compute node 1:
1. physnet3:br-eth0
2. physnet2: br-eth2
Compute node 2:
1. physnet3:br-eth0
2. physnet1:br-eth1
3. physnet2:br-eth2
When I boot an instance with a
On 08/17/2016 08:25 AM, Kelam, Koteswara Rao wrote:
Hi All,
I have two computes
Compute node 1:
1. physnet3:br-eth0
2. physnet2: br-eth2
Compute node 2:
1. physnet3:br-eth0
2. physnet1:br-eth1
3. physnet2:br-eth2
When I boot an instance with a network of provider-network physnet1,
nova is