Wikimedia Release Engineering Team/Checkin archive/20150317

2015-03-17

Team Business

• split the team/meetings up? (moved to end of meeting)
  • The team overall likes being informed of all others activities.
  • Peoplel can always set their own meetings to go deeper in details.
  • Our team is slightly different than features, so one per week meeting is just fine.
• RelEng/QA things at the Hackathon
  • https://phabricator.wikimedia.org/T92565
  • Antoine has no clues / too many to pick :(

Escalation

• LocalizationUpdate issues:
  • https://phabricator.wikimedia.org/T92721
  • https://phabricator.wikimedia.org/T92823
• Chad / Mukunda will look at it

Team Quarterly Goals

https://phabricator.wikimedia.org/maniphest/query/O9isnUt5IGLP/#R

Scrum of Scrums

https://phabricator.wikimedia.org/project/board/64/

Blocked on us: https://phabricator.wikimedia.org/maniphest/?statuses=open%2Cstalled&allProjects=PHID-PROJ-arpazvuktn2l647rb6us#R

Beta Cluster stability

https://phabricator.wikimedia.org/project/board/497/?order=priority

Quarterly Priority: Green nightly builds on staging: https://phabricator.wikimedia.org/T88701

Quarterly Priority: Stable uptime metrics of the Staging cluster: https://phabricator.wikimedia.org/T88705

• groundwork done mostly: ENC, Autosigner, autopuppetmaster, tin and palladium are functional
• Chad has ES patch (I think) Tyler has MX patch for operations puppet
• Next steps--think it's time to move on to apps

Test history

Quarterly Priority: By team test history: https://phabricator.wikimedia.org/T88706

Slamed by MW-V things last week.

Isolated CI instances

https://phabricator.wikimedia.org/tag/continuous-integration/board/?order=priority

Quarterly Priority: Disposable VMs - https://phabricator.wikimedia.org/T47499

Ops responds with a question: How many VMs, and what other hardware will this require?

Roughly 10 at start, then ~ 50 which is the number of executors we have on current Jenkins. The pool size will depends on the speed to spawn a new instance and replenish the pool being consumed.

The idea is to start with a few projects (ex: releng repos), then extend to the rest progressively starting end of June.

10 is not a problem, but for 50 we'll need to allocate new virt hardware.

Some ops (_joe_, specifically) want to discuss using chroots instead. Andrew is struggling to get someone to respond to Antoine directly.

We had exchanges last summer about isolation. chroots can be escaped, lxc/docker needs some additional isolation work. kvm is isolated out of the box and using openstack as a provider let us reuse the NodePool software already written. Though ideally we would use OpenStack + LXC to speed up the vm spawning.

• Zuul package ready for precise and trusty
  • need a review by an opsen (fillipo/godog)
  • Antoine to contact fillipo
• Antoine to create procurment ticket
  • This is the next big timesink/blocker
  • Might need servers to be physically moved between racks.
• Antoine to loopback with Andrew B / Yuvi to present the arch and more or less validate it.

MediaWiki Releases

Quarterly Priority: Release MediaWiki 1.25: https://phabricator.wikimedia.org/T88709

Other Work

• MW-Vagrant
  • reimplementation of role settings to allow _incremental_ and pre-provision changes https://phabricator.wikimedia.org/T92549
  • refactoring to better accommodate MW services (clone into the right places, etc.)
    • https://phabricator.wikimedia.org/T89919
    • https://phabricator.wikimedia.org/T92311

Vacations/Confs/etc

• Dan in France the week before offsite (May 11-15)
• Week before hackathon: Team offsite in France - https://phabricator.wikimedia.org/T89036
• May: Hackathon in Lyon, France
• Chad vacation after offsite (maybe, dubious now)
• Elena on vacation May26-June07
• Antoine: observing french holidays: Mon April 6th, Fri May 1, Fri May 8, Thurs May 14