yahoo-eng-team team mailing list archive

[Kevin Benton <1478464@xxxxxxxxxxxxxxxxxx>]

You can't control where a VM will be with the host_id parameter. If you
attach a port to VM, nova updates the host_id field with the hostname of
the compute node.

If you are trying to boot the VM to a specific host, you need to do that
with nova scheduling.

** Changed in: neutron
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1478464

Title:
  Binding:host_id  changes when creating vm

Status in neutron:
  Invalid
Status in OpenStack Security Advisory:
  Won't Fix

Bug description:
   I use the parameter binding:host_id to create port,  trying to allocate the port to a specified host. For example:
         neutron port-create e77c556b-7ec8-415a-8b92-98f2f4f3784f  --binding:host_id=dvr-compute1.novalocal
  Then creating a vm assigning to the port created above,
         nova boot --flavor=1 --image=cirros-0.3.4-x86_64 --nic port-id=2063c4db-7388-49dc-a2e0-9ffa579f870c testvm
  After the vm created, the neutron port-show result shows the value binding:host_id changed.
  Further more, I changed the --binding:host_id to the original one. Then the value --binding:host_id changed, but not the same as the host the vm(created before) belongs to.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1478464/+subscriptions