> On 25 Sep 2015, at 14:37, thomas.mo...@orange.com wrote: > > Kevin, Miguel, > > I agree that (4) is what makes most sense. > (more below) > > Miguel Angel Ajo : >> Do you have a rough idea of what operations you may need to do? > > Right now, what bagpipe driver for networking-bgpvpn needs to interact with > is: > - int_br OVSBridge (read-only) > - tun_br OVSBridge (add patch port, add flows) > - patch_int_ofport port number (read-only) > - local_vlan_map dict (read-only) > - setup_entry_for_arp_reply method (called to add static ARP entries) >
Sounds very tightly coupled to OVS agent. >> Please bear in mind, the extension interface will be available from >> different agent types >> (OVS, SR-IOV, [eventually LB]), so this interface you're talking about could >> also serve as >> a translation driver for the agents (where the translation is possible), I >> totally understand >> that most extensions are specific agent bound, and we must be able to >> identify >> the agent we're serving back exactly. > > Yes, I do have this in mind, but what we've identified for now seems to be > OVS specific. Indeed it does. Maybe you can try to define the needed pieces in high level actions, not internal objects you need to access to. Like ‘- connect endpoint X to Y’, ‘determine segmentation id for a network’ etc. Ihar
signature.asc
Description: Message signed with OpenPGP using GPGMail
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
