Page MenuHomePhabricator
Create Task
Maniphest T236557

"google-api-proxy" Cloud VPS project jessie deprecation (medium)
Closed, ResolvedPublic
Actions

Description

The end of life of Debian Jessie is approaching in 2020 and we need to move to Debian Buster (or Stretch) before that date.

All instances in the google-api-proxy project need to upgrade as soon as possible. Instances not upgraded by 2019-12-31 may be subject to deletion unless prior arrangements for an extended deadline has been approved by the Cloud VPS administration team.

Remaining Debian Jessie instances (live report):

Listed administrators are:

See also:

More info on current project instances is available via openstack browser

Details

Due Date
Dec 31 2019, 11:59 PM

Related Objects
Search...

Event Timeline

StrikerBot triaged this task as Medium priority.Oct 26 2019, 12:32 AM
StrikerBot created this task.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptOct 26 2019, 12:32 AM
bd808 added a subtask: T233740: google-api-proxy: Move Debian Jessie instances to Buster.Oct 27 2019, 4:29 AM
MusikAnimal merged a task: T233740: google-api-proxy: Move Debian Jessie instances to Buster.Oct 29 2019, 1:18 AM
MusikAnimal added a subscriber: Krenair.

I've merged T233740 here because this one is much more descriptive (thanks StrikerBot :). Copying over bd808's reply, for reference:

In T233740#5524436, bd808 wrote:

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:

  1. Request temporary +1 IP Address quota for the project
  2. Provision a new m1.small instance with Buster as the base image
  3. Attach a public IP to the instance
  4. Apply role::labs::google_api_proxy on that node along with needed Hiera settings
  5. Add the new public IP to the Google account configuration
  6. Verify that the nginx reverse proxy works via curl from the new instance directly
  7. Delete and recreate the https proxies so that they point to the new instance
  8. Verify that the nginx reverse proxy works via the proxy hostnames
  9. Release the public IP from the old instance
  10. Delete the old instance
  11. Release the temporary +1 IP quota bump
  12. Profit!!
MusikAnimal added a project: Community-Tech.Oct 29 2019, 1:19 AM
MusikAnimal moved this task from New & TBD Tickets to Needs Discussion on the Community-Tech board.
MaxSem changed the edit policy from "Custom Policy" to "All Users".Oct 29 2019, 11:23 PM
MusikAnimal added a subscriber: ifried.Oct 29 2019, 11:23 PM
• aezell renamed this task from "google-api-proxy" Cloud VPS project jessie deprecation to "google-api-proxy" Cloud VPS project jessie deprecation (medium).Oct 29 2019, 11:23 PM
• aezell changed the edit policy from "All Users" to "Custom Policy".
ifried moved this task from Needs Discussion to Up Next (May 6-17) on the Community-Tech board.Oct 29 2019, 11:24 PM
• aezell changed the edit policy from "Custom Policy" to "All Users".Oct 29 2019, 11:24 PM
ifried moved this task from Up Next (May 6-17) to Kanban-Q2-2019-20 on the Community-Tech board.Oct 30 2019, 12:03 AM
ifried edited projects, added Community-Tech (Kanban-Q2-2019-20); removed Community-Tech.
MusikAnimal claimed this task.Dec 3 2019, 9:26 PM
MusikAnimal moved this task from Ready to In Development on the Community-Tech (Kanban-Q2-2019-20) board.
bd808 added a comment.Dec 4 2019, 6:06 PM

The Cloud Services team would like to have Debian Jessie systems replaced with Debian Buster (or Stretch if necessary) before 2019-12-31. Please do respond of this task with comments if you know you will not be able to meet that target date or have additional questions about what to do or how to do it. Ideally you will create new instances in your Cloud VPS project, test them, and then migrate any final state data to the new instances before deleting the old Jessie instances. If you need more quota space in your project to create new instances in parallel with your existing instances please create a quota request task describing the increase you need and referencing this deprecation task.

MusikAnimal mentioned this in T239853: Request increased quota for google-api-proxy Cloud VPS project.Dec 4 2019, 6:59 PM
MusikAnimal added a subtask: T239853: Request increased quota for google-api-proxy Cloud VPS project.Dec 4 2019, 9:06 PM
Andrew closed subtask T239853: Request increased quota for google-api-proxy Cloud VPS project as Resolved.Dec 10 2019, 4:05 AM
MusikAnimal reopened subtask T239853: Request increased quota for google-api-proxy Cloud VPS project as Open.Dec 12 2019, 4:56 AM
Andrew closed subtask T239853: Request increased quota for google-api-proxy Cloud VPS project as Resolved.Dec 12 2019, 5:38 AM
MusikAnimal closed this task as Resolved.Dec 12 2019, 8:10 PM
MusikAnimal moved this task from In Development to Done on the Community-Tech (Kanban-Q2-2019-20) board.

All done! The old instance was deleted entirely. Thank you @bd808 for the detailed instructions. I learned a lot from this!

I'm going to go ahead and mark as resolved since there's nothing to test or review.

MusikAnimal mentioned this in T243736: Earwig's Copyvio Detector down due to "The supplied API key is not configured for use from this IP address." from google-api-proxy.Jan 29 2020, 7:16 AM
MusikAnimal added a project: Google-api-proxy.Apr 16 2020, 6:50 PM
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL