How ibmstorage/qe-ceph-manifest works
Project type and purpose
• This is an open-source manifest repository (‘qe-ceph-manifest’) that holds YAML definitions of Ceph component versions, RPM repos, and container images.
• It is consumed by IBM Storage Ceph QE and CI systems (via the cephci tool) to deploy test environments matching specific product, release, build-type, and platform parameters.
File structure
• Top-level files:
• LICENSE, README.md
• Top-level directories by product:
• ceph/…
• ibm/…
• redhat/…
• Each directory contains multiple <version>.yaml files.
• No code, just structured data used at runtime by an external tool.
README for additional insights
• Describes the YAML schema: top-level keys (nightly, stable, released, zN) mapping to cephci --build-type.
• Documents second-level keys (version, repositories, images, optional repo_ids).
• Explains how cephci selects the correct manifest: flags --product, --release, --build-type, --platform.
Components & interactions
a. Main components
• Manifest Git Repository (this project)
• CI Orchestrator (e.g., Jenkins or IBM QE CI)
• cephci client tool
• RPM Repositories (external)
• Container Registry (external)
• Test Environment (KVM or bare-metal cluster)
b. Relationships & data flow
1. CI Orchestrator triggers a job for a test scenario.
2. The job invokes cephci with flags (--product, --release, etc.).
3. cephci clones or pulls the Manifest Repo.
4. cephci parses the selected <product>/<release>.yaml manifest.
5. cephci uses repositories entries to configure yum/baseurl on test nodes.
6. cephci pulls container images from the images registry namespace.
7. cephci orchestrates deployment of Ceph cluster in the Test Environment.
c. Architectural patterns/design principles
• Separation of configuration (YAML manifests) from execution logic (cephci).
• Declarative configuration for easy version-targeted deployments.
• Plugin-like extensibility: add a new product or release by dropping a YAML.
d. Relevant technologies
• Git (source control for manifests)
• YAML (manifest format)
• Python (cephci implementation)
• Jenkins or IBM QE CI (pipeline orchestrator)
• RPM repos (yum) and Docker/Podman registries