홍길동 / onos

1.merge private flow into regular flowrule subsystem.no mirror code any
more.no change flowrule api.
2.define a rich-data-type to carry private flow.
3.modify OpenFlowRuleProvider.class to support for 3rd party private
flow.i don't know whether is suitable.because this class name is
relative with open flow protocal.
4.fix some junit test bug caused by modification of FlowRule interface.

Change-Id: I6c54d1e97f231a75bd1b416f0893e0379613d7ce

…-l] [remote-ip [{karaf-instance-id|-} [ere-pattern]]]

Change-Id: I598f0f5dd5f7f5436c0459f93944d0303cfa355e

Addressed a few issues found while using the flow objectives across a cluster:
 * Flow objectives should be installable from any node, not just the master.
   Therefore we need to ensure all nodes initialize a driver for each switch.
 * We no longer store a list of objectives that are waiting for the switch
   to arrive. If the we don't know about the switch yet we'll try a few times
   over a few seconds to find it, but after that we'll give up and report an
   error to the client.
 * Default drivers need to be available when the FlowObjectiveManager starts
   up, otherwise it is common to get flow objective requests before any
   drivers have been loaded.

Change-Id: I1c2ea6a223232402c31e8139729e4b6251ab8b0f

Change-Id: I1dc6716ee299f1de7608663135a83346800068bf

Also a couple of bug fixes

Change-Id: I8f2ec58ed3403ae03cf7c068dabb30ae4272ff85

for leadership automatically at startup.

Change-Id: I27f297fdd4b62f9cd345df88a772f76ade56d350

…re app id, instead of the requesting app id. This is to prevent packet request flows from vanishing when app removes all its flows. This is a provisional fix until packet requests allow removal via reference counting or a similar tracking strategy.

Change-Id: Ib0e53ae8c6b5ae030a9c17a34407a5897027127b

Change-Id: Idf800e589f12f139b6a39cdcd8144be9214ceb23

…ty itself is not known; it will not be emitted when the component is not known.

Change-Id: Ib0ae105336c2fb2bcddfcf2c8a69ff6a2c501a59

Deprecated transition with table types and added api for transition with table ids.

Change-Id: Ifcf2d87d16810666d992e4d9f5ddca3d0da460be

Change-Id: Iffaf3b46099f868b7245fe0c7819d13e5bff76d3

is empty. This makes the implementation and logic simpler and more consistent.

Change-Id: Ib55c5b9a020e147784cdf6156da2c47e70a3a6c2

Change-Id: Ib98b2996e1ebcca56ad816ea94f25d838c5f4d44

integer representations via Type.ordinal() call

Change-Id: Ie2a26c5ced166e12f0e1ea22e39cd5195455a1ad

Change-Id: I9737cd0e636d94a829c8c79440654c8fe1b55e36

…ice availability change events.

Change-Id: Iaed6359598ff87d5706e10eb9d905ed0883617d9

Change-Id: Iae5dd0b63e567b8218a666ecdbea6558c9e98d70

Change-Id: Ib43e48dcfdd165b27e848ff487f2e2cc58d83005

…ingle OSGi bundle for use in ONOS NetConf providers.

Change-Id: I5b27236070878b483dc199686ca94e2b44a4d5fa

Change-Id: I58c30b663810de42890b75bbcef5c7dc5a4a87ba

Change-Id: I4f767af36101c32493a77570a9729f4e8c300136

Fix ONOS-1247

Change-Id: I8a110bd3cee296f726a63fd1034b5a8f7dc7f0b3

1)Initial Work for ONOS-676: OTN/ROADM (L1/L0 NE) support in ONOS by extending the device/port modeling;
  - extending device type to include L1 OTN NEs;
  - extending port type to include ODUCLT port(T-port), OCH-port(L-port), OMS-port (WDM-port);
  - more standard annotations related to OTN/ROADMs support will come from PCEP provider as well as TL1 providers;
2)Intial Work for ONOS-1276: generic Tunnel subsystem in ONOS for both packet (L3/L2) networks and optical (L1/L0) networks
  - supporting PCEP framework, which is capable of interacting with the PCEP provider;
  - supporting any other kind of tunnel provider;
  - each Tunnel is associated with at least two Labels (abstracted logical entity/Id for virtualization of physical port);
  - same type of Tunnels can be formed as a reachablity graph for other services and NB applications use;

Change-Id: I29af495f90e179e2c5d8753b76e02889a3b4355b

Change-Id: I6a4859fd05edb17a02333e4d68496d54589b586b

Change-Id: Idc2f2e70833bf30c05310f8f09c7daeb68149f98

Change-Id: I762673b1a10aefe1cb5e50fd0c3a05479a1a65c6

Change-Id: I4bf6e102c67c2effd0d8b65538fcf3a8a1db69e1

Change-Id: I9fcc1c85bb4169681b20df08d69ac8fdcc9d5ddc

Change-Id: Ied1fd508c9ced3799d16d0c1591a42ce690afde6

…vice.getCandidates(topic)

Change-Id: I9aaea9dfa14e4e9916103a61c8e59290ad656aa7

Change-Id: I5a1c4e3a73162ee34ede1ea1aba641898822adea

Change-Id: Id8859e24d0c7ac7f948516388069639093bad524

Change-Id: I8be3dbc403ea1202fd496e666955402247f71bf1

Change-Id: Ie6d9fe5e84f82ffe708f124ffdce30a9ca4900ab

LabelResource subsystem will be used to manage label resources such as
MPLS labels, ... (Part of ONOS-1223)

:)

Change-Id: Ib11eac84d81d7d86eaaf0222cf0bd7d3c64d2e51

…pp.origin (optional) is sufficient to trigger generation of boilerplate app.xml and features.xml files.

Change-Id: Ied8f3f8bf8774fae85e11c79a733b34dd5868949

…ly switch between netty and io loop (default is netty)

Change-Id: Id9af0756bf0a542f832f3611b486b2ac680b91e4

Provides an abstraction which isolates the application from any pipeline
knowledge. By using the provided objectives applications can express
their forwarding desires in a pipeline agnostic way. The objectives
are then consumed by a driver for the specific device who converts them
into the appropriate pipeline coherent flows.

Change-Id: I74a68b4971c367c0cd5b7de9d877abdd117afa98

…ps activated by default (via onos-setup-karaf or onos-install/onos-config)  are now onos-drivers and onos-openflow.

Change-Id: I35c7cca79a4b72e966cbc2cebe72b109f2d92706

The app.xml and features.xml pull in the correct bundles to ignite
the application successfully

Change-Id: I719290a700b46042ff5c54ec26c19458032d78cf