Wikimedia Release Engineering Team/Deployment pipeline/2019-04-11

From MediaWiki.org
Jump to navigation Jump to search

Last Time[edit]

General[edit]

TODOs from last time[edit]

  • N Not done TODO various attack vectors document to start
  • TODO: Joe & James_F to work on eventual 2019-04-01 email
    • Beware: announces on 04/01 can be considered an April's fool [and James is out on 1 April itself. <-- this is an april fool's joke for sure]
    • postponed until there are docs ~2019-05-xx
    • Draft: https://etherpad.wikimedia.org/p/LZKuNSFpM4iKbuHkdPRf
    • Shall we send one soon, more a "hey, what do you think?" e-mail?
    • a preliminary email for people to be able to comment on work so far and how that jives with their needs
    • wikitech-l, engineering-l, services@lists.wm.org
    • what is the call to action?
      • Is there documentation you expect to see?
      • Poke around this project?
    • Overview
    • Who cares about this email?

To do To do send email about email

RelEng[edit]

 build  run  publish  deploy

    • each stage step exports binding with the results of a step, subsequent steps can access ancestor bindings
    • Mulitple images with multiple charts with a single repo
    • config.yaml: orchestrating steps for CI
      • can specify different blubber configs to different services
      • refers to blubber variants internally
    • blubber.yaml: creates build manifests
    • Timelines: start experimenting possibly next week
    • experiment with ORES possibly(?) since they need this functionality
    • Might use for restbase possibly
    • MCS split into MCS / PCS (?)

Serviceops[edit]

  • Yes Done cxserver training. Deployment done today
  • ongoing Upgrades to infrastructure ongoing, kubernetes 1.12.7 next week
  • started Started work on kask+wikidata termbox SSR
  • ongoing Need to resume work on changeprop
  • started A tech talk proposal (late june per organizers' request)

Services[edit]

  • ChangeProp is ready to go.
  • RB split is coming
  • MCS/PCS are eager to move to node10. Maybe for Q1?

As Always[edit]