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
Implications of Eureka adoption
Eureka adopter support
Introduction
The community has two key questions to answer:
...
On what timeline does the community make Eureka the official FOLIO architecture release?
On what timeline does the community stop supporting Okapi?
Implications of Eureka adoption
...
Changes
Move from module based platform to application-based platform
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 (private 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
CLI for local deployment: https://github.com/folio-org/eureka-setup
Planned support
Hosting early adopter program will begin in January 2025 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
...
Timeline options for community transition to Eureka
In Sunflower EBSCO will shift support from Okapi to Eureka.
In order for the community to transition to Eureka in Sunflower as well, these high level requirements/milestones should be met:
Hosting providers beyond EBSCO and FOLIO community devops 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 If the community to support Okapi after EBSCO shifts to Eurekais unable to shift to Eureka and must continue supporting the Okapi architecture these high level requirements will need to be met:
Community support for an 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 and perhaps modules from future releases as well
How long does the community support Okapi? Does the community shift from Okapi to Eureka in Sunflower? Will the councils affirm an intention to shift to Eureka in Sunflower?
...
Continued knowledge transfer to community dev ops teams
Onboard additional hosts into early adopter program
Implications of Eureka adoption
Changes
Move from module based platform to application-based platform
Change in maintenance through deprecation of homegrown modules:https://folio-org.atlassian.net/wiki/spaces/TC/pages/518946885/0010-eureka#Deprecations
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 (private 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
CLI for local deployment: https://github.com/folio-org/eureka-setup
Planned support
Hosting early adopter program will begin in January 2025 with GBV and potentially others
Gaps in support
Additional operational and development support will be needed