As we deprecate account and ssh management in wikitech in favor of bitu, we need an equivalent for management in codfw1dev.
@SLyngshede-WMF thinks that this will be straightforward, we just have to find a place to install it.
As we deprecate account and ssh management in wikitech in favor of bitu, we need an equivalent for management in codfw1dev.
@SLyngshede-WMF thinks that this will be straightforward, we just have to find a place to install it.
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
P:trafficserver::backend remove CloudIDM. | operations/puppet | production | +0 -5 |
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Open | None | T189531 All Wikimedia developer services should use single sign-on | |||
Resolved | None | T161859 Make Wikitech an SUL wiki | |||
Open | SLyngshede-WMF | T360795 Set up a bitu instance for codfw1dev | |||
Open | SLyngshede-WMF | T362128 Site: 1 VM for codfw1dev bitu deployment | |||
Resolved | ABran-WMF | T362619 Database request for Bitu Cloud DEV installation | |||
Resolved | SLyngshede-WMF | T376871 Decommission cloudidm2001-dev |
Management of the LDAP directory used in the codfw1dev OpenStack deployment. This is the "staging cluster" for WMCS OpenStack changes. It uses a project local LDAP directory that has historically been managed with https://labtestwikitech.wikimedia.org, but as Bitu replaces Wikitech's Developer account LDAP management features we need an equivalent replacement in the staging cluster.
Just to ensure that everyone agrees on what we need. This will be one Ganeti VM, running Bitu, and an LDAP instance.
Do we need to have do a data migration from the old setup?
The labtest LDAP currently runs on cloudservices2004/2005-dev. I think we have two options: Either a separate Ganeti VM for the labtest/Bitu instance or we simply install it on cloudservices2004/2005, given that Bitu can simply be installed via a deb and only pulls in some moderate dependencies.
I'd prefer that it go on its own ganeti VM, as I'm trying to pare down on the total number if weird things that run on cloudservices.
Fair enough. Do you have any preference on the name? cloudidm2001.codfw.wmnet, e.g.?
idm2001-dev.codfw.wmnet (or, possibly, cloudidm2001-dev.codfw.wmnet) is consistent with naming elsewhere. The attached subtask (T362128) has more details.
@Andrew Sorry, this is still pending. I need to figure out what to do about the Redis dependency. The correct solution would be to build a Redis container, but that's yet another thing to maintain, so I'll see if I can make it work without it.
FWIW, getting this deployed simplifies a lot of database stack see T328289: update labtestwiki user and password for example.
Change #1078895 had a related patch set uploaded (by Slyngshede; author: Slyngshede):
[operations/puppet@production] P:trafficserver::backend remove CloudIDM.
Change #1078895 merged by Slyngshede:
[operations/puppet@production] P:trafficserver::backend remove CloudIDM.