Define Escalation Paths for Incidents

[rhiananthony]

Ops Lead needed from each service:
-[] ingestion
-[] upload
-[] data store
-[] secondary analysis
-[] orange box
-[] logging

We should also schedule an operations team meeting. Continued improvement tracking/planning

[sampierson]

@kozbo said: @sam Pierson Jodi, Matt, Mallory, Rhian and I have been working on a doc to describe the escalation path, which we are turning into an RFC. We are hoping to submit it by the end of the week.

[kozbo]

Document in progress is here: https://docs.google.com/document/d/1urMBYYi0_I8LNd8BwtuCBZguN7t_OdayHw7k2wQ_NrA/edit?usp=sharing

[stahiri]

@kozbo can you confirm whether or not this work is complete? In the meantime, I'm removing the tag for GA release as this will need to be updated.

Also, from chatting with a few folks I believe this is meant to address user issues rather than security incidents, so this ticket will need a new owner. This has been added to the TechArch agenda.

[kozbo]

Correct, this is meant for user issues not security incidents. The RFC is stuck waiting for oversight to decide how to structure the funding. Groups will not sign off on thew RFC unless it will be funded.

Here is the RFC: HumanCellAtlas/dcp-community#72

[kozbo]

Assuming that this ticket is only about tracking user issues and not security incidents, I am closing this ticket. As noted above the work for how we will track user issues is being tracked in a separate repo.