Availability¶
Status¶
Status: Limited peer review
TDA Precedence¶
TDA Submission | Relationship |
---|---|
67 Digital Admissions | Influenced by |
75 Activate Account | Used in answers and approved (version 0.1.0) |
NFRs¶
NFRs | Relationship |
---|---|
NFR.001 | Potentially Answers |
NFR.002 | Potentially Answers |
NFR.027 | Potentially Answers |
NFR.053 | Partially Answers |
NFR.055 | Potentially Answers |
NFR.081 | Potentially Answers |
NFR.071 | Potentially Answers |
NFR.057 | Partially Answers |
Means to achieve¶
1 - UIS Terraform Modules and Boilerplate¶
The web service is expected to be available 24/7 under normal circumstances.
Exceptions to this include:
- automatic managed service updates outside of normal working hours
- major database version changes that may require manual updates during work hours approximately every 2-3 years.
The service is self-healing. The service is tolerant to network failures and uses components that are HA, unless they do not effect direct delivery of the service. The service is tolerant to cloud zone failures (e.g. switch, power system, etc.) and is multi-zonal. See https://cloud.google.com/compute/docs/regions-zones.
Backups are performed daily. Backups can be used to recover state to datastores in the event of ransomware attack from before the point off attack. See Data Backup Service.
DevOps change practices are followed: https://docs.google.com/document/d/1tGIYU-11l7G7byz1IZw-mhDHjJMPRnS_rIrAX5esyTM/edit?usp=sharing.
For public domains a service uptime check is included.
Compliance Requirements¶
- For HTTP use, Cloud Run Terraform Module
- Cloud SQL via Boilerplate Google Cloud
Deployment
- Cloud SQL settings should be unchanged.
- For asynchronous tasks use the ucam-faas library, docker base image and terraform module
- Other Google managed services with maintenance windows should match Boilerplate SQL windows and use a HA option