The release of the Apache CloudStack 4.17 cloud platform has taken place, enabling the automation of deployment, configuration, and maintenance of private, hybrid, or public cloud infrastructure (IaaS, Infrastructure as a Service). The CloudStack platform was handed over to the Apache Foundation by Citrix, which acquired the project following the acquisition of Cloud.com. Installation packages have been prepared for CentOS, Ubuntu, and openSUSE.
CloudStack is hypervisor-agnostic and allows for the simultaneous use of multiple hypervisors within a single cloud infrastructure, including Xen (XCP-ng, XenServer/Citrix Hypervisor, and Xen Cloud Platform), KVM, Oracle VM (VirtualBox), and VMware. A web interface and a dedicated API are provided for managing the user base, storage, compute, and network resources. In its simplest form, a CloudStack-based cloud infrastructure consists of a single management server and a set of compute nodes on which guest operating systems are virtualized. More complex systems support the use of a cluster of multiple management servers. servers The infrastructure can be segmented, with each segment operating in a separate data center.
Release 4.17 is classified as LTS (Long Term Support) and will be supported for 18 months. Key innovations include:
- Support for updating Virtual Routers (VR) through in-place replacement, allowing for updates without downtime (previously, updating required stopping and removing the old instance, then installing and starting the new one). No-downtime updates are achieved through the use of live patches applied on the fly.
- For isolated and VPC networks, a support for IPv6has been provided, which was previously only available for Shared networks. This includes the ability to configure static IPv6 routes with dedicated IPv6 subnets for virtual environments.
- The core package includes a storage plugin for the Software Defined Storage (SDS) platform StorPool, allowing capabilities such as instant snapshots, partition cloning, dynamic space allocation, backup, and separate QoS policies for each virtual disk.
- Users are now able to create Shared Networks and Private Gateways independently through the standard web interface or API (these features were previously only available to administrators).
- The ability to link networks to multiple accounts (multiple users can share one network) without involving Virtual Routers and without port forwarding has been provided.
- The web interface now allows the addition of multiple SSH keys to the environment without manually editing the .ssh/authorized_keys file (keys are selected during the environment creation).
- In the web interface, information about system events used for auditing and identifying the causes of failures has been structured. Events are now explicitly associated with the resource that triggered them. Searching, filtering, and sorting of events by objects is possible.
- An alternative method for creating snapshots of virtual machine storage running under the KVM hypervisor has been added. In the previous implementation, snapshots were created using libvirt, which does not support working with virtual disks in RAW format. The new implementation utilizes the specific capabilities of each storage type and allows for the creation of snapshots of virtual disks without memory dumps.
- The environment and section migration wizard has been enhanced with support for explicit binding of a section to a specific primary storage.
- The administrator interface now includes reports on the status of management servers, resource distribution servers, and database servers.
- For KVM host environments, the option to use multiple local storage partitions has been introduced (previously, only one primary local storage was allowed, which hindered the addition of extra disks).
- The ability to reserve public IP addresses for later use in your networks has been provided.
Source: opennet.ru
