Creating a new php70 webservice docker image looks relatively straightforward, except we need a base wikimedia-stretch image first. I'll make that a subtask.

Would love to upgrade some of my Toolforge tools from the Kubernetes PHP 5.6 image to an image with PHP 7.

What sort of priority does tis have from the cloud services team?
I'd love to see it get done and it seems to be getting more and more support from people

Is there anything we can do to help?

In T195689#4438900, @bd808 wrote:

In T195689#4426490, @Addshore wrote:

What sort of priority does tis have from the cloud services team?

Unfortunately the priority for this is low relative to the projects we are actively working on:

• OpenStack software defined network migration to Neutron
• Ubuntu Trusty deprecation
• ToolsDB/Postgres server replacement

The team is currently operating at 3/5th normal capacity while we replace team members who have moved on to other organizations/teams. Hiring is a priority for myself as the team manager and combined with my other duties has made individual contributions such as working on non-trivial upgrade projects like this unlikely.

That's cool :) @Legoktm & I are gonna try and make this happen! :)

In T195689#4442833, @Addshore wrote:

That's cool :) @Legoktm & I are gonna try and make this happen! :)

• T200124: Nomination of Legoktm for Toolforge admin role
• T200125: Nomination of Addshore for Toolforge admin role

I think at some point I forgot that we are a community and not a closed project that can only depend on a dedicated team. Let's try a first step to change that wrong thinking and see where we can go together.

In T195689#4442919, @bd808 wrote:

I think at some point I forgot that we are a community and not a closed project that can only depend on a dedicated team.

If only everyone knew this :)

Based on discussions at Wikimania between @bd808, @Addshore, and myself, we're going to work on T188318: Support PHP 7.2 webservices on Toolforge Kubernetes cluster first. If that goes well, we'll just skip 7.0 entirely (and decline this task).

Given that 7.0 becomes unsupported in 4 months, skipping it and going 7.2 sounds like a good idea.

Now with the php72 container images and Toolforge moving to Stretch with PHP 7.2, this is done, right?

I'd say so, yes! It seems on the sub task @bd808 is also working on making it the default. I don't know if that's meant to be part of it, but I'll leave it open for now.

In T195689#5045135, @GTirloni wrote:

Now with the php72 container images and Toolforge moving to Stretch with PHP 7.2, this is done, right?

Mostly! PHP 7.2 is on both the Kubernetes cluster and the Stretch job grid. The remaining work is to make php7.2 the default (rather than PHP 5.6) for Kubernetes webservices. Then at some point I guess a follow up to deprecated php5.6 and remove that container, but that is probably something to go with T213641: Design mechanism and process for upgrading Kubernetes container runtimes.