Nova will modify it when scheduling. You should let nova schedule the vm to the given host: dvr-compute1.novalocal.
On Mon, Jul 27, 2015 at 3:14 PM, Kevin Benton <[email protected]> wrote: > If it's a VM, Nova sets the binding host id. That field is set by the system > using the port. It's not a way to move ports around. > > On Jul 26, 2015 20:33, "于洁" <[email protected]> wrote: >> >> Hi all, >> >> Recently I used 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 >> But when creating a vm assigning to the port created above, the >> binding:host_id changed. Is this normal? Or the parameter binding:host_id >> does not work well? >> Any suggestion is grateful. Thank you. >> >> Yu >> >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: [email protected]?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Li Ma (Nick) Email: [email protected] __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
