홍길동 / onos

1. Partial REST API implementation
2. Partial Event Manager backend implementation

Change-Id: Ieaf703f7a3f6e296aea8ffcf155c7a1b603236ca

Change-Id: Ia87f0898e51704ce8d02d877e9f0d57219099a53

Change-Id: If2ef21201d4d86a2f3f4b95365d41a01d8feda98

Change-Id: I0849d87ad1c7f9a8e08aabebd547dfd2dfde49df

Change-Id: I3387bef3babd402268cb49d371d37ac9e192fba6

Change-Id: I5d1956992c9353c9a9080bf6f59a8ff73cce32c0

Change-Id: Ib1e470fa9b1cf8faf0e0686c160b5c69adfbf16f

Change-Id: I5a04cfa7b97c51cdedd65bbcaeaec1cb500fd2de

Change-Id: I0a3424f7e3b13a3c18e668a5eed5151755bce4f9

Change-Id: I4efb76819007cc757dce123f3fd1ba83e2bc2c74

Change-Id: Id213d1e84d4ded0b529bb70ee4c0105415b7aa09

Change-Id: I37a85b38b61d9b008dc3456345bbd9ded6718281

Change-Id: Ide265b68d809ccea2ea8900993999bf8ae3184fc

Change-Id: Id34a9de669a3ab571e690b27072b44057d863768

Change-Id: I422f54f908998460ceff994f9b3bfbf3d2f81a56

Change-Id: I60399c5cc9a00857f275fa8016520b2d909e9912

Change-Id: I9b2674195a754a0774013f9adf717764ea18c9a6

Change-Id: I0de6b27152b4384617689a1db05d9606baf79ec0

Change-Id: Id3ec5cfed2b8e2a7d2d580786c70b5804f03ecfa

Change-Id: I8ddd216b85786949d27a05010b11b715fb7edcba

Change-Id: I025e21a670562e387138afddcdd78a214b3a81e1

Change-Id: I96f1855bc71a002335946150b51e911ae6ac2fb2

Change-Id: I457f12a2b0edaadee5ff888e0297b40854d53096

Change-Id: I45936bee910ba4c81805f59daf2702bea5e60d08

Change-Id: I9412c06c34f5e62e1283f1972f0417b01b55d545

Change-Id: I129eaec0c8f81c674a994a579650f18499340052

Removed old parsing logic. Now it uses Bmv2FlowRuleTranslator to
translate ONOS flow rule into Bmv2 model-dependent table entries.

Change-Id: I1febc23b334acade027e806c8a8c266acc061277

In Bmv2, tables, header fields and actions all depend on the packet
processing model configuration (Bmv2Model) currently deployed on the
device. For this reason, translation is needed from protocol-aware ONOS
FlowRule objects into properly formatted, protocol-independent
Bmv2TableEntry objects. Translation is based on a TranslatorConfig that
provides a mapping between ONOS types and Bmv2 model-dependent types.

Change-Id: I620802c2024b5250867dc6b1b988b739177f582a

translator (ONOS-4044)

- Added new classes for different match parameters (exact, ternary, lpm,
  valid)
- Divided api package in two sub-packages, model (previously under
  drivers) and runtime (old api package)
- Improved Bmv2ThriftClient caching and table entry handling

Change-Id: I23c174cf3e8f9f6ecddb99c2d09dc531e8f1c73f

Such a model is used to define the way BMv2 should process packets
(i.e. it defines the device ingress/egress pipelines, parser, tables,
actions, etc.) and can be generated (i.e. JSON) by compiling a P4
program using p4c-bm.

Change-Id: Ic08df68bed5a0261cb50b27dc7dbfe9d35e1fb71

BMv2 devices can now be discovered (along with port informations) using
net-cfg (see tools/test/config/bmv2-cfg.json)

Change-Id: Ief2ca790dceb4d047b75aae6c5e1a89a05215e5f

Provides Thrift-based implementation for FlowRuleProgrammable and
PortDiscovery behaviours.

Change-Id: Ibbf8720d92301bcd23c5c583d156f464015ff1ef

- Add unit test for chartBuilder.js

Change-Id: I2f5c56b878dda660c28af13ec0229b5ab3665156

Change-Id: I27c0e5e30596d77d9099094a1ebda0f50d4b29ac

- Replace SRNextObjectiveContext with DefaultObjectiveContext
- Move several log messages to lower log level

Change-Id: Ice2fb598b8e4502cb4acee1a95235551ec7c8db7

Change-Id: I2dfd6b88c4ae14a02d258a2cdc9ee35b9ff08292

The original value overflows the 16-bits allowed by OpenFlow so that
example doesn't work very well for OpenFlow devices.

Change-Id: I0b61404ff7ae6c542f92787c9e8ab5c7a2e058f1

Change-Id: Idc4864b10f7f2e4cc92a9a25f1fa74835148eab8

Change-Id: Ic19387d76e41003d4f9d2f4f515d555d8683dd14

Change-Id: Icc1ec3070fe595bfc1439048234d6a6f23127c13