> ovn-architecture.7.xml
> <https://github.com/doonhammer/ovs/blob/master/ovn/ovn-architecture.7.xml>
> ovn-nb.xml <https://github.com/doonhammer/ovs/blob/master/ovn/ovn-nb.xml>
>
> I have talked to the networking-sfc team and I think we have an approach
> to use the networking-sfc interface in Openstack. I think it is better than
> the API I created in Openstack and leverages their driver model. I am going
> to try and get something working to illustrate the model. Simple case
> should be relatively easy - if we want to add multiple VNF’s it will get a
> little harder.
>

John, Thank you for taking time to document your ideas. I am looking into a
slightly different use case where the chains are not static as defined by
the networking-sfc. We are geared more into the mobile networks. For my use
case, I could just use the ACL table expanded to have more "match" entries
and similar action entries as in the ACL handling. I had a few discussions
earlier with Russell but I was busy with other stuff past couple of months.
This weekend I was catching up with these email threads and also looking
into ovn code for changes needed at my end.

My idea is that the services could be modeled as "device" equivalent in
nova/neutron and does not need to have a logical service in ovn. The
service chain could be abstracted as custom flow definition. The sfc and
your approach looks kind of geared to a specific static chain/service
insertion definition, It is OK at openstack end to have what you need but
we could keep ovn more generic. I wanted to throw in this idea & see if you
could model all your "logical services" in networking-ovn (neutron side)
and not add additional entity in ovn? The neutron db can have the sfc/sfi
info, interpreted/translated to custom flows at networking-ovn.

Also would it be possible to have a more generic ACL table (with more
generic name), so we can define custom flows using logical ports and
logical flows? This is a general question, not necessarily related to sfi
or sfc. This way the ovn is purely defining the data paths and manages
ports. External ids can provide mappings to device id as we do in
nova/neutron.

We could talk over the phone if you wish tomorrow. I have added my work
email also here.

-Murali
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to