[affinity-dev] Virtualization Edition Guide for VTN Manager

Suchi Raman <suchi.raman@...>

A quick solution for the first release may be to assign a priority to each application. FRM does some degree of conflict detection and resolution (calculating intersections of overlapping rules) but does not look at or assign flow priority fields. These are expected to come from the caller.

Today the main entry points for flow rules are the forwarding rules manager and flow programmer service. We should centralize the main entry point for any user-initiated configuration or policy tasks requiring flow rule creation in the switches where such priority and conflicts can be evaluated and resolved. I say user-initiated in contrast to flow rules from network events -- arp, learning bridge, ...

On Fri, Nov 15, 2013 at 11:09 PM, Ed Warnicke (eaw) <eaw@...> wrote:

This is a problem as affinity is also part of the virtualization edition... what can be done to allow peaceful coexistence?


> On Nov 15, 2013, at 12:00 AM, "Hideyuki Tai" <h-tai@...> wrote:
> Hi all,
> I've written the procedure how to run VTN Manager without any trouble in the Virtualization Edition
> in the following page.
>  https://wiki.opendaylight.org/view/OpenDaylight_Virtual_Tenant_Network_(VTN):Installation:Virtualization_Edition
> VTN Manager does not work correctly when the following bundles are running:
> * arphandler bundle (org.opendaylight.controller.arphandler)
> * sample bundles (org.opendaylight.controller.samples.*)
> * affinity bundles (org.opendaylight.affinity.*)
> For example, simpleforwarding (org.opendaylight.controller.samples.simpleforwarding) sets
> flow entries automatically after detecting host information.
> These flow entries might be inconsistent with flow entries installed by VTN Manager.
> To let VTN Manager work correctly in the Virtualization Edition,
> you have to stop the above bundles.
> For example, to prevent OSGi framework from automatically installing and starting the above bundles,
> please edit configuration/config.ini as follows.
> 47 # Avoid to auto-install following bundles, that means those need
> 48 # to be started manually or in other way like osgi.bundles
> 49 #felix.fileinstall.filter=^(?!org.apache.felix.fileinstall).*
> 50 felix.fileinstall.filter=\
> 51     ^(?!org\\.(apache\\.felix\\.fileinstall|\
> 52                opendaylight\\.(affinity|\
> 53                                controller\\.(arphandler|samples)))).*
> 54
> Installation Guide for VTN Coordinator is available here:
>  https://wiki.opendaylight.org/view/OpenDaylight_Virtual_Tenant_Network_(VTN):Installation:VTN_Coordinator
> To test VTN Coordinator, please check the above guide.
> VTN Coordinator is not included in the Virtualization Edition yet,
> but I believe that it will be included soon.
> Regards,
> Hideyuki Tai
> _______________________________________________
> integration-dev mailing list
> integration-dev@...
> https://lists.opendaylight.org/mailman/listinfo/integration-dev
affinity-dev mailing list