홍길동 / onos

Change-Id: Ib40b557a724e9c11ea9c6c30ab99b903ecb21823

Change-Id: Icf91b863af766ec4d8869208a64bfe68805c02d0

- Implement region add/update/remove CLI
- Implement devices add/remove CLI

Change-Id: I38b40b24df7f864b0725104f63347081257743ac

Change-Id: Id9b48c9fe0d15c4aad8cb56c18b97b778dc49b74

Change-Id: I192a1b3e04b843fa0446d011cc98393a1950a5a9

Change-Id: I25ce0b5fc9058195498aa407d01aef1fa78a95e4

Change-Id: I22ad1faac713bb50f0b7ad3dde132363a6588723

Change-Id: I24661c002abd54d85d2bd154f47de13d3821d135

 - consolidated common glyph elements.
 - updated server-side constants.

Change-Id: Ia962f8827dafbb10fdbffed6dcb64c1ebcfc8c4d

Change-Id: I1455ad9bbf373cd3b5742d35b8edb7392c4ca9d7

Change-Id: Ie369f4eee4c28e70ef86852cfbeea78fea8fae4f

Previously, it would succeed since the checksum command would
return nothing in standard output.

Change-Id: I1a73d20a0e085107be8362a6226b1a213ecdab78

Change-Id: If246d09af29cfa0379ee9666de2931a3175f46e9

Change-Id: I12877d0012b50392a36e0d819e7b787066503dfc

Change-Id: I41a98702e781544fe6e0bebe3e281ff2bcd9a6fa

In order to avoid nextId collisions, all users of the flow objective
service should use the provided allocateNextId() method when
constructing new NextObjectives. I found one instance where this was not
the case: CordMcast.

Solution: removed private id generator from CordMacst and replaced it
with allocateNextId.

Change-Id: I134931b58c524291ae937dd6f0051ee549236734

Change-Id: I8b292edc9afdc7a8c3aaab511ed338b8497eb6de

Change-Id: I81e7f7e8de38ce20addd63548414a486b7e2ffb8

- Using @Property and @Modified annotations
- Fix DistributedPacketStore / DistributedStatisticStore / DistributedFlowStatisticStore

Change-Id: I6c907498496b9f21a8ef13b7badeb24770cb88ff

It is impossible to use openstack4j directly from ONOS apps
due to the Jersey version conflict.

Change-Id: I2df32430de42d627b03e0a2f8d8d2b9067ad3e14

Change-Id: I1eac3bda717ca227874ebac46fd5840247bfbe11

Change-Id: I1d68899e0056fa0db6322e83f7e9d3ff9b3b1ee0

Change-Id: I23092577a6da8f43b959a11b9590c282f4d50a5c

Change-Id: I4989e1a8e18c9a1b7172bfa941f53b4b9b76a550

Change-Id: I1da6f7d6201f880c27885659e5e52edc3fccbdd6

Change-Id: I8ce8236669c149f2ee810c5ff2c71591fa5a843c

Change-Id: Iabd50b529eb3f247463a71d29f7c447806c3afe7

Problem: The decoder in GroupCodec (used by the REST layer) chopped the
upper 16 bit in caller-provided group IDs. Since group IDs are
inherently greater than 16-bit on any OFDPA-based device, the current
casting rendered the REST layer unusable for such devices.

Fix: removed casting, verified that all tests pass, and verified that I
can now create healthy group entries on OFDPA-based switches.

Change-Id: Ieb51071ff9b0d47f4ff1f90d80970b6c0df946b7

Change-Id: I309e9da9cfd714f1b19ee73806c3a8c8233730c7

Change-Id: Id32535e154557cba8a4030d9e504c8bd15aa6e9a

- Impelent Region management REST API
- Add unit test for Region management REST API
- Add swagger docs for Region management REST API
- Add SCR Component and Service annotation for RegionManager

Change-Id: I042e92ed7144d596659b779a59239afba832ca62

Change-Id: I19e103e09e48a09900240b671b05ceba4970c058

Change-Id: I20aa9f986874e6ac7c602b8ae58b7c7b0df9a835

Change-Id: Ibe8f07a5de6b2927217cff5aeb29c6c103cd96ef

Change-Id: I14be43184e1ebd8d9ab16ab0728d6f84d64699d7

Change-Id: If257c73da8fe2dcc2f4111f103967cfcdd7fa273

Change-Id: I461b76457d4abdadad3b458cad8bf9d1a8a38f6b

Change-Id: I4e239509df747238905ca0995f41019679093627

Change-Id: Ic1a2fda1226e6a6c452bd37e6d010e2066239204

Change-Id: Ib2c440450abf94b9e93f7bdf59f9e5b1109c977f