T274666: Add keystone auth middleware to the puppet enc api needs a newer version of keystone middeware than what is on stretch or buster. Upgrading the current stretch instances to bullseye seems the best option to me.
Description
Details
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | taavi | T295246 Dynamicproxy API should be useful without the Horizon dashboard | |||
Resolved | taavi | T295234 Add keystone auth for dynamicproxy api | |||
Resolved | taavi | T295235 Update project-proxy proxies to Debian Bullseye | |||
Resolved | taavi | T295245 Request increased quota for project-proxy Cloud VPS project |
Event Timeline
Change 737173 had a related patch set uploaded (by Majavah; author: Majavah):
[operations/puppet@production] dynamicproxy: Drop python 2 redis client
Change 737173 merged by Andrew Bogott:
[operations/puppet@production] dynamicproxy: Drop python 2 redis client
Mentioned in SAL (#wikimedia-cloud) [2021-11-09T10:52:13Z] <majavah> create new pair of proxies on bullseye T295235
Change 737653 had a related patch set uploaded (by Majavah; author: Majavah):
[operations/puppet@production] hieradata: add new project-proxies
Change 737653 merged by Andrew Bogott:
[operations/puppet@production] hieradata: add new project-proxies
Mentioned in SAL (#wikimedia-cloud) [2021-11-11T13:21:13Z] <majavah> failing over to proxy-03 T295235
Traffic is now flowing through proxy-03. I shut down the old instances, since they can't replica from the newer redis server in 03 they are not worth keeping around as backup instances I think.