What is migration?
Applying schema form changes to an existing deployment
If you have updated an intent type schema form, you can apply the updated intent type values to an existing deployment.
To do this, migrate the deployments from a template created with the old schema form, the source template, to a template created with the new schema form, the target template.
Important! Migrating configuration deployments between templates is only available if the source and target templates meet the following criteria.
The following is an example scenario.
-
Template set_mtu was created with intent type port_config, using the viewConfig form gold_ports.viewConfig
-
Template set_mtu was deployed to the network, configuring ports on NE1 and NE2.
-
gold_ports.viewConfig was updated, automatically updating the schema form and causing the config form state of the set_mtu template to become outdated.
-
Template set_mtu was cloned to create set_mtu2.
To apply the updates in the new version of gold_ports.viewConfig to the ports on the NEs, migrate the deployments from template set_mtu to template set_mtu2.
After migration, NSP automatically aligns the deployments with the new template, pushing the new template configuration to the targets.
Note: Deployments with a Deployment Status of Not-started, Saved, Auditing, Aligning, or Association Failed cannot be migrated. These deployments will not appear in the Migrate Deployments form.
Modified attributes
When modifying the viewConfig file in Network Intents, you can make changes to some attributes. This includes adding and removing attributes, changing attribute values, and changing attributes from fixed to flexible or vice versa. Attributes can be modified if their values are entered into a field or selected from a dropdown. Table and list attributes cannot be modified during a migration. For example, in a QoS configuration template, the Default FC parameter can be changed, but a queue cannot be added.
Migration is not a service impacting operation. The migration operation deploys the new template to the existing configuration, merging the existing configuration and the new configuration. Note that values can be updated either due to changes in fixed values in the target template, or to changes made to flexible attributes when the migration is performed.
-
If the source and target templates have the same attributes and only attribute values have changed, the new deployment has the updated attribute values.
-
If the target template has added attributes, the new deployment has the target template values for all attributes, including the additional ones.
-
If the target template has deleted attributes that appeared in the source template, the new deployment keeps the existing configuration value for the deleted attribute and applies the target template values for the attributes in the target template.
The following table shows an example. In this example, one attribute is changed, one is added, and one is deleted.
|
Existing deployment values configured by source template |
Attribute values applied by migration |
New deployment values |
|---|---|---|