2024-11-20 Eureka Adoption

• Timing of Eureka adoption and Okapi retirement
• How does the TCR process factor into this?
• Updating the OST pages?
• What would be the practical implications of making Trillium rather than Sunflower the Eureka release?

Craig: What happens if the adoption gets pushed further to another FOLIO release?

List of modules for an RFC? - impressive list

Julian:

2 decisions here: Do we adopt for Sunflower even though it's technically past that deadline? The approved technology stack is already approved for Sunflower.

Is there an overlap period for supporting both Okapi/Eureka?

SSO/login modules have completely changed in Eureka.

Marc Johnson:

Does the community approve adopting Eureka in the first place?

Do we have a special process for this?

Points out Ebsco is a large contributor to the community technically

The assumption - At some point if Eureka is adopted by the community at large, is it a given that Okapi envs will stop being supported by the community at large?

There are a set of decisions that need to be made - Community support? Adoption? Need a transition plan? How do we structure these decisions?

Multiple options on the table:

Support Eureka and Eureka only from Sunflower.

Combined support from Sunflower until a future release.

Support Okapi for more long term with transition plan

Next steps? Experience in early adopter program?

Craig:

There are cost implications for supporting both Okapi/Eureka.

Several back-end modules for login no longer needed in Eureka.

Over time less code that needs to be maintained, management users and tokens handled at a higher level.

Concrete action items for next meeting?

Jen:

Isn't the community technically supporting both platforms at the moment?

We are making a decision for the whole community here..

Is it true that development is supported with Okapi on Sunflower? Or after?

Is the early adopter program an actual program?

Vince:

Lots of effort to test both environments.

Development could shift to primarily Eureka environments in Rancher.

New modules have a different workflows, and a different permissions model on the management level.

New development is being done on Eureka, if it needs to be tested on Okapi - but who would be addressing these issues? Another way is not to do that, and support the other way around.

Jason:

Putting the cart before the horse - still need to vote on adoption or not.

Asks about what development resources would be shifted or different with Okapi vs Eureka.

We need to decide if there's a transition plan, because some have stated you can just run on Okapi as a fall-back?

Who in the community would support this? Not many outside of Ebsco who have exp. with running the platform right now..

Kristin:

Needs to be able to organize their platform upgrades/transitions.

Points out that this platform is currently only running on AWS infra - no other "local" or "non-AWS" examples out there.

Will Eureka be supported for local installations? Adoption needs to be planned securely and sustainably.

Needs to be vetted for local installations by the community.

Mark V:

The more people that start getting involved in the early adoption, the better off we'll be.

...

(More notes to come after I review the recording, hard to keep up with the convo...)

Overall chicken in egg scenario: Community is blocked on adoption until TC agrees, but community doesn't have experience to help in deciding to adopt or to support.

Craig, Mark and Vince will come up with narrowed options based on discussion.

Slack conversations:

• expectations around Eureka modules and the TCR process... Is the expectation that we should submit all of these for inclusion into Sunflower?  Is it too soon, given where we stand with the RFC process?  There's a lot here, so I think we'd want to get started sooner than later so we don't wind up with a huge backlog of these things closer to the deadline. https://folio-project.slack.com/archives/C02HP10PPGB/p1730467357615359
• I request that we put the 0010-eureka RFC into the next status stage on Monday. Implementers need a decision now whether the community adopts Eureka for Sunflower or not so that they can plan their work. https://folio-project.slack.com/archives/C02HP10PPGB/p1731076265224589

RFC in preparation:

• 0010-eureka

Relevant dates:

• Sunflower OST acceptance: Sept 27, 2024
• Sunflower scope deadline: Sept 27, 2024
• January tri-council meeting: Jan 13, 2025
• Sunflower API freeze? Jan 24 2025
• Sunflower module acceptance deadline: Jan 24, 2025
• FOLIO support period is the current release and two releases back? Officially Supported Technologies
• RFC public review timebox: 1 month

Maccabee Levine an Alle 17:06
FWIW libraries didn't need much of a change from our existing TCR processes...just ignoring a few criteria

Kirstin Kemner-Heek an Alle 17:14
Who is live with Eureka now? On Quesnalia?

Sie an Alle 17:34
++Kirstin

Florian Gleixner an Alle 17:36
If we decide as community for this tight timeline, then we have to commit as community to support the upgrade to Eureka

Jenn Colt an Alle 17:37
This is a hosting question?

Marc Johnson 17:37
I don’t think it’s only a hosting provider question

Kirstin Kemner-Heek an Alle 17:40
Exact! I'm just asking if the timeline is doeable :-)

Mark Veksler 17:41
apologies if i misunderstood your question :-)

Julian Ladisch an Alle 17:43
If Eureka with Sunflower doesn't work for some community members:
We release critical service patches.
On the very unlikely case that this doesn't work in time we may extend the Ramsons support period of Ramsons with Okapi way.

Kirstin Kemner-Heek an Alle 17:44
+1 Jason.

vbar an Alle 17:45
Eureka platform doesn’t have any AWS specific dependencies - just like an Okapi platform. So the risk is not high that a non-AWS environment will be an issue.

Marc Johnson an Alle 17:45
@Jason Root

At this point, I’m not advocating for one or the other, I’m advocating for the community deciding what options are available and how to choose between them, and then what the timeline for that is

Kirstin Kemner-Heek an Alle 17:48
That would be fine

Marc Johnson an Alle 17:54
When I say support, I mean the commitment from the wider community that it will support this software (even if members are no longer able to)

Jenn Colt 17:57
Is lack of community approval keeping people from committing bandwidth or is it just a resourcing problem?

Julian Ladisch 17:58
Yes, lack of community approval keeps people from committing bandwidth.

vbar 18:01
Maybe the TC can issue a formal statement of intent. That Eureka is being evaluated (early adopter) with a desire to adopt

Marc Johnson 18:01
I agree that special case process for eureka should be part 2