Debian Jessie is reaching its End Of Life. We need to create a new instance for the google-api-proxy that runs on Buster, and delete the old one running on Jessie.
More information at https://wikitech.wikimedia.org/wiki/News/Jessie_deprecation
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Invalid | None | T197804 Puppet: forbid new Python2 code | |||
| Open | None | T218426 Upgrade various Cloud VPS Python 2 scripts to Python 3 | |||
| Resolved | BUG REPORT | • Bstorm | T218423 Add python 3 packages to openstack::clientpackages::common | ||
| Resolved | MoritzMuehlenhoff | T232677 Remove support for Debian Jessie in Cloud Services | |||
| Resolved | MusikAnimal | T236557 "google-api-proxy" Cloud VPS project jessie deprecation (medium) | |||
| Duplicate | None | T233740 google-api-proxy: Move Debian Jessie instances to Buster |
Event Timeline
Comment Actions
@bd808 With your help, Community Tech created this way back when T136862: Create project Google-api-proxy. I don't think any of us know how to set it up from scratch, though. Could you assist? :)
Comment Actions
@MusikAnimal There is a bit of documentation at https://wikitech.wikimedia.org/wiki/Nova_Resource:Google-api-proxy. There is a puppet role that does the setup of a proxy instance.
If I was going to be the person doing this work I think I would:
- Request temporary +1 IP Address quota for the project
- Provision a new m1.small instance with Buster as the base image
- Attach a public IP to the instance
- Apply role::labs::google_api_proxy on that node along with needed Hiera settings
- Add the new public IP to the Google account configuration
- Verify that the nginx reverse proxy works via curl from the new instance directly
- Delete and recreate the https proxies so that they point to the new instance
- Verify that the nginx reverse proxy works via the proxy hostnames
- Release the public IP from the old instance
- Delete the old instance
- Release the temporary +1 IP quota bump
- Profit!!