This page describes the ODTN Phase1.0 demonstration details which is done at NTT Communication's lab environment, and what is achieved by ODTN Phase1.0 development.
Scope
- Point to point network
- Directly connected transponders, or OLS configured out-of-band
- TAPI NB, OpenConfig SB
- No optical configuration (Configure only port enable/disable and frame mapping)
Available Devices
- NEC
- Only enable/disable client port and line port
- Infinera XT3300
- Setup logical-channel-assignment which associate client port and line channel
- Now support static frame mapping only, but with some additional work we can support dynamic frame mapping using optical channel resource management feature
- Configuration used in this demo is described here: https://docs.google.com/presentation/d/1RJkPq_6Yt6aS8txHNwZbKjAx3MK2SDhkoRoctj9_oNY/edit#slide=id.g3873fc6400_0_944
Available models
- OpenConfig model
- Each vendor support different OpenConfig model, please check detailed version from here: https://wiki.onosproject.org/display/ODTN/Available+OpenConfig+models+and+versions+for+phase+1
- TAPI model
- v2.0.2
Available TAPI NBI endpoints
- tapi-common
- get-service-interface-point-details
- get-service-interface-point-list *
- tapi-connectivity-service
- create-connectivity-service
- delete-connectivity-service
- get-connectivity-service-details
- get-connectivity-service-list *
* Not working correctly and only one entity will be returned even if there are more than two entities. This limitation is caused by the issue that onos-yang-tool cannot deal with list without keys.
This will be fixed in the near future, please check: https://groups.google.com/a/opennetworking.org/forum/#!topic/odtn-sw/ls-p9JkKnuo
Demo Setup and Scenario for Infinera XT3300
Installation
Install and setup onos as a single-instance.
Setup pair of above available transponders or NETCONF emulators
- You can get dockerized emulator from here (ODTN internal use only):
https://drive.google.com/drive/folders/1Md2zGKBKuIMnhTlYhiVSVhIeU-1fGqK6
Demo
Setup onos
$ ok clean ... $ onos localhost Welcome to Open Network Operating System (ONOS)! ____ _ ______ ____ / __ \/ |/ / __ \/ __/ / /_/ / / /_/ /\ \ \____/_/|_/\____/___/ Documentation: wiki.onosproject.org Tutorials: tutorials.onosproject.org Mailing lists: lists.onosproject.org Come help out! Find out how at: contribute.onosproject.org Hit '<tab>' for a list of available commands and '[cmd] --help' for help on a specific command. Hit '<ctrl-d>' or type 'system:shutdown' or 'logout' to shutdown ONOS. onos> apps -a -s * 8 org.onosproject.yang 2.1.0.SNAPSHOT YANG Compiler and Runtime * 9 org.onosproject.config 2.1.0.SNAPSHOT Dynamic Configuration * 10 org.onosproject.configsync 2.1.0.SNAPSHOT Dynamic Configuration Synchronizer * 11 org.onosproject.faultmanagement 2.1.0.SNAPSHOT Fault Management * 12 org.onosproject.netconf 2.1.0.SNAPSHOT NETCONF Provider * 13 org.onosproject.configsync-netconf 2.1.0.SNAPSHOT Dynamic Configuration Synchronizer for NETCONF * 21 org.onosproject.restsb 2.1.0.SNAPSHOT REST Provider * 27 org.onosproject.drivers 2.1.0.SNAPSHOT Default Drivers * 34 org.onosproject.restconf 2.1.0.SNAPSHOT RESTCONF Application Module * 39 org.onosproject.optical-model 2.1.0.SNAPSHOT Optical Network Model * 40 org.onosproject.drivers.optical 2.1.0.SNAPSHOT Basic Optical Drivers * 42 org.onosproject.proxyarp 2.1.0.SNAPSHOT Proxy ARP/NDP * 44 org.onosproject.hostprovider 2.1.0.SNAPSHOT Host Location Provider * 45 org.onosproject.lldpprovider 2.1.0.SNAPSHOT LLDP Link Provider * 46 org.onosproject.openflow-base 2.1.0.SNAPSHOT OpenFlow Base Provider * 47 org.onosproject.openflow 2.1.0.SNAPSHOT OpenFlow Provider Suite * 57 org.onosproject.protocols.restconfserver 2.1.0.SNAPSHOT RESTCONF Server Module * 61 org.onosproject.pathpainter 2.1.0.SNAPSHOT Path Visualization * 88 org.onosproject.models.tapi 2.1.0.SNAPSHOT ONF Transport API YANG Models * 89 org.onosproject.models.ietf 2.1.0.SNAPSHOT IETF YANG Models * 90 org.onosproject.models.openconfig 2.1.0.SNAPSHOT OpenConfig YANG Models * 91 org.onosproject.models.openconfig-infinera 2.1.0.SNAPSHOT OpenConfig Infinera XT3300 YANG Models * 92 org.onosproject.models.openconfig-odtn 2.1.0.SNAPSHOT OpenConfig RD v0.3 YANG Models * 93 org.onosproject.odtn-api 2.1.0.SNAPSHOT ODTN API & Utilities Application * 94 org.onosproject.drivers.netconf 2.1.0.SNAPSHOT Generic NETCONF Drivers * 95 org.onosproject.drivers.odtn-driver 2.1.0.SNAPSHOT ODTN Driver * 96 org.onosproject.odtn-service 2.1.0.SNAPSHOT ODTN Service Application * 177 org.onosproject.mobility 2.1.0.SNAPSHOT Host Mobility
Initially there are no devices/ports/links registered.
onos> devices onos> ports onos> links
In DCS store, only TAPI context and topology are initially set. We can see the TAPI model state in DCS by using following command:
onos> odtn-show-tapi-context XML: <context xmlns="urn:onf:otcc:yang:tapi-common"> <connectivity-context xmlns="urn:onf:otcc:yang:tapi-connectivity"/> <topology-context xmlns="urn:onf:otcc:yang:tapi-topology"> <topology> <uuid>c4b7a7fb-32b9-4f11-a146-1b7df7f59839</uuid> </topology> </topology-context> </context>
Setup Emulator
To setup OpenConfig emulator, all you have to do is to download and setup emulator image(https://drive.google.com/drive/folders/1Md2zGKBKuIMnhTlYhiVSVhIeU-1fGqK6),
if it's the first time you are running the demo plea go into the dowloaded folder of the emulator(for example, "emulator-oc-xt3300") and execute
# Dockerfile contains docker's configuration, <tag> is just the docker-image name. docker build -f Dockerfile -t <tag> .
then for this run and for any consequent run of the emulator you can do
# <tag> specifies the docker-image you built just now. <host_port>:<container_port> defines port mapping between your own host and docker's container created from <tag>. In Dockerfile, "EXPOSE 830" means open port 830, so <container_port> should be 830. docker run <tag> -p <host_port>:<container_port>
or using docker-compose, you can run pair of OpenConfig emulator as follows (Suggested):
$ cat docker-compose.yml version: '2' services: openconfig_xt3300_1: build: ./emulator-oc-xt3300 ports: - "11002:830" openconfig_xt3300_2: build: ./emulator-oc-xt3300 ports: - "11003:830" $ docker-compose up -d
If you want to check that the docker instance works correctly, you can use netconf-console command and send "hello" request to emulator. netconf-console need to be installed, please google that.
Once docker containers are started, the default user is root. So you need to use useradd and passwd to create user admin.
$ netconf-console --host=127.0.0.1 --port=11002 -u admin -p admin --hello <nc:hello xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0"> <nc:capabilities> <nc:capability>urn:ietf:params:netconf:base:1.0</nc:capability> <nc:capability>urn:ietf:params:netconf:base:1.1</nc:capability> <nc:capability>urn:ietf:params:netconf:capability:candidate:1.0</nc:capability> <nc:capability>urn:ietf:params:netconf:capability:confirmed-commit:1.0</nc:capability> <nc:capability>urn:ietf:params:netconf:capability:confirmed-commit:1.1</nc:capability> <nc:capability>urn:ietf:params:netconf:capability:xpath:1.0</nc:capability> <nc:capability>urn:ietf:params:netconf:capability:validate:1.0</nc:capability> <nc:capability>urn:ietf:params:netconf:capability:validate:1.1</nc:capability> <nc:capability>urn:ietf:params:netconf:capability:rollback-on-error:1.0</nc:capability> <nc:capability>urn:ietf:params:netconf:capability:with-defaults:1.0?basic-mode=explicit&also-supported=report-all-tagged</nc:capability> <nc:capability>urn:ietf:params:netconf:capability:yang-library:1.0?revision=2016-06-21&module-set-id=206f40597ee8e8d35d0f0e10eebccb9e</nc:capability> <nc:capability>http://tail-f.com/ns/netconf/actions/1.0</nc:capability> <nc:capability>http://tail-f.com/ns/netconf/extensions</nc:capability> <nc:capability>http://openconfig.net/yang/interfaces?module=openconfig-interfaces&revision=2016-05-26</nc:capability> <nc:capability>http://openconfig.net/yang/interfaces/ethernet?module=openconfig-if-ethernet&revision=2016-12-22</nc:capability> <nc:capability>http://openconfig.net/yang/openconfig-ext?module=openconfig-extensions&revision=2015-10-09</nc:capability> <nc:capability>http://openconfig.net/yang/openconfig-types?module=openconfig-types&revision=2017-01-13</nc:capability> <nc:capability>http://openconfig.net/yang/optical-amplfier?module=openconfig-optical-amplifier&revision=2016-03-31</nc:capability> <nc:capability>http://openconfig.net/yang/platform?module=openconfig-platform&revision=2016-06-06</nc:capability> <nc:capability>http://openconfig.net/yang/platform-types?module=openconfig-platform-types&revision=2016-06-06</nc:capability> <nc:capability>http://openconfig.net/yang/platform/transceiver?module=openconfig-platform-transceiver&revision=2016-12-22</nc:capability> <nc:capability>http://openconfig.net/yang/terminal-device?module=openconfig-terminal-device&revision=2016-12-22</nc:capability> <nc:capability>http://openconfig.net/yang/transport-line-common?module=openconfig-transport-line-common&revision=2016-03-31</nc:capability> <nc:capability>http://openconfig.net/yang/transport-types?module=openconfig-transport-types&revision=2016-12-22</nc:capability> <nc:capability>http://tail-f.com/ns/aaa/1.1?module=tailf-aaa&revision=2015-06-16</nc:capability> <nc:capability>http://tail-f.com/ns/common/query?module=tailf-common-query&revision=2017-12-15</nc:capability> <nc:capability>http://tail-f.com/ns/kicker?module=tailf-kicker&revision=2017-09-28</nc:capability> <nc:capability>http://tail-f.com/yang/acm?module=tailf-acm&revision=2013-03-07</nc:capability> <nc:capability>http://tail-f.com/yang/common?module=tailf-common&revision=2018-03-01</nc:capability> <nc:capability>http://tail-f.com/yang/common-monitoring?module=tailf-common-monitoring&revision=2013-06-14</nc:capability> <nc:capability>http://tail-f.com/yang/confd-monitoring?module=tailf-confd-monitoring&revision=2013-06-14</nc:capability> <nc:capability>http://tail-f.com/yang/netconf-monitoring?module=tailf-netconf-monitoring&revision=2016-11-24</nc:capability> <nc:capability>http://tail-f.com/yang/xsd-types?module=tailf-xsd-types&revision=2017-11-20</nc:capability> <nc:capability>urn:ietf:params:xml:ns:yang:iana-crypt-hash?module=iana-crypt-hash&revision=2014-08-06&features=crypt-hash-sha-512,crypt-hash-sha-256,crypt-hash-md5</nc:capability> <nc:capability>urn:ietf:params:xml:ns:yang:iana-if-type?module=iana-if-type&revision=2016-11-23</nc:capability> <nc:capability>urn:ietf:params:xml:ns:yang:ietf-inet-types?module=ietf-inet-types&revision=2013-07-15</nc:capability> <nc:capability>urn:ietf:params:xml:ns:yang:ietf-interfaces?module=ietf-interfaces&revision=2014-05-08&features=pre-provisioning,if-mib,arbitrary-names</nc:capability> <nc:capability>urn:ietf:params:xml:ns:yang:ietf-netconf-acm?module=ietf-netconf-acm&revision=2012-02-22</nc:capability> <nc:capability>urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring?module=ietf-netconf-monitoring&revision=2010-10-04</nc:capability> <nc:capability>urn:ietf:params:xml:ns:yang:ietf-netconf-notifications?module=ietf-netconf-notifications&revision=2012-02-06</nc:capability> <nc:capability>urn:ietf:params:xml:ns:yang:ietf-yang-library?module=ietf-yang-library&revision=2016-06-21</nc:capability> <nc:capability>urn:ietf:params:xml:ns:yang:ietf-yang-types?module=ietf-yang-types&revision=2013-07-15</nc:capability> <nc:capability>urn:ietf:params:xml:ns:netconf:base:1.0?module=ietf-netconf&revision=2011-06-01</nc:capability> <nc:capability>urn:ietf:params:xml:ns:yang:ietf-netconf-with-defaults?module=ietf-netconf-with-defaults&revision=2011-06-01</nc:capability> </nc:capabilities> </nc:hello>
Device registration and topology discovery
Register transponder devices using onos-netcfg. Please replace "10.1.8.124" by your host's IP address.
$ cat openconfig-device.json { "devices" : { "netconf:10.1.8.124:11002" : { "basic" : { "driver":"infinera-xt3300" }, "netconf" : { "ip" : "10.1.8.124", "port" : "11002", "username" : "admin", "password" : "admin" } }, "netconf:10.1.8.124:11003" : { "basic" : { "driver":"infinera-xt3300" }, "netconf" : { "ip" : "10.1.8.124", "port" : "11003", "username" : "admin", "password" : "admin" } } } } $ onos-netcfg localhost openconfig-device.json
Check the registered devices and ports.
You can see these devices and ports from both ONOS GUI and CLI.
onos> devices id=netconf:10.1.8.124:11002, available=true, local-status=connected 8s ago, role=MASTER, type=TERMINAL_DEVICE, mfr=Infinera, hw=XT-3300, sw=unknown, serial=unknown, chassis=0, driver=infinera-xt3300, ipaddress=10.1.8.124, locType=none, name=netconf:10.1.8.124:11002, port=11002, protocol=NETCONF id=netconf:10.1.8.124:11003, available=true, local-status=connected 8s ago, role=MASTER, type=TERMINAL_DEVICE, mfr=Infinera, hw=XT-3300, sw=unknown, serial=unknown, chassis=0, driver=infinera-xt3300, ipaddress=10.1.8.124, locType=none, name=netconf:10.1.8.124:11003, port=11003, protocol=NETCO onos> ports id=netconf:10.1.8.124:11002, available=true, local-status=connected 12s ago, role=MASTER, type=TERMINAL_DEVICE, mfr=Infinera, hw=XT-3300, sw=unknown, serial=unknown, chassis=0, driver=infinera-xt3300, ipaddress=10.1.8.124, locType=none, name=netconf:10.1.8.124:11002, port=11002, protocol=NETCONF port=[GIGECLIENTCTP.1-A-2-T1](1), state=enabled, type=packet, speed=1000 , oc-name=GIGECLIENTCTP.1-A-2-T1, oc-type=GIGECLIENTCTP.1-A-2-T1, odtn-connection-id=connection:1, odtn-port-type=client port=[GIGECLIENTCTP.1-A-2-T3](3), state=enabled, type=packet, speed=1000 , oc-name=GIGECLIENTCTP.1-A-2-T3, oc-type=GIGECLIENTCTP.1-A-2-T3, odtn-connection-id=connection:2, odtn-port-type=client port=[GIGECLIENTCTP.1-A-2-T5](5), state=enabled, type=packet, speed=1000 , oc-name=GIGECLIENTCTP.1-A-2-T5, oc-type=GIGECLIENTCTP.1-A-2-T5, odtn-connection-id=connection:3, odtn-port-type=client port=[GIGECLIENTCTP.1-A-2-T7](7), state=enabled, type=packet, speed=1000 , oc-name=GIGECLIENTCTP.1-A-2-T7, oc-type=GIGECLIENTCTP.1-A-2-T7, odtn-connection-id=connection:4, odtn-port-type=client port=[GIGECLIENTCTP.1-A-2-T9](9), state=enabled, type=packet, speed=1000 , oc-name=GIGECLIENTCTP.1-A-2-T9, oc-type=GIGECLIENTCTP.1-A-2-T9, odtn-connection-id=connection:5, odtn-port-type=client port=[GIGECLIENTCTP.1-A-2-T11](11), state=enabled, type=packet, speed=1000 , oc-name=GIGECLIENTCTP.1-A-2-T11, oc-type=GIGECLIENTCTP.1-A-2-T11, odtn-connection-id=connection:6, odtn-port-type=client port=[GIGECLIENTCTP.1-L1-1-1](101), state=enabled, type=och, speed=1000 , oc-name=GIGECLIENTCTP.1-L1-1-1, oc-type=GIGECLIENTCTP.1-L1-1-1, odtn-connection-id=connection:1, odtn-port-type=line port=[GIGECLIENTCTP.1-L2-1-1](102), state=enabled, type=och, speed=1000 , oc-name=GIGECLIENTCTP.1-L2-1-1, oc-type=GIGECLIENTCTP.1-L2-1-1, odtn-connection-id=connection:2, odtn-port-type=line port=[GIGECLIENTCTP.1-L3-1-1](103), state=enabled, type=och, speed=1000 , oc-name=GIGECLIENTCTP.1-L3-1-1, oc-type=GIGECLIENTCTP.1-L3-1-1, odtn-connection-id=connection:3, odtn-port-type=line port=[GIGECLIENTCTP.1-L4-1-1](104), state=enabled, type=och, speed=1000 , oc-name=GIGECLIENTCTP.1-L4-1-1, oc-type=GIGECLIENTCTP.1-L4-1-1, odtn-connection-id=connection:4, odtn-port-type=line port=[GIGECLIENTCTP.1-L5-1-1](105), state=enabled, type=och, speed=1000 , oc-name=GIGECLIENTCTP.1-L5-1-1, oc-type=GIGECLIENTCTP.1-L5-1-1, odtn-connection-id=connection:5, odtn-port-type=line port=[GIGECLIENTCTP.1-L6-1-1](106), state=enabled, type=och, speed=1000 , oc-name=GIGECLIENTCTP.1-L6-1-1, oc-type=GIGECLIENTCTP.1-L6-1-1, odtn-connection-id=connection:6, odtn-port-type=line id=netconf:10.1.8.124:11003, available=true, local-status=connected 12s ago, role=MASTER, type=TERMINAL_DEVICE, mfr=Infinera, hw=XT-3300, sw=unknown, serial=unknown, chassis=0, driver=infinera-xt3300, ipaddress=10.1.8.124, locType=none, name=netconf:10.1.8.124:11003, port=11003, protocol=NETCONF port=[GIGECLIENTCTP.1-A-2-T1](1), state=enabled, type=packet, speed=1000 , oc-name=GIGECLIENTCTP.1-A-2-T1, oc-type=GIGECLIENTCTP.1-A-2-T1, odtn-connection-id=connection:1, odtn-port-type=client port=[GIGECLIENTCTP.1-A-2-T3](3), state=enabled, type=packet, speed=1000 , oc-name=GIGECLIENTCTP.1-A-2-T3, oc-type=GIGECLIENTCTP.1-A-2-T3, odtn-connection-id=connection:2, odtn-port-type=client port=[GIGECLIENTCTP.1-A-2-T5](5), state=enabled, type=packet, speed=1000 , oc-name=GIGECLIENTCTP.1-A-2-T5, oc-type=GIGECLIENTCTP.1-A-2-T5, odtn-connection-id=connection:3, odtn-port-type=client port=[GIGECLIENTCTP.1-A-2-T7](7), state=enabled, type=packet, speed=1000 , oc-name=GIGECLIENTCTP.1-A-2-T7, oc-type=GIGECLIENTCTP.1-A-2-T7, odtn-connection-id=connection:4, odtn-port-type=client port=[GIGECLIENTCTP.1-A-2-T9](9), state=enabled, type=packet, speed=1000 , oc-name=GIGECLIENTCTP.1-A-2-T9, oc-type=GIGECLIENTCTP.1-A-2-T9, odtn-connection-id=connection:5, odtn-port-type=client port=[GIGECLIENTCTP.1-A-2-T11](11), state=enabled, type=packet, speed=1000 , oc-name=GIGECLIENTCTP.1-A-2-T11, oc-type=GIGECLIENTCTP.1-A-2-T11, odtn-connection-id=connection:6, odtn-port-type=client port=[GIGECLIENTCTP.1-L1-1-1](101), state=enabled, type=och, speed=1000 , oc-name=GIGECLIENTCTP.1-L1-1-1, oc-type=GIGECLIENTCTP.1-L1-1-1, odtn-connection-id=connection:1, odtn-port-type=line port=[GIGECLIENTCTP.1-L2-1-1](102), state=enabled, type=och, speed=1000 , oc-name=GIGECLIENTCTP.1-L2-1-1, oc-type=GIGECLIENTCTP.1-L2-1-1, odtn-connection-id=connection:2, odtn-port-type=line port=[GIGECLIENTCTP.1-L3-1-1](103), state=enabled, type=och, speed=1000 , oc-name=GIGECLIENTCTP.1-L3-1-1, oc-type=GIGECLIENTCTP.1-L3-1-1, odtn-connection-id=connection:3, odtn-port-type=line port=[GIGECLIENTCTP.1-L4-1-1](104), state=enabled, type=och, speed=1000 , oc-name=GIGECLIENTCTP.1-L4-1-1, oc-type=GIGECLIENTCTP.1-L4-1-1, odtn-connection-id=connection:4, odtn-port-type=line port=[GIGECLIENTCTP.1-L5-1-1](105), state=enabled, type=och, speed=1000 , oc-name=GIGECLIENTCTP.1-L5-1-1, oc-type=GIGECLIENTCTP.1-L5-1-1, odtn-connection-id=connection:5, odtn-port-type=line port=[GIGECLIENTCTP.1-L6-1-1](106), state=enabled, type=och, speed=1000 , oc-name=GIGECLIENTCTP.1-L6-1-1, oc-type=GIGECLIENTCTP.1-L6-1-1, odtn-connection-id=connection:6, odtn-port-type=line
At the same time, device event and port event kick the topology discovery process.
Topology discovery process requests NETCONF "get" and gets the device config and operational state, then it generates TAPI Node/NEP/SIP corresponding to devices and their ports.
After device registration and discovery, we can see the TAPI topology state updated.
onos> odtn-show-tapi-context XML: <context xmlns="urn:onf:otcc:yang:tapi-common"> <service-interface-point> <uuid>86d7bcb3-43c5-4dbd-800e-026731e8d585</uuid> <layer-protocol-name>DSR</layer-protocol-name> <name> <value-name>onos-cp</value-name> <value>netconf:10.1.8.124:11002/[GIGECLIENTCTP.1-A-2-T7](7)</value> </name> </service-interface-point> <service-interface-point> <uuid>c59b459d-34d3-4281-b02f-54339fe89cf8</uuid> <layer-protocol-name>DSR</layer-protocol-name> <name> <value-name>onos-cp</value-name> <value>netconf:10.1.8.124:11002/[GIGECLIENTCTP.1-A-2-T9](9)</value> </name> </service-interface-point> <service-interface-point> <uuid>b1272233-2682-4af3-954b-7c02ee085628</uuid> <layer-protocol-name>DSR</layer-protocol-name> <name> <value-name>onos-cp</value-name> <value>netconf:10.1.8.124:11002/[GIGECLIENTCTP.1-A-2-T5](5)</value> </name> </service-interface-point> <service-interface-point> <uuid>c47fe15e-a3ee-4ea2-87f9-f79b7e5b0c0b</uuid> <layer-protocol-name>PHOTONIC_MEDIA</layer-protocol-name> <name> <value-name>onos-cp</value-name> <value>netconf:10.1.8.124:11003/[GIGECLIENTCTP.1-L6-1-1](106)</value> </name> </service-interface-point> <topology-context xmlns="urn:onf:otcc:yang:tapi-topology"> <topology> <node> <owned-node-edge-point> <mapped-service-interface-point> <service-interface-point-uuid>395390ca-4bef-4de3-bc97-68227600c5b1</service-interface-point-uuid> </mapped-service-interface-point> <cep-list xmlns="urn:onf:otcc:yang:tapi-connectivity"> <connection-end-point> <parent-node-edge-point> <node-edge-point-uuid>745eb44d-6308-4dc9-aac9-6609fcc91741</node-edge-point-uuid> <topology-uuid>c4b7a7fb-32b9-4f11-a146-1b7df7f59839</topology-uuid> <node-uuid>21c8368a-6e5d-4ada-82b7-d61c96375644</node-uuid> </parent-node-edge-point> <uuid>aeefa738-acf7-4e72-b55e-7b0987df7428</uuid> </connection-end-point> </cep-list> ... </node> </topology> </topology-context> <service-interface-point> <uuid>2bf713b6-d53b-4631-be34-4a93ac58b58a</uuid> <layer-protocol-name>PHOTONIC_MEDIA</layer-protocol-name> <name> <value-name>onos-cp</value-name> <value>netconf:10.1.8.124:11003/[GIGECLIENTCTP.1-L4-1-1](104)</value> </name> </service-interface-point> <service-interface-point> <uuid>00b3b767-bdb3-449c-8d18-c89e1d6e2cee</uuid> <layer-protocol-name>DSR</layer-protocol-name> <name> <value-name>onos-cp</value-name> <value>netconf:10.1.8.124:11003/[GIGECLIENTCTP.1-A-2-T3](3)</value> </name> </service-interface-point> ... <service-interface-point> <uuid>9eaffa1f-653b-4f05-b759-ff18c98f65c6</uuid> <layer-protocol-name>DSR</layer-protocol-name> <name> <value-name>onos-cp</value-name> <value>netconf:10.1.8.124:11002/[GIGECLIENTCTP.1-A-2-T3](3)</value> </name> </service-interface-point> </context>
Currently, we don't have any link discovery feature, so we also need to register links between devices.
Temporary, all optical channels are represented as different links, and all optical channel endpoints are dealt with as ConnectPoint in onos. It might not be ideal and we should re-consider how to map TAPI topology models and onos models.
$ cat openconfig-device-link.json { "links": { "netconf:172.24.3.5:11001/41-netconf:172.24.3.5:11011/41": { "basic": { "type": "DIRECT" } }, "netconf:172.24.3.5:11002/101-netconf:172.24.3.5:11003/101": { "basic": { "type": "DIRECT" } }, "netconf:172.24.3.5:11002/102-netconf:172.24.3.5:11003/102": { "basic": { "type": "DIRECT" } }, "netconf:172.24.3.5:11002/103-netconf:172.24.3.5:11003/103": { "basic": { "type": "DIRECT" } }, "netconf:172.24.3.5:11002/104-netconf:172.24.3.5:11003/104": { "basic": { "type": "DIRECT" } }, "netconf:172.24.3.5:11002/105-netconf:172.24.3.5:11003/105": { "basic": { "type": "DIRECT" } }, "netconf:172.24.3.5:11002/106-netconf:172.24.3.5:11003/106": { "basic": { "type": "DIRECT" } } } } $ onos-netcfg localhost openconfig-device-link.json
After that, we can find that links are registered and TAPI link are also set in DCS.
onos> links src=netconf:172.24.3.5:11001/41, dst=netconf:172.24.3.5:11011/41, type=DIRECT, state=ACTIVE, expected=false src=netconf:172.24.3.5:11002/101, dst=netconf:172.24.3.5:11003/101, type=DIRECT, state=ACTIVE, expected=false src=netconf:172.24.3.5:11002/102, dst=netconf:172.24.3.5:11003/102, type=DIRECT, state=ACTIVE, expected=false src=netconf:172.24.3.5:11002/103, dst=netconf:172.24.3.5:11003/103, type=DIRECT, state=ACTIVE, expected=false src=netconf:172.24.3.5:11002/104, dst=netconf:172.24.3.5:11003/104, type=DIRECT, state=ACTIVE, expected=false src=netconf:172.24.3.5:11002/105, dst=netconf:172.24.3.5:11003/105, type=DIRECT, state=ACTIVE, expected=false src=netconf:172.24.3.5:11002/106, dst=netconf:172.24.3.5:11003/106, type=DIRECT, state=ACTIVE, expected=false src=netconf:172.24.3.5:11003/101, dst=netconf:172.24.3.5:11002/101, type=DIRECT, state=ACTIVE, expected=false src=netconf:172.24.3.5:11003/102, dst=netconf:172.24.3.5:11002/102, type=DIRECT, state=ACTIVE, expected=false src=netconf:172.24.3.5:11003/103, dst=netconf:172.24.3.5:11002/103, type=DIRECT, state=ACTIVE, expected=false src=netconf:172.24.3.5:11003/104, dst=netconf:172.24.3.5:11002/104, type=DIRECT, state=ACTIVE, expected=false src=netconf:172.24.3.5:11003/105, dst=netconf:172.24.3.5:11002/105, type=DIRECT, state=ACTIVE, expected=false src=netconf:172.24.3.5:11003/106, dst=netconf:172.24.3.5:11002/106, type=DIRECT, state=ACTIVE, expected=false src=netconf:172.24.3.5:11011/41, dst=netconf:172.24.3.5:11001/41, type=DIRECT, state=ACTIVE, expected=false onos> odtn-show-tapi-context <context xmlns="urn:onf:otcc:yang:tapi-common"> <topology xmlns="urn:onf:otcc:yang:tapi-topology"> <uuid>ab09b19e-c09a-4f0c-8f72-af072b3a8071</uuid> ... <link> <uuid>e8a61532-a9f4-4570-a09c-696b278dbdd6</uuid> <node-edge-point> <owned-node-edge-point-id>41bdf1bb-301f-423e-8d06-2bfac62afa99</owned-node-edge-point-id> <node-id>4b84de46-abd5-4f72-80e5-a4ffdb6253ea</node-id> <topology-id>ab09b19e-c09a-4f0c-8f72-af072b3a8071</topology-id> </node-edge-point> <node-edge-point> <owned-node-edge-point-id>2a97e1d8-76b7-404c-9c61-ef24124a1e4f</owned-node-edge-point-id> <node-id>65e78268-f183-4223-818d-a975303b6302</node-id> <topology-id>ab09b19e-c09a-4f0c-8f72-af072b3a8071</topology-id> </node-edge-point> </link> ... </topology> ... </context>
All devices and links which needs for this demonstration are already registered, now we have following TAPI topology in DCS and we can use this stored topology and TAPI connectivity-service NBI
to request end-to-end path request.
We can also get the TAPI ServiceInterfacePoint via RESTCONF NBI. (There is an limitation, please check Available TAPI NBI endpoints)
$ curl -X POST -H Content-Type:application/json -T empty-body.json http://localhost:8181/onos/restconf/operations/tapi-common:get-service-interface-point-list | jq { "tapi-common:output": { "sip": [ { "uuid": "78650c37-2a9b-4512-8619-a372b73bfe37" } ] } } # by using jq filter, we can get SIP uuid directly $ curl -X POST -H Content-Type:application/json -T empty-body.json http://localhost:8181/onos/restconf/operations/tapi-common:get-service-interface-point-list | jq '.[].sip[][]' "78650c37-2a9b-4512-8619-a372b73bfe37"
Since devices/links registration and TAPI topology creation are done, we are ready to request path creation to ONOS/ODTN.
Create TAPI Connectivity Service
Send create-connectivity-service request to onos via RESTCONF NBI.
$ cat create-connectivity-service.json { "tapi-connectivity:input": { "end-point" : [ { "local-id": "foo", "service-interface-point": { "service-interface-point-id" : "7b4385cf-8f4a-4161-bf90-d084acb1015f" } } , { "local-id": "bar", "service-interface-point": { "service-interface-point-id" : "fcc00b2d-ae2c-4add-94c6-5109bf62c9ce" } } ] } } $ curl -X POST -H Content-Type:application/json -T create-connectivity-service.json http://localhost:8181/onos/restconf/operations/tapi-connectivity:create-connectivity-service | jq { "tapi-connectivity:output": { "service": { "uuid": "20b8de56-f2c3-46dc-a605-4c36e4482987", "end-point": [ { "local-id": "234184e5-b5af-45dd-a27e-6818e96aad87", "service-interface-point": { "service-interface-point-id": "7b4385cf-8f4a-4161-bf90-d084acb1015f" } }, { "local-id": "343b8d8a-384f-4af8-9672-fa2eac4d2f7f", "service-interface-point": { "service-interface-point-id": "fcc00b2d-ae2c-4add-94c6-5109bf62c9ce" } } ], "connection": [ { "connection-id": "31733d3a-2527-4473-93df-ae654c93b687" } ] } } }
Checking the TAPI context, you can see following objects are created:
- New connectivity service you request
- Top level connection of the connectivity service and its endpoints(CEPs)
- Lower connections which are needed in order to build top level connection, and their endpoints(CEPs)
onos> odtn-show-tapi-context XML: <context xmlns="urn:onf:otcc:yang:tapi-common"> ... <connection xmlns="urn:onf:otcc:yang:tapi-connectivity"> <uuid>31733d3a-2527-4473-93df-ae654c93b687</uuid> <connection-end-point> <connection-end-point-id>f233e5e1-78a4-452c-a087-0a4a057d8281</connection-end-point-id> <owned-node-edge-point-id>fe4e2f4e-6f93-4c29-8547-9695ac8364ff</owned-node-edge-point-id> <node-id>c85b5b10-49aa-4c57-a318-aa6ba50dab71</node-id> <topology-id>ab09b19e-c09a-4f0c-8f72-af072b3a8071</topology-id> </connection-end-point> <connection-end-point> <connection-end-point-id>0b845841-3cb5-4116-a802-98e69d8dfda5</connection-end-point-id> <owned-node-edge-point-id>5711ea26-da27-4412-bdde-203416027f6e</owned-node-edge-point-id> <node-id>70fbc84d-ed4f-4bb3-9e09-d9dcaab9b4ff</node-id> <topology-id>ab09b19e-c09a-4f0c-8f72-af072b3a8071</topology-id> </connection-end-point> <lower-connection> <connection-id>0e3d1732-d736-415a-a3bc-e2de60ba89b2</connection-id> </lower-connection> <lower-connection> <connection-id>27f5b9ba-feaa-43e4-a501-0e64924706b8</connection-id> </lower-connection> <route> <local-id>36711d93-c181-4d78-8405-fa39c5d4d189</local-id> <connection-end-point> <connection-end-point-id>f233e5e1-78a4-452c-a087-0a4a057d8281</connection-end-point-id> <owned-node-edge-point-id>fe4e2f4e-6f93-4c29-8547-9695ac8364ff</owned-node-edge-point-id> <node-id>c85b5b10-49aa-4c57-a318-aa6ba50dab71</node-id> <topology-id>ab09b19e-c09a-4f0c-8f72-af072b3a8071</topology-id> </connection-end-point> <connection-end-point> <connection-end-point-id>436d8a4b-5536-47b0-8b2b-c68f1d7be898</connection-end-point-id> <owned-node-edge-point-id>966ece6b-2627-4b81-bc10-873bae079852</owned-node-edge-point-id> <node-id>c85b5b10-49aa-4c57-a318-aa6ba50dab71</node-id> <topology-id>ab09b19e-c09a-4f0c-8f72-af072b3a8071</topology-id> </connection-end-point> <connection-end-point> <connection-end-point-id>0b845841-3cb5-4116-a802-98e69d8dfda5</connection-end-point-id> <owned-node-edge-point-id>5711ea26-da27-4412-bdde-203416027f6e</owned-node-edge-point-id> <node-id>70fbc84d-ed4f-4bb3-9e09-d9dcaab9b4ff</node-id> <topology-id>ab09b19e-c09a-4f0c-8f72-af072b3a8071</topology-id> </connection-end-point> <connection-end-point> <connection-end-point-id>274a2aca-359e-4592-ba26-dad2b6db1f3c</connection-end-point-id> <owned-node-edge-point-id>bf886c96-d911-4fa9-aac8-827d18cb0b87</owned-node-edge-point-id> <node-id>70fbc84d-ed4f-4bb3-9e09-d9dcaab9b4ff</node-id> <topology-id>ab09b19e-c09a-4f0c-8f72-af072b3a8071</topology-id> </connection-end-point> </route> </connection> <connectivity-service xmlns="urn:onf:otcc:yang:tapi-connectivity"> <uuid>20b8de56-f2c3-46dc-a605-4c36e4482987</uuid> <end-point> <local-id>234184e5-b5af-45dd-a27e-6818e96aad87</local-id> <service-interface-point> <service-interface-point-id>7b4385cf-8f4a-4161-bf90-d084acb1015f</service-interface-point-id> </service-interface-point> </end-point> <end-point> <local-id>343b8d8a-384f-4af8-9672-fa2eac4d2f7f</local-id> <service-interface-point> <service-interface-point-id>fcc00b2d-ae2c-4add-94c6-5109bf62c9ce</service-interface-point-id> </service-interface-point> </end-point> <connection> <connection-id>31733d3a-2527-4473-93df-ae654c93b687</connection-id> </connection> </connectivity-service> </context>
If you check the remote device/emulator's NETCONF log, you can see that the remote device received following edit-config request and updated its running config.
log ----- <rpc message-id="4" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <edit-config> <target> <running/> </target> <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> <terminal-device xc:operation="merge" xmlns="http://openconfig.net/yang/terminal-device"> <logical-channels> <channel xmlns="http://openconfig.net/yang/terminal-device" xc:operation="merge"> <index>GIGECLIENTCTP.1-A-2-T1</index> <config> <index>GIGECLIENTCTP.1-A-2-T1</index> </config> <logical-channel-assignments> <assignment> <index>GIGECLIENTCTP.1-A-2-T1</index> <config> <assignment-type>LOGICAL_CHANNEL</assignment-type> <logical-channel>GIGECLIENTCTP.1-L1-1-1</logical-channel> <allocation>100</allocation> </config> </assignment> </logical-channel-assignments> </channel> </logical-channels> </terminal-device> </config> </edit-config> </rpc> 23-Jul-2018::16:44:26.872 **< sess:53 write: <rpc-reply message-id="4" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <ok/> </rpc-reply> diff of running-config ------------------------ devices { device xt3300_1 { config { oc-opt-term:terminal-device { logical-channels { + channel GIGECLIENTCTP.1-A-2-T1 { + config { + index GIGECLIENTCTP.1-A-2-T1; + } + logical-channel-assignments { + assignment GIGECLIENTCTP.1-A-2-T1 { + config { + assignment-type LOGICAL_CHANNEL; + logical-channel GIGECLIENTCTP.1-L1-1-1; + allocation 100.0; + } + } + } + } } } } } }
You can get the created connectivity service from RESTCONF NBI (There is an limitation, please check Available TAPI NBI endpoints).
$ curl -X POST -H Content-Type:application/json -T empty-body.json http://localhost:8181/onos/restconf/operations/tapi-connectivity:get-connectivity-service-list | jq { "tapi-connectivity:output": { "service": [ { "uuid": "20b8de56-f2c3-46dc-a605-4c36e4482987", "end-point": [ { "local-id": "234184e5-b5af-45dd-a27e-6818e96aad87", "service-interface-point": { "service-interface-point-id": "7b4385cf-8f4a-4161-bf90-d084acb1015f" } }, { "local-id": "343b8d8a-384f-4af8-9672-fa2eac4d2f7f", "service-interface-point": { "service-interface-point-id": "fcc00b2d-ae2c-4add-94c6-5109bf62c9ce" } } ], "connection": [ { "connection-id": "31733d3a-2527-4473-93df-ae654c93b687" } ] } ] } }
Delete TAPI Connectivity Service
Get the connectivity-service uuid you want to delete from RESTCONF NBI, and send delete-connectivity-service request.
$ curl -X POST -H Content-Type:application/json -T empty-body.json http://localhost:8181/onos/restconf/operations/tapi-connectivity:get-connectivity-service-list | jq '.[][][].uuid' "20b8de56-f2c3-46dc-a605-4c36e4482987" $ cat delete-connectivity-service.json { "tapi-connectivity:input": { "service-id-or-name" : "20b8de56-f2c3-46dc-a605-4c36e4482987" } } $ curl -X POST -H Content-Type:application/json -T delete-connectivity-service.json http://localhost:8181/onos/restconf/operations/tapi-connectivity:delete-connectivity-service | jq { "tapi-connectivity:output": { "service": { "uuid": "20b8de56-f2c3-46dc-a605-4c36e4482987" } } }
If you run "odtn-show-tapi-context" from ONOS CLI, you can find that all TAPI objects related to the deleted connectivity-service are removed.
Also you can see that the remote device received following edit-config request and updated its running config. The config which has created at the create-connectivity-service request are deleted.
log ----- <rpc message-id="5" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <edit-config> <target> <running/> </target> <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> <terminal-device xc:operation="merge" xmlns="http://openconfig.net/yang/terminal-device"> <logical-channels> <channel xmlns="http://openconfig.net/yang/terminal-device" xc:operation="delete"> <index>GIGECLIENTCTP.1-A-2-T1</index> <config> <index>GIGECLIENTCTP.1-A-2-T1</index> </config> <logical-channel-assignments> <assignment> <index>GIGECLIENTCTP.1-A-2-T1</index> <config> <assignment-type>LOGICAL_CHANNEL</assignment-type> <logical-channel>GIGECLIENTCTP.1-L1-1-1</logical-channel> <allocation>100</allocation> </config> </assignment> </logical-channel-assignments> </channel> </logical-channels> </terminal-device> </config> </edit-config> </rpc> 23-Jul-2018::16:46:59.870 **< sess:53 write: <rpc-reply message-id="5" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <ok/> </rpc-reply> diff ----- devices { device xt3300_1 { config { oc-opt-term:terminal-device { logical-channels { - channel GIGECLIENTCTP.1-A-2-T1 { - config { - index GIGECLIENTCTP.1-A-2-T1; - } - logical-channel-assignments { - assignment GIGECLIENTCTP.1-A-2-T1 { - config { - assignment-type LOGICAL_CHANNEL; - logical-channel GIGECLIENTCTP.1-L1-1-1; - allocation 100.0; - } - } - } - } } } } } }