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.
Please answer the following questions so that we understand your requirement.
Extend integration testing for CentOS based on fedora tests. Be able to execute tests via OpenQA centOS instance https://openqa.integration.sig.centos.org/
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
yes, I need bare metal/vms with nested virt -> need to setup OpenQA worker there for execute there installation tests e.g. anaconda
nothing special, just baremetal with virt support or VMs with nested virt
Project_name: openqa Project_admins: - jscotka
Metadata Update from @arrfab: - Issue assigned to arrfab
Metadata Update from @arrfab: - Issue tagged with: centos-ci-infra, high-gain, medium-trouble
@jscotka : iirc we discussed that already and you're fine using our duffy CI service , right ? Once confirmed, I'll just create integration-sig as tenant there and send you (gpg encrypted) the duffy api key and ssh key to use to then get root access on ephemeral ec2 instances Just let me know ASAP and I (or @gwmngilfen) will be able to onboard you
integration-sig
Metadata Update from @arrfab: - Issue priority set to: Waiting on Reporter (was: Needs Review)
hi Fabian, @arrfab yes, I would like to use duffy CI service. I hope this will be completely fine for me.
I hope there will be possible network communication between https://openqa.integration.sig.centos.org/ and these machines, ideally over internal (EC2) network, to avoid to expose the communication publicly. But also public IPs will be fine.
There is important to be able to ask for bare metal, and If I understood it correctly I'll be able to ask for baremetal also via this Duffy API.
Thanks a lot Honza
your openqa EC2 instance is in the same VPC so yes, that will be "internal network" between openqa and provisioned duffy nodes (but duffy itself being remote and accessible over https for the api call)
I'll create you tenant/key and transmit these over gpg encrypted email
duffy api and ssh keys sent over gpg encrypted email. Closing
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.