Manage a workerpool
A workerpool manager is an essential actor in the iExec network. It will be in charge of proposing available computing resources (workers) to task requesters.
An iExec workerpool is orchestrated by an iExec Core Scheduler. The iExec Core Scheduler watches on-chain deals and schedules off-chain computation among available workers.
My Workerpool Dashboard
You can deploy your own workerpool on iExec with this repository. Be sure to check a particular release before starting your deployment.
Orders enable setting custom governance for resources.
Here you will learn how to manage your workerpool's monetization rules.
Initialize a
workerpoolorder:iexec order init --workerpool
Edit the
workerpoolorder part in iexec.json to set the conditions to use your workerpool:key | description |
|---|---|
workerpool | workerpool address |
workerpoolprice | price to charge the requester for each execution of the app (in nRLC) |
volume | number of authorized uses, each use decreases this number |
tag | restrict usage to a specific runtime such as Scone or Gramine TEE frameworks |
category | Order category, will define the deal workClockTimeRef and its deadlines |
trust | Trust level of the execution, impacts the number of replicates |
apprestrict | restrict the workerpool usage to a specifig app (1) |
datasetrestrict | restrict the workerpool usage to a specific dataset (1) |
requesterrestrict | restrict the workerpool usage to a specific requester (1) |
- 1.the restriction is disabled by default with 0x0000000000000000000000000000000000000000.
The supported tags for workerpool orders are:
Tag value | Description |
|---|---|
0x0000000000000000000000000000000000000000000000000000000000000000 | Order for the execution of a standard task |
0x0000000000000000000000000000000000000000000000000000000000000003 | Order for the execution of a TEE task with Scone framework |
0x0000000000000000000000000000000000000000000000000000000000000005 | Order for the execution of a TEE task with Gramine framework |
- 1.Do not publish workerpool orders with a tag value out of the specified list. Such an order could produce undesirable and unpredictable behaviors. The iExec SDK implements all required preflight checks to avoid erroneous orders publishing.
- 2.Currently, TEE workflow do not support tasks replication on several workers. TEE workerpool orders must be published with
trustvalue equal to1.
As soon as your
ẁorkerpoolorder complies to your requirements, you must sign it and you may publish it.iexec order sign --workerpool && iexec order publish --workerpool
List the published orders for your workerpool.
iexec orderbook workerpool <your workerpool address>
Copy the
orderHash of the order you want to removeUnpublish the
workerpoolorder from the iExec Marketplaceiexec order unpublish --workerpool <orderHash>
An unpublished order is still valid on the blockchain, to invalidate it use the cancel command.
iexec order cancel --workerpool <orderHash>
Last modified 1mo ago