[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: |
|
||||||||||||||||||||||||
| 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
|