I don't expect we will be able to get simultaneous coexistence between the
VTN/OpenDOVE/OVSDB virtualization implementations in the first release ,
for example. I was always expecting some kind of configuration needed to
select which approach to use based on the user environment. Using
multiple implementations also has implication on NB integrations with
OpenStack, which I don't think we've figured out yet.
That said, it seems odd to me that affinity would be an issue -- my
impression was that it provides a way to specify relationships -- and
other services are essentially clients of the affinity service and pick up
what the user has specified. Is the nature of the incompatibility also
documented somewhere (assuming we have some idea of what is breaking)? Are
any of the virtualization services currently clients of the affinity
service (Open DOVE is not at this point)?
opendove-dev-bounces@... wrote on 11/15/2013 11:09:53
From: "Ed Warnicke (eaw)" <eaw@...>
To: Hideyuki Tai <h-tai@...>,
Cc: "<affinity-dev@...>" <affinity-
Date: 11/15/2013 11:19 PM
Subject: Re: [opendove-dev] [integration-dev] Virtualization Edition
Guide for VTN Manager
Sent by: opendove-dev-bounces@...
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@...>
trouble in the Virtualization Edition
I've written the procedure how to run VTN Manager without any
in the following page.
VTN Manager does not work correctly when the following bundles are
* arphandler bundle (org.opendaylight.controller.arphandler)(org.opendaylight.controller.samples.simpleforwarding) sets
* sample bundles (org.opendaylight.controller.samples.*)
* affinity bundles (org.opendaylight.affinity.*)
For example, simpleforwarding
flow entries automatically after detecting host information.installed by VTN Manager.
These flow entries might be inconsistent with flow entries
installing and starting the above bundles,
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
please edit configuration/config.ini as follows.OpenDaylight_Virtual_Tenant_Network_(VTN):Installation:VTN_Coordinator
47 # Avoid to auto-install following bundles, that means those need
48 # to be started manually or in other way like osgi.bundles
Installation Guide for VTN Coordinator is available here:
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.
integration-dev mailing list
opendove-dev mailing list