Service Orchestration: profile instances configuration

Configuring a default profile instance for a node

In the Services module, go to the definitions tab.
Select the service definition for which you want to configure a default profile instance.
In the diagram page, select the desired node.
In the parameters pane in the lower right corner, select the default profile instance in the Profile dropdown list.

Tip

Configuring the profile instance assignment mode for a node

When Service Orchestration is used, a profile instance can be assigned to a node and its associated interfaces in the following ways:

By value: Further updates of the profile instance will have no impact on bookings that have already been created.
By reference: Further updates of the profile instance will have an impact on future bookings that make use of it. New values will be considered when orchestrating, and updated capacities/capabilities will also be taken into account.

By default, each node in a service definition is set to By value. During booking creation, users can select the By reference checkbox to change the assignment mode.

You can also make sure By reference is selected by default instead:

In the Services module, go to the definitions tab.
Select the service definition and the node.
In the parameters pane in the lower right corner, select By reference.

Tip

Allowing profile instance configuration for disconnected interfaces

If an interface is not connected to other nodes in the service definition, by default the Booking Wizard will not prompt users for profile instances related to that interface. However, you can change this behavior for specific interfaces:

In the Services module, go to the definitions tab.
Select the service definition and the interface.
In the properties pane in the lower right corner, add the NoConnectivityCheck property and set its value to True.

Tip

Setting a profile instance as optional

In the context of Service Orchestration, you can mark a node or interface profile instance as optional:

In the Services module, go to the definitions tab.
Select the service definition and the node or interface.
In the properties pane in the lower right corner, add the IsProfileInstanceOptional property and set its value to True.

Tip

If you want to mark a resource as optional, use the Optional option on the service definition node instead.

Note

From SRM 1.2.20 onwards, it is not possible to create a booking if parameters still need to be configured for a node and there are no profile instances in the system for that node. If you do want it to be possible to create a booking in such a case, for example for a transport node, make sure you have set IsProfileInstanceOptional to True.

Filtering profile instances based on resource selection

In the context of Service Orchestration, you can configure resources so that when they are selected in the Booking Wizard, the list of profile instances is filtered to only show the profile instances matching the capabilities of the selected resources:

In the Resources module, select the pool and the resource.
Go to the properties tab for the resource, and click Add.
Fill in the name FilterProfileInstance and the value Yes, and click OK.

Tip

Configuring resource pool inheritance for a profile instance

When a booking starts and a profile instance gets selected, the values defined in the profile instance are used to apply a configuration on the resource. However, in specific situations, it might be required to not apply the exact same configuration on concurrent bookings to prevent them from interfering with each other. In such cases, resource pool inheritance can be used.

With resource pool inheritance, instead of using a fixed value defined in the selected profile instance for a specific parameter, you extend the service definition to refer to a custom resource pool. When the user selects the profile instance for the booking, they will see a list of discrete values based on the list of items in the resource pool that are available during the booking duration. When the booking is confirmed, the selected resource pool item is saved in the booking, so that it cannot be selected for overlapping bookings.

For example, when a list of multicast IPs need to be applied to encoding functions, but you need to avoid multiple encoders making use of the same multicast IP, you can use this feature to book the IP address as a resource.

To configure resource pool inheritance:

In the Services module, go to the definitions tab.
Select the service definition and the node.
In the parameters pane in the lower right corner, select the checkbox under Value for the relevant parameter, and add the following JSON code as the value
```
{
   "Link": "RESOURCEPOOL",
   "PoolName":"<pool name>", 
   "ShouldAutoSelectResource": <true or false>
}
```
- Replace <pool name> with the name of a resource pool.
- Set ShouldAutoSelectResource to true to enable automatic resource selection. This is supported both for node and interface profile instances.

You can also extend resource pool inheritance to further limit the list of pool items presented to the user based on a capability defined on the selected resource:

Add a capability parameter on the function resource and select which discrete values the resource can support. The discrete values must be part of the custom pool. See Setting up basic resource filtering.

In the Services module, modify the parameter with the resource inheritance configuration as follows:

{
   "Link": "RESOURCEPOOL",
   "PoolName":"<pool name>",
   "ResourceCapability":"<resource capability parameter name>"
}

For example, if the resource is configured with the capability Multicast IP, the parameter can be configured as follows:

{
   "Link": "RESOURCEPOOL",
   "PoolName": "SDMN.SAT.Multicast IP",
   "ResourceCapability": "Multicast IP"
}

In the resource configuration, the allowed parameter values should be specified for the corresponding capability. For example, if the Multicast IP capability is set to "244.0.0.2;244.0.0.3" in the resource configuration, for the parameter above only those two values will be selectable if the resource is selected. If no resource is selected, all options will be available. If a resource is selected that does not have the capability defined in the parameter, all options will also be available.

Table of Contents