Versions Compared

Version Old Version 41 New Version 42
Changes made by

Jenn Colt

Jenn Colt

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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. The FOLIO chairs believe the transition to Eureka will happen and 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 architecture release?

...

we recommend rallying community resources to transition to Eureka on Sunflower.

Timeline 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:

Requirement

Status

FOLIO community devops and hosting providers beyond EBSCO are confident in operating Eureka

Being addressed by hosting provider early adopter program

  • 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

  • Developer documentation for working in the Eureka platform

Existing documentation should be gathered and made findable. More effort may be needed here.

  • 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

  • Hosted reference environments have been built using Eureka, which includes these steps:

    • 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

Addressed in part through the hosting providers early adopters program. Additionally, Kitfox has patterns for reference builds to start from that can be adopted/updated by Index Data

  • Option 2: If the community is unable to shift to Eureka in Sunflower 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?

...