Open Network Intents, Intent Types.

Click CREATE.

In the Create Intent Type form that opens, enter a name for the intent type.

Important! Intent Type names must meet the following requirements.

• The name must begin with a letter.

• The name of an intent type can only contain lowercase letters, dashes or underscores.

  If other characters are present, the intent type cannot be created.

Configure the parameters in the GENERAL pane as required:

• Click in the Mapping Engine field to choose the JavaScript engine.

• Click Composite to create a composite intent type.

• Click Live state retrieval to enable updating intent state attributes in the intent details on demand.

• Enter labels in the Labels field. The intent type must have at least one label.

Configure the parameters in the Policy pane.

If you are not creating a composite intent type, proceed to Step 7.

If applicable, configure the parameters in the Composite Intent Types pane:

1. Click ADD to add child intent types.

2. In the Name field, enter an alias for the child intent type, to be used by the mapping file.

3. In the Intent Type and Version fields, enter the name and version of the intent type you are adding.

4. The Requires Child Intent parameter creates a dependency between child intent types. If the intent type you are adding is dependent on another child intent, enter the name of the other intent and click .

5. Configure target component mapping for each target component in the child intent type:

   1. Click ADD

   2. Choose From Target Component or From Data Component.

   3. In the Name field, enter the To mapping, that is, the component in the child intent to configure.

   4. In the From Target Component or From Constant Value field, enter the From mapping, that is, the composite intent type component or data value to apply to the child intent.

      The following sample shows mapping of a component in the composite intent called Name to a child intent component called serviceName.

      

   5. Click ADD to finish adding the target component mapping.

      Repeat this step as needed to configure mapping for all target components in the child intent type.

6. Click ADD to finish adding the child intent type.

   Repeat this step as needed to add another child intent type.

In the TARGET tab, configure the identification information for intents created from the intent type.

Modify the default text, or enter, copy or paste as needed.

In the YANG tab, configure the form details for creation of an intent.

1. Choose the YANG module in the panel on the left.

2. Modify the default text, or enter, copy, or paste as needed.

Add additional YANG modules as required.

1. Click Yang .

2. In the Add Yang form that opens, enter the name of the module and click ADD.

3. Enter or paste the YANG text in the panel.

4. Repeat as needed to add more modules.

In the SCRIPT tab, configure the script for executing the intent.

Modify the default text, or enter, copy, or paste as needed.

In the RESOURCES tab, add or modify resources as required.

1. Click Resource .

2. In the Add Resource form that opens, enter the name of the resource and click ADD.

3. Enter or paste the resource file in the panel.

4. If the intent type has child intents, a generated mapping file called config-transformer is present. Verify the mapping information in the file and make changes if required.

Resource libraries can be configured using NSP Resource Management. To open Resource Management, click  More, Resource Management at the top of any Network Intents view.

Click CREATE.

End of steps