Skip to content

Create production VM config in release step

Adrien Kohlbecker requested to merge ak/release-config into main

What does this MR do?

Update the release jobs to create a VM configuration pointing to the newly released image. Benefits from the same IO Boost settings used in building images, so we have a correct setting depending on the OS.

Users can only access their VMs, so we need to create two configurations: one for the canary user (used for the canary runners) and one for the beta user (used to host the customer projects during the beta).

Why was this MR needed?

We need to support IO boost before upgrading Orka to 1.6 (it becomes enabled by default and we need to disable it on 10.13 and 10.14). Goal is to make use of the new deploy from known VM configuration feature in autoscaler.

What's the best way to test this MR?

I patched the pipeline to run a test job here https://gitlab.com/gitlab-org/ci-cd/shared-runners/images/macstadium/orka/-/jobs/1569933295 which created the right VM configurations:

❯ orka vm list --filter all


 Not Deployed: 4
   ┌─────────────────────┬───────────────────────────────────┬──────────┬─────────────────────────┬──────────┬─────────────────┐
   │        Name         │               Owner               │ vCPU|CPU │       Base image        │ IO Boost │ Use Saved State │
   ├─────────────────────┼───────────────────────────────────┼──────────┼─────────────────────────┼──────────┼─────────────────┤
   │ mr-112-can-11-12-35 │ autoscaler-orka-canary@gitlab.com │ 4|4      │ mr-112-ork-11-12-35.img │ enabled  │ no              │
   ├─────────────────────┼───────────────────────────────────┼──────────┼─────────────────────────┼──────────┼─────────────────┤
   │ mr-112-ork-11-12-35 │ autoscaler-orka-beta@gitlab.com   │ 4|4      │ mr-112-ork-11-12-35.img │ enabled  │ no              │

What are the relevant issue numbers?

Edited by Adrien Kohlbecker

Merge request reports