|Administration Guide / Operations|
For most production deployments, we recommend that you use a configuration management tool. Customers have been successful deploying using the following:
This section describes the most commonly applied post-install customizations and the issues they pose:
Over-subscription refers to the practice of expanding your computer beyond its limits. Over-subscription applies only to node controllers. You may modify disks and cores to allow enough usage buffer for your instance.
|NC_WORK_SIZE||Defines the amount of disk space available for instances to
Defaults to 1/3 of the currently available disk space on the NC, and NC_CACHE_SIZE defaults to the other 2/3.
|NC_CACHE_SIZE||Defines how much disk space is needed for images to be cached.|
|MAX_CORES||Defines the maximum number of cores that can be provided to VMs on each NC. If it is 0 or not present, then the only limit on the number of instances is the number of cores available on the NC. If it is present, any value greater than 256 is treated as 256.|
You can modify the default by adding network IPs to your cloud or changing your network from Managed to EDGE mode. Changing these values do not require shutting down the whole system.
To add network IPs:
You can modify the default network from Managed to EDGE networking mode.
You can change the following reporting and CloudWatch properties:
|cloud.monitor.default_poll_interval_mins||This is how often the CLC sends a request to the CC for sensor data. Default value is 5 minutes. If you set it to 0 = no reporting. The more often you poll, the more hit on system performance.|
|reporting.default_write_interval_mins||How often polled data is written to the database.|
|cloud.monitor.history_size||This is how many data value samples are sent in each sensor data request. The default value is 5. How many samples per poll interval.|
|cloudwatch.disable_cloudwatch_service||Disables CloudWatch when set to true.|