Mirantis, the number one pure-play OpenStack vendor has introduced the enhanced version of Mirantis OpenStack Version 5.0, the only commercially supported OpenStack distribution on the market that enables you to deploy and run OpenStack bits shipped by a variety of vendors — because what you get is pure OpenStack. The product is fully equipped with the latest OpenStack release, Icehouse, and features interoperability between VMware and OpenStack environments.
Adrian Ionel, CEO of Mirantis, said in a statement, "With Mirantis OpenStack 5.0, we are offering customers a future-proof solution for OpenStack, along with key new features that help make OpenStack robust enough to support mission-critical workloads."
Mirantis OpenStack 5.0 offers support for interoperability with VMware vCenter Server. Now the customers using VMware vCenter Server environments can deploy and control workloads that run directly on VMware vSphere in their VMware vCenter Server clusters directly from Mirantis OpenStack, as an alternative to KVM.
VMware resources are made available transparently within the pool of compute resources assigned through the OpenStack Horizon console.
Mirantis OpenStack 5.0 includes The Murano application catalog, an OpenStack project in Stackforge, which provides vending-machine style deployment of application workloads, Point-and-click deployment of Sahara, and improved scalability for Ceilometers.
Dan Wendlandt, director of product management at VMware said, "Our partnership with Mirantis is an example of how VMware promotes customer choice, giving organizations many options for how to build a cloud that includes compute, network, storage or management technologies from VMware. Mirantis' impressive track-record with OpenStack, combined with Mirantis OpenStack 5.0 interoperability with VMware vCenter™ Server, provides customers with a proven combination to implement OpenStack cloud APIs on top of VMware's enterprise-grade infrastructure."
Additionally, the Fuel master node, which controls deployment automation, is now packaged using Docker containers. It makes it possible for cloud and datacenter operators to upgrade their Fuel master node -- the server that controls the automation -- in place, without rebuilding or incurring cloud downtime in their deployed environments.