OpenShift.io registration queuing

[qodfathr]

Although OpenShift.io needs to scale (#2028) , there may be times when the number of new registrations per unit time is dramatically increased (e.g. after a press announcement, during a presentation at a public event, a viral tweet, etc.). As such, the elastic capacity of OpenShift.io may occasionally face temporary challenges in meeting customer need.

Typical flow when the service has capacity/registration rates are low

Normally, when a user registers, they should be granted access to OpenShift.io effectively instantly. (Once the overall registration process is complete, which may require email verification.) A welcome email may be sent to the user, but it should not be necessary for the user to open that email in order to log in.

In essence, the user should be able to register and log in as part of a single, easy flow. If the user already has an RHD account, they would simply need to register for OpenShift.io, logging in with their existing RHD credentials, potentially need to accept some additional Ts&Cs, and then immediately access OpenShift.io. Understandably, it may take a few minutes for all of the necessary tenant services to be deployed and operational.

Flow when service has a capacity issue/registrations rates are high

When a lot of registrations occur at a similar time, the registration system should start queueing registrations in FIFO order. When getting to the point in time of logging into OpenShift.io, the user should be shown information letting them know that their environment is being created. This should include information regarding the user's place in the queue and/or estimated time.

If this user is on this screen once they are processed in the queue, they should be auto-redirected to the initial login experience of OpenShift.io.

Any user who was queued for more than 2 minutes should receive an email once they are provisioned letting them know that their account is ready for use.

If a user revisits OpenShift.io and logs in while still in the queue, they should have the same experience of seeing exactly where in the queue they are and/or estimated time until their account is ready.

Parent Fundamental

#2015 OpenShift.io registration and on-boarding process is Pleasant and Inviting

[alexeykazakov]

cc: @luciddreamz

[stevengutz]

Where are we on this? I notice that the scenario it's attached to hasn't progressed.

[joshuawilson]

Looks like it is waiting on UXD. cc @catrobson

[catrobson]

Thanks @joshuawilson @stevengutz - I don't think I recognized this was tagged as a Heather goal. We'll start working on flow & screens for this immediately.

[catrobson]

Completed flow can be found here: https://redhat.invisionapp.com/share/PYG7IRFXZQD
Screen designs for OpenShift.io website are still being reviewed and finalized before implementation.