This looks interesting, too.

What is the goal for making it "runnable as a service"? Just exposing a REST API that can be accessed on a local machine? Or would you like it deployed somewhere?

And as a sanity check, are we talking about this tool here or its successor? Or something else entirely?

In T269697#6737282, @cmassaro wrote:

This looks interesting, too.

What is the goal for making it "runnable as a service"? Just exposing a REST API that can be accessed on a local machine? Or would you like it deployed somewhere?

We'd want it to extend our standard "service runner" framework, and use the CI system to build and publish docker images on merge that could be hosted to do this. I'd recommend doing this as distinct steps.

And as a sanity check, are we talking about this tool here or its successor? Or something else entirely?

Ish. Per recent discussions, the code in that repo is almost all actually stuff that should be in https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/services/function-orchestrator/ and the evaluator codebase is pretty much non-existent. (We should have a task for this.)

Would it be appropriate to start working on this? Or is this somewhat blocked on splitting out the orchestrator stuff?

I think we could start work on this right now, yeah; some of the orchestrator stuff will need deleting, but that's fine.