On 06/24/2015 08:30 PM, Ben Pfaff wrote: > On Tue, Jun 23, 2015 at 03:18:57PM -0400, Russell Bryant wrote: >> On 06/23/2015 02:22 PM, Russell Bryant wrote: >>> While working on OpenStack Neutron integration for OVN, I came across a >>> small >>> feature gap. The Neutron API supports setting a port as administratively >>> down. >>> One way to implement that would be to delete ports from OVN while >>> administratively down. However, it seemed to me that it would be nice to >>> keep >>> the list of ports that currently exist in sync between the CMS (Neutron in >>> this >>> case) and OVN. This patch is a first attempt at supporting this OVN by >>> updating >>> the Pipeline to drop packets to/from a port that is administratively down. >>> >>> [PATCH 1/2] ovn: Add logical port 'enabled' state. >>> [PATCH 2/2] ovn: Add get/set-enabled to ovn-nbctl. >>> >>> northd/ovn-northd.c | 14 +++++++++--- >>> ovn-nb.ovsschema | 1 >>> ovn-nb.xml | 7 ++++++ >>> ovn-nbctl.8.xml | 13 +++++++++++ >>> ovn-nbctl.c | 59 >>> ++++++++++++++++++++++++++++++++++++++++++++++++++++ >>> 5 files changed, 91 insertions(+), 3 deletions(-) >>> >> >> After some more looking around, it seems the appropriate way to do this >> is with the equivalent of "ovs-ofctl mod-port". I'll look into how to >> do that some more. > > I'm happy enough to have this concept at the OVN level. I don't want > Neutron to have to talk to OpenFlow at all, if OVN is in the picture. >
I was thinking of propagating it down to OVN_Southbound and having ovn-controller speak OpenFlow. If you're happy with this first patch though, that's certainly good with me. :-) Thanks! -- Russell Bryant _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev