All Classes and Interfaces
Class
Description
common interface for different possible results of the query
utility methods for parsing graphql scalars as returned by the merlin interface
plan details read from merlin services that are used by the scheduler
controls how the scheduling service outputs its scheduled activities
json serialization methods for data entities used in the scheduler response bodies
interfaces used to coordinate parties interested in the scheduling results
(following example of merlin.server.ResultsProtocol)
interface that can both read and write to a scheduling result object
observer for a schedule result
common interface for different possible results of scheduling
scheduling failed; likely need to change inputs before re-running
scheduling in progress, full results not yet available
Scheduling in enqueued.
scheduling completed successfully, contains the full results
producer for a scheduling result
error whose getMessage() should be reported to a ResultsProtocol.WriterRole.failWith()
after reporting to the relevant ResultsProtocol, the exception should be consumed
used to allow idiomatic java control flow unwinding and uniform message passing
while still differentiating from more serious exceptions that should propagate out
represents the query for the results of a scheduling run
the query can be run using the scheduling service configured at construction, possibly resulting in the activation of
a scheduling agent to produce the results (depending on caching etc)
common interface for different possible results of the query
scheduler completed successfully; contains the requested results
scheduler completed unsuccessfully, eg in an error or canceled
scheduler has not completed running
Scheduler has enqueued this request.
agent that can handle posed scheduling requests
scheduler service entry point class; services pending scheduler requests until terminated
set up mapping between scheduler http endpoints and java method calls
details of a scheduling request, including the target schedule specification version and goals to operate on
summary of results from running the scheduler, including goal satisfaction metrics and changes made
TODO: @param javadocs (Adrien)
json parsers for data objects used in the scheduler service endpoints
services operations at the intersection of plans and scheduling goals; eg scheduling instances to satisfy goals
provides both mutation operations to actively improve a plan's goal satisfaction score (eg by inserting activity
instances into the plan) and passive queries to ascertain the current satisfaction level of a plan
occurs when an interface object is encountered that does not match any of an expected set of sub-types