-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
155 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,38 @@ | ||
# These settings determine the behaviour of runbook.md's Runbook Validator bot | ||
# https://github.com/financial-times/runbook.md | ||
|
||
# Everything below is optional | ||
|
||
runbooks: | ||
# All available settings are listed below | ||
|
||
# Disable checks for this repo | ||
# defaults to `false` | ||
disabled: false | ||
|
||
### SUPPORT FOR MULTIPLE RUNBOOKS IN A SINGLE REPOSITORY | ||
|
||
# Fail checks if `any` | `all` | `none` runbooks fail validation | ||
# defaults to `any` | ||
failOn: any | ||
|
||
### SUPPORT FOR UPDATING BIZ-OPS | ||
|
||
# Update valid Biz-Ops runbooks on merge to a specific branch | ||
#### IF YOUR DEPLOYMENTS ARE AUTOMATED (CircleCI, Heroku Pipelines) | ||
#### PLEASE INTEGRATE WITH CHANGE-API INSTEAD | ||
#### https://github.com/Financial-Times/change-api#change-api---v2 | ||
# defaults to `false` | ||
updateOnMerge: true | ||
|
||
# Merges to this branch trigger Biz-Ops updates updateOnMerge is `true` | ||
# defaults to `master` | ||
updateBranch: master | ||
|
||
### UPDATING BIZ-OPS REQUIRES EACH RUNBOOK TO BE TIED TO A VALID SYSTEM CODE | ||
# Mappings between paths and system codes | ||
# unless a custom mapping is specified here | ||
# runbook.md tries to parse the system code from the runbook's filename (format: my-sys-code_runbook.md) | ||
systemCodes: | ||
# paths are relative to root, omitting ./ (case-insensitive) | ||
upp-list-notifications-rw: runbooks/runbook.md |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,117 @@ | ||
# UPP - List Notifications RW | ||
|
||
This service is responsible for writing/reading change events for every list publish to/from a Mongo document store. This API is used to discover list updates. | ||
|
||
## Primary URL | ||
|
||
<https://upp-prod-delivery-glb.upp.ft.com/__list-notifications-rw/> | ||
|
||
## Service Tier | ||
|
||
Platinum | ||
|
||
## Lifecycle Stage | ||
|
||
Production | ||
|
||
## Delivered By | ||
|
||
content | ||
|
||
## Supported By | ||
|
||
content | ||
|
||
## Known About By | ||
|
||
- hristo.georgiev | ||
- robert.marinov | ||
- elina.kaneva | ||
- georgi.ivanov | ||
- tsvetan.dimitrov | ||
- kalin.arsov | ||
- mihail.mihaylov | ||
- boyko.boykov | ||
- donislav.belev | ||
- dimitar.terziev | ||
|
||
## Host Platform | ||
|
||
AWS | ||
|
||
## Architecture | ||
|
||
Responsible for serving and writing notifications for lists. Similar functionality to the Java-based `notifications-rw` but specific for lists. | ||
|
||
## Contains Personal Data | ||
|
||
No | ||
|
||
## Contains Sensitive Data | ||
|
||
No | ||
|
||
## Dependencies | ||
|
||
- upp-mongodb | ||
|
||
## Failover Architecture Type | ||
|
||
ActiveActive | ||
|
||
## Failover Process Type | ||
|
||
FullyAutomated | ||
|
||
## Failback Process Type | ||
|
||
FullyAutomated | ||
|
||
## Failover Details | ||
|
||
The service is deployed in both Delivery clusters. The failover guide for the cluster is located here: | ||
<https://github.com/Financial-Times/upp-docs/tree/master/failover-guides/delivery-cluster> | ||
|
||
## Data Recovery Process Type | ||
|
||
NotApplicable | ||
|
||
## Data Recovery Details | ||
|
||
The service does not store data, so it does not require any data recovery steps. | ||
|
||
## Release Process Type | ||
|
||
PartiallyAutomated | ||
|
||
## Rollback Process Type | ||
|
||
Manual | ||
|
||
## Release Details | ||
|
||
Manual failover is needed when a new version of the service is deployed to production. Otherwise, an automated failover is going to take place when releasing. For more details about the failover process please see: <https://github.com/Financial-Times/upp-docs/tree/master/failover-guides/delivery-cluster> | ||
|
||
## Key Management Process Type | ||
|
||
Manual | ||
|
||
## Key Management Details | ||
|
||
To access the service clients need to provide basic auth credentials. | ||
To rotate credentials you need to login to a particular cluster and update varnish-auth secrets. | ||
|
||
## Monitoring | ||
|
||
Service in UPP K8S delivery clusters: | ||
|
||
- Delivery-Prod-EU health: <https://upp-prod-delivery-eu.upp.ft.com/__health/__pods-health?service-name=list-notifications-rw> | ||
- Delivery-Prod-US health: <https://upp-prod-delivery-us.upp.ft.com/__health/__pods-health?service-name=list-notifications-rw> | ||
|
||
## First Line Troubleshooting | ||
|
||
<https://github.com/Financial-Times/upp-docs/tree/master/guides/ops/first-line-troubleshooting> | ||
|
||
## Second Line Troubleshooting | ||
|
||
Please refer to the GitHub repository README for troubleshooting information. |