Expand CI automation to support multiple nodes and services
(FOLIO-496)
|
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Expand CI automation to support multiple nodes and services |
| Type: | Sub-task | Priority: | P3 |
| Reporter: | John Malconian | Assignee: | John Malconian |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 2 days, 30 minutes | ||
| Original estimate: | Not Specified | ||
| Sprint: |
| Description |
|
We utilized Terraform in some initial CI work before switching to the simpler Vagrant and Docker mechanisms. It's time to revisit the use of Terraform to provision AWS CI resources since it comes with support for a wide range of support for AWS resources - including load balancers, RDS services, auto-scaling, and EC2 container services. |
| Comments |
| Comment by John Malconian [ 10/Mar/17 ] |
|
Committed a Terraform CI group "ci01" to folio-org/folio-infrastructure that we can use for testing Ansible roles. |
| Comment by John Malconian [ 14/Mar/17 ] |
|
Terraform configuration for CI group 'ci01' is complete and can be easily be used to create additional groups. 'ci01' consists of a configurable number of okapi ec2 instances (currently two), an ec2 'classic' load balancer (ELB) that fronts okapi, one, dedicated postgres instance, and route53 updates to create DNS aliases for the ELB. |