Barometer Container Deployment Sunku Ranganath Krzysztof Kepka Kamil

Barometer Container Deployment Sunku Ranganath Krzysztof Kepka Kamil Wiatrowski

Existing Container Deployment • Deploys collectd container based on latest release (5. 8) branch • Functest runs with Collectd 5. 8 Intent Development Collectd Releases • Stable branches Barometer Releases • For early Input & Test

Gaps w/ Existing Approach • Unknown Collectd release cadence • Difficult to showcase new features • Does not incorporate upstream fixes

Proposed Container Deployment • 3 container approach 1. “Stable” – currently available container with latest stable release branch (5. 8). 2. “Master” – new container, based on latest collectd master branch. – Patches ready, to be upstreamed – Need to integrate with upstream CI, leverage existing CI infrastructure 3. “Experimental” – new container, with selected patches, that are not accepted/merged yet – Based on latest collectd master branch. – Treated as unstable, and any issues with additional patching may not be addressed immidietly. – No Functest support – Cherrypick a list of PRs using scripts • Changes required • Add new containers to CI builds • Tag containers appropriately

Proposal The idea is to provide multiple containers with different set of features and level of stability for early evaluation. Collectd 5. 9 Collectd 5. 8 Merge PR 2 PR 1 Rebase Collectd Master PR 3 Rebase Barometer Experimental Container

Experimental Container Patch Process 1. Submit a PR to the Collectd Master 2. Propose in Barometer mailing list or weekly call on updates to Experimental container 3. Provide a patch in the Barometer Gerrit 4. Get +2 5. Update the experimental container. 6. If any conflicts/issues, go through mailing list/Barometer call for fast resolution.

Pros Vs Container Stable Pros Cons Last stable release packed in Lack of features introduced same manner after last release Master All changes already accepted by community Time between creating PR and merge to master Experimental Latest features available to check and test May be unstable and fixing may not be immidietly

Next Steps • “Master” container to be upstreamed shortly • To be integrated with Functest CI • Figure out to get in to G release • Deadline is about 2 -3 weeks from now • “Experimental” container under development