CSI driver for Ceph
Go to file
Niels de Vos 893da82f71 ci: use VM_DRIVER=podman for AWS virtual-machines
With the CentOS CI machines moving to AWS EC2 virtual-machines, there is
no option to run minikube with a VM anymore. Instead, run minikube with
the Podman driver and partition the extra xvdb EBS volume into three
pieces.

Signed-off-by: Niels de Vos <ndevos@redhat.com>
2022-10-10 07:18:28 +00:00
deploy ci: use CentOS Stream 8 for infra containers 2022-02-04 03:12:34 +00:00
jobs ci: run k8s v1.26 jobs on request 2022-09-22 04:50:27 +00:00
mirror ci: update rook image in centos ci 2022-10-07 16:11:37 +00:00
scripts ci: use Helm 3.1.2 in test container 2021-04-20 07:08:16 +00:00
.commitlintrc.yml ci: error out for invalid component in commit header 2020-08-19 11:15:09 +00:00
.gitignore cleanup: add unwanted files to gitignore 2022-05-05 09:44:57 +00:00
ci-job-validation.groovy ci: request CentOS Stream 8 bare-metal machines 2022-02-02 12:41:11 +00:00
commitlint.groovy ci: request CentOS Stream 8 bare-metal machines 2022-02-02 12:41:11 +00:00
containerized-tests.groovy ci: replace docker.io ceph image with quay.io path 2022-03-30 09:11:37 +00:00
k8s-e2e-external-storage.groovy ci: replace docker.io ceph image with quay.io path 2022-03-30 09:11:37 +00:00
Makefile build: only use --cpuset options when the cgroup controller is available 2021-03-03 05:48:42 +00:00
mini-e2e-helm.groovy ci: replace docker.io ceph image with quay.io path 2022-03-30 09:11:37 +00:00
mini-e2e.groovy ci: replace docker.io ceph image with quay.io path 2022-03-30 09:11:37 +00:00
podman2minikube.sh ci: use VM_DRIVER=podman for AWS virtual-machines 2022-10-10 07:18:28 +00:00
prepare.sh ci: add the root user to the libvirt group 2021-07-16 09:59:45 +00:00
README.md ci: update links to new OCP4 deployment 2020-07-24 14:11:42 +00:00
run-k8s-external-storage-e2e.sh ci: skip Ephemeral-volume kubernetes external-storage tests 2021-06-30 13:40:08 +00:00
single-node-k8s.sh ci: use VM_DRIVER=podman for AWS virtual-machines 2022-10-10 07:18:28 +00:00
system-status.sh ci: collect kubelet status 2022-05-06 06:49:58 +00:00
upgrade-tests.groovy ci: request CentOS Stream 8 bare-metal machines 2022-02-02 12:41:11 +00:00

Continuous Integration Jobs for the CentOS CI

  • dedicated Jenkins instance for Ceph-CSI
  • Jenkins is hosted on OpenShift in the CentOS CI
  • scripts and Jenkins jobs are hosted in the Ceph-CSI repository (ci/centos branch)
  • a Jenkins Pipeline is used to reserve bare metal system(s), and run jobs on those systems

Repository/Branch Structure

This is the ci/centos branch, where all the scripts for the Jenkins jobs are maintained. The tests that are executed by the jobs are part of the normal projects branches.

As an example, the containerized-tests Jenkins job consists out of the following files:

  • jobs/containerized-tests.yaml is a Jenkins Job Builder configuration that describes the events when the job should get run and fetches the .groovy file from the git repository/branch

  • containerized-tests.groovy is the Jenkins Pipeline that contains the stages for the Jenkins Job itself. In order to work with the bare-metal machines from the CentOS CI, it executes the following stages:

    1. dynamically allocate a Jenkins Slave (node('cico-workspace')) with tools and configuration to request a bare-metal machine
    2. checkout the centos/ci branch of the repository, which contains scripts for provisioning and preparing the environment for running tests
    3. reserve a bare-metal machine with cico (configured on the Jenkins Slave)
    4. provision the reserved bare-metal machine with additional tools and dependencies to run the test (see prepare.sh below)
    5. run make containerized-tests and make containerized-build in parallel
    6. as final step, return the bare-metal machine to the CentOS CI for other users (it will be re-installed with a minimal CentOS environment again)
  • prepare.sh installs dependencies for the test, and checks out the git repository and branch (or Pull Request) that contains the commits to be tested (and the test itself)

Deploying the Jenkins Jobs

The Jenkins Jobs are described in Jenkins Job Builder configuration files and Jenkins Pipelines. These need to be imported in the Jenkins instance before they can be run. Importing is done with the jenkins-jobs command, which runs in a jjb container. To build the container, and provide the configuration for Jenkins Job Builder, see the documentation in the deploy/ directory.