Page MenuHomePhabricator

Taavi knowledge transfer: python-flask-keystone, novaproxy, enc api
Closed, ResolvedPublic

Description

Taavi writes:

I look after the Novaproxy and Puppet ENC APIs. They're functionally rather stable, but need regular OS upgrades and tweaks to match library upgrades in newer OS versions. <- Andrew will inherit
** This means I'm the de facto maintainer of the python-flask-keystone package (https://gitlab.wikimedia.org/repos/cloud/deb/python-flask-keystone) that they use for authentication. The libraries were originally written by Rackspace, were Debianized (as Wikimedia-specific debs) by me, and are today logging some deprecation warnings that we'll need to eventually fix to be able to upgrade the hosts these APIs run on.

I'm pretty familiar with the proxy and enc api, but need to learn more about that abandoned package!

Event Timeline

Andrew renamed this task from Taavi knowledge transfer: python-flask-keystone to Taavi knowledge transfer: python-flask-keystone, novaproxy, enc api.Apr 25 2024, 2:44 PM

From a meeting about these services today:

novaproxy api + enc api
+ Added keystone auth
+ Less horizon integration, mostly managed via the api code
+ keystoneauth deprecation wornings, from the flask/keystone integration

  • We might wind up maintainign/hosting the keystone/flask library

Possible future fixes:

  • remove the redis layer
  • suppor arbitrary (non-designate-managed) domains for novaproxy; allow proxy to redirect from/to 'vanity' domains

Novaproxy canonical data is in the cloudinfra dabases; redis is a cache to provide quick response for nginx

I (Andrew) am accepting this task to investigate deprecation warnings in these services and (probably) take over maintenance of python-flask-keystone.