Hosted EVE-OS Images

Updated

Introduction

Hosted EVE-OS Images simplifies the process of updating your edge nodes with the most recent EVE-OS image. This enhancement provides a centralized, ZEDEDA-hosted data store for all supported EVE-OS images, eliminating the need to manage your own EVE-OS image repositories.

Having ZEDEDA hosting EVE-OS images reduces the cost and effort of maintaining your EVE-OS versions and infrastructure, while bolstering security by ensuring that all EVE-OS images are sourced directly from ZEDEDA. This simplifies the process of keeping your edge infrastructure updated with the most recent security patches and other new features.

To use this new feature, you don’t need to configure the data store, since ZEDEDA will be hosting the EVE-OS images in an S3 bucket in the AWS cloud.

Prerequisites

  • You must have either the SysManager or SysAdmin role in your ZEDEDA Cloud enterprise.
  • The edge nodes in your enterprise must be able to reach your ZEDEDA-hosted data store in AWS S3. Therefore, you must open the firewall’s external connections between your edge nodes and the ZEDEDA-hosted data store URL. To find the URL for this hosted data store, see Locating the FQDN.

 

Import ZEDEDA-Hosted EVE-OS Image

To import one of the hosted EVE-OS images:

  1. Log into the ZEDEDA GUI.
  2. From the left panel, go to Library > EVE-OS Images to display images in List view.
    The List view table displays all of the EVE-OS images that are included in this enterprise (ZEDEDA-hosted and all others). The table has the following columns:
    • Name: The name of the ZEDEDA-hosted EVE-OS image.
    • Image Format: The image format, such as QCOW2 or RAW.
    • Image Architecture: The type of CPU, such as AMD64 or ARM64.
    • Image Status: The status of the image. For example, this could be Ready, Max, Pending, and so on. For a complete list, see Status Distribution (step 4 below).
    • Data Store: For ZEDEDA-hosted images, this will say “Zededa-AWS-Image”
    • Image Size: This is the total file size for the image, which varies by version.

      For longer definitions for these fields above, see "identity attributes" in EVE-OS Image Entries in ZEDEDA Cloud.
       
  3. Click Expand (arrow at upper right) to display the Summary section. In addition to the “Status Distribution” and “Architecture Distribution”, the summary region also shows the default EVE-OS images for ARM and AMD architectures:

    Note: To change the default EVE image for new nodes, see Set the Default Image.

     
  4. The “Status Distribution” shows the following for EVE-OS images:
    • Archived: The OS image is no longer actively used or available for new deployments, but retained for historical purposes.
    • Created: The OS image record has been created in the system.
    • Failed: The OS image upload or processing failed, making it unusable.
    • In Use: The OS image is currently deployed and running on edge nodes.
    • Max: The maximum number of OS images has been reached.
    • Pending: The OS image is awaiting further action or processing.
    • Ready: The OS image is fully prepared and available for deployment.
    • Uplinking: The OS image metadata is being synchronized with the storage.
    • Uploading: The OS image file is actively being transferred to cloud storage.
       
  5. Click the Import EVE-OS icon at upper right to display the Import Image to Library modal. This modal lists all available LTS (long-term support) images not already part of this enterprise.
    • Images with the most recent date published will appear near the top of the modal.
    • Some images may NOT appear. For example, any images that are hosted on your local FTP server, or anywhere other than the ZEDEDA-managed S3 bucket, will not be listed here.
    • You can learn more about a specific image (in terms of new features and bug fixes), by clicking the "Release Notes" link at upper right.
       
  6. From the modal that appears, make the following configurations:
    • Version: Enter the number of the image you want to import.
    • Architecture: Select AMD64 or ARM64 to reduce the images displayed.
    • Select the radio button next to the EVE-OS image you want to import.
    • Click Import to being downloading the image to your enterprise. When the download is finished, a toast message appears, and the image is listed in the EVE-OS Images table.
       

Set the Default EVE-OS Image

You can set the default EVE-OS image that will be used to onboard all future edge nodes:

  1. Log into the ZEDEDA GUI.
  2. Navigate to Library > EVE-OS Images
  3. Select the target image you want to use as the default.
  4. Select More Actions (ellipsis at upper right).
  5. Click Set as Default.
     

Delete an EVE-OS image

You can delete an EVE-OS image from the data store:

  1. Log into the ZEDEDA GUI.
  2. Navigate to Library > EVE-OS Images.
  3. Click on the target image.
  4. Select More Actions (ellipsis).
  5. Select Delete. 

    Notes:
    • An EVE-OS image cannot be deleted if it is currently set as the 'default'.
    • An EVE-OS image cannot be deleted if that image is installed on an edge node in your enterprise.

 

Locate the FQDN for the ZEDEDA-Hosted Data Store

You can locate the URL for the ZEDEDA-hosted data store as follows:

  1. Log into the ZEDEDA GUI.
  2. Navigate to Library > Data Stores.
  3. From the list of available data stores, use the Name column to find the data store named “ZEDEDA-Image-Repository” and click on it. This data store will be auto-provisioned as part of all enterprise environments.
  4. Scroll down to the Details section of the page, and locate the FQDN for the data store. 
    It should look similar to this: “https://s3-eu-north-1.amazonaws.com”
Was this article helpful?
0 out of 0 found this helpful