Page MenuHomePhabricator

Developer account creation without OpenStackManager
Open, Stalled, HighPublic

Description

When an account is created on Wikitech, that account gets a 'shell name' in addition to other account attributes. I'm pretty sure this happens via a hook in OpenStackManager; we need a way to create that fully-featured account in the post-OSM world.

Event Timeline

Andrew created this task.Jun 1 2018, 3:46 PM
Andrew added a comment.Jun 1 2018, 4:17 PM

... I suppose another option is to leave OpenStackManager in place but unused apart for user creation, until we make wikitech SUL and move all developer account creation to Striker.

Harej added a subscriber: Harej.Jun 20 2018, 3:57 AM

Doesn't Striker support doing this? We could just take the account creation logic out of Striker and have people create accounts that way.

Dzahn removed a subscriber: Dzahn.Jun 20 2018, 7:30 AM
bd808 added a comment.Jun 20 2018, 4:49 PM

Doesn't Striker support doing this? We could just take the account creation logic out of Striker and have people create accounts that way.

Yes, that solution is described in T179463: Create a single application to provision and manage developer (LDAP) accounts. Doing this would mean developing a new Django based application, getting it through security review, and getting it deployed followed by some amount of support for fixing bugs once it is rolled out. Not impossible at all, but not a trivial amount of work either. It is my preferred long term solution, but it would be nice to find a way to keep that from blocking the removal of MediaWiki-extensions-OpenStackManager from wikitech which is the main blocker to hosting wikitech in the main wiki cluster.

This sounds hacky, but until we provision a new identity management application, couldn't we just tell people to sign up via Striker?

bd808 added a comment.Jun 21 2018, 5:32 PM

This sounds hacky, but until we provision a new identity management application, couldn't we just tell people to sign up via Striker?

Yes, that would be possible. It would not be too difficult to make some mostly cosmetic changes to the workflow there as well to make that a bit less confusing. The most efficient thing to do by time and effort would be to combine the developer account and Toolforge use-cases into a single tool (Striker). In the longer term however that may be working counter to other goals (e.g. streamlining the Toolforge on-boarding process).

When I started planning Striker my intent was to hide as many of the "power user" use-cases as I could so that the experience of joining and using Toolforge was as simple and direct as possible. The assumption was that a typical new Tool maintainer does not care about VPS instances, Gerrit, or even Phabricator; they care about deploying a webservice or bot to help on their home wiki. I still generally believe this, so I'm hesitant to "temporarily" move in the other direction because I know that once the pressure is off we are less likely to build the better solution (T179463).

Vvjjkkii renamed this task from Developer account creation without OpenStackManager to 4tbaaaaaaa.Jul 1 2018, 1:06 AM
Vvjjkkii triaged this task as High priority.
Vvjjkkii updated the task description. (Show Details)
TerraCodes renamed this task from 4tbaaaaaaa to Developer account creation without OpenStackManager.Jul 1 2018, 12:58 PM
TerraCodes raised the priority of this task from High to Needs Triage.
TerraCodes updated the task description. (Show Details)
Harej removed a subscriber: Harej.Feb 10 2020, 11:37 PM
Bstorm changed the task status from Open to Stalled.Feb 11 2020, 5:16 PM
Bstorm triaged this task as High priority.
Bstorm added a subscriber: Bstorm.

Waiting on SSO stuff