Versions Compared

Old Version 25

changes.mady.by.user Harikrishna Patnala

Saved on

compared with

New Version 26

changes.mady.by.user Harikrishna Patnala

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

2) pool.storage.capacity.disablethreshold: Percentage (as a value between 0 and 1) of storage utilization above which allocators will disable using the pool for low storage available

3) VM Allocation Algorithmvm.allocation.algorithm: 'random', 'firstfit', 'userdispersing', 'userconcentratedpod_random', 'userconcentratedpod_firstfit' : Order in which hosts within a cluster will be considered for VM/volume allocation

...

4) cluster.memory.allocated.capacity.notificationthreshold: Percentage (as a value between 0 and 1) of memory utilization above which alerts will be sent about low memory available

5) cluster.storage.allocated.capacity.notificationthreshold: Percentage (as a value between 0 and 1) of allocated storage utilization above which alerts will be sent about low storage available

6) cluster.storage.capacity.notificationthreshold: Percentage (as a value between 0 and 1) of storage utilization above which alerts will be sent about low storage available

Schema:

We will add the name value pairs of these cluster level parameters in the cluster_details table as key value pairs*.*

...

We use existing updateConfugration and listConfguration APIs to update/list the configuration parameters at any level (Global/zone/cluster/pool/account).

We introduce two 4 additional parameters scope, idcorresponding to 4 scopes(zone/cluster/storagepool/account).

 - If scope id is not mentioned then it is considered to update/list the global configuration.

 - If scope is given with value id of zone/cluster/pool/account id given, then it considers at the specific level and update/list the corresponding parameter at that level.

 - When updating the parameter with given scopeid, first it validates the scope of the parameter corresponding to the id provided.

 - checks the resource details table and updates there, if not present then will fetch from the global configuration parameters and create entry in the details table.

- If the value is set to null at a particular scope then it means to use the global value.

API name

Existing API Parameters

New additional optional API Parameters

API Response

updateConfiguration

name: the name of the configuration
value: the value of the configuration

zoneid: ID of the zone
clusterid: ID of the cluster
storagepoolid: ID of the storagepool
accountid: ID of the acount

updateconfigurationresponse with scope and updated value 

listConfiguration

category: lists configurations by category
name: lists configuration by name

zoneid: ID of the zone
clusterid: ID of the cluster
storagepoolid: ID of the storagepool
accountid: ID of the acount

listconfigurationsresponse with scope and value at the corresponding scope of the parameters.

...