1. Task 57 Scope – Job Task Purpose – Specifically –
Includes – Job management or job usage ?
Excludes – none
External Dependencies – none
Assumptions – none
Risks – none

2. Team Members
Leader - Members
???

3. IPR Declaration Is there any IPR associated with this presentation NO
NOTICE: This contribution has been prepared to assist the ONF. This document is offered to the ONF as a basis for discussion and is not a binding proposal on Cisco or any other company. The requirements are subject to change in form and numerical value after more study. Cisco specifically reserves the right to add to, amend, or withdraw statements contained herein.
THE INFORMATION HEREIN IS PROVIDED “AS IS,” WITHOUT ANY WARRANTIES OR REPRESENTATIONS, EXPRESS, IMPLIED OR STATUTORY, INCLUDING WITHOUT LIMITATION, WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

4. Mistral

5. Mistral Supports two types of workflows
Direct workflow
“Direct workflow consists of tasks combined in a graph where every next task starts after another one depending on produced result. So direct workflow has a notion of transition. Direct workflow is considered to be completed if there aren’t any transitions left that could be used to jump to next tasks.”
Reverse workflow
“In reverse workflow, all relationships in the workflow task graph are dependencies. In order to run this type of workflow we need to specify a task that needs to be completed; it can be conventionally called the ‘target task’. When Mistral Engine starts a workflow it recursively identifies all the dependencies that need to be completed first.”
This option gives less control but is more intent based
This option gives more control but is more procedural
Depends on

6. Example Mistral YAML
Direct workflow
Reverse workflow

7. Mistral UML Equivalent
Could change command to an array of commands, one for each TOSCA ‘lifecycle transitions’.
Not sure of the chaining rules though.

8. Netflix Conductor UML Equivalent (Cloud Orchestrator)

9. Proposed Model – Package Dependencies
Running Software Process
Control Construct
Network Functions (FC, LTP …)
Job

10. Job compute resource usage is already covered
Existing compute model

11. Associating a Job to its targets is a bit trickier
Creating a JobConstraintDomain may be useful