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

[FOLIO-510] Refactor Ansible module registration and deployment Created: 22/Mar/17  Updated: 12/Nov/18  Resolved: 20/Apr/17

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: Wayne Schneider Assignee: Wayne Schneider
Resolution: Done Votes: 0
Labels: sprint11
Remaining Estimate: Not Specified
Time Spent: 1 day, 7 hours, 15 minutes
Original estimate: Not Specified

Issue links:
Blocks
blocks FOLIO-498 Test existing module Ansible roles in... Closed
Sprint:

 Description   

Rather than having separate roles for each module, look at building two generalized roles for module registration and deployment, driven by variables.



 Comments   
Comment by Wayne Schneider [ 23/Mar/17 ]

Also update to use Okapi facility for docker pull ( OKAPI-283 Closed )

Comment by Wayne Schneider [ 17/Apr/17 ]

John Malconian – I think I have a version of this working in branch FOLIO-510 Closed of folio-ansible – do you want to try it out? Check folio.yml for the roles required to build a demo system, and check group_vars/blackbox for an example of the variables that need to be set.

This should take care of the dependency on a local Postgres as well (see FOLIO-498 Closed ).

If this works, I will take some time to update the documentation and merge into master.

Comment by Wayne Schneider [ 20/Apr/17 ]

Work merged into master branch of folio-ansible. Release folio/folio-backend-auth v0.10.0 built using refactored roles.

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