Deploying a workload intent

Deploying a workload intent creates a functioning instance of the workload intent as an overlay to your fabric.

The following circumstances can prevent you from deploying a workload intent:

  • If any of the fabric intents associated with this workload intent are in the process of being altered (implying a fabric intent alteration which began somewhere in the interval since you created the workload intent), you cannot deploy the workload intent. Any attempt to deploy the workload intent from the deployment pipeline fails, displaying an error message about the fabric underlays having been altered.

    In such a case, the system requires you to delete the current candidate version of the fabric intents, thereby reverting to the previous version. You can then proceed with the deployment of your workload intent.

    Note: You can still deploy the workload intent if the fabric intent alteration is under another workload intent, but uses different nodes.
  • If any of the fabric intents associated with this workload intent has undergone a deployed topology change, you cannot deploy the workload intent. Any attempt to deploy the workload intent from the deployment pipeline fails, displaying an error message about the fabric underlays having been altered.

    In such a case, the system requires you to discard or delete the workload.

  • If any of the nodes within the associated fabric intent are unavailable (that is, not in a Ready state), you cannot deploy the workload intent.

    In such a case, you must correct the node state. When all nodes are back in a Ready state, you can proceed with the deployment of your workload intent.

  • If any of the nodes that belong to a workload intent are already under deployment by another workload intent, you must wait until the deployment of the previous workload intent has completed.

Before you can deploy your workload intent you must have saved the workload intent and generated its configuration.

Deploying the workload intent involves two procedures:

  1. From the workload intent list or the Design view for an individual workload intent, add the workload intent to the region's deployment pipeline.
  2. From the deployment pipeline, select the workload intent and select Deploy from the actions menu.

Adding a workload intent to the deployment pipeline

To add the workload intent to the region's deployment pipeline, do the following:
  1. Open the list of workload intents as described in Viewing a workload intent.
  2. Select the workload intent you want to deploy from the displayed list.
  3. Click the More actions icon ( ) at the right edge of the workload intent's row, and select Open from the drop-down menu.
  4. Click the Deploy icon ( ).
  5. Click the ADD TO PIPELINE button.
    The system adds the workload intent to the deployment queue for the region, and updates the workload intent's Status to "Queued for Deployment."

Deploying a workload intent from the deployment pipeline

After you add a workload intent to the deployment pipeline, it remains there until you tell the system to proceed with the deployment.

When you are ready to proceed with deployment, do the following:

  1. Click the menu.
  2. Select Workload VPN Intents.
    The Workload Intents page displays, showing a list of workload intents already created. You can sort and filter the list of fabric intents as described in Lists.
  3. Select the row corresponding to the workload intent you want to deploy.
  4. Click the icon at the far-right edge of the row and select Deployment Pipeline... from the actions list.
  5. Find your workload intent in the deployment pipeline list.
  6. At the right edge of the row, click the More actions icon ( ).
  7. From the resulting actions list, select Deploy.

    If deployment fails, the failure is reported as follows:

    • Queue status: reports Error with detailed status reason

    • Fabric intent: reports Deployed and shows a new entry in the Event log showing that the Workload deployment failed

    • Workload intent: reports Failed

      In the workload intent Design view, the system also highlights them as deployment issues in the status bar by adding a red circle to the fabrics affected by the deployment error, and with entries in the Events log.