This repository has been archived by the owner on May 10, 2019. It is now read-only.
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
27 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,27 @@ | ||
<!-- This Source Code Form is subject to the terms of the Mozilla Public | ||
- License, v. 2.0. If a copy of the MPL was not distributed with this | ||
- file, You can obtain one at http://mozilla.org/MPL/2.0/. --> | ||
|
||
This document details the Persona production environment, how we maintain it, and how we deploy new code. | ||
|
||
# Persona Production Environment | ||
|
||
The Persona service is deployed, in production, as a set of clusters | ||
with DNS load-balancing across them. Each cluster is internally | ||
redundant, so no single host failure will take down the | ||
service. Geographic distribution of clusters exists for failover and | ||
scale. At this time, there are two clusters at two geographically | ||
distant data centers. The number of clusters will likely increase. | ||
|
||
A single Persona cluster looks like: | ||
|
||
![](./persona_arch.png "Optional title") | ||
|
||
## Processes | ||
|
||
## Hosts | ||
|
||
|
||
# Deploying New Code | ||
|
||
# Monitoring & Escalation |
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.