Per T309413, and the fact `deployment-deploy03` is running `debian-10.0-buster` (deprecated 2021-07-30), I am going to spin up a `deployment-deploy04` instance and work on getting it configured.
This task is to track the **creation** and **configuration** of the instance — once complete, it will require testing and configuration changes in Jenkins before it can be used.
== Hostname ==
- `deployment-deploy04`
== Image ==
- `debian-11.0-bullseye`
== Flavour ==
- `g3.cores4.ram8.disk20`
== Puppet classes ==
```
role::beta::deploymentserver
role::deployment_server
role::aptly::server
profile::ci::slave::labs::common
```
== Hiera config ==
```
aptly::manage_nginx: false
profile::ci::slave::labs::common::manage_srv: false
```
=== Project hiera config notes ===
- The config explicitly sets `deploy03` as the `role::aptly::client::servername`, so this instance won't be in conflict
== Considerations ==
[x] Check the project has sufficient resource quota available
[x] Check that the hostname `deployment-deploy04` is unused
[x] Check the `deployment.deploy` puppet prefix for any conflicts
[x] Check the project hiera config for any conflicts
[x] Do a codesearch of "[[ https://codesearch.wmcloud.org/search/?q=deployment-deploy03&i=nope&files=&excludeFiles=&repos= | deployment-deploy03 ]]" and "[[ https://codesearch.wmcloud.org/search/?q=deployment-deploy04&i=nope&files=&excludeFiles=&repos= | deployment-deploy04 ]]" to check for any conflicts