홍길동 / onos

… an entry in the navigation panel.
- Added placeholder "flow" view.

Change-Id: I3a969d16baf608b132c10cfc7f154d0ce51c765e

More explict handling of versatile forwarding flows in corsa driver.
Moving TunnelConnectivityManager to use flowObjectives instead of flowRules.

Change-Id: If43023f30a6e7a028dfdefbe1ffbcc710a1c7be3

Change-Id: I12b16eb97b011899984fda00db229b5a8ff00fa3

- Add 'olo' command to filter log of remote ONOS instance
- Modify 'onos-log' such that it can run on OSX

Change-Id: Iddab996564af01672c14caca725397c574267bad

Change-Id: If2df3abb78838cbd666353474ff276e0d1fb4610

…the specified IP, if given. Otherwise, it will attempt to use ONOS_IP and if that's not available ONOS_NIC to find an adapter with a matching IP address. Usage is backwards compatible.

Also added new onos-karaf command which runs onos-setup-karaf && karaf $@ as a convenience; aliased to 'ok'.

Corrected onos-build-selective to propagate error status only if the build fails.

Change-Id: I920b06fa21edc95b7d651270efe2f95da90ff010

Change-Id: Ibea4415d3c1fc717e609aebcd2205d0bba01c96d

… result in a cascaded build of app modules which require the modified modules.

Change-Id: I1c41ca2d11c936bfeb7307ce0e01b20d0141daa6

Change-Id: I8c77e5e04d7d7a4480dbff47578ef46aa7637054

Change-Id: I9f9fc4c2c251fa1519115ef60485890a4514c751

Change-Id: I2c7a8b5dd3e3817b1f1e1a91a4ef5d9953a8a283

Change-Id: I56b981355b02face3a5bb09d2ca2e2bd29f7c715

…automated system tests!!!

Change-Id: I821214cc274377dc22cb5ab88c48567eaab778cb

Change-Id: I0035c8cdd9f909af24a47b0db04d306c33aa8c44

Change-Id: Ie8fad0186f5a41596877463c0293748e6cf2d74f

Change-Id: Ia3fc4ab8406dadcecc5d718e905a951f77a807cf

Change-Id: Idd845ac2cb2ac2739735c384bd8f096fb975210c

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