Transaction Language 1 (TL1) is a management protocol that is widely used in the optical networking space. ONOS comes with the needed building blocks to connect and interact with TL1 devices.
Tl1Device
is a container that holds the Netty channel and some device attributes such as login and password.
Tl1Command
represents a command that is sent from the controller to a network element. Its typical structure is as below, and the interface defines various accessor methods as well as a builder.
VERB-MODIFIER:<tid>:<aid>:<ctag>::parameter-list; |
Tl1Controller
maintains a list of TL1 devices, allows you to connect to them, send and receive messages, and register listeners.
Tl1Listener
defines the interface for notification of device connect/disconnect events.
Implementations of all these interfaces are prefixed with Default
, for instance DefaultTl1Controller
holds the implementation of the Tl1Controller
interface.
The ONOS TL1 southbound is implemented in the Tl1DeviceProvider
.
Adding devices to ONOS is done by injecting them into the device provider, more specifically Here is an example JSON, that you will inject into ONOS using onos-netcfg $OC1 tl1.json
.
{ "devices": { "tl1:10.128.14.81:3082": { "basic": { "name": "Lumentum", "driver": "lumentum-waveready" } } }, "apps": { "org.onosproject.tl1": { "devices": [ { "ip": "10.128.14.81", "port": 3082, "username": "test", "password": "test" } ] } } } |
Adding a new device to ONOS requires implementing a set of behaviors. For instance, to discover devices and their ports, implement the DeviceDescriptionDiscovery
. If your device supports flow rules, implement the FlowRuleProgrammable
. And so on. Go here for more information: Device Driver Subsystem.
In the following, let's take LumentumWaveReadyDiscovery
as an example. Here you can see how the behavior interacts with the TL1 controller. For example, this is how we fetch the device description.
// Fetch device description Tl1Command ddCmd = DefaultTl1Command.builder() .withVerb(RTRV) .withModifier(NETYPE) .withCtag(101) .build(); Future<String> dd = ctrl.sendMsg(deviceId, ddCmd); try { String ddResponse = dd.get(TIMEOUT, TimeUnit.MILLISECONDS); return new DefaultDeviceDescription(defaultDescription, true, extractAnnotations(ddResponse)); } catch (InterruptedException | ExecutionException | TimeoutException e) { log.error("Device description not found", e); return defaultDescription; } |
We do three things: (1) build a TL1Command
using a builder pattern, (2) send the message using the controller, and (3) wait for a response to arrive.
After implementing your behaviors, ensure that ONOS knows about them. Here is an example of the lumentum-drivers.xml
.
<driver name="lumentum-waveready" manufacturer="Lumentum" hwVersion="WR*"> <behaviour api="org.onosproject.net.device.DeviceDescriptionDiscovery" impl="org.onosproject.drivers.lumentum.LumentumWaveReadyDiscovery"/> <behaviour api="org.onosproject.net.optical.OpticalDevice" impl="org.onosproject.net.optical.DefaultOpticalDevice"/> </driver> |
Here is a list of desirable features that unfortunately are not available in the current code base. Patches and bug reports are very welcome!
Sending messages using the Tl1Controller uses the following signature. Ideally, we don't want to return a String
but a Tl1Message
that can easily be parsed.
CompletableFuture<String> sendMsg(DeviceId deviceId, Tl1Command msg); |
Tl1Device
, use ONOS' DeviceKeyService
sub-system dedicated to this job.Tl1DeviceProvider
will only login to the device when that instance becomes the master. In a multi-instance deployment, it's probably a good idea to have (some of) the standby instances logged in, ready to take over when they becomes master. This requires reworking the Tl1DeviceProvider
, as well as a way to store multiple accounts per device.