Downloading the Assets#

Caution

These steps are meant to be executed in the public environment with Internet access.

There are two types of assets that need to be downloaded:

Assets Bundles - The bundles that contain all the resources needed to run Nokia EDA. This includes container images, repositories, tools and more.
Base Talos VM Image - The base images for the Nokia EDA Kubernetes nodes (VMs) that will run the Nokia EDA application.

Downloading the Assets Bundles#

Change into the edaadm repository.
changing into edaadm repository directory
```
cd path/to/edaadm
```
Select Nokia EDA version.

Set the EDA_CORE_VERSION environment variable in your shell to the target Nokia EDA release version, otherwise the latest version will be assumed. This will ensure that the correct version of the cache and assets is downloaded and prepared for the Assets VM.
```
export EDA_CORE_VERSION=26.4.1
```
Download the Assets Bundles.

Container images used in Nokia EDA which are grouped by their function are called Assets Bundles. Users need to download these bundles to have all the necessary components available for the air-gapped installation.

To optimize the download time and storage space, set the environment variables to skip downloading certain versions and/or types of assets. For example, consider the following set of environment variables and the inline explanations provided:
```
export SKIP_APPS_25_8=1 #(1)!
export SKIP_APPS_25_4=1
export SKIP_APPS_24_12=1
export SKIP_APPS_24_8=1
export SKIP_APPS_24_4=1
export SKIP_APPS_CONNECT=1 #(2)!
```
1. Skip Nokia EDA applications for older Nokia EDA versions.
2. Skip Nokia EDA Connect-related assets if Nokia EDA Cloud Connect is not in use.
Instead of downloading all bundles, individual bundles can also be downloaded as described in the section below.

The following command will download all Assets Bundles defined in the bundles folder respecting the environment variables set above and store them in the eda-cargo folder.
```
make -C bundles/ save-all-bundles
```
Downloading individual bundles

In case individual bundles need to be downloaded, use the following command to list the available bundles:
```
make -C bundles/ ls-bundles
```
Using the following command, you can then use the following command to download a specific bundle:
```
make -C bundles/ save-<bundle-name>
```

Downloading the Base Talos VM images#

To deploy the Nokia EDA Kubernetes VMs, the base Talos image is needed for KVM or VMware vSphere. These images can also be downloaded using the edaadm bundles folder as described below.

Change into the edaadm repository.

In case you have changed directories, ensure that you are in the edaadm repository.
changing into edaadm repository directory
```
cd path/to/edaadm
```

Download the base Talos images.

The following command downloads all images for both KVM and VMware vSphere.

make -C bundles/ download-talos-stock-boot-media

The output should look similar to the following:

--> INFO: List of goals: download-talos-stock-boot-media
--> Downloading boot media for vmware
    From: https://factory.talos.dev/image/903b2da78f99adef03cbbd4df6714563823f63218508800751560d3bc3557e40/v1.9.2/vmware-amd64.iso
    To: /path/to/edaadm-repository/bundles/eda-cargo/talos-stock-boot-media/vmware-amd64.iso
############################################################################################################################### 100.0%
    From: https://factory.talos.dev/image/903b2da78f99adef03cbbd4df6714563823f63218508800751560d3bc3557e40/v1.9.2/vmware-amd64.ova
    To: /path/to/edaadm-repository/bundles/eda-cargo/talos-stock-boot-media/vmware-amd64.ova
############################################################################################################################### 100.0%
--> Downloading boot media for nocloud
    From: https://factory.talos.dev/image/376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba/v1.9.2/nocloud-amd64.iso
    To: /path/to/edaadm-repository/bundles/eda-cargo/talos-stock-boot-media/nocloud-amd64.iso
############################################################################################################################### 100.0%
    From: https://factory.talos.dev/image/376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba/v1.9.2/nocloud-amd64.raw.xz
    To: /path/to/edaadm-repository/bundles/eda-cargo/talos-stock-boot-media/nocloud-amd64.raw.xz
############################################################################################################################### 100.0%
--> Downloading boot media for metal
    From: https://factory.talos.dev/image/376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba/v1.9.2/metal-amd64.iso
    To: /path/to/edaadm-repository/bundles/eda-cargo/talos-stock-boot-media/metal-amd64.iso
############################################################################################################################### 100.0%
    From: https://factory.talos.dev/image/376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba/v1.9.2/metal-amd64.raw.zst
    To: /path/to/edaadm-repository/bundles/eda-cargo/talos-stock-boot-media/metal-amd64.raw.zst
############################################################################################################################### 100.0%
    From: https://factory.talos.dev/image/376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba/v1.9.2/metal-amd64.qcow2
    To: /path/to/edaadm-repository/bundles/eda-cargo/talos-stock-boot-media/metal-amd64.qcow2
############################################################################################################################### 100.0%

The downloaded images will be stored in the ./bundles/eda-cargo/talos-stock-boot-media/ folder and can be used during the deploying the Assets VM step.

Depending on the approach used to host the services, follow the appropriate section below.

Using EDA Assets VM

When using the EDA Assets VM you next step is to deploy the Assets VM.

Deploy the Assets VM
Using existing services

In case you are using existing services for one of the required components (git server, container registry or web server), you need to upload the relevant assets using the edaadm.

Upload the assets