Versions Compared

Key

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

...

  • 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? Will the councils affirm an intention to shift to Eureka in Sunflower?

Timeline if the community transitions in Sunflower:

...