Guys, to prevent any further misunderstandings -> skip flag with default
setting ON were merged into stable/beryllium.
Jozef
From: Abhijit Kumbhare
Sent: Thursday, May 12, 2016 12:52 AM
To: Luis Gomez
Cc: Jozef Bacigal -X (jbacigal - PANTHEON TECHNOLOGIES at Ci
I think the reasons for retiring the inventory model are: 1) it is not based in
any standard model (e.g. IETF) and 2) current topology IETF topology models
allow for inventory information by augmenting node information. This
consolidation will also avoid data duplication inventory-topology.
BR/
In the end having two models cuts capacity of a node by some measurable amount.
I like having backwards compatible API’s but supporting two models is just not
sustainable.
It is interesting that in a service provider context outside of ODL, topology
is usually a derivation of inventory or multi
The key advantage to doing away with two models is to make writing code
that deals with both the topology and inventory models (which is nearly all
code for OpenFlow) in Java reasonable to write. As it stands, you can only
import one "Node" class in java via anything other than it's full class
name
Hi Icaro,
*-config modules are created for dependency injection (config-subsystem). In
config module you usually define your module dependencies and provided service
instances in config file. If your implementation is placed in some already
defined module, you don't need to create new *-config
