On Fri, Apr 15, 2016 at 05:12:08PM -0400, Russell Bryant wrote: > On Thu, Apr 14, 2016 at 5:47 PM, Ben Pfaff <b...@ovn.org> wrote: > > > On Mon, Apr 11, 2016 at 03:35:58PM -0400, Ramu Ramamurthy wrote: > > > With proposed native-dhcp implementation in OVN, there is no need > > > to run the neutron-DHCP-agent in Openstack. Since DHCP-based > > > metadata was implemented by the dhcp-agent, A new approach is > > > needed to implement the metadata-service. > > > > This is an interesting proposal. The alternative, which strikes me as a > > terrible idea, would be to somehow implement a TCP/IP stack and HTTP > > server inside OVS. > > > > Does there need to be a single metadata server per hypervisor, or one > > per logical switch per hypervisor? > > > > I think that a lot of the commit message (include some bits that I > > snipped) should go into documentation. > > > > I feel like this needs to be properly evaluated by someone who > > understands OpenStack and Neutron better than me. Maybe Russell? > > neutron-ovn-metadata would be something we maintain in our OpenStack plugin > repo (networking-ovn), right? > > I like this proposal. It suggests adding only the minimal amount of > support needed from OVN itself to enable us to get our OpenStack-specific > job done. This is much better than anything I had thought of.
I brought up the metadata proxy during a lunch conversation. Justin proposed what sounds to me like an interesting idea: what if the metadata service were implemented using service function chaining? Justin--do you want to explain the idea in more detail? _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
