홍길동 / onos

Only the master of the source device do path calculations

Change-Id: I29f6d49f039d61014f0ff8ddce73db2ad18eb6e4

Change-Id: I066e03ad9a491ad99816a976bc5561667878031a

Change-Id: I6da200db4c946708df97d1fa35ae198ea68f0451

Change-Id: Ib91b7c47c95e005a0ace1fdaa7e82fbdb7f02533

Change-Id: Iad44ac863449afdbf21d8766479af569f9ba9b6e
(cherry picked from commit a2ccaa56)

This should fix the problem seen in VirtualBox where you
may have some random interface which is host-only which needs
to have port forwarding set up on it.

Change-Id: Iacdbb129d52529783bdab1c3d768131f6eaf0364
(cherry picked from commit 930138e3)

Change-Id: I013b78422014cc8285d2d2481d44ff2140af6b7d

Similarly to ONOS-4206, due to a bug in kryo, a non-registered class
(Date in this case) was causing such a problem.

Change-Id: I993f4b41d4deaa617065b29086a49d834832eca8

- `buck targets` was failing due to this

Change-Id: I0f35abdcaad2900cd4616d494f6d4f4c1e9c1b81

Change-Id: I4ea41890ed8a0ef22dd75fece6817eab34212f00

Change-Id: Ibc3836049b6442033920a78a4937022dc20f1751

Change-Id: Id31312419eb97362b8ec4cad92ed215911574010

Change-Id: Ie708e932d95d3eedad417075f39135aae31064d9

Change-Id: Ia8097bcd487e2300c1e22664ac0f41231d421c30

Most notably:
- Added support for onos.py's ONOSCluster controller (it works with
	"mn --custom onos.py,bmv2.py --switch onosbmv2 ...")
- Randomly select an open port for the Thrift RPC server

Change-Id: Ifa974741dc4a3693777f01866b1f6203d0e7e75e

Change-Id: Ic412e5032341dfd9e41d1065ffd35070265409d3

This doesn't seem quite right, because it doesn't match
a supposedly legal use case where you omit the output file
and list the node IP addresses. However, it's better than
what we have now, which simply ignores the output file name.

Intended to help with ONOS-4667

Change-Id: Ib46195e7b829bc4d304c4dd51138b73acd4f1501
(cherry picked from commit 50df0982)

Change-Id: I8b674f0360744590b9c04c3b344594e4681036f4

Change-Id: I040e22e1ad322b8f6de8c19665d7706831f92ea0

Change-Id: Ie4fb7054e0f51821119616b337a3827c4897c622

Change-Id: I3e2966cf9850c00a7c8223992b4cf6f6709e23df

Change-Id: Iabf8efe106d07c9eafe3bf0a242e3cd12182bed1

Change-Id: I4551078f3f3924235e00ecf1306448e4935d622b

Change-Id: Ia2853932db8e27bd1447d225b160c8e583d7df61

Change-Id: I1945f614c02a39326d22e268fbb015e50d075368

Also, added a test for serialization

Change-Id: I77e80fa7597b552c71e80c9d39d03549e0325778

Serialization was failing when the inner ByteBuffer instance was a
HeapByteBuffer. Also, simplified ImmutableByteSequence.toString()

Change-Id: I4f75086a9b6536205fb43b78a0e4d2bfce9e8a5c

Change-Id: I1b047624dd96383baee8f93e9f94052a4c5ff10a

Also, adding fixme that can be a common pitfall in Buck build land

Change-Id: I96828aa520d6b81c71d1d7b2ce1841d93c92a843

Change-Id: Id1d5cbaa84d63e0e09af5ff919dacab1f245f13d

Change-Id: I543201c54883e06182c1c83c4c64dd16a18e096c

Change-Id: I1a7fbcf8e867e95bc514fa4745f35226b99d0d3b

Change-Id: Ib87efe01cb926a3b4c789c9875458ad2ba1b7c8c

Change-Id: I967a952e9fe014a88b73abadb3003b5f8b6e45b9

Change-Id: I5e6ab619f66ca71badc25efc7be7560070639051

Fix the problem that only local delegation is triggered

Change-Id: Ibe7b4a6abb447b9a8e3a0959882ef2da0d21f4be

Change-Id: Ic7a68e1e28d9f2fb090ffb9c2ebcc2e4e6fbc586

Change-Id: I81c7282f7c5c47ad6d088b3df1deadf1d44d2772

Madan suggested that this might help vs. the pipelined
startup we were doing before, so let's try it.

We will unpack/install all nodes before we start up,
so that we can start the whole cluster at about the same
instant.

Note that this is probably closer to what we'd see in hardware.

The disadvantage is that we don't get a "clean" environment
with each invocation of start().

Change-Id: I0a45984f50e1ef25a7d8a836e46978fdbdff0bd0

Change-Id: Ia8e6a305bebb51556974b72c83d86b472b6918e5