[FOLIO-2284] Allow per-module container limit override in folio-ansible Created: 25/Sep/19 Updated: 03/Jun/20 Resolved: 27/Sep/19 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Wayne Schneider | Assignee: | Wayne Schneider |
| Resolution: | Done | Votes: | 0 |
| Labels: | devops, platform-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | CP: sprint 73 |
| Story Points: | 2 |
| Development Team: | Core: Platform |
| Description |
|
For FOLIO systems built on releases, the container limits for modules listed in the module descriptors may not be correct, but we don't want to have to make a new module release in order to change it. We need a way to override the settings using Ansible variables. |
| Comments |
| Comment by Wayne Schneider [ 26/Sep/19 ] |
|
This would require updates to the okapi-deployment and okapi-register-modules roles. The module-kubernetes role doesn't currently use the folio_modules variable to set the environment – I thought we had done that, somehow? So that would require more significant refactoring. |
| Comment by Wayne Schneider [ 27/Sep/19 ] |
|
The folio_modules variable can now contain a docker_mem key that will override the memory setting in the module's launch descriptor for the okapi-register-modules and okapi-deployment roles. This covers both "testing" and "snapshot" use cases for single-server builds, but it does not affect Kubernetes builds. |