Global Config Parameter changes

High level requirement

There are some global configuration parameters that some users want it to be more granular.

User Requested Changes:

Parameter

Priority

Granularity

CPU/Memory/Storage Notification and Capacity Thresholds

P1

Per Cluster

Storage Limit per Pool

P1

Per Zone

Oversubscription Ratio

P1

Per Zone

Local Storage support

P1

Per Zone

VM Allocation Algorithm

P1

Per Zone

VR Network Throttling Rate

P1

Per Zone

Router Template ID

P2

Per Zone

Guest Domain Prefix

P2

Per Zone

External DNS Usage

P2

Per Zone


Another User Requested Changes:

Global Variable

Proposed Change

Default Value

Applicable

Description

allow.public.user.templates

Per Account, overrides the global, e.g. for resellers not end customers

true

 

If false, users will not be able to create public templates.

capacity.skipcounting.hours

per cluster, overrides global

3600

resource reclaiming impacts allocation

Time (in seconds) to wait before release VM's cpu and memory when VM in stopped state

cpu.capacity.threshold

per cluster, overrides global

0.85

Alerting

Percentage (as a value between 0 and 1) of cpu utilization above which alerts will be sent about low cpu available.

max.account.snapshots

Offer additional parameter, link to sec storage capacity, per account

20

 

The default maximum number of snapshots that can be created for an account

max.account.templates

As per snapshots, ensure it includes ISOs

20

 

The default maximum number of templates that can be deployed for an account

max.account.user.vms

n/a

20

 

The default maximum number of user VMs that can be deployed for an account

max.account.volumes

This should refer to data vols, sys vols should be inherent from user VMs

20

 

The default maximum number of volumes that can be created for an account

max.template.iso.size

per account, also limited by sec storage - see snapshots, templates. So perhaps a new global/per account setting for max sec storage

50

 

The maximum size for a downloaded template or ISO (in GB).

mem.overprovisioning.factor

per cluster, overrides global

1

 

Used for memory overprovisioning calculation

network.gc.interval

per cluster, overrides global

600

Network Cleanup

Seconds to wait before checking for networks to shutdown

network.gc.wait

per cluster, overrides global

600

Network Cleanup

Time (in seconds) to wait before shutting down a network that's not in used

network.redundantrouter

Per Account (also per project?), overrides the global or via network offering

false

redundant router

enable/disable redundant virtual router

network.throttling.rate

Per Account (also per project?), overrides the global or via network offering

200

Network Setting

Default data transfer rate in megabits per second allowed in network. On V Router

ping.interval

per cluster, per AZ - possible "long distance" Azs (variable latencies)

60

Network Health Check

Ping interval in seconds

ping.timeout

per cluster, per AZ - possible "long distance" Azs (variable latencies)

2.5

Network Health Check

Multiplier to ping.interval before announcing an agent has timed out

remote.access.vpn.client.iprange

Per Account, overrides the global

10.1.2.1-10.1.2.8

VPN Setting

The range of ips to be allocated to remote access vpn clients. The first ip in the range is used by the VPN server

remote.access.vpn.psk.length

Per Account, overrides the global

24

VPN Setting

The length of the ipsec preshared key (minimum 8, maximum 256)

remote.access.vpn.user.limit

Per Account, overrides the global

8

VPN Setting

The maximum number of VPN users that can be created per account

snapshot.max.daily

Usage to count against sec storage usage, as per max.account.snapshots comment

8

?

Maximum daily snapshots for a volume

snapshot.max.hourly

Usage to count against sec storage usage, as per max.account.snapshots comment

8

?

Maximum hourly snapshots for a volume

snapshot.max.monthly

Usage to count against sec storage usage, as per max.account.snapshots comment

8

?

Maximum monthly snapshots for a volume

snapshot.max.weekly

Usage to count against sec storage usage, as per max.account.snapshots comment

8

?

Maximum weekly snapshots for a volume

storage.cleanup.interval

Per AZ, eg for Private/Reseller AZ to offer differing storage service

86400

Storage Cleanup

The interval (in seconds) to wait before running the storage cleanup thread.

cpu.overprovisioning.factor

per cluster, overrides global

1

 

Used for CPU overprovisioning calculation; available CPU will be (actualCpuCapacity * cpu.overprovisioning.factor)

storage.overprovisioning.factor

per storage (per sysvol/datavol usage), overrides global

1

Availability Zones

[NFS ONLY] Used for storage overprovisioning calculation; available storage will be (actualStorageSize * storage.overprovisioning.factor)

use.user.concentrated.pod.allocation

per cluster, per account additional granularity to override global

true

Allocation algorithm

If true, deployment planner applies the user concentration heuristic during VM resource allocation

vm.allocation.algorithm

per cluster, per account additional granularity to override global

random

Allocation algorithm

If 'random', hosts within a pod will be randomly considered for VM/volume allocation. If 'firstfit', they will be considered on a first-fit basis.

vmware.root.disk.controller

Don't overrride what is in the template!

ide

Availability Zones

Specify the default disk controller for root volumes, valid values are scsi, ide


  • No labels