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.
How does your project relates to Fedora/CentOS? - RamenDR is an open source project that provides recovery and relocation services for workloads and their persistent data across a set of OCM-managed clusters. - We want to test functionality on CentOS using a public CI to more appropriately test an end-to-end environment for relocate and recovery scenarios. Current testing options are either private, not integrated into our CI pipeline, or limited to a single system (unrealistic for a DR scenario).
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. - Current workflow: create PR on GitHub, run GitHub Actions to compile and lint the build, run single-system-based unit tests, and conditionally create a container build and push to Quay. - Desired updates to this workflow: augment existing CI pipeline with e2e testing involving more than one node (multiple nodes are not supported by GitHub Actions). Current e2e test processes exist, but are manual and the results aren't visible to others by default.
Do you need bare-metal/vms checkout capability? (we prefer your workflow containerized) - Ideally we could run these workloads bare-metal or on VMs. We may be able to run similar tests with a containerized version.
Project_name: RamenDR Project_admins: - tjanssen@redhat.com
Metadata Update from @arrfab: - Issue tagged with: centos-ci-infra, namespace-request
Adding some more context to the request:
The disaster recovery solution that we are working on with Ramen consumes the Ceph and Ceph-CSI projects as the core storage providers in the kubernetes landscape, which are part of CentOS sig-storage
Our major constraint due to which we require acceptance into the CentOS CI framework is that we need to run 2-3 minikube instances for each test, as this involves recovery from a k8s cluster to another where Ceph is the backing store across both instances, and we are unable to do so in other CI frameworks at present as they lack the required hardware or abstractions to provide us the required support
Please let us know what we can do to gain acceptance in this regard, Thanks!
There is an ongoing survey for existing CI infra tenants as it can be that CI infra will be downsized and moved. So accepting tenants that aren't even directly related to centos/fedora is actually "blocked" until it it's all sorted out
Metadata Update from @arrfab: - Issue tagged with: blocked
[backlog refinement call] : after discussion with the infra and releng team, and also due to some resources limitations on current centos ci infra, we unfortunately can't accept your request to use our infra to host your ci tests.
Metadata Update from @arrfab: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.