홍길동 / onos

Change-Id: Ie94bf690a1df836b4d5b1d6a1297518f823258c2

Change-Id: Id2d3b0f4686888a48feb09eacef3f27136c1df0e

Also, simplifying onos.bucklet by using the rule

Change-Id: If89633db2d83cbfc56a8e70d2bea665ffaf186ff

Change-Id: Iad43824624fbe702bf96248510ce04ecb46de7be

Change-Id: I62c8219b976b1a2a4e35d30ffc7611d0b6aa1f9c

Change-Id: I598b704d9ef77c483bb3c4f83198833d07b38ae1

Also, fixing up the base directory for RC packaging.

Change-Id: Id3c80a75ec27bd887b01a04a3122a2660c8f281b

Change-Id: I4d6680a852183c26d78649f277183164014608c8

Change-Id: I4db2fee926161719d431617ce2fe65ea39968e8a

thus it is mutable.

This reverts commit e38b866a.

Change-Id: Ie71a4cf2d795e2fd781e96fc1274cfcbfc659cb5

If the same path is selected, the flows will not be reinstalled.
This patch fixes that.

Change-Id: I78da0015f7e3b39f3b7ff842f821053c2494b8e6

Change-Id: Iae9bae29acb45f4df86f4125b7975f2ac0186e7e

Change-Id: If965adef131e62f8e27e4b82c8649e572b6b49a5

Change-Id: Icc162201a50de8ae48abdb8e769fb6ed86138a03

Change-Id: I04b96109296125849bc91d5bc92e476338749935

Change-Id: Icf570d086829df51cc4107b3f6efef3efa9e9d21

Change-Id: I57b6e44e03c576be88c5f130f852d5ca5bcb00c9

Change-Id: I61158511680851be375b93c365fc32c0573e9edc

We can print this message in EventuallyConsistentMapImpl rather than printing
a stack trace which doesn't add any value because the exception always comes
from the same place.

Change-Id: Ia233e7ae8605b2b59ffd4ef834209fdaa86e9376

Change-Id: If74914d5c0a4ed0694cf4926fa7deae7927783c8

Change-Id: I2cc29d5672d11aa176c7fa774e9d66f32b2d300f

Change-Id: I3bacbbfcc84259b8bb6904d21b45a1e9e9e60e7a

Change-Id: Ic5c920b0efc40d472d454b0e1a0305f16b39e98c

A set of mininet based HA tests based on onos.py
Currently includes the following tests:
    - a control network partitioning test
    - A dynamic cluster scaling test

Change-Id: I9a8e1019dcc51666fee1d933afd66ff390592525

Change-Id: Iac2b6473a71c1d981b6d2dadc316a31d9b4a02df

Change-Id: I80ad924a8dfde61ac2fbc1d9836d3f145bfc48dc

Change-Id: If73a41687a9c2400de23bbde6179a63ac7f75d15

Change-Id: If6fbc0c3ea432e8d33f6d790491342312333cee4

Change-Id: I4b1af699c90e07811e046335ff2896ec402959b6

There doesn't seem to be any reason to require users to specify an empty
Optional when they want to request from all devices.

Change-Id: I2394bfa3ed07cae5c5f514dd24faea74409a33f4

I think the EdgeService has to use one or the other, because the
TopologyService is not in sync with the Link/Device services. The problem
with using the TopologyService is that it does not handle Port events,
only Device and Link, so it is not suitable for building an inventory of
edge ports.

Change-Id: If31d6d7013985da3e03f8c83f2f2eb2957deffe1

Change-Id: Id34dbef9bd6cfa9971d0d10adf4bbc141f03a913

Change-Id: I7956d1392f620a5bdb4800bc45bfaef1a03d8e38

Change-Id: Ibe69a777105198ab42b9408f9fa9bc1e2bd93696

Change-Id: I88f84f28d9c5243c6ce42c81914b0f87e41bbd3e

Change-Id: I2fc947b3785c6edf1ad20eb432dafc1642781ca7

Change-Id: Ibe7c67e6615f5a19fe4c4c7dea182e1a59dc5eea

Change-Id: I88f6266142da2cfe7bf3569cbe317925c17e3bca

Change-Id: I300d410994361de505558bfcdeb732a8a6c14b91

Change-Id: Ic87885195a6c302d6737b985413eece3fa260e26