Wikimedia Release Engineering Team/Checkin archive/20150505
2015-05-05
editTeam Business
edit- Annual review time! Get your nominations for coworker feedback in
- "weekly" triage meetings?
- team happy about the idea. Have to make it happens now
Team Quarterly Goals
edithttps://phabricator.wikimedia.org/maniphest/query/O9isnUt5IGLP/#R
Scrum of Scrums
edit- https://phabricator.wikimedia.org/project/board/64/
- Blocked on us: https://phabricator.wikimedia.org/maniphest/?statuses=open%2Cstalled&allProjects=PHID-PROJ-arpazvuktn2l647rb6us#R
Setup new wikis in Beta Cluster for Content Translation https://phabricator.wikimedia.org/T90683
- Doc updated https://wikitech.wikimedia.org/wiki/Nova_Resource:Deployment-prep/Add_a_wiki
- TODO harmonize beta and prod docs
- reorder steps in doc
- Jenkins could probably read the list of db to upgrade from the dblist.
Deployment Cabal
edit- There is no cabal.
- https://lists.wikimedia.org/mailman/listinfo/deployment-systems
Test history
edit- Quarterly Priority: By team test history: https://phabricator.wikimedia.org/T88706
Isolated CI instances
edit- https://phabricator.wikimedia.org/tag/continuous-integration/board/?order=priority
- Quarterly Priority: Disposable VMs - https://phabricator.wikimedia.org/T47499
Image building Antoine: attempted to build base images using Trusty image + operations/puppet.git to include the class we need. That is not pretty.
Images are currently build on a labs instance and context copied from it to the image being build. That is an egg and chicken problem to properly bootstrap an image from scratch.
Vagrant more or less works: https://github.com/hashar/vagrantwmflabs/ --> puppet overrides bunch of root files such as sudo / pam / ssh / resolv.conf
With vmbuilder (which we currently use for Ubuntu images), inject a puppet run when image is created --> https://gerrit.wikimedia.org/r/#/c/208939/1/modules/labs_vmbuilder/files/postinst.sh,unified
- facter does not work because of lack of /proc :]
Splitting Jenkins
Currently used for:
- CI tests
- browser tests
- deployments on beta (and later prod deployment?) ex: https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin
Currently we have bad interactions between various plugins. Thus functionalities could/should be split.
CI will get rid of Jenkins at one point. Might be used as a high level wrapper on top of scap/git-deploy/new deployment system (or just use something else).
OpenStack puppetized Jenkins https://phabricator.wikimedia.org/T95049 make it easier to spawn multiple instances. Zuul can be attached multiple Jenkins so no change on Gerrit/Zuul side.
Antoine to poke engineering and wikitech-l (when there's a plan) list about it.
MediaWiki Releases
edit- Quarterly Priority: Release MediaWiki 1.25: https://phabricator.wikimedia.org/T88709
- 27 open tasks. Please take one :)
- Definitely going to sprint at hackathon
- beta1 coming this week. Starting the process today.
Phabricator
edit- Kevin Smith as part time product manager
- upgrade tomorrow
Other Work
editHiring
edit- Automation Engineer: https://boards.greenhouse.io/wikimedia/jobs/62416
- (short link grnh.se/gj5op4)
Vacations/Confs/etc
edit- Antoine: observing french holidays: Fri May 7-8, Thurs May 14
- Dan in France the week before offsite (May 11-15, leaving evening of Thursday May 7)
- Week before hackathon: Team offsite in France - https://phabricator.wikimedia.org/T89036
- May: Hackathon in Lyon, France
- Chad vacation after offsite/hackathon (through 5/31)
- Andrew Bogott: May 8, May 20-26, hackathon &c., July 18-27, mostly unreachable