After successfully configuring your VM Auto Scaling Groups, you can modify scaling thresholds and scaling policies, update replica configuration or associate an ALB via the VM Auto Scaling Manager.
To modify the values, follow these steps:
Log in to DCD with your username and password.
Go to Menu > Management > VM Auto Scaling.
Click on the respective group to modify its values.
You can modify the following:
click Configuration to update the name of the group, modify scaling thresholds and policies.
Note: You cannot modify a DCD after it is associated with the group.
click Replica Configuration to update storage settings, NICs and associated ALBs, or storage volumes.
click Servers to view the servers that are associated with the group.
click Jobs to view the list of tasks.
Click Save to save the changes.
Result: The corresponding VM Auto Scaling Group is successfully modified.
In the Replica Configuration tab, you can configure the size, networks, and storage volumes for the VM instances that VM Auto Scaling creates. You may also use the CloudInit mechanism to configure VM instances.
You can configure the following on the Replica Configuration tab:
Note:
Certain limitations listed on this page apply during the deployment and are subject to change as the product evolves.
During the EA phase, it is possible to delete replicas manually. Manual deletion of replicas does not remove the IP address of the replica from the Targets list (Network > Target Groups > select a Target Group and click Targets); ensure that you remove them manually from the Targets list before you delete the associated replica.
To configure VM replica settings, follow these steps:
Go to the Replica Configuration tab in the Create VM Auto Scaling Group window and configure the Settings, Network, and Volumes tabs.
Click Clone Settings and Volumes from the drop-down list to clone the CPU Architecture, Cores, and RAM automatically from your VMs in the VDC. You can also use the slider to configure them manually.
You can configure the network connection between a VM instance and a virtual network using a . You can create a NIC instantly by clicking +Add and associating it with a . VDC automatically creates an IP address for the associated NIC. By associating a NIC with a LAN, you define the networking features for the respective VM Auto Scaling Group. If you have already defined NICs, select one from the drop-down list.
Name: Enter a name for the NIC.
DHCP: Select the checkbox to provision IP addresses for your VM instances.
LAN: Enter the LAN ID to be used for accessing the VM instances on the network.
Firewall active: Select the checkbox to activate the firewall. By default, an active firewall without defined rules blocks all incoming network traffic except for the rules that explicitly allow specific protocols, IP addresses, and ports.
Firewall Type: Select Ingress, Egress, or Bidirectional to choose firewall rules for the type of queries that will be allowed on the NIC. By default, Ingress is used if you do not specify a value.
Firewall Rules: Click Manage Rules to allow managing requests from external networks. When configured, all firewall rules defined for the specified NIC are listed.
Flow Logs: Select a flow log from the drop-down list to log all network packets. The list of all flow logs for the specified NIC is displayed. You can instantly create a new flow log, if necessary.
Note: During the EA phase, Flow Logs are not supported. If you apply a configuration, the creation of VM Auto Scaling Groups will fail.
VM Auto Scaling creates VM instances based on the specified storage volumes during scaling.
Name: Enter a name for the storage volume.
Boot device: Select a value from the drop-down list to use the corresponding volume as a boot volume. You can select one of these values:
Choose Auto to allow VDC to delegate the provisioning engine to select the boot volume automatically.
Choose Primary to set the configured volume as a boot volume.
Choose None if you do not want to configure a boot volume.
Note: You can either set one volume to Primary or set all volumes to Auto.
Bus: Select a driver from the drop-down list. The predefined values are VIRTIO and IDE.
Storage Type: Select either HDD, SSD Premium or SSD Standard from the drop-down list to configure the type of storage. IONOS provides three different types of disks and you can choose to attach either of these to the VM Auto Scaling Group.
Size in GB: Specify the size of the selected storage type.
Image: Select either an Image or an Image Alias from the drop-down list to associate it with a VM Auto Scaling Group. A Password is mandatory to configure either of these. You can also associate the following with the storage volume:
SSH keys: Select the checkbox to use the SSH keys to validate the request and create an encrypted connection for communication.
Cloud-Init User Data: Click No configuration to specify the user data (Cloud-Init) for this replica volume.
Backup Unit: Select a backup unit from the drop-down list, if already configured. Otherwise, you can create one instantly. Backups of VM instances are stored in the associated backup unit regularly.
Important: The VM Auto Scaling feature creates replicas based on the configuration. Changes to the existing configuration will only apply to new replicas but not the instances that are already running. Hence, we recommend that you configure Settings, Network, and Volumes before clicking Create to avoid any discrepancies later.
Click Create to configure your VM Auto Scaling Group.
Result: Your VM Auto Scaling Group is successfully configured and can be managed via the VM Auto Scaling Manager.
When you associate an ALB with a replica configuration, the ALB can use all of the VM replicas created by the VM Auto Scaling feature, which means your application can scale and receive requests from different queries based on the configured ALB.
To associate an ALB with a replica configuration, go to the Replica Configuration tab in the Create VM Auto Scaling Group window and specify the following:
Target Group: Select a value from the drop-down list. You can also click Create new Target Group from the drop-down list to instantly create a new target group. When you specify a target group, the scaling process associates replicas with the target groups. The ALB checks these target groups to verify the available IP addresses to process requests.
Note: You cannot delete a target group if it is associated with the replica of the VM AutoScaling group and in use. We recommend deleting the AutoScaling group first before deleting the target group.
Port: Select a value from the drop-down list to decide the port on which the queries must be redirected. It is recommended to set the port to TCP port 80. This port is used by the ALB to distribute traffic to individual replicas.
Weight: The traffic is distributed proportionally to the target weight, which is the ratio of the total weight of all targets. A target with a higher weight receives a larger share of traffic. The valid range is from 1 to 256. We recommend using values in the middle range to leave room for later adjustments.
Note:
Note: During the EA phase, we recommend using the DHCP feature from IONOS to advertise the assigned IPs to the network; otherwise, detection within the may not work as expected.
. You can also associate an ALB after configuring replicas.
An from the VDC can be associated with the replica configuration. As a result, a replica can be linked to multiple target groups if a target group contains several NICs. This way an ALB ensures that the load is equally distributed among the replicas.
If you have not already configured an ALB, log in to the DCD with your username and password, drag-and-drop the Application Load Balancer from the Palette on the left side of the screen into your VDC to start configuring it. For more information about connecting your target group to an ALB, see .
It is mandatory to define at least one network before you configure an ALB, so you can associate an ALB with the group after .
The VM Auto Scaling Manager displays the list of all servers associated with the selected VM Auto Scaling Group. Each server is given a unique identification string as its name automatically.
Note: The unique identification string is a name and not a server ID. Hence, it cannot be used to retrieve information over the API.
To view the associated servers, follow these steps:
Log in to DCD with your username and password.
Go to Menu > Management > VM Auto Scaling.
Click Servers to view one of these:
click Console to open the remote console to access your VM.
clicking Focus Server opens the VDC and preselects the server automatically.
VM Auto Scaling Groups are a collection of virtual servers that automatically scale the number of VM replicas based on the metrics.
Note:
This process is limited to contract owners, administrators, and users with access rights to the data center hosting the VM Auto Scaling Group.
Configuration of a VM Auto Scaling Group triggers the creation of two monitoring alarms for scale in and scale out operations according to the policy settings.
Prerequisites:
When provisioning a VM Auto Scaling Group, ensure that the necessary resources are available and that they are within the configured resource limits of your contract. To check the contract resource limits in DCD, see Resource Overview.
IONOS recommends that you enable CloudInit or use existing images.
Follow these steps to configure a VM Auto Scaling , and define thresholds and scaling policies:
1. Log in to DCD with your username and password.
2. Go to Menu > Management > VM Auto Scaling.
3. Click Create to create a group and define replicas. The Create VM Auto Scaling Group window displays the Configuration and the Replica Configuration tabs.
4. Define the following in the Configuration tab:
5. Configure replicas. For more information, see Configure replicas.
Important: The application applies a default replica setup if you do not configure replicas. Hence, we recommend that you configure replicas before you click Create. It is also mandatory, as the ALB uses the IP addresses of the NICs linked to the VM instances. Provisioning the replica defaults does not configure a network, thus, the associated ALB is left without NICs or IP addresses.
6. Click Create to save the configuration.
Result: Your VM Auto Scaling Group is successfully configured. You can now manage it via the VM Auto Scaling Manager.
You can specify a name for your VM Auto Scaling Group and the minimum number and the maximum number of VM instances it can contain during scaling. The minimum number ensures that you never run out of VM instances and the group always has at least one VM instance. The feature cannot provide more than the maximum number of VM instances during a scale out operation.
To create a VM Auto Scaling Group, go to the Configuration tab in the Create VM Auto Scaling Group window and specify the following:
Name: Enter a name for the VM Auto Scaling Group.
Data Center: Select a data center from the drop-down list. You can either select an existing Virtual Data Center (VDC) or create a new one if required. The application lists all the VDCs in your DCD. The group is valid only within the selected VDC to which it belongs.
Minimum Count: Enter the minimum number of VMs the group must scale to. The minimum replica count is one. VM Auto Scaling uses this as a reference value to stop deleting VM instances for a group. This is necessary to ensure that scaling does not reduce the VM instances beyond the specified count.
Maximum Count: Enter the maximum number of VMs the group must scale to. VM Auto Scaling uses this as a reference value to stop adding new VM instances for a group. This is necessary to ensure that scaling does not increase beyond the specified count. To improve the efficiency of the VM Auto Scaling service, we recommend limiting the maximum number of VMs in an Auto Scaling Group to 100 or less.
A Policy defines the rules to trigger VM Auto Scaling to analyze the resource utilization rate at regular intervals. You can only define one metric policy per group that triggers the scaling process.
To define policies, go to the Configuration tab in the Create VM Auto Scaling Group window and specify the following:
Metric: Select a metric from the drop-down list whose performance must be monitored. The pre-defined values are based on the CPU utilization average or network bytes for incoming and outgoing bytes or packets.
Scale In Threshold: Enter a value to specify when VM Auto Scaling must trigger the scale in operation. The value specified here indicates the percentage of the CPU utilization rate or the network packets or network bytes, based on which the scale in action is triggered for the metric. For example, if you specify the CPU utilization rate as 30, VM Auto Scaling automatically begins scaling inwards and deletes the additional VM instances when the CPU utilization rate is 30%.
Scale Out Threshold: Enter a value to specify when VM Auto Scaling must trigger the scale out operation. The value specified here indicates the percentage of the CPU utilization rate or the network packets or bytes based on which the scale-out action is triggered for the metric. For example, if you specify the value as 70, the application automatically begins scaling outwards and adds additional VM instances when the CPU utilization rate reaches 70%.
Note: Ensure that the Scale In Threshold and the Scale Out Threshold field values differ by 40%. For example, if you set the Scale In Threshold to 15%, Scale Out Threshold cannot contain a value lesser than 55%.
Range: Enter a time range in hours, minutes, or seconds. Example: 1h, 3m, 120s. It is the period during which VM Auto Scaling measures the percentage of chosen metric utilization at regular intervals and automatically scales in or scales out based on the demand. If specifying in seconds, ensure that the value is not less than 120 seconds.
Unit: Select a unit from the drop-down list. You can specify whether the scaling process should be initiated every hour, minute, or second for other predefined metrics. This is automatically set to Total for an instance CPU utilization average metric.
Scale in defines the action triggered during a scale in operation. Based on the values defined, the feature automatically deletes the specified number of VM instances after the cooldown period.
To define scale in policies, go to the Configuration tab in the Create VM Auto Scaling Group window and specify the following:
Amount Type: Select a value from the drop-down list to define the number of replicas that must be deleted. You can choose either Percentage or Absolute.
Amount: Enter the number of VM instances to be deleted during a scale in operation. The minimum value is one. Scale in jobs with a large number of VMs may encounter performance issues. Hence, we recommend limiting the deletion of VMs to at most five, regardless of whether the Amount Type is absolute or percentage.
Cooldown Period: Enter the cooldown period to indicate the interval between each auto scaling action in the group. The cooldown period can be measured in minutes, seconds, or hours. For example, when the value is set to 5m, the scale in action is activated every 5 minutes. VM Auto Scaling automatically deletes the given number of VM instances when the resource consumption is lower.
Note:
Only one scaling action remains in progress for a VM Auto Scaling Group. The metric is reevaluated after the current scaling action completes.
The minimum value is two minutes, and the maximum value is 24 hours.
If specifying in seconds, ensure the minimum value is not less than 120 seconds.
The application considers the default value of five when a period is not specified.
Termination Policy: Select a value from the drop-down list to choose whether the oldest or the most recent replica must be deleted first. Choosing the Oldest replica first delegates the scaling process to delete the oldest replicas. Otherwise, choose the Youngest replica first to begin scaling by deleting the most recent replica.
Delete attached volumes: Select a value from the drop-down list to indicate if the attached volumes must be deleted. Choose Don’t delete to retain the attached volumes; otherwise, choose Delete.
Scale out defines the action triggered during a scale out operation. The feature automatically adds the specified number of VM instances after the cooldown period based on the demand.
To define scaling out policies, go to the Configuration tab in the Create VM Auto Scaling Group window and specify the following:
Amount Type: Select a value from the drop-down list to define the number of replicas added when the metric utilization exceeds the specified amount. You can choose either Percentage or Absolute.
Amount: Enter a number to indicate the number of VM instances that must be added. The minimum value is one. Scale out jobs with a large number of VMs may encounter performance issues. Hence, we recommend limiting the addition of VMs to at most five, regardless of whether the Amount Type is absolute or percentage.
Cooldown Period: Enter the cooldown period to indicate the interval between each auto scaling process in the group. The cooldown period can be measured in minutes, seconds, or hours. For example, when the value is set to 5m, the scale out process is activated every 5 minutes. VM Auto Scaling automatically adds the given number of VM instances when the resource consumption is higher. The notes mentioned in scale in policies are also applicable to scale out policies.
Deletion of a VM Auto Scaling Group results in the deletion of all the VMs associated with the respective group.
To delete a group, follow these steps:
Log in to DCD with your username and password.
Go to Menu > Management > VM Auto Scaling.
Click Delete to delete the selected group.
Select the checkbox to confirm deletion.
Enter your Password to proceed with the deletion process.
Select the Skip password verification for the next 60 minutes checkbox if you want to avoid specifiying your password for any operation during the next 60 minutes.
Click OK.
Result: The application deletes the selected VM Auto Scaling Group and the associated VMs, if any.
You can configure VM Auto Scaling via DCD. This feature combines granular configurable options wherein you can create a group and define when the feature must scale in or scale out based on demand. You must also specify the minimum (for scale out) and the maximum (for scale in) number of replicas a group can contain for the replicas to stay within the given threshold.
Configure replicas after configuring thresholds and policies, where you define the settings, network, and storage volumes for the replicas created by the feature. After you define the network, you may add an Application Load Balancer (ALB) to the group.
After successfully creating a group, you can modify its details, delete it, and view its associated servers and list of jobs.
The following links redirect you to the relevant pages.
Configure a VM Auto Scaling group and define group-wide policies for scaling.
Configure storage size, networks, and storage volumes for the VM instances. You can also associate an Application Load Balancer (ALB) with the group.
Modify the group name and scaling policies.
Delete an existing VM Auto Scaling group.
View the servers associated with the group.
View the list of scaling operations.
The scale in and scale out operations performed by the VM Auto Scaling feature are displayed in a chronological order.
To view the list of operations and their statuses, follow these steps:
Log in to DCD with your username and password.
Go to Menu > Management > VM Auto Scaling.
Click on the corresponding VM Auto Scaling Group to view its status. The application displays the following information:
The Status of a job indicates whether it is completed successfully, in progress, or failed.
An Action indicates if the feature scaled in (deleted) or scaled out (added) VM instances.
The Timestamp provides the date and time when the process began.
