On 02/24/2015 05:47 PM, Ben Pfaff wrote: > On Tue, Feb 24, 2015 at 05:46:04PM +0100, Russell Bryant wrote: >> On 02/24/2015 05:43 PM, Ben Pfaff wrote: >>> On Tue, Feb 24, 2015 at 05:37:53PM +0100, Russell Bryant wrote: >>>> On 02/20/2015 07:19 AM, Ben Pfaff wrote: >>>>> This commit adds preliminary design documentation for Open Virtual >>>>> Network, >>>>> or OVN, a new OVS-based project to add support for virtual networking to >>>>> OVS, initially with OpenStack integration. >>>> >>>> I had another thought about the OpenStack integration. I don't remember >>>> seeing any mention of DHCP in the design docs. That could mean we have >>>> to integrate with the existing DHCP agent in OpenStack. It would be >>>> great if something in OVN could negate the need for it, though. Do you >>>> have any thoughts about this? >>> >>> DHCP is an obvious service to add to OVN eventually, but I guess that >>> the initial versions won't have it built-in. So, if OpenStack already >>> has an agent and it's not too much of a hassle to integrate with OVN, it >>> might be the way to go. >> >> That works. I'd love to get to where none of the current agents are >> needed. It's good to at least agree that it makes sense to add eventually. > > Do you have a list of the other agents that you think are eventually > undesirable? I can add some of this (including DHCP) to the > ovn-architecture document. >
I think the l2, l3, and now DHCP ones are covered. The only other one is a metadata agent. That one does some OpenStack specific magic, though. It intercepts an HTTP request, does some OpenStack lookups and adds HTTP headers needed to uniquely identify the request to the VM it came from. Then it proxies the request on to the metadata API exposed by Nova. I'm not sure if it makes sense to do anything with that. -- Russell Bryant _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
