DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
Page History
...
8) storage.cleanup.interval: The interval (in seconds) to wait before running the storage cleanup thread
API Changes:
Instead of over loading the present createZone API and updateZone API a new API is introduced say "UpdateZoneLevelParamter API".
During the creation of zone default values for these parameters will be set in the data_center_details table.
These can be updated using the "updateZoneLevelParamter" API each at a time by sending the name value pair with zone id.
...
API Name
...
API Parameters
...
API response
...
updateZoneLevelParamters
...
Schema:
We will add the name value pairs of these zone level parameters in the data_center_details table*.*
...
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
Here we introduce new API called updateClusterLevelParameter to update the cluster level parameters. During the cluster creation time default values will be set to these parameters, later we can use this API to modify the value as per needed for each cluster.
...
API Name
...
API Paramerters
...
API Response
...
updateClusterLevelParameters
...
Schema:
We will add the name value pairs of these cluster level parameters in the cluster_details table as key value pairs*.*
...
2) remote.access.vpn.client.iprange: The range of ips to be allocated to remote access vpn clients. The first ip in the range is used by the VPN server
Here we introduce new API called updateAccountLevelParameter. During the account creation time default values will be set to these parameters, later we can use this API to modify the value as per needed for each account.
...
API Name
...
API Parameters
...
API Response
...
updateAccountLevelParameters
...
Schema:
We will add the name value pairs of these account level parameters in the account_details table as key value pairs*.*
...
Here we introduce new API called updateStorageLevelParameter. During the addition of storage pool default values will be set to these parameters, later we can use this API to modify the value as per needed for each storage.
Schema:
We will add the name value pairs of these storge level parameters in the storage_pool_details table as key value pairs*.*
API Changes
We use existing updateConfugration and listConfguration APIs to update/list the configuration parameters at any level (Global/zone/cluster/pool/account).
We introduce two additional parameters scope, id.
- If scope is not mentioned then it is considered to update/list the global configuration.
- If scope is given with value zone/cluster/pool/account it considers at the specific level and update/list the corresponding parameter at that level.
- When updating the parameter with given scope, first it validates the scope of the parameter
- 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.
API name | Existing API Parameters | New additional API Parameters | API Response |
|---|---|---|---|
updateStorageLevelParameters updateConfiguration | id name: UUID of the storage pool |
Schema:
...
scope: scope(zone/cluster/pool/account) of the parameter that needs to be updated | updateconfigurationresponse with scope and updated value | ||
listConfiguration | category: lists configurations by category | scope: scope(zone/cluster/pool/account) of the parameter that needs to be updated | listconfigurationsresponse with scope and value at the corresponding scope of the parameter. |
Here are the global config parameters and their proposed granularity.
...
Overview
Content Tools