Build a New UAN Image Using the Default Recipe

Build or rebuild the User Access Node (UAN) image using either the default UAN image or image recipe. Both of these are supplied by the UAN product stream installer.

Prerequisites

  • Both the Cray Operation System (COS) and UAN product streams must be installed.
  • The Cray administrative CLI must be initialized.

Overview

The Cray EX User Access Node (UAN) recipe currently requires the Slingshot Diagnostics package, which is not installed with the UAN product itself. Therefore, the UAN recipe can only be built after either the Slingshot product is installed, or the Slingshot Diagnostics package is removed from the recipe.

First, determine if the Slingshot product stream is installed on the HPE Cray EX system. The Slingshot Diagnostics RPM must be removed from the default recipe if the Slingshot product is not installed.

Remove Slingshot Diagnostics RPM From Default UAN Recipe

This procedure does not need to be followed if the Slingshot package is installed.

  1. Perform Upload and Register an Image Recipe procedure to download and extract the UAN image recipe, cray-sles15sp1-uan-cos, but stop before the step that modifies the recipe.

  2. Edit the file config-template.xml.j2 within the recipe by removing these lines:

     <!-- SECTION: Slingshot Diagnostic package -->
         <package name="cray-diags-fabric"/>
    
  3. Resume the Upload and Register an Image Recipe procedure, starting with the step that locates the directory that contains the Kiwi-NG image description files.

    The next step requires the id of the new image recipe record.

  4. Perform the Build an Image Using IMS REST Service procedure in order to build the UAN image from the modified recipe. Use the id of the new image recipe.

Build the UAN Image Automatically Using IMS

This procedure does not need to be followed if choosing to build the UAN image manually.

  1. (ncn-mw#) Identify the UAN image recipe.

    cray ims recipes list --format json | jq '.[] | select(.name | contains("uan"))'
    

    Example output:

    {
      "created": "2021-02-17T15:19:48.549383+00:00",
      "id": "4a5d1178-80ad-4151-af1b-bbe1480958d1",
      "link": {
        "etag": "3c3b292364f7739da966c9cdae096964",
        "path": "s3://ims/recipes/4a5d1178-80ad-4151-af1b-bbe1480958d1/recipe.tar.gz",
        "type": "s3"
      },
      "linux_distribution": "sles15",
      "name": "cray-shasta-uan-cos-sles15sp1.x86_64-@product_version@",
      "recipe_type": "kiwi-ng"
    }
    
  2. Save the ID of the IMS recipe in an environment variable.

    IMS_RECIPE_ID=4a5d1178-80ad-4151-af1b-bbe1480958d1
    
  3. Using the saved IMS recipe ID, follow the Build an Image Using IMS REST Service procedure to build the UAN image.

Build the UAN Image By Customizing It Manually

This procedure does not need to be followed if the previous procedure was used to build the UAN image automatically.

  1. (ncn-mw#) Identify the base UAN image to customize.

    cray ims images list --format json | jq '.[] | select(.name | contains("uan"))'
    

    Example output:

    {
      "created": "2021-02-18T17:17:44.168655+00:00",
      "id": "6d46d601-c41f-444d-8b49-c9a2a55d3c21",
      "link": {
        "etag": "371b62c9f0263e4c8c70c8602ccd5158",
        "path": "s3://boot-images/6d46d601-c41f-444d-8b49-c9a2a55d3c21/manifest.json",
        "type": "s3"
      },
      "name": "uan-PRODUCT_VERSION-image"
    }
    
  2. Save the ID of the IMS image in an environment variable.

    IMS_IMAGE_ID=4a5d1178-80ad-4151-af1b-bbe1480958d1
    
  3. Using the saved IMS image ID, follow the Customize an Image Root Using IMS procedure to build the UAN image.