use okapi deployment persistence for vagrant/AWS deployment

Description

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

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Wayne SchneiderSeptember 26, 2018 at 3:08 PM

Most of the work for this has actually been done on . Remaining work:

  • Convert snapshot build to use new roles

  • Deprecate okapi-tenant-modules role

Wayne SchneiderFebruary 15, 2018 at 5:37 PM
Edited

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.

Details

Assignee

Reporter

Priority

Development Team

Core: Platform

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created November 22, 2017 at 2:22 PM
Updated January 10, 2019 at 3:43 PM
TestRail: Cases
TestRail: Runs