Content Comparison

28 Feb 2025

Prepare pre-Sunflower BF environment (on Ramsons GA)

List of Eureka applications with their versions can be foud there:

Сreate infrastructure from snapshot, adjust cloned db, configure admin token lifespan (set 60 min), (update sessios and tokens). deploy modules, copy params(x16)
/fse/tenant/eureka-bugfest-ramsons-aqa.int.aws.folio.org, create tenant(x16), enable apps(load data), user & roles migration(x16), update admin role, create UI (x4) (keycloak configuration(RTR Configuration on Eureka )), validate consortia (for all members). Reindex(instances, authorities). Smoke test/validation. Revert token lifespan according to documentation.

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

US1363766: Eureka pre-sunflower cluster creation

FSE Platform

28 Feb 2025

Correct dataset by executing the following data-related activities

Full list of topics that should be reviewed -

US1363768: Validate and update dataset with findings from Ramsons release

FSE Platform

one time operation before DB snapshot is created

06 Mar 2025

Create DB snapshot with corrected date

Create a snapshot that can be re-used later. Please mark it with do-not-delete tag

FSE Platform

06 Mar 2025

DB Vacuum

Example:

06 Mar 2025

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

Work with development teams and check is there any changes in resources usage.

Any changes should be highlighted there

FSE Platform

Denis

07 Mar 2025

Execute marc migrations

FSE Platform

10 Mar 2025

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

PO/Denis

Denis

07 Mar 2025

Prepare sFTP access to pre-Bugfest env

similar to

FSE Platform

01 Mar 2025

Prepare scripts (pipelines) for new modules

FSE Platform

20 Feb 2025 Fu

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

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

FSE Platform

Ostap Voitsekhovskyi
Oleg Kurdyayev
Oleksii Petrenko

Verify capabilities for existing users

Done as part of infra creation for all users + consortium

FSE Platform

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

FSE Platform

Create a data snapshot of Pre-Sunflower set up

FSE Platform

Prepare sunflower branch for platform-complete + fse.hosting.configuration with Sunflower modules versions

Branch in fse.hosting.configuration should be compatible with Ramsons-release-branch. It looks like we do not need to have multiple branches for consortia.

FSE Platform

Prepare/Generate/Validate Applications for Sunflower release

US1363770: Prepare/Generate/Validate Applications for Sunflower release

FSE Platform

EBSCO edge passwords should be the same

similar to

FSE Platform

Edge keys are unique for all tenants and validated

Update automation to entitle applications on the new sunflower requirements

FSE Platform

Reset password links

similar to

FSE Platform

Migrate Pre-BF env to Sunflower (+ any manual process from R to S)

FSE Platform

Entitle Sunflower Applications

FSE Platform

Update capabilities for default roles and users

FSE Platform

UI update

FSE Platform

Marc-migrations

FSE Platform

Perform Instance reindex

authority + location reindex

jenkins job

FSE Platform

Validate environment (some testing)

AQA-test jenkins job

FSE Platform

Disable deprecated capabilities

FSE Platform

SMTP - check that emails are working

similar to

FSE Platform

Deployment to Sunflower BF env is competed

FSE Platform

Add DB reader

FSE Platform

Update tenants DNS

FSE Platform

RTR configuration

RTR Configuration on Eureka

30 Mar 2025

DOCUMENTATION

Update documentation.
manual changes,
release notes,

errors and fixes,
snapshots

US1363774: Document/validate documentation Sunflower Eurek bugfest environment

FSE Platform

24 Mar 2025

Add new functionality to update ticket status.

US1363763: Eureka bugfest update new functionality related to jira tickets update

FSE Platform

The data set is ready. Create Sunflower DB snapshot

Add tag 'DO-NOT-DELETE = true'

Snapshot will be available for 180 days

Replicate snapshot and make sure that it won’t be deleted.

FSE Platform

Prepare and share links to Sunflower Eureka BF logs

similar to https://folio-org.atlassian.net/issues/BF-791?jql=textfields%20~%20%22bugfest%20logs%2A%22%20AND%20project%20%3D%20BF

US1363775: Configure logging for Eureka Bugfest Sunflower environment

FSE Platform

Setup SSO

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

Release Manager

POs check the Bugfest env

POs

Smoke test - Manual & Automated

Results:

Oleg Kurdyayev Ostap Voitsekhovskyi

High Availability verification

Verify new modules:

•  <new modules>?

FSE Platform

DB Schema comparison

Denis to work with FSE Ops

FSE Operations

Re-index time measurement

Denis to work with FSE Ops

FSE Operations

Migration from Ramsons to Sunflower time measurement 

Denis to work with FSE Ops

FSE Operations

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

FSE Platform

Troubleshoot Eureka Sunflower BF environment issues project with label ‘eureka-bugfest_R1.2025’)

FSE Platform

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

FSE Platform