Re: [ovs-dev] [PATCH RFC] ovn: distributed logical port for VM metadata access

Hi Ramu, On Tue, Apr 19, 2016 at 8:12 AM, Ramu Ramamurthy wrote: > On Mon, Apr 18, 2016 at 2:55 PM, Aaron Rosen > wrote: > > I like this idea as well. > > > > The one question I have with is is how we should determine which ip > address > > to

Re: [ovs-dev] [PATCH RFC] ovn: distributed logical port for VM metadata access

> > We can use the dhcp-port (and its IP address) for the distributed-port. > > The current native-dhcp proposal > (http://openvswitch.org/pipermail/dev/2016-April/069787.html) > assumes that a dhcp-server ip-address "server_id" is defined on the subnet. > > action=(dhcp_offer(offerip = 10.0.0.2,

Re: [ovs-dev] [PATCH RFC] ovn: distributed logical port for VM metadata access

On Mon, Apr 18, 2016 at 2:55 PM, Aaron Rosen wrote: > I like this idea as well. > > The one question I have with is is how we should determine which ip address > to select for the 'distributed' port? Aaron, Thanks for your review, and feedback. We can use the dhcp-port

Re: [ovs-dev] [PATCH RFC] ovn: distributed logical port for VM metadata access

I like this idea as well. The one question I have with is is how we should determine which ip address to select for the 'distributed' port? In your example above you picked 10.0.0.100. I'm wondering if there is a more flexible way to handle this. It seems to me like this ip needs to be selected a

Re: [ovs-dev] [PATCH RFC] ovn: distributed logical port for VM metadata access

> > neutron-ovn-metadata would be something we maintain in our OpenStack plugin > repo (networking-ovn), right? > Russell, Thanks for your review and feedback, neutron-ovn-metadata would be maintained in networking-ovn repo. > I like this proposal. It suggests adding only the minimal amount of

Re: [ovs-dev] [PATCH RFC] ovn: distributed logical port for VM metadata access

> On Apr 15, 2016, at 2:33 PM, Ben Pfaff wrote: > > 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

Re: [ovs-dev] [PATCH RFC] ovn: distributed logical port for VM metadata access

On Fri, Apr 15, 2016 at 05:12:08PM -0400, Russell Bryant wrote: > On Thu, Apr 14, 2016 at 5:47 PM, Ben Pfaff 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

Re: [ovs-dev] [PATCH RFC] ovn: distributed logical port for VM metadata access

On Thu, Apr 14, 2016 at 5:47 PM, Ben Pfaff wrote: > On Mon, Apr 11, 2016 at 03:35:58PM -0400, Ramu Ramamurthy wrote: > > A new logical-port-type called "distributed" is introduced with this > change. > > > > A distributed logical port is not bound to any chassis. An instance of > >

Re: [ovs-dev] [PATCH RFC] ovn: distributed logical port for VM metadata access

> 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? > Ben, Thanks for

Re: [ovs-dev] [PATCH RFC] ovn: distributed logical port for VM metadata access

On Mon, Apr 11, 2016 at 03:35:58PM -0400, Ramu Ramamurthy wrote: > A new logical-port-type called "distributed" is introduced with this change. > > A distributed logical port is not bound to any chassis. An instance of > the distributed port is created as an ovs internal port at all chasses >

[ovs-dev] [PATCH RFC] ovn: distributed logical port for VM metadata access

A new logical-port-type called "distributed" is introduced with this change. A distributed logical port is not bound to any chassis. An instance of the distributed port is created as an ovs internal port at all chasses where the datapath has at least 1 vif. VIFs on a chassis can communicate with