Questions to be answered:
How does this correlate to the new architecture?
Will the calling service manage load balancing / retries
How will the calling service trigger the load? (scp/ssh, web calls, tcp, etc…)
How do instructions relate to jobs? (many jobs to one instruction?, one to one?)
...
Rationale: Storing instructions in the file system as static JSON objects moves state information away from the central repository of information about a job, confuses users, and does not play well with dynamic instances or state queries.
...
Further additions to the api can be discussed, but this is all that is needed to make it functional.
...
Questions to be answered:
...
How does this correlate to the new architecture?
Will the calling service manage load balancing / retries
How will the calling service trigger the load? (scp/ssh, web calls, tcp, etc…)
...
How do instructions relate to jobs? (many jobs to one instruction?, one to one?)
...