Implementing Metal3 IPA build pipelien suitable to start releaseing custom Metal3 IPA to public

[Rozzii]

IPA build pipeline has already existed as part of the Fullstack build pipeline. I am working the first refactoring PR to support building and releasing IPA on multiple distros. First PR is just a draft now as I am reorganizing the whole pipeline structure and testing is a bit complicated and not everything works yet: metal3-io/project-infra#1167 , IPA images will land in nordix Artifactory: https://artifactory.nordix.org/artifactory/metal3/images/ipa/staging/centos/ as tarballs and in quay as OCI images.

[Rozzii]

/cc @elfosardo @dtantsur

[s3rj1k]

I would really like to see support of Rocky Linux 10 base for IPA

[dtantsur]

Could you eventually move the building scripts from under project-infra? I think we'll want to extend the ownership of that to the Ironic side of our team without giving everyone rights on project-infra.

[dtantsur]

For the OCI part, we need to agree on how we name and tag images.

• CPU architecture can be a part of the metadata
• The distribution clearly needs to be a part of the tag
• Since we have two components (kernel and initramfs), do we have two images on quay or two types of tags?
• I also assume we'll need to include some version to account for possibility of branching.

I.e. do we have quay.io/metal3-io/ironic-agent-image:kernel-cs10-latest and quay.io/metal3-io/ironic-agent-image:initramfs-cs10-latest, or do we have quay.io/metal3-io/ironic-agent-kernel:cs10-latest and quay.io/metal3-io/ironic-agent-initramfs:cs10-latest? The latter looks nicer to me but I'm worried about the pair getting out of sync in case of build or Quay problems. Am I overthinking it?