What is a blueprint?

Blueprints

A blueprint is a type of template that can be used to apply changes to all its deployments at once, similar to a global policy in NFM-P. A blueprint template must have a logical role.

The target identifier is configured as part of creation of the blueprint and can only be edited if the blueprint is in draft status and has no deployments associated with it. Therefore, once the template is released and deployed, all deployments of the blueprint have the same target identifier.

In a blueprint template, the configuration form can be edited from the Configuration Templates view. When the blueprint is updated the updated values are distributed to deployments of the blueprint. Distribution requires a blueprint distribution status of global definition, that is, the deployment parameters match the blueprint.

Example 1:

  1. A blueprint template called Gold QoS is created with two queues:

    1 CIR 100 PIR 200

    2 CIR 100 PIR 200

  2. The blueprint template is deployed to NE 1 and NE 2, creating queues on both NEs with the configured CIR and PIR values.

    The deployments are not edited after they are created, therefore their Blueprint Distribution Status is Global Definition.

  3. The blueprint template is edited to change the CIR and PIR values on queue 2 to 200.

  4. After the blueprint template is edited, the new values are pushed to the eligible deployments. The CIR and PIR values on queue 2 are updated on both NEs.

Example 2:

  1. A blueprint template called Gold QoS is created with two queues:

    1 CIR 100 PIR 200

    2 CIR 100 PIR 200

  2. The blueprint template is deployed to NE 1 and NE 2, creating queues on both NEs with the configured CIR and PIR values.

  3. The configuration deployment on NE 2 is edited to change the PIR value on queue 2 to 300.

  4. The Blueprint Distribution Status on the deployment on NE 2 is updated to Local Definition.

  5. The blueprint template is edited to change the CIR and PIR values on queue 2 to 200.

  6. After the blueprint template is edited, the new values are pushed to the deployments with global status, that is, the deployment on NE 1. NE 2 is not updated by this action.