https://pagure.io/centos-infra/issue/1705

1. 1. CentOS CI - On-boarding

Please note that Infra space is for Fedora and CentOS related projects to
consume. Decision may take some time (often up to 2 weeks) as these are decided
by the whole team.
Once decided as go, we will create you a namespace in a openshift cluster where
you can configure your CI. We do provide a Jenkins template in case you want to be
able to consume vms/baremetal nodes to perform your CI.

• Request based on https://gitlab.com/CentOS/Integration/general/-/issues/8
• connected with
• centos openqa instance: https://pagure.io/centos-infra/issue/1631
• OAuth2 cli via id.centos.org - https://pagure.io/fedora-infrastructure/issue/12476
• jenkins not needed as resources will be reserved dynamically by openqa instance.

Please answer the following questions so that we understand your requirement.

• How does your project relates to Fedora/CentOS?
  ` Extend integration testing for CentOS based on fedora tests. Be able to execute tests via OpenQA centOS instance https://openqa.integration.sig.centos.org/`
• Describe your workflow and if you need any special permissions (other than
  admin access to namespace), please tell us and provide a reason for them.
  `Workflow: new compose created -> reserve resource inside EC2 -> setup it as worker for OpenQA -> test execution -> test finished -> return machine to the pool`
  `Not really, just be able to reserve bare metal machines for test execution with virt support, so in case special permission means also nested virt on virt machines in cluster, then also this could help`
• Do you need bare-metal/vms checkout capability? (we prefer your workflow
  containerized)
  `yes, I need bare metal/vms with nested virt -> need to setup OpenQA worker there for execute there installation tests e.g. anaconda`
• Resources required
  `nothing special, just baremetal with virt support or VMs with nested virt`

```
Project_name: openqa
Project_admins:

• jscotka

```