Upgrading DataEngine Runtime Version

In the event that you need to upgrade DataEngine runtime, follow this procedure:

1. Run the DataEngine CLI, and make sure it is updated to the latest builder image:

   1. Use vastde builders inspect to check current builder image URL:
      

      user@user-machine:~$ vastde builders inspect
      Current Builder Image Configuration
      
      Builder Image URL: https://github.com/vast-data/dataengine-cli/releases/tag/v5.4.1-dev.29d4871e
      
      To change the builder image, use: vastde builders set <image-url>
      To view tag details, use: vastde builders inspect <tag>

   2. Run vastde builders list to list available builder images.

   3. Run vastde builders set to update the CLI configuration with the latest builder image URL:
      

      user@user-machine:~$ vastde builders set v5.4.1-dev.c0b8b3d5
      Using default repository, full image: vastdataorg/vast-builder:v5.4.1-dev.c0b8b3d5
      Builder image URL updated successfully!
      
      Previous: https://github.com/vast-data/dataengine-cli/releases/tag/v5.4.1-dev.c0b8b3d5
      Current:  vastdataorg/vast-builder:v5.4.1-dev.29d4871e
      
      This builder image will be used for building DataEngine functions

2. Rebuild each function and push it to the container registry. You can do this with vastde functions build:

   user@user-machine:~$ vastde functions build my-function --target ./my-function-code --image-tag v2.0 --push

3. Update each function resource to point to its new image. You can do this from the DataEngine GUI:

   1. From the left navigation menu, select Manage Elements (  ) and then Functions.

   2. Right-click the function and select Edit.

      The revision number is incremented automatically from the previous revision.

   3. In the Image Tag field, enter the image tag attached to the new version of the container image.

   4. Modify other fields as needed:

      Revision Alias	An alias for the revision.
      Revision Description	A description specifically for the revision.
      Container Registry	The container registry where the image of the function is stored. If different from selected, select the correct container registry from the dropdown.
      Artifact Source	The path on the container registry where the image resides.
      Full image path	This is the full path to the image. It is formed automatically from the container registry, artifact source and image tag values that you supply.

   5. Click Update Function.

      A new revision is created and listed in the Functions page as a revision of the original function.

4. Redeploy each pipeline with new revisions of its functions:

   1. From the left navigation menu, select Manage Pipelines ( ) and then Pipelines.

   2. Right-click the pipeline and select Go to Builder.

   3. For each function:

      1. Select the function in the builder.

      2. Click Settings to show the function deployment configuration in the Settings pane on the right.

      3. From the Revision Number dropdown, select the new revision of the function.

   4. When you are done updating function revisions and making any other changes, click Deploy.

      The pipeline is redeployed.

5. Once all pipelines are redeployed with rebuilt function images, navigate to the dashboard (click ).

6. Verify that under the heading System-Wide Overview: Functions And Pipelines Performance And Trends, you no longer see the error and you now see data. The graphs now include Active Pipelines, Failing Pipelines and Slowest Pipelines.