홍길동 / onos

Change-Id: I2e7faeb56d7ec3eafa5e1ab2398b852e81c13d74

Change-Id: Ia7a56644ad55c458ef17f31b2cf7ec9b9210dd06

Addresses one of the causes of ONOS-4605 - not sure if there are others.

Change-Id: I2897e84a10b13ac00d5a03c31b7a08daae57d8cb

Changes:
- Discards Link events if one of the switch is down;
- Triggers the paths optimization after device-down event;

Change-Id: I4114f2450401e0d1ff5658d592daf319d977f20e
(cherry picked from commit 2c51531a)

Change-Id: Icab56fcd9ca874e8a33836288163a7650e17599f

Change-Id: Ia82b8d70de0b5d824d808f9593ada64d3c1fbd09

thus it is mutable.

This reverts commit 4b3e2f67.

Change-Id: I624fafd95c61766b3952263612a2a44f85d022a8

Change-Id: I2cc29d5672d11aa176c7fa774e9d66f32b2d300f

Change-Id: I3bacbbfcc84259b8bb6904d21b45a1e9e9e60e7a

Change-Id: Ic5c920b0efc40d472d454b0e1a0305f16b39e98c

Change-Id: I2fc947b3785c6edf1ad20eb432dafc1642781ca7

Change-Id: I61158511680851be375b93c365fc32c0573e9edc

Change-Id: I828cd738efb63e23f519bdd6a5d8b2bb58240df2

Change-Id: I9b4d30114b22dcd32b228e4f17bb541beed4ebed

Change-Id: I6a7adbce08e589e29763b1f7144d3a8d8742df9d

Change-Id: I19f2ad98e56352570478a66f896c1e9c6a3573e5

Change-Id: I445eb6505c99d770e612c43eb8fca6d53cf806d4

Change-Id: I1b1c5ac141a68a6d6308238ae0934249c7a3af96

Change-Id: Icde0d7e8806f59da99082089a83dda26b23d12a8

Change-Id: I732920bc81d6955b84a222b095bfa18c6974abe3

Change-Id: Icba699c84194170143c54e249af6317003ecdfc6

Change-Id: Ie9d454fe03a92a9f865d45882de5749f55f2f2f9

Change-Id: I206e8a392f8bb158a8de42ef0c536e509fd21433

Different threads could call run(), satisfy() and fail() method.
Each of the methods reads/writes multiple fields during the method call.
These method calls need to be synchronized to gurantee to see the
latest value.

Change-Id: Ic252b56e0902170d7e0fdb83f96f0fb2e55ec56b

Change-Id: I47d46be0c36bf3ee7e4a9bab7f6dd3dfc4d80256

The field assignment doesn't change over the life time

Change-Id: I022dbe7ce8a1cbae8837fd97bff8610a4cada610

This reverts commit 2451a099.

Change-Id: Iab7afd7c61cc1e25292e093660170101da779cf8

Change-Id: I7389fa017287f0daac299229914e7fbf9c60a91e

Change-Id: I180ee4fb26383c017fbeff98c324d99dc21a34c4

Change-Id: I95f87b93f18da98a0bd0b77d7c41b83aa9f7390e

Change-Id: I806f32c13df33f137d199618de0ad495833a5d0e

Updated unit tests, and added a test for the app context in the URL.

Change-Id: I110b62ff8366a503c3309df0f26a7dd213ae0c5f
(cherry picked from commit fa875bb1)

Change-Id: Iffb518c80a5b06354c8966c621cc1190fb104499

…nos is behind an app prefix

Change-Id: I271da533f39091efdd01d8104c1e6740effead52

Change-Id: Ib964252dd05754ce7069a7a82ccb1d1c29bfa978

Change-Id: Ie0c100868c949335aea31e2d086d262a32f5d49e

Multiple threads could access the field, lastSink, then they should read
the latest value of lastSink

Change-Id: I279ed6fa3db357008603cde5cb2c57671e66b33c

The field, dispatchFuture, is accessed in activate() method and the thread
where Watchdog is running. Then, different threads could access the field
and couldn't read the latest value.

Change-Id: Iceb390bcf3c5711c1dbb59198667138c8a90b036

The field, dispatchLoop, is accessed in activate() method and the thread
where Watchdog is running. Then, different threads could access the field
and could miss the latest value.

Change-Id: Id218522f5b318fb3d05833ba57d908a1bf6d2949

The field, lastStart, is read/written from different thread pools.
As a result, the field could be accessed from different threads.

Change-Id: Ia50c5bd3405bf2af98abb9d14f7e35d840f62483