Story Description

This ticket documents the definition of done for our first production environment.

Helpful Context, Background

We are going to be opening up Sid for the first time in production on Oct 30th 2019.

Turn on the Production Environment

End User Documentation Hosting

[x] Pick a methodology, preferably free, for hosting our end-user facing documenation.
[X] run it by Danny/Phil to make sure we're following dataverses' lead on how we do documentation.
the guidelines we have thus far are that it must be something using a markdown language and it must be checked into version control)
This decision will impact our other projects (e.g. Heroku) Covererd here:
Epic: document several common user operations to establish initial user facing documentation hmdc/sid#817
Capture the process for creating documentation (worked out in hmdc/sid#705) into a Sid wiki operations page hmdc/sid#832 (part of Epic hmdc/sid#817)

End User Documentation

[X] Create a public facing document that captures the definition of what's in 1.0
- Include items are documented internally in the G1.0 definition of done project.
Include policies and policy enforcement rules Answer:
Sid G1.0 Value slides

Resource Enforcement

[X] Define a process for monitoring and notification of resource out of policy resources. What will we look at? How often? will it alarm? who will monitor it? What will we do to respond to resource over utilization?
include this either in or referenced by the G1.0 definition of done project Answer:
This is not a one and done process. And will not be close to finished at 1.0 For the latest updates search on the following labels: logging-and-monitoring, metrics, ResourcesQuatasBilling Example:
Show a count of jobs in DataDog hmdc/sid#792

Auto-scaling

[ ] Configure enough total resources allocated to allow the environment to automatically grow to support up to 100 jobs (1CPU/4GB each)
- The PR https://github.com/hmdc/sid-tf/pull/26 which set up the ASG creates a max of 7 m5a.xlarge nodes which each can fit 3 jobs, plus 3 m5a.large nodes which each can fit 1 job, for a total of 24 jobs
- The PR https://github.com/hmdc/sid-tf/pull/28 will amend this to a max of 33 m5a.xlarge nodes which each can fit 3 jobs, plus 3 m5a.large nodes which each can fit 1 job, for a total of 102 jobs

AAA

End User Support

[ ] Get guidance and buy-in from Soner on this section
[ ] Define a New User Onboarding process (See hmdc/sid#505 for a start )
[ ] Define a User lifecycle process
[ ] Define how we are going to interact and gather usability and feedback information from early adopters.
The first thought here is to use slack Sid-users. Phil mentioned that dataverse has a way that they do this. The Sid team does not
- pre-requisites, gotchas, how-tos, FAQs
[ ] User suport process
- We are going to have to capture many things for documentation around use of the environment.
[ ] git-book
[ ] no forum

For a follow-on release

Related To:

See Also: make Production stage hmdc/sid#240
See Also: Increase CPU & memory allowed in Sid Production Environment to 4CPU X 16GB RAM hmdc/sid#837 ... Updated from gitHub State:open Labels: URL:https://github.com/hmdc/sid-Planning-Board/issues/83 Repo: Event:renamed ... Updated from ZenKit 11/15/19 04:26PM Stage Label: Idea Type Label: Context Label: Item link: https://zenkit.com/i/rgEZtexav/9qGtMTK6F Collection Link: https://zenkit.com/c/rgEZtexav URL: URL2: ... Updated from gitHub State:open Labels: URL:https://github.com/hmdc/sid-Planning-Board/issues/83 Repo: Event:renamed ... Updated from ZenKit 11/15/19 04:28PM Stage Label: Idea Type Label: Context Label: Item link: https://zenkit.com/i/rgEZtexav/aIuFOJcng Collection Link: https://zenkit.com/c/rgEZtexav URL: URL2: ... Updated from gitHub State:open Labels: URL:https://github.com/hmdc/sid-Planning-Board/issues/83 Repo: Event:added_to_project ... Updated from ZenKit 11/15/19 04:45PM Stage Label: Idea Type Label: Context Label: Item link: https://zenkit.com/i/rgEZtexav/aIuFOJcng Collection Link: https://zenkit.com/c/rgEZtexav URL: URL2: