Versions Compared

Key

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

...

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

Architecture support given a transition in Sunflower:

The FOLIO support policy provides for support on the current release and one previous release. Therefore if the community transitions to the Eureka architecture in Sunflower, official support for Okapi will cease upon release of Trillium.

...