Eureka | PO definition of readiness

This page outlines FOLIO POs definition of readiness wrt a successful Eureka migration.

Environment(s)

Type	Primary Contact	Details

Type	Primary Contact	Details
Rancher (ECS/non-ECS)	Kitfox @Oleksii Petrenko	TBD
Snapshot (ECS/non-ECS)	Kitfox	Reference environments
Sprint (ECS/non-ECS)	Kitfox	Reference environments
PTF (ECS/non-ECS)	TBD	TBD
Bugfest (ECS/non-ECS)	EBSCO FSE @Denis Environment updates: Join slack channel #eureka-bugfest-notify Quesnelia bug fest environment update will be triggered two times a day(based on the availability of new releases): 2:00 am ET 10:00 am ET	Eureka ECS (ecs_admin\|admin): https://eureka-bugfest-ramsons-consortium.int.aws.folio.org/ Eureka Non-ECS (folio\|folio) : https://eureka-bugfest-ramsons.int.aws.folio.org/

Testing

ASAP: Teams should execute all Sunflower feature development testing on non-ECS/ECS Eureka snapshot.

ASAP: QA test cases should account for Eureka roles/capabilities/policies.

By end of Sprint 210: Regression testing: PO conducts smoke and exploratory testing of key workflows on Eureka snapshot environments.

Create JIRAs if the snapshot environment(s) is not setup in the way you need to conduct testing.

By end of sprint 211: Create JIRAs for PTF testing on Eureka.

By sprint 211/212: Conduct smoke and exploratory testing of key workflows with applicable SIG(s).

Suggestion: Work with your applicable SIG convener(s) to conduct these tests and collect feedback.

Encourage SIG(s) to test third party integrations if possible.

TBD: Karate testing. Right now Karate is not compatible with Eureka. @Oleksii Petrenko will provide details on the plan to make Karate compliant.

Functionality

INN-Reach integration
Reporting LDP/MetaDB
Third party integration - See list: List of Integrations

Development / QA

Confirm that developers have documentation to setup Eureka dev environments

Confirm that developers have documentation that will provide them all the details needed to be successful.

Confirm if there are FAQs.

Confirm that @Lee Braginsky or @Craig McNally have a checklist of all materials and actions a team must review and do. This checklist should include a primary contact to ask questions about Eureka.

Review FOLIO dev - definition of done documentation. Has/should it change due to Eureka?

Confirm that QA has all it needs wrt Eureka. @Yogesh Kumar and @Craig McNally

What is the role of the Core Platform team wrt Eureka?

What is the role of DevOps wrt Eureka?

What about teams that do occasional development such as MOL? Team Bama? How will they be onboarded? - @Craig McNally and @Lee Braginsky

Eureka Team Development

TBD

Requirements analysis

Better understand roles/capabilities/policies

Create JIRAs for enhancements or defects.

Better understand keycloak? Especially wrt timers?

Create JIRAs for enhancements or defects.

Verify if requirements/behavior should change wrt long jobs.

Confirm with @Craig McNally what additional Eureka functionality should be accounted for when defining requirements (especially Ramsons/Sunflower/Trillium)

Confirm with Craig any Eureka dependencies on other teams for Sunflower and Trillium.

Documentation & Training

Eureka Developer Guide

TBD - Must confirm if Documentation working group will create user documentation

Gather a list of Eureka topic(s)/issue(s) that POs want a better understanding and provide list to @Craig McNally to schedule training(s).

In the next two weeks: Create a Eureka Points of Contact list.

Hosting

Release notes - should they change?

From Sobha: Known issues should clearly distinguish OKAPI issues from Eureka. Further distinguish ECS from non-ECS.

Get feedback from hosting providers?

Do hosting providers or self hosters need documentation related to

What/how to migrate from OKAPI to Eureka?

Anything else?

Support

Support SIG

When should the group start reviewing Eureka issues?

Should we distinguish OKAPI issues from Eureka issues?

Enhancements

Should enhancement requests be handled in the same way as other FOLIO enhancements?

Product Owners