[FOLIO-948] use okapi deployment persistence for vagrant/AWS deployment Created: 22/Nov/17  Updated: 10/Jan/19

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

Type: Task Priority: P3
Reporter: Jakub Skoczen Assignee: Wayne Schneider
Resolution: Unresolved Votes: 0
Labels: ci, sprint32, sprint33, sprint47, sprint48
Remaining Estimate: Not Specified
Time Spent: 1 hour, 30 minutes
Original estimate: Not Specified

Issue links:
Blocks
blocks FOLIO-1247 set up a performance playground envir... In Progress
Relates
relates to FOLIO-1515 folio-ansible: update okapi-tenant-mo... Closed
relates to FOLIO-812 construct a vagrant image based on th... Closed
relates to FOLIO-1245 create automated performance testing ... Closed
Sprint:
Development Team: Core: Platform

 Description   

Instead of configuring the okapi-deploy service to maintain deployment information, let Okapi manage deployment persistence (feature of Okapi 2.4.0)



 Comments   
Comment by Wayne Schneider [ 15/Feb/18 ]

For persistence to work as expected, we need to have a predefined Okapi nodename (either by setting -Dnodename= or, in dev mode, using the -Dhost= setting), add a nodeId key to our deployment descriptors with the nodename as the value, and post deployment descriptors to /_/discovery/modules rather than /_/deployment/modules.

This suggests we should also update the okapi role in folio-ansible to set the nodename.

Comment by Wayne Schneider [ 26/Sep/18 ]

Most of the work for this has actually been done on FOLIO-1515 Closed . Remaining work:

  • Convert snapshot build to use new roles
  • Deprecate okapi-tenant-modules role
Generated at Thu Feb 08 23:09:30 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.