+OC service creation
+^^^^^^^^^^^^^^^^^^^
+
+Use the following REST RPC to invoke *service handler* module in order to create a bidirectional
+end-to end Optical Channel (OC) connectivity service between two add/drop ports (PP port of SRG
+node) over an optical network only composed of rdm nodes.
+
+**REST API** : *POST /restconf/operations/org-openroadm-service:service-create*
+
+**Sample JSON Data**
+
+.. code:: json
+
+ {
+ "input": {
+ "sdnc-request-header": {
+ "request-id": "request-1",
+ "rpc-action": "service-create",
+ "request-system-id": "appname"
+ },
+ "service-name": "something",
+ "common-id": "commonId",
+ "connection-type": "roadm-line",
+ "service-a-end": {
+ "service-rate": "100",
+ "node-id": "<xpdr-node-id>",
+ "service-format": "OC",
+ "clli": "<ccli-name>",
+ "tx-direction": {
+ "port": {
+ "port-device-name": "<xpdr-client-port>",
+ "port-type": "fixed",
+ "port-name": "<xpdr-client-port-number>",
+ "port-rack": "000000.00",
+ "port-shelf": "Chassis#1"
+ },
+ "lgx": {
+ "lgx-device-name": "Some lgx-device-name",
+ "lgx-port-name": "Some lgx-port-name",
+ "lgx-port-rack": "000000.00",
+ "lgx-port-shelf": "00"
+ }
+ },
+ "rx-direction": {
+ "port": {
+ "port-device-name": "<xpdr-client-port>",
+ "port-type": "fixed",
+ "port-name": "<xpdr-client-port-number>",
+ "port-rack": "000000.00",
+ "port-shelf": "Chassis#1"
+ },
+ "lgx": {
+ "lgx-device-name": "Some lgx-device-name",
+ "lgx-port-name": "Some lgx-port-name",
+ "lgx-port-rack": "000000.00",
+ "lgx-port-shelf": "00"
+ }
+ },
+ "optic-type": "gray"
+ },
+ "service-z-end": {
+ "service-rate": "100",
+ "node-id": "<xpdr-node-id>",
+ "service-format": "OC",
+ "clli": "<ccli-name>",
+ "tx-direction": {
+ "port": {
+ "port-device-name": "<xpdr-client-port>",
+ "port-type": "fixed",
+ "port-name": "<xpdr-client-port-number>",
+ "port-rack": "000000.00",
+ "port-shelf": "Chassis#1"
+ },
+ "lgx": {
+ "lgx-device-name": "Some lgx-device-name",
+ "lgx-port-name": "Some lgx-port-name",
+ "lgx-port-rack": "000000.00",
+ "lgx-port-shelf": "00"
+ }
+ },
+ "rx-direction": {
+ "port": {
+ "port-device-name": "<xpdr-client-port>",
+ "port-type": "fixed",
+ "port-name": "<xpdr-client-port-number>",
+ "port-rack": "000000.00",
+ "port-shelf": "Chassis#1"
+ },
+ "lgx": {
+ "lgx-device-name": "Some lgx-device-name",
+ "lgx-port-name": "Some lgx-port-name",
+ "lgx-port-rack": "000000.00",
+ "lgx-port-shelf": "00"
+ }
+ },
+ "optic-type": "gray"
+ },
+ "due-date": "yyyy-mm-ddT00:00:01Z",
+ "operator-contact": "some-contact-info"
+ }
+ }
+
+As for the previous RPC, this RPC invokes the *PCE* module to compute a path over the
+*openroadm-topology* and then invokes *renderer* and *OLM* to implement the end-to-end path into
+the devices.
+
+OTN OCH, OTU4 and ODU4 service creation
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Use the following REST RPC to invoke *renderer* module in order to create adequate interfaces on
+otn device in order to support a bidirectional end-to-end Low-Order OTN connectivity service on
+network port of a MUXPDR or SWITCH xpdr node.
+
+**REST API** : *POST /restconf/operations/transportpce-device-renderer:service-path*
+
+**Sample JSON Data**
+
+.. code:: json
+
+ {
+ "input": {
+ "nodes": [
+ {
+ "node-id": "<otn-node-id>",
+ "dest-tp": "<otn-network-port-logical-connection-point>"
+ }
+ ],
+ "modulation-format": "qpsk",
+ "operation": "create",
+ "service-name": "<service-name>",
+ "wave-number": "<wavenumber-returned-by-PCE>"
+ }
+ }
+
+1GE/ODU0 and 10GE/ODU2e service creation
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Use the following REST RPC to invoke *renderer* module and create adequate interfaces on otn xpdr
+device (MUXPDR or SWITCH) in order to support a low-order otn service on its client port.
+
+- 1GE and ODU0 interfaces for 1GE services
+- 10GE and ODU2e interfaces for 10GE services
+
+The following example corresponds to the creation of a 10GE service
+
+*REST API** : *POST /restconf/operations/transportpce-device-renderer:otn-service-path*
+
+**Sample JSON Data**
+
+.. code:: json
+
+ {
+ "input": {
+ "service-rate": "10G",
+ "service-type": "Ethernet",
+ "ethernet-encoding": "something",
+ "trib-slot": "<trib-slot-number-inside-supported-ODU4>",
+ "trib-port-number": "<trib-port-number-inside-supported-ODU4>",
+ "operation": "create",
+ "service-name": "something",
+ "nodes": [
+ {
+ "node-id": "<otn-node-id>",
+ "client-tp": "<client-port-logical-connection-point>",
+ "network-tp": "<network-port-logical-connection-point>"
+ }
+ ]
+ }
+ }
+
+.. note::
+ OTN links are not automatically populated in the topology after the ODU2e interfaces have
+ been created on the two client ports of the xpdr. The otn link can be posted manually through
+ the REST API (APIDoc).
+
+.. note::
+ With Magnesium SR0, the service-list corresponding to 1GE/10GE and OTU4/ODU4 services is not
+ updated in the datastore after the interfaces have been created in the device.
+
+.. note::
+ trib-slot is used when the equipment supports contiguous trib-slot allocation (supported in
+ Magnesium SR0). The trib-slot provided corresponds to the first of the used trib-slots.
+ complex-trib-slots will be used when the equipment does not support contiguous trib-slot
+ allocation. In this case a list of the different trib-slots to be used shall be provided.
+ The support for non contiguous trib-slot allocation is planned for later Magnesium release.
+