class: center, middle, inverse # Cloud SIG Update ## Haïkel Guémar - @hguemar --- ## whoami .right-column[
] .left-column[ * CentOS/Fedora developer * RDO Release Wrangler @ Red Hat ] --- class: center, middle, inverse # Introduction --- class: middle ## Current active groups
--- class: middle ## What's RDO RDO is a freely-available and community supported distribution of OpenStack packaged and integrated for Enterprise Linux (CentOS, RHEL). More on http://rdoproject.org --- class: middle ## What happened this cycle * Pike Release early september * Build tagging automation * RDO Cloud * CICO Cloud now relies on RDO Pike --- class: middle ## Some statistics * 3 supported releases (Newton, Ocata, Pike) + master (Queens) * 1709 binary packages * 820 sources packages * 313 OpenStack projects packages (including 37 clients, 97 puppet modules) * 4 different installers tested: Puppet, Packstack, TripleO, Kolla --- class: middle ## More statistics * 1966 commits (10 commits merged per day avg) * 87 contributors (13 not from Red Hat) In comparison, upstream: * 1800+ contributors * 250 commits per day
More on [repoXplorer instance](https://38.145.33.181/repoxplorer/project.html?pid=RDO/rdo) --- class: middle ## Even more statistics | Release | Upstream | RDO | Delay | |:------: |:--------------:|:--------------:|:--------:| | Newton | Oct, 6th 2016 | Oct, 7th 2016 | 1 day | | Ocata | Feb, 22nd 2017 | Feb, 22nd 2017 | 12 hours | | Pike | Aug, 30th 2017 | Sep, 2 2017 | 3 days | --- class: middle ## What we learnt this cycle * Automation enables more people to contribute *safely* * Better planning to cover PTO * Pipeline release speed matters [Pike release post-mortem](https://review.rdoproject.org/etherpad/p/pike-release-preparation) --- class: middle, inverse, center # Cross-SIG collaboration --- class: middle ## SIGs we work with The ones we depend on: * Virt SIG: qemu-kvm-ev, docker * Storage SIG: Ceph * Opstools SIG (optional) The ones relying on us: * OPNFV --- class: middle, inverse, center # Infrastructure --- class: middle ## Buildsystem Setup * RDO trunk builds are available for Fedora and EL7 through DLRN * RDO for Enterprise Linux is built in CentOS Community Build System and relies only on content published by CentOS --- class: middle ## Packaging/Patches review * Using gerrit like OpenStack upstream * Patches and packaging changes runs through a review * [Hosted on gerrithub](https://review.gerrithub.io/#/q/project:openstack-packages) * Trigger a serie of CI jobs --- class: middle ## DLRN DLRN is a Continuous Delivery platform that take every upstream commit and build it as a consumable package for CI purpose. ```bash +------------+ +---------+ +------------+ +-------------------+ | | | | | | | | | New commit +----> current +----> consistent +----> current+passed+ci | | | | | | | | | +------------+ +---------+ +-----^------+ +---------^---------+ | | | | +-----+------+ +---------+---------+ | RDO CI | | Upstream CI | +------------+ +-------------------+ ``` --- class: middle ## DLRN CI ```bash +------------+ +---------+ +------------+ +-------------------+ | | | | | | | | | New commit +----> current +----> consistent +----> current+passed+ci | | | | | | | | | +------------+ +---------+ +-----^------+ +---------^---------+ | | | | +-----+------+ +---------+---------+ | RDO CI | | Upstream CI | +------------+ +-------------------+ ``` * master: every commit or almost is built * consistent: set of packages without build failures * current-passed-ci: snapshot that passed CI * stable releases: packages from upstream tagged tarballs + sanity checks * RDO CI targets consistent snapshots * Upstream CI projects targets current-passed-ci (e.g. packstack, tripleO, kolla, puppet) --- class: middle ## WeiRDO * Ansible-based framework using gate jobs and make them usable outside upstream gates * Goal is to improve coverage upon what upstream provides. ```bash +------------+ +-----------------------+ +---------------+ | | | | | | WeIRDO | Provision | | Install dependencies | | run_tests.sh | [1] | test node +------> & patch assumptions +---> or tox | | | | | | | +------------+ +-----------------------+ +---------------+ +---------------+ +--------------------+ +----------------+ | | | | | | tox | Install | | Install/Configure | | Test | [2] | dependencies +---> OpenStack +------> (e.g. Tempest) | | | | | | | +---------------+ +--------------------+ +----------------+ +---------------+ +------------+ | | | | WeIRDO | Recover logs | | Destroy | [1] | and results +---> test node | | | | | +---------------+ +------------+ 1. with Ansible 2. or run_tests.sh provided by upstream ``` [WeiRDO documentation](http://weirdo.readthedocs.org/en/latest/) [WeiRDO jobs on ci.centos.org](https://ci.centos.org/view/rdo/) --- class: middle ## rdopkg: swiss army knife for RDO packaging * Automate most of the annoyances * Rebase/Updating patches/Submit updates etc. [Available here](https://copr.fedoraproject.org/coprs/jruzicka/rdopkg/) --- class: middle, center, inverse # Contributing to RDO --- class: middle ## RDO packaging documentation [documentation](https://rdoproject.org/documentation/packaging) [sources](https://review.gerrithub.io/#/admin/projects/?filter=openstack-packages) <= Gerrit reviews are welcome! --- class: middle ## Communication channels * mailing-list: http://www.redhat.com/mailman/listinfo/rdo-list * IRC: #rdo @freenode --- class: middle, center, inverse # Q/A