Page MenuHomePhabricator

Request to enable XFF headers for test XTools hostnames
Closed, InvalidPublic

Description

Project Name:

xtools

Request:

Enable XFF headers for xtools2.wmcloud.org

Also, I think the old xtools.wmflabs.org can be removed. There's no web proxy in Horizon for it anymore, nor do we have it defined in the Apache config.

Rationale:

I am setting up a new pair of VMs for deploying Anubis as well as upgrading to Debian Bookworm and PHP 8.2. Anubis requires the IP to function. I could spoof it, but it'd be nice to have another hostname for this very purpose of testing new VMs, which happens every other year or so.

Event Timeline

I was interested to write a patch for this, but it seems the instance-puppet repo is hosted on Gerrit but not committed to on Gerrit (?)

I was interested to write a patch for this, but it seems the instance-puppet repo is hosted on Gerrit but not committed to on Gerrit (?)

That git repo is an audit log of the changes made via the Puppet screens in horizon.wikimedia.org. The actual Puppet ENC backend itself does not read data from the git repo.

taavi subscribed.

Is the new proxy meant to be temporary or will it exist permanently?

Is the new proxy meant to be temporary or will it exist permanently?

I'm asking to keep it permanently, if that's okay. It'd be nice to have XFF headers enabled on a test installation for whenever I need to upgrade the VMs again. Before this wasn't an issue as I didn't need to test with XFF headers, but we do now that we use Anubis.

I was expecting this to be an uncontroversial request that would be actioned quickly. If there's any hesitation, we can just decline this. I put a lot of effort into uptime so this was just in the spirit of that. Realistically things should be okay… what makes the prod setup different though is there's an API server. I can make xtools-dev have an API server to accurately replicate that (xtools-dev.wmcloud.org has the XFF headers), but I'm already out of quota on instances! So I guess I can delete the old xtools-dev VM and use that quota for the new API dev server. Then there's no need for xtools2.wmcloud.org.

Finally got back to working on this, and realized I can simply temporarily point xtools-dev.wmcoud.org to the new prod servers and that will allow me to fully replicate the prod setup. Closing as invalid. Apologies for the noise.