Skip to end of banner
Go to start of banner

Ramsons (R2 2024) OKAPI Bugfest environment preparation plan

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Kitfox contact point - Dmytro

Outstanding issues

  1. Recommended resource utilization need to be updated by dev teams

  2. Share DB level migrations information with Kitfox & FSE Platform team

PRE-Ramsons Environments

DiKu tenants 3:

Non-ECS (folio|folio)
bugfest - https://pre-bugfest-ramsons.int.aws.folio.org/
bugfest-aqa - https://pre-bugfest-ramsons-aqa.int.aws.folio.org/
bugfest-plus - https://pre-bugfest-ramsons-plus.int.aws.folio.org/

Consortia tenants(ECS)1+10+1:

ECS (ecs_admin\admin)
https://pre-bugfest-ramsons-consortium.int.aws.folio.org/

Quesnelia BugFest preparation EPIC - https://folio-org.atlassian.net/browse/BF-752

Overall Ramsons BF prep status

Outstanding tasks

Carry over from Quesnelia bugfest

Backlog of tasks

key summary status
Refresh

Completed tasks 

key summary status
Refresh

Sprint 202

Backlog of tasks

key summary status
Refresh

Completed tasks 

key summary status
Refresh

Sprint 203 week 1

Backlog of tasks

key summary status
Refresh

Completed tasks

key summary status
Refresh

Sprint 203 week 2

Backlog of tasks

key summary status
Refresh

Completed tasks

key summary status
Refresh

Bugfest preparation plan

Date

Action

Status

Description/Comments

Jira

Responsible Team

1

Prepare pre-Ramsons bugfest environment

DONE

Kitfox

2

Trigger re-index

DONE

Kitfox

3

Prepare sFTP access to Ramsons BF env

DONE

4

Adjust data at new bugfest env → POs & MQAs

IN PROGRESS

POs & QAs

5

Scripts are ready for new modules deployment:

  • mod-marc-migrations
  • mod-reading-room
  • mod-record-specifications
  • ui-reading-room

IN PROGRESS

Kitfox

6

Create a data snapshot for Pre-Ramsons

PLANNED

Kitfox

7

Prepare master branch for planform-complete with Quesnelia modules versions

PLANNED

Kitfox

8

Migrate Quesnelia Bugfest to Ramsons

PLANNED

Kitfox

9

Deploy new modules

PLANNED

Kitfox

10

Add the default permission sets and users (the ones in the hosted ref envs)

PLANNED

Kitfox

11

Verify permissions for existing users 

PLANNED

Kitfox

12

-

Deployment to Ramsons bugfest env is competed.

Data set is ready

Snapshot will be used for Sunflower bf env preparation

PLANNED

These are the outstanding items that need to be verified/changed in bugfest-R env:

  • Change the URL to https://pre-bugfest-mg.folio.ebsco.com(Route53 entries and Cloudfront)
  • Verify mount of data at 
  • Check entries in mod-configuration that use either the okapi URL or Folio host URL
  • Modify analyzers according to
    Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • When reindex is done need to verify inventory search (recreate index)
  • After indexing is done, please verify and compare counts of tables items, instances and holdings in pbf

Kitfox

13

Verify that modules configuration is updated in FSE branch 

PLANNED

Kitfox

14

Create a data snapshot for Pre-Sunflower 

PLANNED

Kitfox

15

Turn emails on for Ramsons Bugfest

PLANNED

16

Prepare and share links to Ramsons BF logs

PLANNED

How to get logs from Q bugfest environment (Logs are updated every 15 minutes)Couple of ways to access logs:

  1. aws s3 ls s3://int-folio-bugfest-logs/mg/ --no-sign-request --recursive --human-readable --summarize

  2. If you want to use the UI, then go to https://int-folio-bugfest-logs.s3.amazonaws.com/ and search for the module based on timestamp and attach the <key> to the URL - You can download logs that way but there is a max limit of 1000 objects that get displayed from UI

Kitfox

17

-

Smoke test - Manual & Automated

PLANNED

Results: - 

Oleg Kurdyayev

18

-

POs check the Bugfest env

PLANNED

POs

19

Tests claimed

PLANNED

Community testers and EPAM MQAa

20

DB Schema comparison - 

PLANNED

Denis  → Create Rally ticket

key summary assignee priority status resolution

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

ticket is created in Rally

FSE

21

High Availability verification

Verify new modules:

  • mod-marc-migrations
  • mod-reading-room
  • mod-record-specifications
  • ui-reading-room

DevTeams

22

Re-index time measurement

PLANNED

Denis → Ask FSE

FSE

23

Multi Tenant verification

PLANNED

Share test plan

Oleg Kurdyayev

24

Migration from Quesnelia to Ramsons time measuring → 

PLANNED

Please create ticket in Rally Denis 

FSE

25

Review release notes with DevOps (FSE + Community) and discuss deployment approach

RM

Extra configuration notes

Edge user used by module edge-inventory need to have following permissions to be able to obtain authority data, authority source record data and marc record

data-export.download-record.item.get

inventory-storage.authorities.item.get

inventory-storage.authorities.collection.get

source-storage.records.get


  • No labels