Cinder Third Party CI ... What's in it for you?

on YouTube ↗46m

" summary

Cinder keeps vendor drivers in-tree but requires each vendor to run a third-party CI that executes the Cinder Tempest plugin and reports results; if CI stops responding a driver is marked unsupported and operators must set an unsupported driver flag in cinder.conf or risk removal. Most vendor CIs are flaky (pandemic access and legacy devstack/Zuul v2 issues), Brocade’s FC zone manager lost CI during Python2→3 migration, and teams are urged to deploy Zuul v3 or Software Factory and publish logs.

AI-written summary · about

" chapters (4)

1. 0:00Start
2. 1:43General Project Information
3. 13:08What Can Attendees Expect To Learn Supported versus Unsupported Drivers
4. 16:35Why the Third Party Ci Is Important

" related talks

• 34mDeep Dive: CNCF CIW. Watson, Denver Williams · KubeCon + CloudNativeCon North America 2019
• 24mIntro: CNCF CILucina Stricko, Denver Williams · KubeCon + CloudNativeCon Europe 2019
• 36mThe trials and tribulations of a CI pipeline on Apache InfraMick Semb Wever · ApacheCon@Home 2021
• 15mFedora Zuul CI - an updateFabien Boucher, Matthieu Huin · DevConf.CZ 2021
• 26mDeep Dive: CNCF CILucina Stricko, Denver Williams · KubeCon + CloudNativeCon Europe 2019
• 13mProviding Continuous Integration at CERNDaniel Juarez Gonzalez · Voxxed Days CERN 2019
• 22mCI and CD as a Service: A multi-vendor driven systemSharath Rao, Abhijeet Singh, Avinash Raghavendra · OpenInfra Summit 2020
• 01h 05mFedora CI MeetupMichal Srb, Aleksandra Fedorova, Miroslav Vadkerti, Fabien Boucher · DevConf.CZ 2021