@SLyngshede-WMF, how is bitu currently deployed? Ganeti, k8s, somewhere else?

Bitu is currently installed as a .deb package on two Ganeti hosts.

What is the intended use case here? We already have a staging instance for Bitu

In T360795#9704885, @MoritzMuehlenhoff wrote:

What is the intended use case here? We already have a staging instance for Bitu

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.

Ah, right. Forgot about the local LDAP data base on it.

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.

In T360795#9707776, @Andrew wrote:

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.?

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.