- 23 Apr, 2015 16 commits
-
-
…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
Thomas Vachuska authored -
… result in a cascaded build of app modules which require the modified modules. Change-Id: I1c41ca2d11c936bfeb7307ce0e01b20d0141daa6
Thomas Vachuska authored -
…automated system tests!!! Change-Id: I821214cc274377dc22cb5ab88c48567eaab778cb
Thomas Vachuska authored -
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
jcc authored -
…-l] [remote-ip [{karaf-instance-id|-} [ere-pattern]]] Change-Id: I598f0f5dd5f7f5436c0459f93944d0303cfa355e
Thomas Vachuska authored -
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
Jonathan Hart authored
- 22 Apr, 2015 10 commits
-
-
for leadership automatically at startup. Change-Id: I27f297fdd4b62f9cd345df88a772f76ade56d350
Ayaka Koshibe authored -
…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
Thomas Vachuska authored -
…ty itself is not known; it will not be emitted when the component is not known. Change-Id: Ib0ae105336c2fb2bcddfcf2c8a69ff6a2c501a59
Thomas Vachuska authored -
Deprecated transition with table types and added api for transition with table ids. Change-Id: Ifcf2d87d16810666d992e4d9f5ddca3d0da460be
alshabib authored -
is empty. This makes the implementation and logic simpler and more consistent. Change-Id: Ib55c5b9a020e147784cdf6156da2c47e70a3a6c2
Ayaka Koshibe authored
- 21 Apr, 2015 14 commits
-
-
integer representations via Type.ordinal() call Change-Id: Ie2a26c5ced166e12f0e1ea22e39cd5195455a1ad
alshabib authored -
…ice availability change events. Change-Id: Iaed6359598ff87d5706e10eb9d905ed0883617d9
Thomas Vachuska authored -
…ingle OSGi bundle for use in ONOS NetConf providers. Change-Id: I5b27236070878b483dc199686ca94e2b44a4d5fa
Thomas Vachuska authored -
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
wei wei authored
-