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.

A template must be created before a deployment can be created.

The deployment provides inputs to the template parameters as needed, and executes the configuration on a target in the network.

Depending on the intent type, some templates can be deployed to multiple targets, or to a group. See the NSP System Administrator Guide for information about creating groups.

Note: Deploying a template to a group requires the SystemAdmin role.

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	NSP is checking the deployment status.
	Migrating	A migration operation is ongoing.
	Deployed Aligned	The deployment is completed and the network configuration matches the configuration that was defined at the time of deployment creation.
	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: A configuration deployed from the API is not valid for the intent type the template is based on For example, if the intent type requires one value for an attribute but two values have been pushed by the API, the deployment fails. 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.
Blueprint distribution status	Local definition	The network configuration does not match the current configuration in the blueprint template.
	Global definition	The network configuration matches the current configuration in the blueprint template.
	Verifying	NSP is checking the blueprint alignment status.
	Globalizing	NSP is aligning the network configuration to the blueprint.
	—	Not applicable: the template deployed is not a blueprint.
Configuration Status	Modified	The deployment includes user-configured parameters.
Configuration Status	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. For a fixed or flexible template, the identifier is entered by the user at deployment creation. Therefore, each deployment of the template can have a different identifier if needed. For a blueprint template, the target identifier is entered at blueprint creation. All deployments of the blueprint have the same identifier.
Template Type	Flexible	The template includes parameters that can be changed by the operator at deployment time.
	Fixed	The template has preset or default values for all parameters.
	Blueprint	The template can be used to apply changes to all its deployments at once.
Template	—	The configuration template in use
Role	Physical	The target is a physical object such as a port
Role	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.