Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

BlueIN PROGRESS

Date

Action

Status

Description/Comments

Ticket

Responsible

Notes

1

-

Prepare pre-Ramsons BF environment (on Quesnelia SP-5)

List of Eureka applications:

app-consortia, app-dcb, app-edge-complete, app-erm-usage, app-platform-complete, app-platform-minimal

Status
colourGreen
titleDONE

Сreate infrastructure from snapshot, adjust cloned db, deploy modules, configure admin token lifespan (set 60 min), copy params(x15), create tenant(x15), enable apps( fs090002, fs090003, load data from repos. OR okapi), user & roles migration(x15), update admin role, update passwords, create UI (x4) (keycloak configuration), create consortia (for all members). Reindex. Smoke test/validation. Revert token lifespan according to documentation. SP5, Quesnelia release branch.

Create admin user with login/password ‘folio/folio’ for stansdalone tenants (should have all capabilities). Create ecs_admin\admin

Note: pre-Bugfest will not have app-erm-usage because of module descriptor validation issue (fixed in Ramsons: link). Impact: while migration of users with erm-usage permissions, the users will not have erm-capabilities. Expect that if in Ramsons Eureka has application 'app-erm-usage', capabilities will be available and FSE Platform team/QA/PO will assign those manually OR some migration will be executed (to be clarified with Eureka dev team)

Done: Consortia tenants - pending the fix: EUREKASUP-8

US1324154

FSE Platform

2

Communication to teams who typically work with the infrastructure components to avoid any changes w/o approval from Kitfox/FSE Platform

Status
colourGreen
titleDONE

NA

FSE Platform

3

Finalize set of Applications for Ramsons Eureka-based Bugfest and a list of modules

Status
colourGreen
titleDONE

Expectation is that the environment might contain modules that will be targeted for inclusion in FOLIO platform after Ramsons release (as for several modules the work is In Progress)

US13270953270

FSE Platform

4

Prepare sFTP access to pre-Bugfest env

https://bugfest-quesnelia.int.aws.folio.org/settings/invoice/batch-group-configuration similar to BF-792

image-20241028-105026.png

<>

FSE Platform

5

by

Prepare scripts (pipelines) for new modules

Status
colourGreen
titleDONE

https://github.com/folio-org/mod-circulation-bff

US1326339

FSE Platform

6

Notify QA leads, Product Owners that Pre-BF environment is ready for data validation

Status
colourGreen
titleDONE

By default, after migration to Eureka platform the password of the user is equal to username (case sensitive: ex. JohnDoe / JohnDoe) and need to be reset.

Please note, on the Eureka Ramsons pre-Bugfest environment the users that were migrated from Quesnelia Bugfest, do not have a capability to reset their passwords. This is a known issue regarding capability and it is fixed in Ramsons (

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyMODUSERSKC-52
)

na

Release Manager

7

-

Verify capabilities for existing users

Status
titleN/A

Denis to work with Artem and Oleg K.

QA/PO

8

Review release notes with Kitfox team and discuss deployment approach, branch creation, adding env. variables

Status
colourGreen
titleDONE

US1326337

FSE Platform/Kitfox/FSE Ops

9

-

Create/modify automation to support Ramsons' reindex

Status
colourBlue
titlein progress

US1326353

FSE Platform

10

Create a data snapshot of Pre-Ramsons set up

Status
colourGreen
titleDONE

Please inform Kitfox once available

US1328411

FSE Platform

11

[OPTIONAL] Update Eureka Bugfest wrapper to handle management modules update

<>

FSE Platform

discussion with Eureka/Kitfox

12

Prepare master branch for platform-complete + hosting.configuration with Ramsons modules versions

Status
colourGreen
titleDONE

Kitfox

13

non-platform-complete modules

list of modules from Ramsons+

(releases from branches), they will not be a part of regular install.json

Status
colourBlue
titlein progress

  • mod-requests-mediated

  • folio_requests-mediated

  • mod-tlr

  • mod-circulation-bff

<>

FSE Platform

will they be a part of platform-complete install.json?

Denis - check frequency of releases? Decide deployment approach

14

Prepare/Generate/Validate Applications for Ramsons release

Applications:

  1. app-consortia

  2. app-dcb

  3. app-edge-complete

  4. app-erm-usage

  5. app-platform-complete

  6. app-platform-minimal

  7. app-marc-migrations

Status
colourGreen
titleDONE

US1328418

FSE Platform

15

Update existing/Create new BF cluster from DB snapshot with all migrations& run adjust-cloned-db pipeline

Status
colourGreen
titleDONE

Updated existing cluster US1324154: Create pre-bugfest environment for Ramsons release

N/A

FSE Platform

16

Required (read release notes more mod-data-export)

Status
colourGreen
titleDONE

similar to BF-807

FSE Platform

17

EBSCO edge passwords should be the same (done with Kitfox)

Status
colourGreen
titleDONE

similar to BF-808

FSE Platform

18

DI slicing should be validated

Status
colourGreen
titleDONE

similar to BF-804

FSE Platform

19

Deploy Ramsons Applications to BF cluster

Status
colourGreen
titleDONE

FSE Platform

20

Reset password links

Status
colourGreen
titleDONE

similar to BF-781

FSE Platform

Check with Dmytro (do we need to set invalid links or not?)

21

-

Migrate Pre-BF env to Ramsons (+ any manual process from Q to R)

Status
colourBlue
titlein progress

Ramsons (R2 2024) Required manual migrations

US1328729

FSE Platform

22

Entitle Ramsons Applications

Status
colourGreen
titleDONE
for non-ECS
Status
colourRed
titleblocked
for ECS

FSE Platform

blocker: EUREKASUP-11

23

[IF NEW CLUSTER]

Create ECS/non-ECS tenant + MARC MIGRATIONS + run reindex + create UI. [IF OLD CLUSTER] update tenant DNS

Status
titleN/A

FSE Platform

create DNS for tenants, not tenants themself

24

[IF NEW CLUSTER]

Add the default roles and users

Status
titleN/A

FSE Platform

25

mod-entities-links migration

Status
colourGreen
titleDone

Ramsons (R2 2024) Required manual migrations

26

LCCN migrations

Status
colourGreen
titleDONE

Script to update tenant mapping rules to include mapping for Canceled LCCN, Date type, Subject Source and Subject Type

Instruction: Login into i-0231a7b0d96d4f8ba instance, devQa, us-east-1, navigate inside “/home/ec2-user“. Here you will find jar file, instructions.txt file and bunch of config files for different tenants.

Expand
titleresults

aqa - fs09000003 - done
image-20241105-171105.png
plus - fs09000002 - done
image-20241105-171241.png

fs09000000 - done
image-20241105-171348.png

FSE Platform

Status
colourGreen
titleQuick migration

27

mod-inventory-storage migration

Status
colourGreen
titleDone
for non-ecs

validated for non-ecs

Status
colourBlue
titlein progress
in progress for ECS

Instruction here
Validation:

Code Block
SELECT 1 FROM <tenant_id>_mod_inventory_storage.instance WHERE jsonb -> 'publicationPeriod' IS NOT NULL LIMIT 1;

FSE Platform

Status
colourRed
titlelong migration

28

Execute marc-migrations

Status
colourRed
titlewill be performed later - dev team not ready

mod-marc-migrations will be used more like external tool now. For Okapi-based deployments, this module can be deployed in the usual way, with no additional changes needed. 

For Eureka-based deployments, the Spitfire team has created an application to facilitate module deployment:

https://github.com/folio-org/app-marc-migrations

In the R release, default mapping rules have changed, and remapping is now required for inventory authorities and instances. 

FSE Platform

29

Roles migration

Status
colourGreen
titleDONE
for non-ECS

Status
colourBlue
titlein progress
for ECS

FSE Platform

q

30

UI creation

Status
colourGreen
titleDONE
for non-ECS
Status
colourBlue
titleto do
for ECS

FSE Platform

q

31

Verify (update admin) capabilities for existing users.

Status
colourGreen
titleDONE
for non-ECS
Status
colourBlue
titleto do
for ECS

FSE Platform

q

32

Perform Instance reindex

Status
colourGreen
titleDONE
for non-ECS
Status
colourBlue
titleto do
for ECS

jenkins job

FSE Platform

33

Perform authority + location reindex

Status
colourGreen
titleDONE
for non-ECS
Status
colourBlue
titleto do
for ECS

jenkins job

FSE Platform

l

34

Validate environment (some testing)

Status
colour

Green
title

DONE
for non-ECS
Status
colourBlue
titleto do
for ECS

FSE Platform

35

Disable deprecated permissions.

N/A

similar to BF-798

FSE Platform

36

SMTP - check that emails are working

Status
colourGreen
titleDONE
for non-ECS

similar to BF-796

FSE Platform

37

DOCUMENTATION

Status
colourBlue
titleIN PROGRESS

similar to BF-780

38

Deployment to Ramsons BF env is competed

FSE Platform

39

[JUST CHECK]

Verify that modules configuration is updated in FSE branch. Update app versions.

Status
colourGreen
titleDONE

FSE Platform/Kitfox

40

Update tenant DNS

Status
colourGreen
titleDONE
for non-ECS
Status
colourBlue
titleto do
for ECS

41

Data set is ready. Create Ramsons DB snapshsnapshot

Status
colourBlue
titleto do

FSE Platform

42

Prepare and share links to Ramsons Eureka BF logs

Check with Dmytro

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

<>

FSE Platform

43

evening - morning

Notify POs/QAs that Eureka Ramsons BF is up and running, and available for sanity testing

Release Manager

44

-

POs check the Bugfest env

POs

45

-

Smoke test - Manual & Automated

Results:

Oleg Kurdyayev

46

High Availability verification

Verify new modules:

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

Dev Teams

47

by

DB Schema comparison

Denis to work with FSE Ops

US1327373

FSE Operations

48

by

Re-index time measurement

Denis to work with FSE Ops

US1327378

FSE Operations

49

by

Migration from Quesnelia to Ramsons time measurement 

Denis to work with FSE Ops

US1327378

FSE Operations

50

Daily updates (morning/evening) of BF env during bugfest and bugfix periods

<>

FSE Platform

51

Troubleshoot Eureka Ramsons BF environment issues (review issues from https://issues.folio.org/projects/BF project with label ‘eureka-bugfest_R2.2024’)

<>

FSE Platform

TBD

52

Maintain slack notifications in following channels: #eureka-bugfest-notify

<>

FSE Platform

TBD

...