Open cloud company Mirantis has announced the availability of Mirantis OpenStack 21.4. This latest version includes a number of important enhancements which enable enterprises to support a broader range of deployment options, extend private clouds over public networks and provide long-term support for OpenStack Victoria.
Enterprises across sectors and regions use Mirantis OpenStack for Kubernetes to construct some of the largest private clouds in the world. Mirantis OpenStack for Kubernetes provides a feature rich environment for hosting both legacy apps and contemporary use cases, such as Network Functions Virtualization, mobile network operations, and large-scale scientific computing. Using Kubernetes, it would ensure configurability, resilience, robustness and seamless updates for OpenStack, which may help simplify operations.
Mirantis OpenStack 21.4 now adds support for edge deployments that may be centrally controlled and dispersed. There is a necessity to deploy sections of the data center computing or storage infrastructure to the edge, as near to their consumers or the source of data as feasible as organizations modernize their IT infrastructures. For edge deployment, Mirantis OpenStack would make sense since it only requires half the number of nodes necessary for a typical deployment while it centralizes the control and administration of distributed, distant resources.
“The latest release of OpenStack creates a number of unique challenges due to the constraints for the deployment of a sufficiently scaled data center, in terms of space, power, cooling and other related factors, as well as the management of distributed data-center clusters,” said Adam Parco, Chief Technology Officer (CTO) at Mirantis. “Traditional distributed management solutions have been relatively resource-heavy when compared to that available in a small edge data center, making such a deployment less than viable.”
For data center operators with distant data centers, Mirantis OpenStack 21.4 now supports connecting numerous private data centers over public infrastructure via BGP-based VPNs utilizing Open vSwitch-based clouds, which enhances flexibility and possibilities. As a result of other OpenStack technologies, BGP-based VPN interconnection was previously accessible, but it added substantial complexity to configuration and administration. It is now possible to use the same set of VPN connectivity across public networks without adding complexity to general-purpose Infrastructure-as-a-Service (IaaS).
Other new features and enhancements in the latest Mirantis OpenStack version include:
- Support for large deployments based on Open vSwitch – For large-scale installations of up to 200 nodes, clients may now deploy Mirantis OpenStack in bigger settings to keep up with their business’s growth.
- Default policy override for core OpenStack services – A mechanism that defines additional policy rules for the core OpenStack services through the OpenStack Deployment Custom Resource. Together with OpenStack domain methods, this improvement enables the creation of “sandboxes” for multi-tenant operation, where different ‘tenants’ inside an OpenStack deployment can have their own isolated areas without danger of harming other ‘tenants.’
- Automatic evacuation of VMs from failed hosts – As part of Instances High Availability Service for OpenStack, the host monitor uses OpenStack Masakari to enable automated instance evacuation from failing instances, increasing deployment resilience.
- Cinder backend for Glance – Generic iSCSI – For clients that rely on external storage appliances to implement block storage, the newly supported Cinder backend for Glance now allows presenting Cinder volumes as Glance images and snapshots, using the same storage appliance for all permanent data in the cloud.
- OpenStack Victoria LTS – OpenStack Victoria LTS with OVS now has LTS status being achieved, and full support is provided for OpenStack Victoria with Tungsten Fabric 5.1 for both greenfield and new deployments. This LTS support would ensure that Mirantis clients have a solid, supported base for their deployments.