Closed hassenius closed 5 years ago
Here is the new configuration for ICP 3.1.1
#################################
##### ICP Instance details ######
#################################
variable "master" {
type = "map"
default = {
nodes = "1"
vcpu = "8"
memory = "16384"
disk_size = "" # Specify size or leave empty to use same size as template.
docker_disk_size = "100" # Specify size for docker disk, default 100.
datastore_disk_size = "50" # Specify size datastore directory, default 50.
datastore_etcd_size = "50" # Specify size etcd datastore directory, default 50.
thin_provisioned_etcd = "" # True or false. Whether to use thin provisioning on the disk. Leave blank to use same as template
thin_provisioned = "" # True or false. Whether to use thin provisioning on the disk. Leave blank to use same as template
eagerly_scrub = "" # True or false. If set to true disk space is zeroed out on VM creation. Leave blank to use same as template
keep_disk_on_remove = "false" # Set to 'true' to not delete a disk on removal.
start_iprange = "" # Leave blank for DHCP, else masters will be allocated range starting from this address
}
}
variable "proxy" {
type = "map"
default = {
nodes = "1"
vcpu = "2"
memory = "4096"
disk_size = "" # Specify size or leave empty to use same size as template.
docker_disk_size = "100" # Specify size for docker disk, default 100.
thin_provisioned = "" # True or false. Whether to use thin provisioning on the disk. Leave blank to use same as template
eagerly_scrub = "" # True or false. If set to true disk space is zeroed out on VM creation. Leave blank to use same as template
keep_disk_on_remove = "false" # Set to 'true' to not delete a disk on removal.
start_iprange = "" # Leave blank for DHCP, else proxies will be allocated range starting from this address
}
}
variable "worker" {
type = "map"
default = {
nodes = "1"
vcpu = "4"
memory = "16384"
disk_size = "" # Specify size or leave empty to use same size as template.
docker_disk_size = "100" # Specify size for docker disk, default 100.
thin_provisioned = "" # True or false. Whether to use thin provisioning on the disk. Leave blank to use same as template
eagerly_scrub = "" # True or false. If set to true disk space is zeroed out on VM creation. Leave blank to use same as template
keep_disk_on_remove = "false" # Set to 'true' to not delete a disk on removal.
start_iprange = "" # Leave blank for DHCP, else workers will be allocated range starting from this address
}
}
variable "management" {
type = "map"
default = {
nodes = "1"
vcpu = "8"
memory = "16384"
disk_size = "" # Specify size or leave empty to use same size as template.
docker_disk_size = "100" # Specify size for docker disk, default 100.
log_disk_size = "50" # Specify size for /opt/ibm/cfc for log storage, default 50
thin_provisioned = "" # True or false. Whether to use thin provisioning on the disk. Leave blank to use same as template
eagerly_scrub = "" # True or false. If set to true disk space is zeroed out on VM creation. Leave blank to use same as template
keep_disk_on_remove = "false" # Set to 'true' to not delete a disk on removal.
start_iprange = "" # Leave blank for DHCP, else workers will be allocated range starting from this address
}
}
variable "management" {
type = "map"
default = {
nodes = "1"
vcpu = "4"
memory = "8192"
disk_size = "" # Specify size or leave empty to use same size as template.
docker_disk_size = "100" # Specify size for docker disk, default 100.
log_disk_size = "50" # Specify size for /opt/ibm/cfc for log storage, default 50
thin_provisioned = "" # True or false. Whether to use thin provisioning on the disk. Leave blank to use same as template
eagerly_scrub = "" # True or false. If set to true disk space is zeroed out on VM creation. Leave blank to use same as template
keep_disk_on_remove = "false" # Set to 'true' to not delete a disk on removal.
start_iprange = "" # Leave blank for DHCP, else workers will be allocated range starting from this address
}
}
I'll will do a new PR now that fix this for us.
As of ICP 3.1 PODs have been more appropriately scoped with resource requests and limits. If minimum resource requirements as specified in https://www.ibm.com/support/knowledgecenter/SSBS6K_3.1.0/supported_system_config/hardware_reqs.html are not met, deployment will fail as PODs will not be scheduled