jetlag

jetlag copied to clipboard

SNO generate discovery iso should use the boot_iso host var

1

akrzos

A quick example would be attempting to run `sno-deploy.yml` but having `cluster_type: bm` or running `bm-deploy.yml` and having `cluster_type: sno`. Ideally the first task or before any interaction with the...

akrzos

akrzos

Discovery task relies on count of machines in the inventory

1

The [task](https://github.com/redhat-performance/jetlag/blob/main/ansible/roles/wait-hosts-discovered/tasks/main.yml#L14) for waiting to see that all booted machines have become discovered relies on the [count of the inventory](https://github.com/redhat-performance/jetlag/blob/main/ansible/roles/wait-hosts-discovered/tasks/main.yml#L9-L12) where as the actual count of machines booted can be...

akrzos

There appears to be 3 different methods to mirroring images into the bastion registry. We should determine if all are necessary or if any can be replaced. Additionally we should...

akrzos

Remove multi-cluster SNO complications.

4

Jetlag will always create a single cluster, whether single or multi-node. SNO inventory discovery will comment all "free" machines past the first, and deployment will always work on the single...

dbutenhof

Add components for ACM to install on SNO clusters

2

Clustertype: SNO did not include the components necessary to be able to install ACM. This patch adds components so that the ztp and hub deploy scripts in acm-deploy-load should be...

radez

[RFE] Have a release cadence

1

To consume jetlag from CI pipelines having a release cadence in place is fundamental.

josecastillolema

Test and document jetlag L3 deployments. Considering two scale lab allocations with public vlans (cloud x and cloud y), it should be possible to deploy cloud y from a bastion...

josecastillolema

renaming bm to mno

7

Patch for PR#441 baremetal is not the right name for the cluster being deployed. It should be named mno: multinode openshift

radez