| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | hashar | T60772 common gating job for mediawiki core and extensions | |||
| Resolved | hashar | T69216 Have unit tests of all wmf deployed extensions pass when installed together, in both PHP-Zend and HHVM (tracking) | |||
| Invalid | Ryasmeen | T90647 Create Jenkins builds for Editing across repositories (MobileFrontend, VisualEditor etc) | |||
| Declined | None | T50407 Jenkins: Setup Vagrant for some jobs (tracking) | |||
| Declined | None | T45266 Write and implement tests for Wikimedia's Apache configuration (redirects.conf, etc.) | |||
| Resolved | hashar | T47499 [EPIC] Run CI jobs in disposable VMs | |||
| Declined | None | T86168 Isolate contintcloud nova project from the rest of the wmflabs cloud | |||
| Declined | • chasemp | T85611 Neutron networking, with IPv6 at eqiad | |||
| Declined | coren | T85610 Distributing tools, deployment-prep to both data centers (availability/redundancy) | |||
| Declined | None | T85609 Labs available in the new data centre (with Neutron/IPv6) | |||
| Resolved | coren | T85605 Set storage service up in codfw |
Event Timeline
Currently, the bigger stumbling block is the architecture of networking with Neutron, which does not support the model we currently use (single, flat, uniform network with DHCP)
We've deprioritized this, and it's no longer a quarterly goal for Ops. There appears to be very little demand for having Labs available in codfw at this time, and even some requests NOT to have it due to added complexity. Also because we're not able to deploy with Neutron yet, we'd have to go with Nova-Network again, and enforce yet another migration for our users later on.
We might still setup a (small) Labs cluster in codfw for very limited (internal?) purposes though. Also, we will continue to have our backup storage in codfw as well.
With T85610 also being declined I'm going to say any work towards this end is a ways off and will be tracked in other tasks