Get desktop application:
View/edit binary Protocol Buffers messages
ResourcePoolService defines the resource pool related methods such as create, get, delete and upgrade resource pools.
Create a resource pool entity for a given config
Request message for ResourcePoolService.CreateResourcePool method.
The unique resource pool UUID specified by the client. This can be used by the client to re-create a failed resource pool without the side-effect of creating duplicated resource pool. If unset, the server will create a new UUID for the resource pool.
The detailed configuration of the resource pool be to created.
Response message for ResourcePoolService.CreateResourcePool method. Return errors: ALREADY_EXISTS: if the resource pool already exists. INVALID_ARGUMENT: if the resource pool config is invalid.
The ID of the newly created resource pool.
Get the resource pool entity
Request message for ResourcePoolService.GetResourcePool method.
The ID of the resource pool to get the detailed information.
Whether or not to include the resource pool info of the direct children
Response message for ResourcePoolService.GetResourcePool method. Return errors: NOT_FOUND: if the resource pool is not found.
The detailed information of the resource pool.
The list of child resource pools.
Delete a resource pool entity
Request message for ResourcePoolService.DeleteResourcePool method.
The ID of the resource pool to be deleted.
Response message for ResourcePoolService.DeleteResourcePool method. Return errors: NOT_FOUND: if the resource pool is not found. INVALID_ARGUMENT: if the resource pool is not leaf node. FAILED_PRECONDITION: if the resource pool is busy. INTERNAL: if the resource pool fail to delete for internal errors.
(message has no fields)
Modify a resource pool entity
Request message for ResourcePoolService.UpdateResourcePool method.
The ID of the resource pool to update the configuration.
The configuration of the resource pool to be updated.
Optional boolean which forces an update, even if the validation fails.
Response message for ResourcePoolService.UpdateResourcePool method. Return errors: NOT_FOUND: if the resource pool is not found.
(message has no fields)
Lookup the resource pool ID for a given resource pool path
Request message for ResourcePoolService.LookupResourcePoolID method.
The resource pool path to look up the resource pool ID.
Response message for ResourcePoolService.LookupResourcePoolID method. Response message for ResourcePoolService.UpdateResourcePool method. Return errors: NOT_FOUND: if the resource pool is not found. INVALID_ARGUMENT: if the resource pool path is invalid.
The resource pool ID for the given resource pool path.
Query the resource pools.
Request message for ResourcePoolService.QueryResourcePools method.
TODO Filters
(message has no fields)
Response message for ResourcePoolService.QueryResourcePools method. Return errors:
The max limit of resources `CONTROLLER`(see TaskType) tasks can use in this resource pool. This is defined as a percentage of the resource pool's reservation. If undefined there is no maximum limit for controller tasks i.e. controller tasks will not be treated differently. For eg if the resource pool's reservation is defined as: cpu:100 mem:1000 disk:1000 gpu:10 And the ControllerLimit = 10 ,Then the maximum resources the controller tasks can use is 10% of the reservation, i.e. cpu:10 mem:100 disk:100 gpu:1
Used in:
ReservationType indicates reservation type for the resourcepool
Used in:
ELASTIC reservation enables resource pool to be elastic in reservation , which means other resource pool can take resources from this resource pool as well as this resource pool also can take resources from any other resource pool. This is the by default behavior for the resource pool
STATIC reservation enables resource pool to be static in reservation , which means irrespective of the demand this resource pool will have atleast reservation as entitlement value. No other resource pool can take resources from this resource pool. If demand for this resource pool is high it can take resources from other resource pools. By default value for reservation type ELASTIC.
Used in:
,Resource Pool Id
ResourcePool spec
Resource Pool's parent TODO: parent duplicated from ResourcePoolConfig
Resource Pool's children
Resource usage for each resource kind
Resource Pool Path
A fully qualified path to a resource pool in a resource pool hierrarchy. The path to a resource pool can be defined as an absolute path, starting from the root node and separated by a slash. The resource hierarchy is anchored at a node called the root, designated by a slash "/". For the below resource hierarchy ; the "compute" resource pool would be desgignated by path: /infrastructure/compute root ├─ infrastructure │ └─ compute └─ marketplace
Used in:
, ,Resource Pool configuration
Used in:
, ,Revision of the Resource Pool config
Name of the resource pool
Owning team of the pool
LDAP groups of the pool
Description of the resource pool
Resource config of the Resource Pool
Resource Pool's parent
Task Scheduling policy
The controller limit for this resource pool
Cap on max non-slack resources[mem,disk] in percentage that can be used by revocable task.
Resource configuration for a resource
Used in:
Type of the resource
Reservation/min of the resource
Limit of the resource
Share on the resource pool
ReservationType indicates the the type of reservation There are two kind of reservation 1. ELASTIC 2. STATIC
Used in:
Type of the resource
Allocation of the resource
slack is the resource which is allocated but not used and mesos will give those resources as revocable offers
Scheduling policy for Resource Pool.
Used in:
This scheduling policy will return item for highest priority in FIFO order
The max limit of resources `REVOCABLE`(see TaskType) tasks can use in this resource pool. This is defined as a percentage of the resource pool's reservation. If undefined there is no maximum limit for revocable tasks i.e. revocable tasks will not be treated differently. For eg if the resource pool's reservation is defined as: cpu:100 mem:1000 disk:1000 And the SlackLimit = 10 ,Then the maximum resources the revocable tasks can use is 10% of the reservation, i.e. mem:100 disk:100 For cpu, it will use revocable resources.
Used in: