[FOLIO-1408] deploy FOLIO on Kubernetes and document the procedure Created: 08/Aug/18  Updated: 26/Jun/19  Resolved: 22/Feb/19

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P3
Reporter: Jakub Skoczen Assignee: Jakub Skoczen
Resolution: Done Votes: 0
Labels: ci, platform-backlog, sprint44, sprint45, sprint48, sprint50, sprint51, sprint52, sprint53, sprint54, sysops_mgt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks UXPROD-1827 CI-integrated continuous deployment (... Closed
blocks FOLIO-2118 CI-integrated continuous deployment (... Closed
blocks UXPROD-1084 Clustered deployment Closed
blocks UXPROD-1429 Clustered deployment pt2 Closed
Sprint: Core: Platform - Sprint 56, Core: Platform - Sprint 57
Story Points: 5
Development Team: Core: Platform

 Description   

SysOP SIG is leaning towards multi-node FOLIO deployment on Kubernetes front-ended by Rancher. Jason Root from TAMU is one of the devops leading the efforts and they have set up and documented an initial cluster. (Notes are available are through the SysOP SIG FOLIO wiki page).

Based on that approach and working with TAMU devops we would like to set up a GitHub repo with scripts, configuration and documentation for FOLIO deployment on Kubernetes, possibly with Rancher as the front-end.

We'd like to understand the best practice of deploying modules and registering them with Okapi through Kubernetes. Let's investigate if the Okapi deployment mechanics should be extended to work directly with Kubernetes or other cloud-specific deployment methods (e.g AWS).

mark.stacy John Malconian Adam Dickmeiss

Notes from the last SIG meeting: https://folio-org.atlassian.net/wiki/display/SYSOPS/2018-08-03+-+System+Operations+and+Management+SIG+Agenda+and+Notes

Acceptance criteria:

  • demostrate a running FOLIO deployed on AWS through Kubernetes
  • present and discuss the approach during a team meeting
  • provide deployment scripts and configuration in the folio-install repository


 Comments   
Comment by Anton Emelianov (Inactive) [ 09/Aug/18 ]

Here is the link to the reasoning why the combination of Kubernetis + Rancher was selected.

Comment by jroot [ 10/Oct/18 ]

Here is the link for the beginning of the Rancher/Kube deployment guide.

Comment by mark.stacy [ 30/Oct/18 ]

Jakub SkoczenAdam Dickmeiss Please find the outline of container builds performed with docker-compose or rancher/k8s.

Images

1. Postgres Database container with OKAPI and FOLIO database created with user role and permission granted.
2. Okapi Environmental variables set and deployed
3. folio-setup - Container runs initialization of database, deploys tenant, sets up superuser, and loads sample data
4. Backend Modules: create a new startup script that registers the module endpoint deploy-enable-service.sh

5. Stripes nginx container - This is a separate deploy. Create a startup script which sets OKAPI Url and Tenant. TODO: Have startup scripts enable frontend modules.

Jakub Skoczen I was not exactly sure what you want for the outline of the deploy process. I'm currently working on documentation.

Comment by mark.stacy [ 02/Nov/18 ]

Jakub Skoczen I have started the documentation regarding the alternative install with docker-compose. The docker-compose organizes the services with the ability to generate the YAML needed for the cluster deploy with Rancher/Kubernetes. Adam Dickmeiss I added under the docker image section the OKAPI interactions.

Please give it a try. Wayne Schneider John Malconian

Comment by Jakub Skoczen [ 09/Jan/19 ]

Per mark.stacy, there is a work on getting the scripts updated to deploy Q4. The docs will be updated by the end of the first week of sprint55.

Comment by Aleksandr Arkhipov [ 14/Feb/19 ]

Here is the documentation: https://github.com/folio-org/folio-install/tree/kube-rancher/alternative-install/docker-compose

Comment by Ann-Marie Breaux (Inactive) [ 19/Feb/19 ]

Hi Jakub Skoczen and mark.stacy and Aleksandr Arkhipov - this is showing in the manual testing queue - not sure that there's anything for us to manually test. Should this maybe be in code review or closed?

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