Skip to end of banner
Go to start of banner

Ramsons (R2 2024) 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

Version 1 Next »

Kitfox contact point - Eldiiar Duishenaliev / Dmytro

DiKu tenants 3:

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

Consortia tenants(ECS)1+10+1:

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


Quesnelia BugFest preparation EPIC -

Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Overall Quesnelia BF prep status

Outstanding tasks

  1. Testing mod-login-saml. Configure own idp. Jira already created

  2. Adjust data export settings → Mikita to create Jira

  3. Create dashboards on pre-Q environment → Owen DONE

  4. Task is to "Edit StringTemplate.Context reference data values in Agreements" on Pre-Q environment. Jira is https://folio-org.atlassian.net/browse/ERM-3063. DONE

  5. Setup RW split for mod-FQM

  6. Folijet - review Kafka topics list, and remove unused

  7. Clean up job profiles (run Poppy CSP2)

  8. Setup patron notice reminder fee data. Setup OKAPI time the same as on Poppy env

  9. Profile picture - review configuration in release notes - https://github.com/folio-org/mod-users?tab=readme-ov-file#configuration-setting-for-profile-picture-feature

  10. Set env variable  BROWSE_CLASSIFICATIONS_ENABLED = true for mod-search

  11. For edge-dcb module there is one permission section mentioned here -https://github.com/folio-org/edge-dcb?tab=readme-ov-file#required-permissions and this should be applied to the edge-dcb user that will be used for DCB functionality.

Carry over from Poppy bugfest

Backlog of tasks

key summary status
Refresh

Completed tasks 

key summary status
Refresh

Q bugfest prep actions

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-Quesnelia bugfest environment

DONE

Kitfox

2

Trigger re-index

DONE

Kitfox

3

Check Update authority data application

DONE

Kitfox

4

Prepare sFTP access to Poppy BF env

DONE

5

Adjust data at new bugfest env → POs

DONE

POs

6

Scripts are ready for new modules deployment:

DONE

Kitfox

7

Create a data snapshot for Pre-Quesnelia

DONE

Kitfox

8

Prepare master branch for planform-complete with Quesnelia modules versions

DONE

Kitfox

9

Migrate Poppy Bugfest to Quesnelia

DONE

Kitfox

10

Deploy new modules

DONE

Kitfox

11

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

DONE

Kitfox

12

Verify permissions for existing users 

DONE

Kitfox

13

-

Deployment to Quesnelia bugfest env is competed.

Data set is ready

Snapshot will be used for Quesnelia bf env preparation

DONE

These are the outstanding items that need to be verified/changed in bugfest-Q 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 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

14

Verify that modules configuration is updated in FSE branch 

DONE

Kitfox

15

Create a data snapshot for Pre- Ramsons 

DONE

Kitfox

16

Turn emails on for Quesnelia Bugfest

DONE

17

Prepare and share links to Quesnelia BF logs

DONE

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

18

-

Smoke test - Manual & Automated

IN PROGRESS

Results: - 

Oleksandr Bashtynskyi 

19

-

POs check the Bugfest env

POs

20

Tests claimed

IN PROGRESS

21

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

22

High Availability verification

TO DO

Verify new modules:

DevTeams

23

Re-index time measurement

PLANNED

Denis → Ask FSE

FSE

24

Multi Tenant verification

PLANNED

https://foliotest.testrail.io/index.php?/runs/view/2414

DevTeams

25

Migration from Poppy to Quesnelia time measuring → 

PLANNED

Please create ticket in Rally Denis 

FSE

26

Prepare R1-2024 branch for planform-complete

Kitfox

27

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

RM



  • No labels