See also T87036 - although silver runs trusty and has PHP 5.5 rather than 5.3, we should still migrate it to HHVM.

This ticket makes no sense, IMO. We have no reason to migrate wikitech to HHVM at the moment.

I'm resolving this ticket as invalid until someone explains me why should we embark in such a migration that - at the moment - does not offer any advantage to us.

In T98813#1413617, @Krenair wrote:

It's an absolute blocker for T91590: [Spike] Try out hack (<?hh) for mediawiki-config, T94149: Get rid of Zend 5.5 tests for wmf branches, and perhaps T75901: Drop PHP 5.3 support. If you want to close this, you'll have to reject at least those first two.

In T98813#1278212, @Krenair wrote:

See also T87036 - although silver runs trusty and has PHP 5.5 rather than 5.3, we should still migrate it to HHVM.

It's not a blocker for dropping PHP 5.3 support then if it's on 5.5

This is not a blocker to drop php 5.3, it is not a blocker to drop zend tests (or are we testing OSM? we might keep tests just for it)

Converting silver could be a 5-minutes job or an engineering nightmare requiring weeks to fix OSM to work correctly with HHVM. I strongly suspect the latter.

If we really want to have an HHVM-only release train, we could re-detach wikitech until we drop OSM.

@andrewbogott: thoughts?

I have no idea whether hhvm will interact badly with OSM. It's pretty different from other extensions so it wouldn't shock me. A day long wikitech outage isn't a huge deal since it doesn't prevent actual labs instances from working -- we'd need to schedule it ahead of time though.

If it were detached from the train would I still be able to manually sync-common or would I be back to upgrading it fully by hand?

Added T161553 as a subtask per above comments.

In T98813#3135116, @greg wrote:

Added T161553 as a subtask per above comments.

I removed OSM deprecation as a blocker. I think we can figure out how to work through any issues that OSM has with HHVM. Its mostly LDAP and cURL.

In T98813#3365586, @bd808 wrote:

In T98813#3135116, @greg wrote:

Added T161553 as a subtask per above comments.

I removed OSM deprecation as a blocker. I think we can figure out how to work through any issues that OSM has with HHVM. Its mostly LDAP and cURL.

Does that mean we can Just Do It™ now?

In T98813#3585990, @Jdforrester-WMF wrote:

Does that mean we can Just Do It™ now?

See T168470. Cloud Services has 2 new physical servers that were purchased to replace the aging silver (wikitech) and californium (horizon, striker) hosts. The rough plan is for these new servers to be built out as Debian boxes and setup with all 3 services on each physical node. Then we can balance traffic between them and make maintenance things easier. We should have the luxury of setting these boxes up in parallel with the existing hosts, so in my mind that would be a good time to attempt to run wikitech's weird mix of extensions on HHVM and make sure that the obvious problems get fixed. This work may become a FY17/18 Q2 goal for the team.

Brilliant. :-)

... or not. T176370 Migrate to PHP 7 in WMF production

In T98813#3661663, @Krinkle wrote:

... or not. T176370 Migrate to PHP 7 in WMF production

The broad plan for PHP7 is to move to HHVM on Debian Stretch first and then move from HHVM to PHP7. Getting wikitech running on Stretch+HHVM will put us in a good place to continue on to PHP7 with the rest of the MW servers.