Wikimedia Release Engineering Team/Deployment pipeline/2018-08-30

Last Time

 * 2018-08-02

General

 * Mathoid /deploy repo
 * Still needed?
 * Remove from CI?
 * TODO: archive on gerrit, remove from CI

RelEng

 * Update Debian package of Blubber (0.5.0-1)
 * Reminder (or maybe this is the first meeting since this happened :)): Blubber is on gerrit now: https://gerrit.wikimedia.org/g/blubber
 * debian/0.5.0-1 has been tagged, package builds after some config changes following gerrit move
 * Needed for Graphoid patches


 * .pipeline is the correct directory for {blubber,helm}.yaml now
 * Update for Mathoid https://gerrit.wikimedia.org/r/#/c/mediawiki/services/mathoid/+/454295/


 * Graphoid
 * Has a task Move Graphoid to Kubernetes via the deployment pipeline
 * Blocked on new Blubber release
 * https://integration.wikimedia.org/ci/blue/organizations/jenkins/service-pipeline-test-only/detail/service-pipeline-test-only/60/pipeline


 * Would it be crazy to run Blubberoid in k8s?
 * Landed in master
 * Not a lot of need for logging, most errors are 400s
 * Uses built-in golang http server
 * Eases packaging need
 * Pros
 * No need to maintain package in WMF
 * Knowing CI talks to latest and greatest
 * Easier deployments
 * Cons
 * Outside the WMF still need package
 * Services in k8s need /_info && ?spec for a swagger spec -- probably doable, but may not be worth it
 * Health endpoint and Swagger spec
 * How will this be built? Currently has a .pipeline/blubber.yaml -> can use FROM scratch -- blubber can build itself


 * Q2
 * Additional Services
 * How many?
 * Which ones? https://phabricator.wikimedia.org/T198901


 * Deployment
 * Can other folks besides Alexandros deploy currently?
 * Do we want to have this part of the pipeline?
 * Pushing live to staging
 * Additional Scap/Helm work?


 * Local Development
 * This has been left behind
 * Next quarter/future quarters?

SREs

 * Zotero V2 in 2-3 months in production ?
 * Node 8 service
 * Want to move to Node 10
 * Could use pipeline
 * Concerns
 * How will helm test work without swagger specs?
 * How does tagging work?
 * Currently uses a date-based tag
 * We could respond to tag pushes to gerrit
 * Needs a blubber.yaml (obvs)
 * Repo: https://github.com/zotero/translation-server-v2
 * Task: https://phabricator.wikimedia.org/T197242

Services
= As Always =
 * Release Pipeline Workboard
 * Meeting notes