Provisions¶

Here, you can access various provisioning actions to efficiently manage your network resources. From configuring DSR to multi-domain provisioning, our tools enable agile and precise implementation of changes. Select an action from the provided list to start optimizing and managing your network with ease and efficiency.

Interactions¶

Debug Provisioning form¶

This option permits to debug a provision with form as output

Click to see more details

Form to complete:

Debug Provisioning form: This option permits to debug a provision with form as output.
Info: Informative info to the user.
Progress: Progress of the operation.
Timeout: Timeout in seconds.
Success: True if the operation was successful, false otherwise.
Informative message to the user.

Form response:

Successfull provisioning: True if the provisioning operation was successful, false otherwise.
Error message: Informative message in the case of not successful provision.

De-commission an existing TAPI Connectivity Service¶

This option permits to de-commission an existing TAPI Connectivity Service (CS) in the network. The CS is identified by its ID, and the operation is executed by a selected Network Discovery Controller Node.

Click to see more details

Form to complete:

De-commission an existing TAPI Connectivity Service: This option permits to de-commission an existing TAPI Connectivity Service (CS) in the network. The CS is identified by its ID, and the operation is executed by a selected Network Discovery Controller Node..
Network controller: The network controller in order to execute the provisioning..
Connectivity Service: The connectivity service selected for delete.
Execute Network Discovery: If checked, the network discovery routine will be executed after the operation..

Form response:

Successfully provisioning: True if the provisioning operation was successful, false otherwise.
Error message: Informative message in the case of not successful provision.

Provision a new TAPI DSR connection¶

This option permits to provision a new TAPI DSR connection between two transceivers in the network. The connection is identified by its Service Interface Point IDs (SIPAs and SIPBs), and the operation is executed by a selected Network Discovery Controller Node.

Click to see more details

Form to complete:

Provision a new TAPI DSR connection: This option permits to provision a new TAPI DSR connection between two transceivers in the network. The connection is identified by its Service Interface Point IDs (SIPAs and SIPBs), and the operation is executed by a selected Network Discovery Controller Node..
Network controller: The network controller in order to execute the provisioning..
Origin node: The origin node of this element.
Origin Service Interface Point ID: The SIP associated with the origin node..
Destination node: The destination node of this element.
Destination Service Interface Point ID: The SIP associated with the origin node..
Connectivity direction: The desired direction for the connection to provision. Options:
- BIDIRECTIONAL: The Fowarding entity supports both BIDIRECTIONAL flows at all Ports (i.e. all Ports have both an INPUT flow and an OUTPUT flow defined).
- UNIDIRECTIONAL: The Forwarding entity has Ports that are either INPUT or OUTPUT. It has no BIDIRECTIONAL Ports..
- UNDEFINED_OR_UNKNOWN: Not a normal state. The system is unable to determine the correct value..
Route objective function: The desired objective function to be used for route calculation for this connection. Options:
- MIN_WORK_ROUTE_HOP: none.
- MIN_WORK_ROUTE_COST: none.
- MIN_WORK_ROUTE_LATENCY: none.
- MIN_SUM_OF_WORK_AND_PROTECTION_ROUTE_HOP: none.
- MIN_SUM_OF_WORK_AND_PROTECTION_ROUTE_COST: none.
- MIN_SUM_OF_WORK_AND_PROTECTION_ROUTE_LATENCY: none.
- LOAD_BALANCE_MAX_UNUSED_CAPACITY: none.
Requested capacity (Gbps): The requested circuit capacity measured in Gbps.

Form response:

Successfull provisioning: True if the provisioning operation was successful, false otherwise.
Error message: Informative message in the case of not successful provision.

Provision a new TAPI OLS Media Channel¶

This option permits to provision a new TAPI OLS Media Channel between two transceivers in the network. The connection is identified by its Service Interface Point IDs (SIPAs and SIPBs), and the operation is executed by a selected Network Discovery Controller Node.

Click to see more details

Form to complete:

Provision a new TAPI OLS Media Channel: This option permits to provision a new TAPI OLS Media Channel between two transceivers in the network. The connection is identified by its Service Interface Point IDs (SIPAs and SIPBs), and the operation is executed by a selected Network Discovery Controller Node..
Network controller: The network controller in order to execute the provisioning..
Origin node: The origin node of this element.
Origin Service Interface Point ID: The SIP associated with the origin node..
Destination node: The destination node of this element.
Destination Service Interface Point ID: The SIP associated with the origin node..
Requested capacity in GHz: The requested capacity for the OLS Media Channel in GHz..
Connectivity direction: The desired direction for the connection to provision. Options:
- BIDIRECTIONAL: The Fowarding entity supports both BIDIRECTIONAL flows at all Ports (i.e. all Ports have both an INPUT flow and an OUTPUT flow defined).
- UNIDIRECTIONAL: The Forwarding entity has Ports that are either INPUT or OUTPUT. It has no BIDIRECTIONAL Ports..
- UNDEFINED_OR_UNKNOWN: Not a normal state. The system is unable to determine the correct value..
Route objective function: The desired objective function to be used for route calculation for this connection. Options:
- MIN_WORK_ROUTE_HOP: none.
- MIN_WORK_ROUTE_COST: none.
- MIN_WORK_ROUTE_LATENCY: none.
- MIN_SUM_OF_WORK_AND_PROTECTION_ROUTE_HOP: none.
- MIN_SUM_OF_WORK_AND_PROTECTION_ROUTE_COST: none.
- MIN_SUM_OF_WORK_AND_PROTECTION_ROUTE_LATENCY: none.
- LOAD_BALANCE_MAX_UNUSED_CAPACITY: none.
Execute Network Discovery: If checked, the network discovery routine will be executed after the provision operation..

Form response:

Successfully provision: True if the provisioning operation was successful, false otherwise.
Error message: Informative message in the case of not successful provision.

Kubernetes - Apply manifest to cluster¶

This option allows you to apply a manifest to a selected Kubernetes cluster.

Click to see more details

Form to complete:

Kubernetes - Apply manifest to cluster: This option allows you to apply a manifest to a selected Kubernetes cluster..
Kubernetes controller: The kubernetes controller to apply the deployment.
Namespace: The namespace to apply the deployment.
Manifest YAML: The manifest file content to apply.
Perform network discovery: Indicates if the network discovery should be performed after the provision.