Unverified Commit 8d3309ed authored by alijawadfahs's avatar alijawadfahs Committed by GitHub
Browse files

Merge branch 'master' into updateJre

parents 00370bba 3e4c226d
......@@ -1019,10 +1019,10 @@ Execute the workflow and set the different workflow's variables as follows:
| A valid token generated by the MaaS_DL Service for user authentication.
| String (default=Empty).
3+^|*Task variables*
| `DEPLOY_MODEL_ENDPOINT`
| A URL endpoint defined by the user where the AI Model was deployed
| `MaaS_DL_INSTANCE_ENDPOINT`
| The endpoint of the started service.
| URL (default=Empty).
| `API_EXTENSION`
| `DEPLOY_ENDPOINT`
| The base path to access the deployment endpoint.
| String (default="/api/deploy")
| `MODEL_URL`
......@@ -1034,9 +1034,6 @@ Execute the workflow and set the different workflow's variables as follows:
| `SERVICE_TOKEN`
| A valid token generated by the MaaS_DL Service for user authentication.
| String (default=Empty).
| `USER_NAME`
| A valid user name having the needed privileges to execute this action.
| String (default=Empty)
| `APPEND`
| If True, the model will be appended to the list of already deployed models.
| Boolean (default=True).
......@@ -1055,21 +1052,18 @@ Execute the Workflow and set the different workflow's variables as follows:
|===
| *Variable name* | *Description* | *Type*
3+^|*Task variables*
|`DEPLOY_MODEL_ENDPOINT`
| A URL endpoint defined by the user where the AI Model was deployed
|`MaaS_DL_INSTANCE_ENDPOINT`
| The endpoint of the started service.
| URL (default=Empty).
| `API_EXTENSION`
| The base path to access the deployment endpoint.
| String (default="/api/deploy")
| `UNDEPLOY_ENDPOINT`
| The base path to access the undeployment endpoint.
| String (default="/api/undeploy_model")
| `MODEL_NAME`
| The name of the model to be undeployed.
| String (default=Empty )
| `MODEL_VERSION`
| The version number of the model that will be undeployed.
| Integer (default=Empty )
| `USER_NAME`
| A valid user name having the needed privileges to execute this action.
| String (default=Empty)
|===
==== Delete/Finish the Service
......
......@@ -2352,7 +2352,7 @@ To know in which scripts these bindings are available, study the <<_variables_qu
This Synchronization API allows for both communication and synchronization between Tasks and between Jobs dynamically at execution. It is based on a Key-Value Store offering atomic operations. It enables to easily put into action all classical synchronization patterns: Critical Sections and Mutual Exclusion, Rendez-vous, Barriers, Producer/Consumer...
To experience concrete use of the Synchronization API, just go to <<_proactive_studio, ProActive Studio>> and use the predefined templates in the Controls menu (e.g., *Key_Value*).
In summary and for simple use, just go to <<_proactive_studio, ProActive Studio>> and use the predefined templates in the Controls menu (e.g., *Key_Value*).
Use those templates in your own workflow to see how it works. You can further try the <<_examples,examples>> below to better understand the usage of the Synchronization API.
Task synchronization is traditionally handled by the ProActive Scheduler through <<Dependency, Task Dependencies>>, where dependent ProActive Tasks are started only after their parents Tasks completed.
......@@ -2622,6 +2622,7 @@ A complete example of Producer / Consumer, _ServiceDeployerConsumer_ can be down
The *Signal API* is a high-level API that enables users to interact with running jobs via signals (we also call them actions).
That is, it allows a job to expose specific signals (e.g., `soft_stop` to properly finish a job) that can be triggered by users from the *Workflow Execution portal*.
You can try the <<_examples_2,examples>> below to better understand how it works.
In summary and for simple use, just go to <<_proactive_studio, ProActive Studio>> and use the 2 predefined templates in the Controls menu: *Check_For_Signals* or *Wait_For_Signals*.
Fill up the Task Variable *SIGNALS*, and use those templates in your own workflow to be able to receive input from, for instance, the Workflow Execution portal.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment