On Tue, May 2, 2017 at 11:31 AM, Ben Pfaff <[email protected]> wrote: > On Tue, Apr 25, 2017 at 11:05:28AM +0000, Daniel Alvarez wrote: >> This patch introduces a new type of OVN ports called "localport". >> These ports will be present in every hypervisor and may have the >> same IP/MAC addresses. They are not bound to any chassis and traffic >> to these ports will never go through a tunnel. >> >> Its main use case is the OpenStack metadata API support which relies >> on a local agent running on every hypervisor and serving metadata to >> VM's locally. This service is described in detail at [0]. >> >> Signed-off-by: Daniel Alvarez <[email protected]> > > Thanks a lot for working on this! My understanding is that the metadata > API support, added to the DNS support that Numan Siddique is building, > will complete OVN's basic OpenStack support, which will be great to > have. > > Before I review this patch in detail, can you help me to understand what > other components, in OVN or in Neutron, will be needed to make the > overall metadata API feature work? Is it just a matter of plugging a > bit into the Neutron networking-ovn driver, or do we need additional > infrastructure in OVN beyond this patch? I'm trying to understand the > full context here.
More complete context is documented here: https://review.openstack.org/#/c/452811/ Latest rendered HTML version would be: http://docs-draft.openstack.org/11/452811/5/check/gate-networking-ovn-docs-ubuntu-xenial/6c6b664//doc/build/html/design/metadata_api.html This patch is the only missing piece from OVN. networking-ovn (the neutron-server driver) will create ports of type=localport. Then we will write an agent that runs on each node along side ovn-controller that will manage OVS ports and corresponding instances of haproxy. -- Russell Bryant _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
