Open Stack

On Thu, May 16, 2013 at 12:28 PM, Robert Kukura <rkukura at redhat.com> wrote:

> >
> > @Mike - I think we'd still want to leave nova-compute to create the tap
> > interfaces and sticking  external-ids on them though.
>
> It also seems nova-compute should call port-update to set
> binding:host_id and then use the returned binding:vif_type, since the
> vif_type might vary depending on the host, at least with ml2. The Arista
> top-of-rack switch hardware driver functionality also depends on the
> binding:host_id being set.
>
> -Bob
>
>
Hmmm, is that really nova-compute's job? Again, that seems to be the
networking abstraction's job to me. We have all these quantum agents, they
have the device_id (instance_uuid). Why not have a quantum component (agent
maybe?) query nova for the host_id and then it calls port-update?

-Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130516/d1c4abbd/attachment.html>