Comment 1 for bug 631778

On Tue, Sep 7, 2010 at 5:34 AM, Stuart Metcalfe
<email address hidden> wrote:
> Public bug reported:
>
> As part of https://dev.launchpad.net/LEP/OpenIdRoadmap
>
> We currently replicate several tables from LP to support our teams
> implementation.  We should be able to use the LP API for this.  A few
> considerations:
>
>  * Some sites depend on the high availability of teams information and would be intolerant of LP downtime.

We're working on downtime - I consider reducing / eliminating downtime
a critical component in reducing the cost of launchpad development. In
the short term DB schema changes will still require downtime but we
hope to eliminate all other causes of downtime by christmas.

>  * LP doesn't expose an immutable user identifier so would things get a bit sticky if the user changed their email *and* username?

We should be able to do what SSO did for this - please file a new bug?

>  * Using the LP API could incur longer load times on SSO.

Thats true; I am thinking about organising a dedicated APIs server
cluster (just partitioning off some of the appservers for APIs) so
that APIs are not affected (positively or negatively) by load spikes
on the web cluster. This might help mitigate SSO concerns. We could,
of course, do a dedicated FE cluster for SSO but I don't think that
that would be needed. We're also driving our response times down very
successfully at the moment, but we can and should put the specific
API's you need into a nagio alert.

>  * We'd need a user-friendly and unobtrusive method of attaching your LP account to your SSO account.

Definitely; worthy of a new bug perhaps? We should prepopulate this as
part of the migration, no need for existing users to have to take
manual action.

-Rob