[FOLIO-3047] upgrade central registry to Okapi 4.7 Created: 01/Mar/21 Updated: 23/Mar/21 Resolved: 06/Mar/21 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P2 |
| Reporter: | Jakub Skoczen | Assignee: | John Malconian |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||
| Sprint: | DevOps Sprint 109 | ||||||||||||||||||||
| Development Team: | FOLIO DevOps | ||||||||||||||||||||
| Description |
|
We need the central registry to use Okapi 4.7 so that the new permission "replaces" keyword is acted upon. |
| Comments |
| Comment by Jakub Skoczen [ 03/Mar/21 ] |
|
John Malconian Wayne Schneider David Crossley Guys, do we need to discuss the implications? We need this to happen before the module release deadline (next week) as some of the Iris modules may use new permission migration related keywords in the Module Descriptors. |
| Comment by John Malconian [ 06/Mar/21 ] |
|
This ended up being a little more work than simply 'apt-get install okapi'. The OS needed an upgrade to ubuntu focal in order to run the latest versions of Okapi. Rather than upgrade the existing system, I created a new folio-registry ec2 instance, moved the local postgresql Okapi database to an RDS postgresql instance, and added an alb. The new registry can also be accessed with the following URL, http(s)://folio-registry.dev.folio.org, in addition to the legacy URL: http://folio-registry.aws.indexdata.com. I also updated the shared jenkins pipeline library to use the new URL and created a separate issue to have documentation updated to point to the dev.folio.org URL. |
| Comment by Peter Murray [ 09/Mar/21 ] |
|
Are you confident that this will stay at at db.t3.medium? If so, I'll get a reserved instance for it. |
| Comment by John Malconian [ 09/Mar/21 ] |
|
Yes, Peter Murray - I believe we are good with db.t3.medium for this. |