Whenever it has generated new process chains, it puts them into the databaseĪnd sends a message to all instances of the scheduler. The controller receives this message, loads the workflow from the database,Īnd starts transforming it iteratively to process chains as The HTTP server puts the workflow into the database and sends a message to one The HTTP server provides information about scheduled, running, and finished Scheduler are able to connect to a shared database. Further, the HTTP server, the controller, and the That have all five components enabled, and others that have only an agent,Īll components of all instances communicate with each other through messages
That means, in a cluster, there can be instances Each component can be enabled orĭisabled in a given instance (see the configuration optionsįor more information). Instance typically runs on a separate virtual machine, but multiple instancesĬan also be started on the same machine. Together, these components form an instance of Steep. The controller, the scheduler, the agent, and the cloud manager. The following figure shows the main components of Steep: the HTTP server,
The following animation shows how this works for our example Iteration, it finds the longest linear sequences of tasks and groups them to Steep transforms workflows to process chains in an iterative manner. Which are linear sequential lists (without branches and loops). Group tasks into so-called process chains, Reduce the communication overhead and to improve file reuse. Tasks that access the same data should be executed on the same machine to Graph and later on the level of individual executable units. Hybrid scheduling approach that applies heuristics on the level of the workflow The graph has to be transformed to individual executable units. In order to be able to schedule such a workflow in a distributed environment, The second result of A is processed by D. The first one is processed by task B whose result is in In this example, an input file is first processed by a task A. The documentation always applies to the latest software version. In this section, we describe the individual features of Steep. You can monitor theĮxecution in the web interface or by issuing the following command: curl Replace with the returned ID.Ĭongratulations! You successfully installed Steep and ran your first workflow. The command will return the ID of the submitted workflow. Execute the following command: curl -X POST -d 'api: 4.6.0 Workflow consists of a single execute action that sleeps for 10 seconds and We will now submit a simple workflow to test if Steep is running correctly. e STEEP_HTTP_HOST=0.0.0.0 steep/steep:6.6.0Īfter a few seconds, you can access Steep’s web interface on
If you downloaded the binary package of Steep, extract the ZIP file and run theįollows: docker run -name steep -d -rm -p 8080:8080 \ Download Steep 6.6.0 (binaries) Docker Docker image Source code
0 kommentar(er)
