Expand CI automation to support multiple nodes and services (FOLIO-496)

[FOLIO-498] Test existing module Ansible roles in folio-ansible in multinode FOLIO environment Created: 08/Mar/17  Updated: 11/Jul/19  Resolved: 11/Jul/19

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: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 1 day, 5 hours, 30 minutes
Original estimate: Not Specified

Issue links:
Blocks
is blocked by FOLIO-510 Refactor Ansible module registration ... Closed
is blocked by RMB-360 Tenant postgres db initialization fai... Closed
Relates
relates to FOLIO-1236 Deploy and Document FOLIO implementat... Closed
Sprint:

 Description   

Test existing ansible roles in folio-ansible project for compatibility with multi-node FOLIO environments - including mutiple node Okapi clusters and non-local DBs. Identify compatibility issues and file as separate Jira issues.



 Comments   
Comment by John Malconian [ 14/Mar/17 ]

I've come a few subtle changes that need to be made to existing folio-ansible roles in order to use the roles to deploy FOLIO environment on multiple nodes. I've made changes to 'common' so that postgresql client packages are installed on all nodes regardless of whether a postgres server is installed. I've also updated the okapi role to manipulate the postgres DB remotely. These changes have been committed to folio-ansible branch 'FOLIO-496-a'. My intentions is too stagger changes across multiple branches so that too many changes are not merged into 'master' all at once that may break existing 'blackbox' functionality.

Comment by John Malconian [ 03/Apr/17 ]

I think I'm in a holding pattern at the moment. Running the existing module roles from folio-ansible will not work across a multi-node cluster due to some dependency issues in individual module roles. For example, the postgresql role is a dependency of each module role, however, in a multi-node environment, we don't want a postgres DB on each node.

Comment by Wayne Schneider [ 03/Apr/17 ]

Changed the link to FOLIO-510 Closed to a blocker to make the dependency more clear.

Generated at Thu Feb 08 23:06:15 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.