pavlovic-ivan/ephemeral-github-runner-image

Hi there 👋

ephemeral-github-runner-image's Issues

Keep image up-to-date with its components [Ubuntu base image]

Describe the improvement request

Ubuntu base image should be kept up-to-date in the image

I think that a daily scheduled workflow could be used to check for updates to Ubuntu base, and create a PR with the new version number set in variables.auto.pkrvars.hcl when an update is detected. We may also want to have a workflow running on PRs that builds and tests the image, but does not save it.

Here is how I think the check for updates could be done for each component:

Ubuntu base image
Use gcloud to query for the latest image in the ubuntu-2004-lts family

gcloud compute images list --filter family=ubuntu-2004-lts --format "value(NAME)"

Update Packer GitHub action in lint workflow

Describe the improvement request

Look for a Packer Github Action of the same version. Repo has a workflow .github/workflows/lint.yaml hat validates Packer codebase. Replace the appropriate steps with Packer Github Action.

Action is available here

ORA ticket OSS45

Keep image up-to-date with its components

Describe the improvement request

The following components should be kept up-to-date in the image:

• Ubuntu base image
• GitHub Actions Runner
• NVIDIA drivers

I think that a daily scheduled workflow could be used to check for updates to each of those components, and create a PR with the new version number set in variables.auto.pkrvars.hcl when an update is detected. We may also want to have a workflow running on PRs that builds and tests the image, but does not save it.

Here is how I think the check for updates could be done for each component:

Ubuntu base image

Use gcloud to query for the latest image in the ubuntu-2004-lts family

gcloud compute images list --filter family=ubuntu-2004-lts --format "value(NAME)"

GitHub Actions Runner

Use the GitHub REST API to query for the latest release (the v prefix will need to be removed)

gh api /repos/actions/runner/releases/latest | jq -r .tag_name

NVIDIA drivers

The decision to go from one major version to another should be done by a human (e.g. by updating the scheduled workflow).
The latest datacenter driver versions can be found on https://docs.nvidia.com/datacenter/tesla/index.html. We should probably parse this HTML file (e.g. with https://pypi.org/project/beautifulsoup4/ or https://developer.mozilla.org/en-US/docs/Web/API/DOMParser/parseFromString) and figure out the latest version for a given major (e.g. 470 -> 470.103.01 at the time of writing).

We don't need to have all 3 components done before we can roll out this feature. It seems to me that the first 2 are low hanging fruits and we would immediately benefit from having these always up-to-date.

Keep image up-to-date with its components [NVIDIA drivers]

Describe the improvement request

NVIDIA drivers should be kept up-to-date in the image.

I think that a daily scheduled workflow could be used to check for updates of NVIDIA drivers, and create a PR with the new version number set in variables.auto.pkrvars.hcl when an update is detected. We may also want to have a workflow running on PRs that builds and tests the image, but does not save it.

NVIDIA drivers
The decision to go from one major version to another should be done by a human (e.g. by updating the scheduled workflow).
The latest datacenter driver versions can be found on https://docs.nvidia.com/datacenter/tesla/index.html. We should probably parse this HTML file (e.g. with https://pypi.org/project/beautifulsoup4/ or https://developer.mozilla.org/en-US/docs/Web/API/DOMParser/parseFromString) and figure out the latest version for a given major (e.g. 470 -> 470.103.01 at the time of writing).

Update Packer GitHub action in build workflow

Describe the improvement request

Look for a Packer Github Action of the same version. Repo has a workflow .github/workflows/build.yaml. There is one job with three steps.
Adapt the job and its steps so that Packer Github Action is used, instead of installing it with inline script. Do the same for the build step.

Action is available here

ORA ticket OSS45

Add Support for building amd64 images on the AWS platform

Describe the improvement request

The project should be able to support amd64 images on the AWS platform

Add Support for building arm64 images on the AWS platform

Describe the improvement request

The project should be able to support arm64 images on the AWS platform