In some cases it is required to submit jobs through the network (like so a sidecar).
Not all JobTracker implementation supports that functionality. Hence a general
JobTracker implementation which splits in a server part and a client part can
be useful. The server part should be implementable on top of any existing JobTracker
implementation, while the client part should not bother about the actual
server implementation.
In order to provide a well-defined interface between the client and server, the
JobTracker interface was re-implemented inside the OpenAPI v3 specification.
The current specification file in this directory. oapi-codegen created client
and server stubs out of the specification. Using them resulted in the remote
client and remote server packages. The OpenAPI specification might be generally
useful for other language bindings or later implementations using protobuf as
more efficient protocol.