Draft report on adoption and timeline of the Eureka platform

Table of contents
Introduction
Implications of Eureka adoption
Eureka adopter support
Timeline
Next steps for councils
Next steps for hosts and implementers
Next steps for EBSCO

Introduction

The community has two key questions to answer:

• Does the community adopt Eureka?

There is significant community momentum toward the Eureka environment, and it was extensively discussed in 2024. There will also be significant benefit from well coordinated migration to the new platform and quick consolidation on just one platform. FOLIO will be moving to Eureka as its new platform, and away from Okapi, therefore:

• On what timeline does the community make Eureka the official FOLIO release?

• On what timeline does the community stop supporting Okapi?

Implications of Eureka adoption

• Changes

  • Move from module based platform to application-based platform

  • 0005-application-formalization

  • 0010-eureka

  • Change in maintenance through deprecation of homegrown modules:https://folio-org.atlassian.net/wiki/spaces/TC/pages/518946885/0010-eureka#Deprecations

• Benefits

  • https://folio-org.atlassian.net/wiki/spaces/TC/pages/518946885/0010-eureka#Benefits

• Challenges

  • Uncertainty of non-FSE providers ability to adopt for Sunflower

  • Incomplete documentation

  • RFC process not completed

Eureka adopter support

• Existing support

  • End-user early adopter program has begun (closed slack channel #eureka-early-adopters)

  • Some documentation exists on the Wiki: Eureka - How to ...

  • Docker-based minimal eureka platform: https://github.com/folio-org/eureka-platform-bootstrap

  • Reference environments (links, schedule)

• Planned support

  • Hosting early adopter program will begin in January with GBV and potentially others

• Gaps in support

  • Additional operational and development support will be needed

Timeline

• Sunflower: EBSCO shifts support from Okapi to Eureka

• High level requirements/milestones for adoption of Eureka by the community

  • People in the community beyond EBSCO/FSE who are confident in operating Eureka

  • Developer documentation for working in the Eureka platform

  • Define flower releases using Eureka based applications

    • Replaces the release branches (e.g. 2024 R2) of current platform-complete definitions

    • May use a different repository

      • May want to be consistent with how the Eureka based Rancher environments are being defined

  • Build hosted reference environments using Eureka

    • Define environment configurations using Eureka based applications

      • Similar to above for flower releases, instead for the snapshot branch

    • Use Eureka based architecture

      • Including Keycloak, Kong, sidecars for module docker containers etc

    • Use Eureka management API to enable applications defined above

• High level requirements for the community to support Okapi after EBSCO shifts to Eureka

  • Community support for Okapi-based bugfest environment

  • Community support for Okapi-based CSPs

  • Community dev ops is able to prove the Ramsons release of Okapi will run Sunflower modules

• How long does the community support Okapi? Does the community shift from Okapi to Eureka in Sunflower?

Timeline if the community transitions in Sunflower:

Next steps for councils if Eureka is approved

• Technical council

  • Determine how to approve the large number of modules in time for Sunflower, or agree to approve as a package: https://folio-org.atlassian.net/wiki/spaces/TC/pages/518946885/0010-eureka#New-Components

  • Update module approval processes to account for application formalization

• Product council

  • Support SIGs and POs in implementation of application formalization

• Community council

Next steps for community dev ops

• Plan to work collaboratively with EBSCO teams in the new year to build reference environments using Eureka and provide community support for Eureka adoption.

• Gap analysis and further investigation

Next steps for hosts and implementers

• Implementers participating in the early adopter end user program should report their experiences as they are able

• Sysops SIG participants should continue to voice their needs for support to TC and EBSCO

Next steps for EBSCO

• Continued knowledge transfer to community dev ops teams

• Onboard additional hosts into early adopter program