Skip to content

Guidelines for resource pool permissions

Zenoss recommends that multi-host Resource Manager deployments include separate Control Center resource pools for the following host or groups of hosts:

  1. The Control Center master host
  2. Control Center delegate hosts for the most or all Resource Manager services
  3. Control Center delegate hosts for remote collectors (may be multiple pools)

Pools one and two require distributed file system (DFS) and administrative permissions. Pool three requires neither.

From the serviced CLI, the command that displays information about pools uses integers to summarize the permissions associated with a resource pool. The following table associates the values with the permissions they represent.

Value Definition
0 No permissions
1 Administrative permission
2 DFS access permission
3 Both permissions

Setting permissions on resource pools

Use this procedure to set permissions on a resource pool.

  1. Log in to the master host as a user with serviced CLI privileges.

  2. Display the list of resource pools and their permissions.

    serviced pool list -v | grep -E 'ID|Permissions'
    

    Example result on a deployment with four resource pools:

    "ID": "default",
    "Permissions": 3,
    "ID": "rm_pool",
    "Permissions": 3,
    "ID": "2",
    "Permissions": 0,
    "ID": "3",
    "Permissions": 0,
    
  3. Optional: Remove DFS access permission from a pool.

    If you intend to remove both DFS access and administrative access permissions from a resource pool, you must remove DFS access permissions first.

    Replace Pool-Name with the name of a resource pool:

    serviced pool set-permission --dfs=false Pool-Name
    
  4. Optional: Remove administrative permission from a pool.

    If you intend to remove both DFS access and administrative access permissions from a resource pool, you must remove DFS access permissions first.

    Replace Pool-Name with the name of a resource pool:

    serviced pool set-permission --admin=false Pool-Name