PoC for hosted development environment for FOLIO teams (FOLIO-2601)

[FOLIO-2623] SPIKE: Deploy platform-core backend FOLIO stack in configurable K8s namespaces Created: 01/Jun/20  Updated: 08/Jul/20  Resolved: 08/Jul/20

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None
Parent: PoC for hosted development environment for FOLIO teams

Type: Task Priority: P2
Reporter: John Malconian Assignee: Stanislav Miroshnichenko
Resolution: Done Votes: 0
Labels: dev-environment
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by FOLIO-2622 Utilize install.json, install-okapi.j... Closed
Relates
relates to FOLIO-2624 SPIKE: Build and deploy Stripes bund... Closed
Sprint: DevOps: sprint 92, DevOps: sprint 90
Development Team: FOLIO DevOps
Epic Link: PoC for hosted development environment for FOLIO teams

 Description   

Each development team will be provided with the ability to trigger a job in FOLIO Jenkins that will build a FOLIO stack based on platform-core/snapshot branch to their respective namespace on the FOLIO K8s cluster. The stack will be fixed with a default tenant and admin user as well as reference and sample data similar to existing folio-snapshot builds.



 Comments   
Comment by John Malconian [ 01/Jun/20 ]

Deployment of backend modules to specified Kubernetes namespace where an Okapi and Postgresql instances are already available. There is the question of how DB data will be handled on iterative builds. List of backend modules deployed derived from okapi-install.json which would reside in platform-core snapshot branch.

Deployment consists of the following tasks:

  • pull MDs from folio-registry
  • Post deployment descriptor to local instance of Okapi.
  • Ansible role with deployment and service templates.
  • DB info in pre-installed K8s secrets
  • Secure supertenant. Does supertenant require it's own designated deployment of mod-perms, mod-auth, mod-login, and mod-users? Seems a bit much.

Tenant configuration:

  • Configuration of a 'default' tenant and the loading of reference and sample data and additional configuration.
Comment by Stanislav Miroshnichenko [ 25/Jun/20 ]

Implemented with Terraform and Helm.
First, all core backend modules have `Helm chart.
All core modules deploying into the Project by Terraform to Rancher Application (Folio Helm repository).
Default source for images - DockerHub/folioci.
Helm has postinstall-hook and upgrade-hook to install module decriptor, module deployment, tenant creation and registration.

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