홍길동 / onos

Change-Id: I7f214c6ce5a876f458626e12c8cfdd3072ad107f

Change-Id: Ic787d73d9d541a93f5e957a3369dbab4b5fa9a6c

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

We were missing the selector during the
building of the sp2mp and mp2sp.

Change-Id: Ica456e7c92ef346721ce3f4ceccaf55033d25029

Change-Id: I8fdb27749893fefbe27bba02437b36e7860701b4

Topo2: Limit icon scaling

Change-Id: I9b203183ebfe25ae9993a9ee8813608969867849

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

Change-Id: I1039d5acc145f51f930dee28c5895b9593070628

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

Change-Id: I88394307cb9be30237be0bb17e013d7af88a607c

Change-Id: I2b261c3d91d345907b165bd61eb7b6c45011c247

Change-Id: I31d7c054f94b5192ab1ef5ebd2af1151a7338437

Change-Id: I60f2988910eea5f9ffdfd14e7d47863af63b2691

This reverts commit a32f6da9.

Change-Id: Ic023d701d18f0ae7af2579bc43777714a0e701dc

Change-Id: I24dd34c20a47f2a7462565ef7ec381f847f60130

- 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

Change-Id: Ie21f2fbbdf8b936719c5c2745a83c3bd662c8cc1

Change-Id: Ib49ac1d8f7e42323d72a99d1c807f610f48b71ee

- 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

Change-Id: I652f4620a741f64bc71f2555ad801eb00e7c951f

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

Change-Id: I6d1e45b1152b2387d4ff981dc0666868235eb1c3

Change-Id: I802f1f10f4e1ee408aa13652c0ba039425fa8e4d

Change-Id: I89b60602247a25a1879e4394a60c57d480881f74

Change-Id: I770a2efee9557371caff7066bf71306d375c3fdf

Change-Id: Ibe9062c904ad9a6c3ba001fe57be7cec49eb8a4d

Change-Id: I9b7e0ff861efeff0f65f6ac2d30fdda51df5e253

[onos-5262] Adding patchset 2

Change-Id: I43cb43deca16bcfe1874699bccdb94b0301d30d1

 - modify key of the security group maps.
 - search for a subnet interface to the host.

Change-Id: I502a35735b423fb6c27bab6b83b642a5f916e37c

Change-Id: I79be3924790bd42902e45c4f948a12cf07564728

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

Change-Id: I515d48a664ad2edc18be801977e4bff7713f1052

- 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

Change-Id: I1730ec5ae0692651cb774c2b546c31773115676c

Change-Id: Ied14896955595ce4f694885991231b75be2e63c5

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

 - fix javadoc longer than 80 char limit
 - fix javadoc that missing @params
 - chain calls to StringBuilder.append()
 - combine constant strings in place

Change-Id: Ie2ef4fd4c19e955ad2d5a5584f5017a842abb790

Change-Id: Id93a647b35b24c47f2828763a799b56a50113faf

Simplify logic around scheduling a balancing task and listen
to RegionEvents. Region Membership updates and Region Updates
should also trigger a rebalance.

Now, it is possible to queue up another balancing task even
if there is one running. They'll still never run in parallel
and will still run with at least a few seconds in between (30),
but this way we don't ever risk missing an event that makes it
necessary to rebalance - not even if we were rebalancing exactly
when that event fired.

Change-Id: I64e1c6fc5e87f2b1fffbefb54c96303dac55d1d1