-
Improvement
-
Resolution: Won't Do
-
Medium
-
None
-
None
-
None
-
None
I would like to be able to set up the "real" MD SAL implementation, as opposed to the in-memory test one, so exactly the same as is used in today's production environment under Karaf/OSGi, in a "standalone" Java SE environment.
Primary interest and driver for this is my https://github.com/vorburger/opendaylight-simple/, but I guess it could be of interest in general for other users as well.... but specifically for opendaylight-simple the goal is basically to be able to get completely rid of its InMemoryControllerModule and MdsalModule and be able to consume (something like) it from an "upstream" ODL project...
I'm thinking of moving some of that today is in Blueprint into POJOs. This should not be tied to Guice, but be able to be easily used by Guice wiring if desired.
- blocks
-
COE-51 Light weight ("simple") COE distribution
- Open
-
OPNFLWPLUG-1046 Migrate OFP from XML to annotation based blueprint
- Resolved
- is blocked by
-
CONTROLLER-1832 Transaction Trace tool wiring creates second BindingToNormalizedNodeCodec
- Resolved
-
CONTROLLER-1834 Transaction Trace tool wiring for ping-pong DataBroker is wrong
- Resolved
-
MDSAL-418 Wiring classes for mdsal
- Resolved
- relates to
-
INFRAUTILS-63 Guice Inject utility ideas
- Resolved