---
# System prepended metadata

title: Ceph and TripleO
tags: [Design]

---

# Ceph and TripleO
###### tags: `Design`

Context here is that we have some additional ci resources
coming online and it looks like helping Guilo and John Fulton
would be a good thing.

## latest ceph status
https://etherpad.openstack.org/p/tripleo-integration-squad-status

## rpm builds
* repo closure
* The undercloud needs the [ceph-ansible](https://cbs.centos.org/koji/packageinfo?packageID=3726) RPM which is maintained as part of the CentOS storage SIG
* CBS
    * https://cbs.centos.org/koji/builds?tagID=1891
    * https://cbs.centos.org/koji/buildinfo?buildID=28564

## container builds
* centos-8 currently using https://opendev.org/openstack/kolla/src/branch/master/docker/base/ceph_master.repo
    * where are the official repos being created?
* The overcloud uses the [ceph-container from docker hub](https://hub.docker.com/r/ceph/daemon)

## testing with do not merge patches
* Gulio has [DNM patches](https://review.opendev.org/#/q/owner:%22Giulio+Fidente+%253Cgfidente%2540redhat.com%253E%22+DO-NOT-MERGE+status:open) which test new versions of ceph-ansible and ceph-container against TripleO.
* If a DNM patch passes, then the build (RPM or container) can be promoted to the new stable.
* TripleO (without the DNM patches) only uses stable versions of these pacakges
* This process keeps changes in ceph-ansible or ceph-container from breaking TripleO CI


## third party github ci
### ceph-ansible
Some work has been done to test the latest ceph-ansible builds from
github.  Dashboard is here: http://dashboard-ci.tripleo.org/d/jiglzyLWk/third-party-dependency-check?orgId=1

* double check these jobs to esure ceph-ansible is consumed and tested


## future w/o ceph-ansible
* when does this change
* what is the impact
* how should tripleo and tripleo-ci respond, cover etc.. to continue to ensure quality

### Possible Roadmap
- There's already a tested combination of versions between OpenStack/Ceph: Queens+Rocky on Luminous,  Stein+Train+Ussuri on Nautilus
- In Octopus, ceph-orchestrator may take the place of ceph-ansible for non-k8s deployments (it's not yet feature complete enough to do so)
- If Victoria moves to Octopus, then one option is to keep as many THT parameters as possible and replace calls to ceph-ansible with calls to ceph-orchestrator. See [tripleo-ansible ceph roles](https://github.com/openstack/tripleo-ansible/commit/4d38019467694469c5df1e549e8a0be73b727814) for context.
- Even if calls to ceph-orchestrator are minimal, TripleO needs to verify it supports HCI. So jobs which test HCI should remain regardless of what deployed Ceph.

## Current in progress work
* https://review.opendev.org/#/c/706889/