Original usage with specifiying a phyiscal port is also in supporting.
Changes.
1. vnet-create-port allow to create virtual port
without a specific virtual port
2. vnet-bind-port command is added to newly bind or to update
3. Virtual binding point is changed from Port to ConnectPoint.
Change-Id: I4c8f9a2b9b2786ba519ead3559d7f005390fee86
Refactored NodeModel
Added class to the surrounding rect for selected class
Renamed Panels to avoid conflict with classic topo
Topo2: Details Panel for single device selection
Topo2: Added Equalize Masters keyboard shortcut
Topo2: Toggle Link Port highlighting
Topo2: Node Labels was returning empty string
if friendly name was null
Topo2: Reset map zoom and panning
Change-Id: I0a949b2f8205e1abcfcac5aaec65c18d76e77cff
The provider introduces IETF TE Topology YANG models and interacts with RESTCONF
client and YMS to provide IETF TE Topology to TE Topology Core subsystem.
This issue implements the interaction with RESTCONF client to obtain network topology
in JSON from south bound.
Change-Id: If203a98db69a516c8b09cb9247724e49a95abe4f
The APP introduces IETF TE Topology YANG models as RESTCONF NBI,
and it works as an adapter for data conversion between
YMS(YANG generated JAVA classes) and TE Topology Core subsystem.
The APP implements the following interfaces:
IetfNetworkService Interface
IetfTopologyService Interface
IetfNetworkTopologyService Interface
Change-Id: I761ff684bde4b64ca42bb1b0d5b1ddfb8a2377fd
- receives multiple TE topologies from SB provider, and merge into one native TE topology
- store both original, received TE topologies and the native topology in TE topology data store
- provide APIs for NB APP to retreive and display the TE topologies.
Change-Id: Id0b2f3433966694fcf197cc0b8ad19a063e92f36
- Allows creating/deleting/enabling VLANs on a device as a whole
- Not to be confused with applying VLANs on interfaces (e.g. access/trunk VLANs)
Change-Id: Ib830ecea77cdf882b3f9486fbea23d2acea6b947
This APP creates and manages a hierarchy of TE topologies received from SBI TE provider and from user configurations from NBI.
The API contains internal data structures for TE attributes that are aligned with the TE attributes definition in standard IETF YANG TE topology model (https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-05).
This commit includes the following interface definitions:
- TE topology provider service, which is called by the TE topology provider from SB to pass TE topologies to the TE topology core APP
- TE topology service, which provides service APIs for an external APP to get/set TE topologies and their attributes.
- Network, Node, Link definitions for TE networks and their default class implementation
Change-Id: Iafcf6911b8d9e494397e3a255cae282bbca74d5c
With the existing implementation, if we want to specify type value
8 to ECM Lisp type, we need to generate several place holders
inside LispType enumerator, otherwise ECM will be assigned a
subsequent number which is 5.
With this commit, we can specify arbitrary number for each Lisp
enum type, therefore, no need to add redundant placeholder for
the purpose of incrementing enum value.
Change-Id: I82a82a3f5bc313dc1f79aaa66a77889408e8c891
- fix intent installion on re-activation
- don't send ARP requests to inport
- send ARP requests to interfaces instead of connect point
Change-Id: I8f9185d174160adb605b8b44e7d7ebddb49bd027
Adding code to support RESTCONF protocol as one of
the supported SBI protocols of ONOS. This RESTCONF SBI extends
the current REST SBI protocl and adds some new APIs/functinalities
so that a provider can subscribe/register to an external restconf
server to receive notification stream.
Change-Id: I21bf0d0f0394cf788e066d743b3ade04735fe07e
- ConsistentMapException while POST a Meter With non existent DeviceId
Changes
1. added DeviceID check mechanism to confirm
the requested ID refers an available device.
2. Changed MeterResourceTest to address
a specific deviceID (of:0000000000000001)
Change-Id: I9ce70a73dc03e9e7516e8aaff3895a66f3b69b13
