[FOLIO-1529] Revamp folio-registry infrastructure Created: 25/Sep/18 Updated: 28/May/20 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | John Malconian | Assignee: | John Malconian |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | |
| Development Team: | FOLIO DevOps |
| Description |
|
folio-registry is currently a single ec2 instance. For better HA, it should probably consist of an Okapi cluster in different availability zones with the VIP fronted by a load balancer. Probably best to change the domain to 'dev.folio.org' as well if possible. |