Open Stack

On Tue, Sep 24, 2013 at 3:18 PM, Stefano Maffulli <stefano at openstack.org> wrote:
> On Tue 24 Sep 2013 03:04:32 PM PDT, Robert Collins wrote:
>> Indeed! Please please please *do not* stand up yet another
>> password-hosting site. Utter waste of everyone's time.
>
> I agree with you: we don't nee more complexity. Having our own OpenID
> provider is needed in order to *reduce* complexity. Remember that the
> Foundation already has to have *one* system to manage the identity of
> Foundations' individual members. All ATCs also need to be members of the
> Foundation, so at the moment all new contributors need to create two
> accounts: one on Launchpad and one on http://openstack.org/profile. That
> sucks.
>
> Since we're using Launchpad for less and less functions nowadays, it
> makes sense to use *one* ID providing system and have such system be
> built on top of the Foundation members database.
>
> On 09/24/2013 02:39 PM, Mark Atwood wrote:
>> If we do stand up an OpenStack.org identity provider, will it also
>> support such an API, and support 2FA, and the various new identity and
>> metadata APIs that have been and are being published?
>
> We're still in the initial phases of the project so there is plenty of
> room to make suggestions. The reason of my original question is to have
> a full understanding of what systems are currently consuming Launchpad
> ID and make sure that whatever system we pick doesn't break them and
> eventually leaves space for improvements.
>
> Going back to the original question: anybody has items to add to the list?
>
Our Jenkins masters
(jenkins|jenkins01|jenkins02|jenkins-dev).openstack.org use LP OpenID
for auth. Also, review-dev.openstack.org (the -dev servers should be
covered by their non dev counterparts).

Clark