Dear all-- I've written up a draft description of the Orchestrator [1] and welcome comments and critiques. As with the GFAC description, this is not necessarily based on the current implementation. The purpose is to create an implementation-independent description of the Orchestrator for future reference.
Some outcomes from this exercise: * The interactions of the Workflow Interpreter, Orchestrator, and API server need to be thought out. Don't take my suggestions here too seriously. * The scheduler component of the Orchestrator needs more thought, especially if there are multiple Orchestrators running (for load balancing): we don't want to run into "thread" issues if multiple schedulers are trying to work with the registry. * Our current concept for extending the Orchestrator is to extend the CPI. You would do this to implement, for example, more sophisticated scheduling. But we could take a GFAC approach of having a core and developer-provided plugins (for scheduling, quality of service, etc). Marlon [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=40511565
