The Apache CloudStack 4.17 cloud platform has been released, which allows you to automate the deployment, configuration and maintenance of a private, hybrid or public cloud infrastructure (IaaS, infrastructure as a service). The CloudStack platform was donated to the Apache Foundation by Citrix, which received the project after it acquired Cloud.com. Installation packages are prepared for CentOS, Ubuntu and openSUSE.
CloudStack does not depend on the type of hypervisor and allows using Xen (XCP-ng, XenServer/Citrix Hypervisor and Xen Cloud Platform), KVM, Oracle VM (VirtualBox) and VMware in one cloud infrastructure at the same time. To manage the user base, storage, computing and network resources, a web interface and a special API are offered. In the simplest case, a cloud infrastructure based on CloudStack consists of one control server and a set of computing nodes on which guest operating systems are organized in virtualization mode. More complex systems support a cluster of multiple management servers and additional load balancers. At the same time, the infrastructure can be divided into segments, each of which operates in a separate data center.
Release 4.17 is categorized as LTS (Long Term Support) and will be maintained for 18 months. Main innovations:
- Support for updating virtual routers (VR, Virtual Router) through replacement in place, which does not require work stoppage (previously, updating required stopping and deleting the old instance, then installing and starting a new one). Non-stop updating is implemented through the use of live patches applied on the fly.
- For isolated and VPC networks, IPv6 support is provided, which was previously only available for Shared networks. In particular, it is possible to configure static IPv6 routes with the allocation of IPv6 subnets for virtual environments.
- The main package includes a storage plugin for the SDS platform (Software Defined Storage) StorPool, which allows you to use features such as instant snapshots, partition cloning, dynamic allocation of space, backup and separate QoS policies for each virtual disk.
- Users are given the opportunity to independently create shared networks (Shared Networks) and private gateways (Private Gateways) through a standard web interface or API (previously, these features were available only to the administrator).
- Provided the ability to link networks with multiple accounts (several users can share the same network) without involving virtual routers and without port forwarding.
- The web interface implements the ability to add several SSH keys to the environment without manually editing the .ssh/authorized_keys file (keys are selected during environment creation).
- The web interface structured information about system events used for auditing and identifying the causes of failures. Events are now explicitly associated with the resource that generated the event. It is possible to search, filter and sort events by objects.
- Added an alternative way to create storage snapshots for virtual machines running under the KVM hypervisor. In the previous implementation, libvirt was used to create snapshots, which does not support working with virtual disks in RAW format. The new implementation uses the specific capabilities of each storage and allows you to create snapshots of virtual disks without cutting the RAM.
- Added support for explicitly linking a partition to a specific primary storage in the Environment and Partition Migration Wizard.
- Reports on the status of control servers, the resource distribution server and the server with a DBMS have been added to the administrator interface.
- For KVM host environments, the ability to use multiple local storage partitions has been added (previously only one primary local storage was allowed, which prevented the addition of additional disks).
- The possibility of reserving public IP addresses for subsequent use in their networks is provided.
Source: opennet.ru