Wikimedia Release Engineering Team/Deployment pipeline/2017-03-28
2017-03-28
editWho's here: Antoine thcipriani, Jean-René, Alexandros, Dan, Marko
Last Time
edit- Little bit about ci-staging k8s
- Lot of focus on next quarter colaboration
- Releng needed to firm up quarterly goal
- In future, once work is under way: shorten this meeting (i.e. Scrum of Pipelines)
Topics
editDocker registry
editThere is one in production already. We should aim to reuse that existing registry (unless something dramatically stops us) either directly or via some namespacing Storage handled via OpenStack Swift (eg: plenty of disk space)
Point of contact: Alexandros
What runs containers ?
editDocker being rearchitectured https://containerd.io/ has some info Preference toward using Docker Maybe later move to rkt (or whatever else) Docker versioning moved to year.month.patch (ex: v17.03.1-ce ) https://github.com/docker/docker/releases
runc/docker etc all adhere to OCI runtime specification. (yeah for standards!) https://github.com/opencontainers/runtime-spec
Homegrown image specification
editAbstraction to generate Dockerfile (eg service-runner). Be prepared for backfire from people already familiar with Dockerfile Will need lot of documentation!!!
Next quarter cooperation
edit- Releng next quarter goals: https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Goals/201617Q4
- Services Q4 goals: https://www.mediawiki.org/wiki/Wikimedia_Engineering/2016-17_Q4_Goals#Services
- tl;dr: build an image from tested/merged code suitable for promotion
- Questions
- Labs project -- Deployment-prep mentioned https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Deployment_pipeline/2017-03-21#Next_quarter_cooperation
- Ops Goal: https://www.mediawiki.org/wiki/Wikimedia_Engineering/2016-17_Q4_Goals#Technical_Operations
- DC switch over, prepare for k8s, reduce Swift tech debt, Asia cache
For next time
edit- PoC use of docker registry
- Review current docker image build jenkins agent