acronis.com Acronis Cyber Infrastructure 4.
Table of contents About this guide 4 Logging in to the self-service panel 5 Managing notifications 6 Managing users and projects Creating users 10 Assigning users to projects 11 Viewing project quotas 13 Managing compute resources Managing virtual machines 15 15 Supported guest operating systems 15 Creating virtual machines 16 Connecting to virtual machines 23 Managing virtual machine power state 23 Attaching ISO images to virtual machines 24 Reconfiguring virtual machines 24 Monit
Preparing templates Managing volumes 58 Creating and deleting volumes 58 Attaching and detaching volumes 59 Resizing volumes 60 Changing volume redundancy 60 Creating images from volumes 61 Cloning volumes 61 Managing volume snapshots 62 Managing virtual networks 64 Managing virtual routers 67 Managing router interfaces 69 Managing static routes 72 Managing floating IP addresses 73 Managing load balancers 74 Managing balancing pools Managing SSH keys 3 52 79 80 © Acronis Inte
About this guide This guide is intended for domain administrators and project members and explains how to manage project users and compute resources using the self-service panel.
Logging in to the self-service panel To log in to the self-service panel 1. Visit the panel’s IP address on port 8800. 2. Enter your domain name (case sensitive) as well as user name and password. Alternatively, if you are given the link to the self-service panel for a specific domain, you will only need to provide the user name and password.
Managing notifications The notification center stores and shows notifications about recent tasks of the current user in the management panel. Notifications are displayed only for tasks performed during the current user session and cleared out when the user logs out. A user is informed about each task by a pop-up notification in the bottom right corner. The same notification also appears in the notification center. After the pop-up window is closed, the notification is available in the notification center.
Next to the bell icon, you can see the notification counter, or the loading sign if you have a running task. To configure notifications 1. On any screen, click the bell icon in the top right corner. 2.
notification center. To clear notifications 1. On any screen, click the bell icon in the top right corner. 2. To clear only one notification, click the cross icon next to it. 3. To clear all of the notifications, click Clear all above the notification list. To mute notifications 1. On any screen, click the bell icon in the top right corner. 2. Click the cogwheel icon, and then turn on the Do not disturb mode. The bell icon will be greyed out, and the notification counter will disappear.
© Acronis International GmbH, 2003-2021
Managing users and projects In the self-service panel, you can create users and assign them to projects within a domain. When you create a user, you select its role. A user can be assigned one of the following roles: l A domain administrator can manage virtual objects in all projects within the assigned domain as well as project and user assignment in the self-service panel. l A project member acts as a project administrator in a specific domain in the self-service panel.
Assigning users to projects Domain administrators can manage project members’ assignment on the Projects and Users screens. To assign a user to a project l On the Projects screen 1. Click the project to which you want to assign users (not the project name). 2. On the project panel, click Assign members. 3. In the Assign members window, choose one or multiple users to assign to the project. Only user accounts with the Project member role are displayed.
l On the Users screen 1. Click the user account with the Project member role whom you want to assign to the project. 2. On the user panel, click Assign to project. 3. On the Assign user to projects window, select one or multiple projects, and then click Assign. To unassign a user from a project l On the All projects screen: 1. Click the project to unassign users from. 2. On the project panel, open the Members tab. 3. Click the cross icon next to a user you want to unassign.
l On the All users tab: 1. Click the user to unassign from the project. 2. On the user panel, open the Projects tab. 3. Click the cross icon next to the project from which you want to unassign the user. Viewing project quotas Each project is allocated a certain amount of compute resources by means of quotas. Domain administrators can view project quotas on the project details screen.
Open Projects, click the desired project in the list, and then switch to the Quotas tab.
Managing compute resources Managing virtual machines Each virtual machine (VM) is an independent system with an independent set of virtual hardware. Its main features are the following: A virtual machine resembles and works like a regular computer. It has its own virtual hardware. l Software applications can run in virtual machines without any modifications or adjustment. Virtual machine configuration can be changed easily, for example, by adding new virtual disks or l memory.
Version Windows Server Edition CPU hot plug RAM hot plug support support Standard, Datacenter Yes Yes Standard, Datacenter No No Home, Professional, Enterprise, Enterprise No No 2012 Windows Server 2008 R2 Windows 10 2016 LTSB Windows 8.1 Home, Professional, Enterprise No No Windows 7 Home, Professional, Enterprise No No * CPU hot plug does not work properly due to a Windows bug with a wrongly installed driver. To fix the issue, refer to this solution.
3. Select the VM boot media: l If you have an ISO image or a template a. Select Image in the Deploy from section, and then click Specify in the Image section. b. In the Images window, select the ISO image or template, and then click Done. l If you have a compute boot volume a. Select Volume in the Deploy from section, and then click Specify in the Volumes section. b. In the Volumes window, click Attach. c. In the Attach volume window, find and select the volume, and then click Attach.
b. [Optional] Add more disks to the VM by creating or attaching volumes. To do this, click the pencil icon in the Volumes section, and then Add or Attach in the Volumes window. c. Select volumes that will be removed during the VM deletion. To do this, click the pencil icon in the Volumes section, click the ellipsis icon next to the needed volume, and then Edit. Enable Delete on termination and click Save. d. When you finish configuring the VM disks, click Done. 5.
l If you selected a virtual network with enabled IP address management In this case, spoofing protection is enabled and the default security group is selected by default. This security group allows all incoming and outgoing traffic on all the VM ports. If required, you can select another security group or multiple security groups. To disable spoofing protection, clear all of the check boxes and turn off the toggle switch. Security groups cannot be configured with disabled spoofing protection.
After specifying the network interface parameters, click Add. The network interface will appear in the Network interfaces list. c. [Optional] If required, edit IP addresses and security groups of newly added network interfaces. To do this, click the ellipsis icon, click Edit, and then set the parameters. d. When you finish configuring the VM network interfaces, click Done. 7.
l Add an SSH key to the VM, to be able to access it via SSH without a password. In the Select an SSH key window, select an SSH key and then click Done. l Add user data to customize the VM after launch, for example, change a user password. Write a cloud-config or shell script in the Customization script field or browse a file on your local server to load the script from.
To inject a script in a Windows VM, refer to the Cloudbase-Init documentation. For example, you can set a new password for the account using the following script: #ps1 net user 8. [Optional] Enable CPU and RAM hot plug for the VM in the Advanced options, to be able to change its flavor when the VM is running. You can also enable hot plug after the VM is created. Note If you do not see this option, CPU and RAM hot plug is disabled in your project.
Connecting to virtual machines Prerequisites l Virtual machines are created, as described in "Creating virtual machines" (p. 16). l To be able to connect via SSH, the virtual machine must have cloud-init and OpenSSH installed. To connect to a virtual machine via the VNC console Select a VM, and then click Console on its right pane. The console will open in a separate browser window.
Attaching ISO images to virtual machines You can attach ISO images to running or stopped virtual machines, for example, to install additional software inside them or to restore their operating system in the rescue mode. To attach an ISO image, you need to convert it to a volume, and then attach this volume to a VM. When you finish installing software from an ISO volume, you can detach it without stopping the VM first. To create a volume from an ISO image 1.
You can change the hot plug settings for both new and existing VMs. A running virtual machine has a resize limit, which defines the maximum number of vCPUs and the maximum amount of RAM you can allocate to the VM. The resize limit on vCPUs is static and equal to 64 for all VMs. The resize limit on RAM, on the contrary, is dynamic and depends on the amount of RAM a running VM is currently using. This limit is updated on a VM startup, and its values are listed in the table below.
l Before resizing a running VM, ensure that the guest operating system supports CPU and RAM hot plug (refer to "Supported guest operating systems" (p. 15)). Note that otherwise the guest operating system may become unstable after a resize. To increase CPU or RAM resources for such a guest operating system, you need to stop the virtual machine first. l Before resizing a running VM, ensure that the guest operating system has the latest updates installed.
secondary IPv6 address is not available for an IPv6 subnet that works in the SLAAC or DHCPv6 stateless mode. Note Secondary IP addresses, unlike the primary one, will not be automatically assigned to the network interface inside the virtual machine guest OS. You should assign them manually. l If you selected a virtual network with enabled IP address management In this case, spoofing protection is enabled and the default security group is selected by default.
Configuring virtual machine volumes You can add new volumes to your virtual machines, attach existing volumes, and detach unneeded volumes from virtual machines. Limitations l You cannot change, detach, or delete the boot volume. l You can only attach and detach non-boot volumes. l You cannot manage volumes of shelved VMs. Prerequisites l To be able to use volumes attached to VMs, they must be initialized inside the guest OS by standard means. To attach a volume to a virtual machine 1.
The default time interval for the charts is twelve hours. To zoom into a particular time interval, select the internal with the mouse; to reset zoom, double-click any chart. The following performance charts are available: CPU / RAM CPU and RAM usage by the VM. Network Incoming and outgoing network traffic. Storage read/write Amount of data read and written by the VM. Read/write latency Read and write latency.
l The rescue mode can use ISO images for booting both Linux and Windows virtual machines and QCOW2 images (templates) for booting Linux VMs. For instructions on making templates, refer to "Preparing templates" (p. 52). l You can send a VM to the rescue mode only if its current status is “Active” or “Shut down”. l There are only three actions available for the VM in the rescue mode: Console, Exit rescue mode, and Delete.
Note If the VM status changes to “Error” when exiting the rescue mode, you can reset its status with the Reset state action. The VM should then return to the “Rescue” status again. To exit the rescue mode for a Windows VM There might be an issue of exiting the rescue mode for a Windows VM. If in the rescue mode you set the original system disk online, its ID becomes the same as that of the rescue disk. Then, when you try to exit the rescue mode, the boot loader cannot find the proper boot disk.
7. Assign the ID that you recorded previusly to the original system disk: > SELECT DISK > UNIQUEID DISK id= Make sure that the value has changed with the UNIQUEID DISK command. You should now be able to exit the rescue mode. Managing guest tools This section explains how to install and uninstall the guest tools. This functionality is required for creating consistent snapshots of a running VM’s disks.
l Inside a Linux VM, create a mount point for the optical drive with the guest tools image and run the installer: # mkdir /mnt/cdrom # mount /mnt/cdrom # bash /mnt/cdrom/install Uninstalling guest tools If you find out that the guest tools are incompatible with some software inside a virtual machine, you can uninstall them by doing the following: l Inside a Windows VM: 1. Remove the QEMU device drivers from the device manager.
b. On DEB-based systems (Debian and Ubuntu): # apt-get remove vzvirtio-balloon-dkms prl-nettool qemu-guest-agent-vz \ vz-guest-udev If any of the packages listed above are not installed on your system, the command will fail. In this case, exclude these packages from the command and run it again. 2. Remove the files: # rm -f /usr/bin/prl_backup /usr/share/qemu-ga/VERSION \ /usr/bin/install-tools \ /etc/udev/rules.d/90-guest_iso.rules /usr/local/bin/fstrim-static \ /etc/cron.weekly/fstrim 3.
l Virtual machines are created, as described in "Creating virtual machines" (p. 16). To remove one virtual machine 1. Click the ellipsis button next to a VM you want to delete, and then click Delete. 2. Click Delete in the confirmation window. To remove multiple virtual machines 1. Select the check boxes next to VMs you want to delete. 2. Over the VM list, click Delete. 3. Click Delete in the confirmation window.
By default, the new security group will deny all incoming traffic and allow only outgoing traffic to assigned virtual machines. To delete a security group 1. On the Security groups screen, click the required security group. 2. On the group right pane, click Delete. 3. Click Delete in the confirmation window. Managing security group rules You can modify security groups by adding and removing rules. Editing rules is not available.
c. Select a predefined subnet CIDR or an existing security group. 4. Click the check mark to save the changes. As soon as the rule is created, it is applied to all of the virtual machines assigned to the security group. To remove a rule from a security group 1. On the Security groups screen, click the required security group. 2. On the group right pane, click the bin icon next to a rule you want to remove.
Managing Kubernetes clusters Self-service users can deploy ready-to-use Kubernetes clusters with persistent storage for managing containerized applications. A Kubernetes cluster includes the following components: Component Name and version Underlying OS Fedora 34 CoreOS Container runtime Docker 20.10.6 Network plugin Flannel with VXLAN Limitations l Kubernetes versions 1.15.x and 1.18.x are no longer supported. Kubernetes clusters created with these versions are marked with the Deprecated tag.
3. In the Network section, select a network that will interconnect the Kubernetes nodes in the cluster. If you select a virtual network, decide whether you need access to your Kubernetes cluster via a floating IP address: l If you select None, you will not have access to the Kubernetes API. l If you select For Kubernetes API, a floating IP address will be assigned to the master node or to the load balancer if the master node is highly available.
6. In the Default worker group section, set a number of workers to create, and then select a flavor for each worker. 7. Click Create. Creation of the Kubernetes cluster will start. The master and worker nodes will appear on the Virtual machines screen, while their volumes will show up on the Volumes screen. After the cluster is ready, click Kubernetes access for instructions on how you can access the dashboard.
l A Kubernetes cluster is created, as described in "Creating and deleting Kubernetes clusters" (p. 38). To add a worker group 1. On the Kubernetes clusters screen, click a Kubernetes cluster. 2. On the cluster right pane, navigate to the Groups tab. 3. In the Workers section, click Add. 4. In the Add worker group window, set a number of workers to create, select a flavor for each worker, and then specify a name for the group. Then, click Add.
Updating Kubernetes clusters When a new Kubernetes version becomes available, you can update your Kubernetes cluster to it. An update is non-disruptive for Kubernetes worker nodes, which means that these nodes are updated one by one, with the data availability unaffected. The Kubernetes API will be unavailable during an update, unless high availability is enabled for the master node. Limitations l You cannot update Kubernetes clusters with version 1.15.x to newer versions.
apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: mysc provisioner: cinder.csi.openstack.org parameters: type: default This manifest describes the storage class mysc with the storage policy default. The storage policy must exist in the compute cluster and be specified in the storage quotas to the current project. Dynamically provisioning persistent volumes Persistent volumes can be dynamically provisioned via persistent volume claims (PVC).
4. Create a pod and specify the PVC as its volume. To do it, click + Create and enter the following YAML file: apiVersion: v1 kind: Pod metadata: name: nginx spec: containers: - image: nginx imagePullPolicy: IfNotPresent name: nginx ports: - containerPort: 80 protocol: TCP volumeMounts: - mountPath: /var/lib/www/html name: mydisk volumes: - name: mydisk persistentVolumeClaim: claimName: mypvc readOnly: false This configuration file describes the pod nginx that uses the persistent volume claim mypvc.
Statically provisioning persistent volumes You can mount existing compute volumes to pods using static provisioning of persistent volumes. To mount a compute volume 1. In the self-service panel, obtain the ID of the desired volume. 2. Access the Kubernetes cluster via the dashboard. Click Kubernetes access for instructions. 3. On the Kubernetes dashboard, create a storage class, as described in "Creating storage classes" (p. 42). 4. Create a persistent volume.
This manifest specifies the persistent volume mypv from the storage class mysc that has 10 GiB of storage and access mode that allows it to be mounted in the read/write mode by a single node. The PV mypv uses the compute volume with the ID c5850e42-4f9d-42b5-9bee-8809dedae424 as backing storage. 5. Create a persistent volume claim. Before you define the PVC, make sure the PV is created and has the status “Available”.
Making Kubernetes deployments highly available If a node that hosts a Kubernetes pod fails or becomes unreachable over the network, the pod is stuck in a transitional state. In this case, the pod's persistent volumes are not automatically detached, and it prevents the pod redeployment on another worker node. To make your Kubernetes applications highly available, you need to enforce the pod termination in the event of node failure by adding rules to the pod deployment.
apiVersion: apps/v1 kind: Deployment metadata: name: nginx spec: replicas: 1 selector: matchLabels: app: nginx template: metadata: labels: app: nginx spec: terminationGracePeriodSeconds: 0 tolerations: - effect: NoExecute key: node.kubernetes.io/unreachable operator: Exists tolerationSeconds: 2 - effect: NoExecute key: node.kubernetes.
1. Access the Kubernetes cluster via the dashboard. Click Kubernetes access for instructions. 2. On the Kubernetes dashboard, create a deployment and service of the LoadBalancer type. To do it, click + Create and specify a YAML file that defines these objects.
l If you have deployed the Kubernetes cluster in a virtual network linked to a physical one via a virtual router, you can use the YAML file above without the annotations section for the loadbalancer service. The created load balancer will receive a floating IP address from the physical network and can be accessed at this external endpoint. The load balancer will also appear in the self-service panel, where you can monitor its performance and health.
This manifest describes the pod nginx that will be assigned to a node from the node group mygroup. When the pod is created, check that the hosting node belongs to the specified worker group. Managing images Acronis Cyber Infrastructure allows you to upload ISO images and templates that can be used to create VM volumes: l An ISO image is a typical OS distribution that needs to be installed on disk. You can upload an ISO image to the compute cluster.
Creating volumes from images You can create volumes from both ISO images and templates. To make a volume from an image 1. Go to the Images screen, and then click the required image. 2. On the image panel, click Create volume. 3. In the Create volume window, specify the volume name, size, and select a storage policy. 4. Click Create. The new volume will appear on the Volumes screen.
1. Install cloud-init and OpenSSH Server in the virtual machine. 2. [Optional] Enable logging for virtual machines that will be created from the template. 3. Convert the VM boot volume to the template, as described in "Creating images from volumes" (p. 61). Preparing Linux templates As all Linux guests have OpenSSH Server preinstalled by default, you only need to make sure a Linux template has cloud-init installed.
e. Open the C:\ProgramData\ssh\sshd_config file: > notepad 'C:\ProgramData\ssh\sshd_config' Comment out the following lines at the end of the file: #Match Group administrators #AuthorizedKeysFile __PROGRAMDATA__/ssh/administrators_authorized_keys Save the changes. f. Create the .ssh directory in C:\Users\ and an empty authorized_keys file inside it: > cd C:\Users\ > mkdir .ssh > notepad .\.ssh\authorized_keys Remove the .txt extension from the created file: > move .\.ssh\authoriz
b.
c. Run Windows PowerShell with administrator privileges and open the file C:\Program Files\Cloudbase Solutions\Cloudbase-Init\conf\cloudbase-init.conf: > notepad 'C:\Program Files\Cloudbase Solutions\Cloudbase-Init\conf\cloudbaseinit.conf' Add metadata_services and plugins on two lines: metadata_services=\ cloudbaseinit.metadata.services.configdrive.ConfigDriveService,\ cloudbaseinit.metadata.services.httpservice.HttpService\ plugins=cloudbaseinit.plugins.common.mtu.MTUPlugin,\ cloudbaseinit.plugins.
Note Make sure to remove all backslashes in the lines above. Save the changes. Enabling logging for virtual machines The console log of a virtual machine can be used for troubleshooting boot issues. The log contains messages only if logging is enabled inside the VM, otherwise the log is empty. The logging can be turned on by enabling the TTY1 and TTYS0 logging levels in Linux VMs and Emergency Management Services (EMS) console redirection in Windows VMs.
Managing volumes A volume in Acronis Cyber Infrastructure is a virtual disk drive that can be attached to a virtual machine. The integrity of data in volumes is protected by the redundancy mode specified in the storage policy. Creating and deleting volumes Limitations l A volume is removed along with all of its snapshots. To create a volume 1. On the Volumes screen, click Create volume. 2.
Attaching and detaching volumes Limitations l You can only attach and detach non-boot volumes. Prerequisites l A volume is created, as described in "Creating and deleting volumes" (p. 58). l To be able to use volumes attached to VMs, they must be initialized inside the guest OS by standard means. To attach a volume to a virtual machine 1. On the Volumes screen, click an unused volume. 2. On the volume right pane, click Attach. 3.
Warning! There is a risk of data loss. Resizing volumes You can change volume size only by increasing it. Volumes can be extended for both running (online resizing) and stopped (offline resizing) virtual machines. Online volume resizing allows users to avoid downtime and enables scaling VM storage capacity on the fly without service interruption. Limitations l You cannot shrink volumes. l During volume resizing, the file system inside the guest OS is not extended.
Creating images from volumes To create multiple VMs with the same boot volume, you can create a template from an existing boot volume and deploy VMs from it. Prerequisites l Linux virtual machines have cloud-Init installed, as described in "Preparing Linux templates" (p. 53). l Windows virtual machines have Cloudbase-Init and OpenSSH Server installed, as described in "Preparing Windows templates" (p. 53).
1. On the Volumes screen, click a volume. 2. On the volume right pane, click Clone. 3. In the Clone volume window, specify a volume name, size, and storage policy. Click Clone. Managing volume snapshots You can save the current state of a VM file system or user data by creating a snapshot of a volume. A snapshot of a boot volume may be useful, for example, before updating VM software. If anything goes wrong, you will be able to revert the VM to a working state at any time.
To manage a volume snapshot Select a volume and open the Snapshots tab on its right pane. You can do the following: l Create a new volume from the snapshot. l Create a template from the snapshot. l Discard all changes that have been made to the volume since the snapshot was taken. This action is available only for VMs with the "Shut down" and "Shelved offloaded" statuses.
Warning! As each volume has only one snapshot branch, all snapshots created after the snapshot you are reverting to will be deleted. If you want to save a subsequent snapshot before reverting, create a volume or an image from it first. l Change the snapshot name and description. l Reset the snapshot stuck in an "Error" state or transitional state to the "Available" state. l Remove the snapshot.
b. Specify a name, and then click Next. 3. If you enabled IP address management, you will move on to the IP address management step, where you can add an IPv4 subnet: a. In the Subnets section, click Add and select IPv4 subnet. b. In the Add IPv4 subnet window, specify the network’s IPv4 address range and, optionally, specify a gateway. If you leave the Gateway field blank, the gateway will be omitted from network settings. c.
4. On the Summary step, review the configuration, and then click Create virtual network.
To edit parameters of a virtual network 1. On the Networks screen, click the required network. 2. On the network right pane, click the pencil icon next to the network name or IPv4 subnet. 3. Make changes and save them. To delete a compute network Click the ellipsis icon next to the required network, and then click Delete. To remove multiple compute networks at once, select them, and then click Delete.
l An external gateway that is connected to a physical network. l An internal port that is connected to a virtual network. With virtual routers, you can do the following: l Create virtual routers l Change external or internal router interfaces l Create, edit, and delete static routes l Change a router name l Delete a router Limitations l A router can only connect networks that have IP management enabled.
3. Click Create. Managing router interfaces Prerequisites l You have a virtual router created, as described in "Managing virtual routers" (p. 67). To add an external router interface 1. If you already have an external gateway, remove the existing one first. 2. On the Routers screen, click the router name to open the list of its interfaces.
3. Click Add on the toolbar, or click Add interface if there are no interfaces to show. 4. In the Add interface window, do the following: a. Select External gateway. b. From the Network drop-down menu, select a physical network to connect to the router. The new interface will pick an unused IP address from the selected physical network. You can also provide a specific IP address from the selected physical network to assign to the interface in the IP address field. c.
1. On the Routers screen, click the router name to open the list of its interfaces. 2. Click Add. 3. In the Add interface window, select a network to connect to the router from the Network dropdown menu. The new interface will attempt to use the gateway IP address of the selected virtual network by default. If it is in use, specify an unused IP address from the selected virtual network to assign to the interface in the IP address field. 4. Click Add. To edit router interface parameters 1.
Managing static routes You can also configure static routes of a router by manually adding entries into its routing table. This can be useful, for example, if you do not need a mutual connection between two virtual networks and want only one virtual network to be accessible from the other. Consider the following example: l The virtual machine VM1 is connected to the virtual network private1 (192.168.128.0/24) via the network interface with IP address 192.168.128.10.
3. Click Add. To edit a static route 1. Click the ellipsis icon next to the required static route, and then click Edit. 2. In the Edit static route window, change the desired parameters, and then click Save. To remove a static route Click the ellipsis icon next to the static route you want to remove, and then click Delete. Managing floating IP addresses A virtual machine connected to a virtual network can be accessed from public networks, such as the Internet, by means of a floating IP address.
l The virtual router connects the physical network, from which a floating IP will be picked, with the VM’s virtual network. To create a floating IP address and assign it to a virtual machine 1. On the Floating IPs screen, click Add floating IP. 2. In the Add floating IP address, select a physical network, from which a floating IP will be picked, and a VM network interface with a fixed private IP address. 3. Click Add. To re-assign a floating IP address to another virtual machine 1.
and then routes incoming requests to a suitable VM based on a configured balancing algorithm and VM health. Limitations l The forwarding rule and protocol cannot be changed after the load balancer is created. Prerequisites l A network where a load balancer will operate has IP management enabled. l All VMs that will be added in balancing pools have fixed IP addresses. To create a load balancer with balancing pools 1. On the Load balancers screen, click Create load balancer. 2.
5. In the Balancing pools section, create a balancing pool to forward traffic from the load balancer to virtual machines by clicking Add. In the Create balancing pool window that opens, do the following: a. In the Forwarding rule section, select a forwarding rule from the load balancer to the backend protocol, and then specify the ports for incoming and destination connections.
c. In the Members section, add members, that is, virtual machines, to the balancing pool by clicking Add. Each VM can be included to multiple balancing pools. In the Add members window that opens, select the desired VMs, and then click Add. d. In the Health monitor section, select the protocol that will be used for monitoring members availability: l HTTP/HTTPS. The HTTP/HTTPS method GET will be used to check for the response status code 200. Additionally, specify the URL path to the health monitor.
responds successfully to three consecutive health checks, it is added to the pool again. You can manually set the health monitor parameters, such as the interval after which VM health is checked, the time after which the monitor times out, healthy and unhealthy thresholds. To change the default parameters, click Edit parameters, enter the desired values, and then click Save. e. Click Create. 6. [Optional] Add more balancing pools, as described above. 7. Click Create.
Open the Overview tab on the load balancer right pane. The following charts are available: Members state The total number of members in the balancing pools grouped by status: “Healthy,” “Unhealthy,” “Error,” and “Disabled”. CPU/RAM CPU and RAM usage by the load balancer. Network Incoming and outgoing network traffic. Active connections The number of active connections. Error requests The number of error requests.
l To edit the balancing settings such as the balancing algorithm and session persistence, click the ellipsis icon next to a pool, and then click Edit. l To edit the health monitor parameters, click the ellipsis icon next to a pool, and then click Edit health monitor. To add more members to a balancing pool Click the ellipsis icon next to the required balancing pool, and then click + Add members.
To delete a public key 1. On the SSH keys screen, select the SSH key you want to delete, and then click Delete. 2. Click Delete in the confirmation window. If this key has been injected into one or more virtual machines, it will remain inside those virtual machines.
