How does configuration deployment work?
Creation of a configuration deployment
A configuration deployment is created when a template is deployed or associated to the network. The deployment object represents the application of a configuration template to a target in the network.
The deployment provides inputs to the template parameters as needed, and executes the configuration on a target in the network.
Some intent types can be deployed to multiple targets, or to a group. See the NSP System Administrator Guide for information about creating groups.
A template must be created before a deployment can be created.
The following table shows the Configuration Deployment parameters.
|
Parameter |
Predefined values |
Notes |
|
Deployment Status |
Not-Started |
The deployment is created in Device Configuration and is in a queue for deployment |
|
Saved |
The configuration has been created and is waiting for a user to deploy it to the network. |
|
Aligning |
An alignment operation is ongoing |
|
Auditing |
An audit operation is ongoing |
|
Migrating |
A migration operation is ongoing. |
|
Deployed Aligned |
The deployment is completed and the network configuration matches the defined configuration. |
|
Deployed Misaligned |
The deployment is completed and the network configuration does not match the defined configuration. |
|
Deployment Failed |
The deployment could not be completed.
Deployments may fail for several reasons:
-
Network Intents function is currently unavailable
-
the required intent type is not found
-
the Opensearch subsystem is down
-
A function downstream of Device Configuration is not responding |
|
Association Failed |
Associating a template to the network could not be completed. |
|
Configuration Status |
Modified |
The deployment includes user-configured parameters |
|
Default |
All parameters are set by the template |
|
NE Name |
— |
— |
|
NE ID |
— |
— |
|
Identifier |
— |
For a physical deployment, the identifier is the network object that is configured by the deployment, for example, a port number.
For a logical deployment, the identifier depends on the template, for example, LAG name and ID. The identifier is entered by the user at deployment creation. |
|
Template |
— |
The configuration template in use |
|
Role |
Physical |
The target is a physical object such as a port |
|
Logical |
The target is a configured object such as QoS |
|
Category |
— |
The type of physical or logical object being configured
The category is defined in the configuration intent type. |
|
Last Updated |
— |
The date and time of the most recent modification or operation performed. |