홍길동 / onos

Change-Id: I0e556f4324375132787a6b1abefccdd1414abf50

This commit implements control message collection feature in
OpenFlow message provider.

Change-Id: I2a3ed2e5edbe1f39b503bb74a10259026b806513

Change-Id: I8e7f6451876c6733bf33667face30b32e5378c99

Change-Id: I28ed2a2dba5bca8ad6d85901c29cd081721cdc9f

Change-Id: Ia2a4953ea68d88e510689a3131398fc003194c1e

Change-Id: I9cd9d80ce0accc017118a944dff96367bca89bde

Change-Id: I6343d0dc528eef5e2446eea6c9f370dcaf6ed7e9

Change-Id: I7f2cb331a19aeca1a578aade6488a6480d15496c

interfaces to use.

Change-Id: I4eb069760df0995d9e831e024ddbc0493bccce0b

Added new config fields
- SSH port, user, private key file
- localManagementIp for connection b/w a compute node and VM

Renamed some config fields and methods
- phyPortName is changed to dataPlaneIntf
- localIp is changed to dataPlaneIp
- ovsdbIp is changed to hostManagementIp and it is used to SSH as well
- checkXXX methods with boolean return are renamed to isXXX

Removed unnecessary OVSDB_CONNECTED state
Removed cordvtn-node-add CLI due to too many arguments

Change-Id: If5efb65fc58bfa8a10767047f01598dc2ac02a04

Change-Id: I29e28ae268693f62631f2d70a5e6f74e482a4643

 * Made PIMNeighbor mostly immutable (apart from updatable timestamp)
 * Equals and hashCode for PIMNeighbor
 * Remove neighbor when we see a HELLO with holdTime==0
 * Periodic task to time out neighbors who haven't sent a HELLO in a while
 * Added a CLI command to view PIM neighbors

Change-Id: I59e52a847f7abcb8e9ac660c2cccace53e46867b

Now the PIM application requires PIM Interface configuration for each interface
that will have PIM enabled (no longer uses all ONOS interfaces). The
interface-specific PIM parameters can be tuned.

Change-Id: Ibc284fdbe1b3aa4da48097b3e92470bce4f349a7

Also added packet request to PacketService to get punt flows installed in switches.

Change-Id: I7340d09a1cf2ec06fb33ac0c4fc14eb43e94f496

Change-Id: I803ca5ee86e4a605c06916687d55a37059fe2ad2

Change-Id: Iaeb0aa0abf9f52d514a2c040598599a5b8a55ee8

Change-Id: I771b23db6920b26b592abc5d5156e9d77cde4f00

DeviceKeyManager and the distributed device key store.

Change-Id: I32544040590b31a59e20f3375fca453a117f940c

Change-Id: I36df7e23792f7004dfae823a8700f6c887ea1efd

Change-Id: Id112f7027454132f00ca45b4254aa3f5c2e7b094

Change-Id: Ib3d1c611ad9eb4491693ea10ee50ea0123f20ee2

Change-Id: I69fdec826b1578777020759f5f4144d4057db1d9

Change-Id: Ie4d2ef90c261f8bb5b560cb2b62c5cf7cca29988

Change-Id: Id9ad101e82a9148ddf029fdcf6404173a9574539

Change-Id: I4a8a209c07db954bb7fb3dcbc236bc3a8018a4b4

Change-Id: I1db2bb120463766d984e33743667ee187cb1378b

Change-Id: Ia0ad61aabf5c35fbfadc5b127662edb497bcc9c0

Change-Id: I0d831cc51199bce0e0dc2b7bb1b5bc2df9fbf90b

- Remove components() method from Resource
- Add isTypeOf() method to Resource

Change-Id: I390eb6057fc7e2c3e93eb2a18d161f661ad6c180

Change-Id: I9604ec59a9eb1e4a582f7af86511c77044edb38b

Change-Id: I03e6f61e2b31df101690c68b68e39f3dd7917c6a

With current implementation, flow id can be either assigned by
fromApp method or withCookie method. This misleads the end-user
to properly instantiate a new flow rule. This commit restricts the
flow id assignment which does not allow to assign cookie and
appId at the same time.

Change-Id: I8d7e27517c7ef636d427c3d8b8f9cc267fcb0702

- also cleaned up some Long/Lat code.
- Note also that metadata from client is structured so 'lng/lat' properties
    (from repositioned node) are wrapped in 'equivLoc' object.

Change-Id: I5afc53d26ef56fc0932f8650e8f7df79b36c3947

Change-Id: Ie31980fec48ccc914f2b384993365d6456f36562

Change-Id: I9104d91541f0f2fcd8476264772a920b59626003

Change-Id: Ica16e43849dd3bb0b90936a20ef4af477045b376

Change-Id: I2940b3db9c6da3a3c43c192a2b390c46b40749e7

Change-Id: I36a007b0ffaac8c3a4ad1dc39ad9822b8d7e5878

…d didn't unregister descendants (ONOS-3827).

Change-Id: I48956234553053e2a54834129b5f10357ca116ea

Change-Id: I18f3376d1466077e95d7324a27a660302f0123b3