Linux engineering team would like to work on accelerators support in the CS space so they can leverage RHEL on GitLab that would be syncing these into RH internal dist-git similar way it works for c10s and RHEL today on the "c10s" branches.

Dist-git

To be able to do the accelerators related work, the team will need CentOS Stream GitLab dist-git branches with name "c10s-aie-nv" for these packages:

• kernel - jstancek@redhat.com
• qemu-kvm - mrezanin
• libvirt - phrdina@redhat.com

Regarding ACL policies, the maintainers will be the same people as there are for c10s, the people above are the main reps of this effort for the packages.

Build setup

The devs will need to be able to build these packages in CS. Ideally they should have a separate tagging structure called "c10s-aie-nv".

That structure would have a build targets called:

c10s-aie-nv-candidate  # To make manual centpkg work
c10s-aie-nv-draft      # To make RoG work (as I assume RoG uses draft builds)

Bould would use a buildroot

c10s-aie-nv-build

Where:

• This buildroot would be containing previously build c10s-aie-nv builds and it would be based on the c10s buildroot (will be inheriting c10s buildroot)
• The dist-tag for builds done in the buildroot should be ".el10nv".
• Architectures the buildroot will be building for are: aarch64 & x86_64

There are likely other tags and config changes that needs to be done.

Composes

This haven't been discussed yet and I'm not sure what are possibilities in CS space, but I believe that having a periodic compose (a periodically generated repository) containing the latest builds of the three included packages would be useful for developers and QE, but it depends if CS team does this.

Notes

cc msrb@redhat.com, vkabatov@redhat.com, ckelley@redhat.com, dzickus@redhat.com to chime in with any CI / RoG related requirements if any.
cc rh-ee-alougovs & ailan@redhat.com from Linux engineering who leads this
cc jstancek@redhat.com, mrezanin, phrdina@redhat.com who are devs working on this