#1631 Request for machine intended for CentOS stream OpenQA instance
Closed: Fixed 16 days ago by arrfab. Opened a month ago by jscotka.

Hi,
I would like to ask to create one machine instance on behalf of the Integration SIG, for OpenQA testing initiative for CentOS streams. (Using Fedora OpenQA tests for CentOS stream)

First version is planned as PoC for testing purposes. whole infra on one machine (there will be containers inside this machine to do dedicated work)

Minimal HW requirements:
- arch: x86_64
- QEMU Virtualization possible directly or nested virt enabled. (to run tests)
- CPU: 4x
- RAM: 8Gb
- Disk: 200Gb

 Thanks
 Honza

Metadata Update from @arrfab:
- Issue private status set to: False (was: True)

a month ago

Hi,

Can you elaborate please ?
As it seems you're not member of the Integration SIG ?
https://accounts.centos.org/group/sig-integration/

Metadata Update from @arrfab:
- Issue priority set to: Waiting on Reporter (was: Needs Review)
- Issue tagged with: need-more-info

a month ago

Hi,
sure. I've asked @bookwar to add me into this group.
Thanks
Honza

We are trying to setup an OpenQA instance to enable the possibility to run tests on CentOS Stream and CentOS Alt SIG images the same way Fedora QA tests Fedora iso.

Jan has ansible playbooks to setup the infrastructure, but we need a place to deploy it. I added him to the Integration SIG

Can you still elaborate as I discussed with @asamalik and he wasn't aware of that either .. :)
What do you want to do ? replace the actual testing.stream.centos.org framework with something else ?
Also, please start a thread on centos-devel list, as it's easier to track/follow/interact there than on a pagure.io ticket

Can you still elaborate as I discussed with @asamalik and he wasn't aware of that either .. :)
What do you want to do ? replace the actual testing.stream.centos.org framework with something else ?
Also, please start a thread on centos-devel list, as it's easier to track/follow/interact there than on a pagure.io ticket

Sure.
I'll create ticket with more details inside integration group to be clear the purpose of this ticket.
Just quick info, it should not replace current testing, at least not now anyhow. It is focused to extend testing of CentOS stream images by using existing fedora tests. So that try to use minimal effort and increase test coverage.

As an official SIG, one can ask for some resources, listed on https://docs.centos.org/centos-sig-guide/ci/

So that can (not must) be openshift namespace and/or ephemeral EC2 instances (through Duffy API)
Worth knowing that default EC2 instances don't support nested virt. We do provide very limited number of bare-metal hosts in the duffy pool (still EC2) but for short period of time and shared between other CI tenants.
But that's also how other tenants in a need to deploy VMs are doing it :

  • ask for a metal host through duffy api (instant access when pool has enough nodes in ready state)
  • configure the machine (through ansible, script, whatever)
  • run tests (including deploying other VMs on top)
  • return the metal host to Duffy (that will terminate the EC2 instance - while Duffy in backend tries to reprovision another metal host in waiting pool)

Thank you very much for renponse, now I'm waiting till https://pagure.io/fedora-infrastructure/issue/12476 to have Oauth2 enabled for OpenQA, and then I'll test this duffy api.

Created new ticket for Oauth2 within centos infra: https://pagure.io/centos-infra/issue/1644

it's becoming difficult to follow if in the ticket for oauth2 you're describing your infra needs :)

Can you keep that organized and so easier to follow please ?
For your frontend/DB host, do you have some specs for the ec2 instance that will be then handed over (but not managed by us so never monitored/backed-up/etc) to you ?
Do you need a hostname ? can we just inject your ssh pub key directly into it and so just give you the details ?

@Hi @arrfab sure.
I've just described it there, to explain it, as you tried to analyse it.

specification (but probably I expect to be able to decrease/increase on demand in the future as I find minimal limits based on usage):

  • arch: x86_64
  • CPU: 4 cores
  • RAM: 8 Gb
  • Storage: 200Gb
  • network: 1 public IP, static hostname FQDN would be fine, to be able use properly HTTPS. some openqa.dev.centos.org or whatever nice :-) (it will be connected with Oauth2 requrest)
  • system: latest released Fedora if it will be provisioned by some base image
  • SSH pub key: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDL78BqdDe7d7PZ4Z5ChiS+zmyC2vU6WhKR48IRratI68B3CyTP8qixyVwmwvMsyp7drfjAqKJXzUMPgvBk2KFo+IICzSqW0tZ14t2qSeb5I1vwLTL8rJSBVh8JtkzPEOpcbjzGpw7VawqGMSRWWJstoPBRPizqayYjPE5sJvfM+1Y+fKF/FRw9SPMc5lOtw4WvPgEwIKd4q2xJIX4xdKNOSbqKDPTg6IFKDXxxcTykhkyFuDbFWA0XPp6qRl52MjJG7rP/xoMTYUKlmX4h4nA4qIRwsSk0T1xxu/kJ6wNgsI1YTcz4ihcaJfaM89eUAvtKf+qmsG6gR4e8hsNLyf+X jscotka@dhcp-25-137.brq.redhat.com

Thanks&Regards
Honza

Metadata Update from @arrfab:
- Issue untagged with: need-more-info
- Issue tagged with: centos-ci-infra, centos-stream, feature-request, medium-gain, medium-trouble

16 days ago

Metadata Update from @arrfab:
- Issue assigned to arrfab

16 days ago

Machine is in DNS and available (deployed, per your request, with Fedora ) :100:

dig @ns1.centos.org +short +noshort openqa.integration.sig.centos.org
openqa.integration.sig.centos.org. 600 IN CNAME openqa.integration.sig.unmanaged-by.centos.org.
openqa.integration.sig.unmanaged-by.centos.org. 600 IN CNAME ec2-18-205-236-1.compute-1.amazonaws.com.

ssh fedora@openqa.integration.sig.centos.org "whoami; uname -a"
fedora
Linux openqa.integration.sigs.centos.org 6.14.0-63.fc42.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Mar 24 19:53:37 UTC 2025 x86_64 GNU/Linux

Your ssh pub key was added to fedora cloud account so you can now use it the way you want (reminder : no backup, no monitoring from centos infra on that machine)

Metadata Update from @arrfab:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

16 days ago

Log in to comment on this ticket.

Metadata