Ryan, Let me do that - I assume adding them to plugin.py is the right approach.
I have cleaned up https://github.com/doonhammer/networking-ovn and did a merge so it should be a lot easier to see the changes. I am going to cleanup ovs/ovn next. Once I have everything cleaned up and make sure it is still working I will move the code over to the port-pair/port-chain model. Let me know if that works for you. Regards John From: Ryan Moats <[email protected]<mailto:[email protected]>> Date: Tuesday, May 10, 2016 at 7:38 AM To: John McDowall <[email protected]<mailto:[email protected]>> Cc: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, OpenStack Development Mailing List <[email protected]<mailto:[email protected]>> Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN John McDowall <[email protected]<mailto:[email protected]>> wrote on 05/09/2016 10:46:41 AM: > From: John McDowall > <[email protected]<mailto:[email protected]>> > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: "[email protected]<mailto:[email protected]>" > <[email protected]<mailto:[email protected]>>, "OpenStack > Development Mailing List" > <[email protected]<mailto:[email protected]>> > Date: 05/09/2016 10:46 AM > Subject: Re: [OVN] [networking-ovn] [networking-sfc] SFC and OVN > > Ryan, > > Thanks - let me try and get the code cleaned up and rebased. One > area that I could use your insight on is the interface to > networking-ovn and how it should look. > > Regards > > John Looking at this, the initial code that I think should move over are _create_ovn_vnf and _delete_ovn_vnf and maybe rename them to create_vnf and delete_vnf. What I haven't figured out at this point is: 1) Is the above enough? 2) Do we need to refactor some of OVNPlugin's calls to provide hooks for the SFC driver to use for when the OVNPlugin inheritance goes away. Ryan
_______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
