Theres’s never been a better time to adopt Mirantis OpenStack to build your cloud. The newest release, Mirantis OpenStack 9.0, offers improvements in simplicity, flexibility, and performance that make deployment, operations, and management faster and easier.
If you missed the July 14 webinar highlighting the rich new features in Mirantis OpenStack 9.0, we’ve got you covered. The webinar’s panel included three Mirantis experts: Senior Director of Product Marketing Amar Kapadia, Senior Manager of Technical Marketing Joseph Yep, and Senior Product Manager Durgaprasad (a.k.a. DP) Ayyadevara.
They talked about the ways in which MOS 9.0 improves the “Day 2” experience of operating your cloud once you’ve deployed it, as well as easier deployment of workloads, and especially improvements in the management of features related to NFV, such as SR-IOV, software acceleration DPDK and NUMA/CPU pinning.
Here’s a selection of questions and answers from those who attended.
Q: Can any plugin be added after initial deployment without disruption?
A: Not all plugins. However, the plugin framework has added metadata and developer functionality that allow developers to build and test their plugins so they can be added as “hot-pluggable.” This means this capability is specific to the plugins themselves as well as with the settings, which are dependent on the environment and type of change to determine whether there will be disruption. An example is StackLight’s Toolchain, which is hot-pluggable post-deployment.
Q: As far as upgrading from Mirantis OpenStack 8.0 to 9.0, is there documentation available for that?
A: Documentation is readily available and always improving. Because upgrades are challenging for large distributed infrastructure software, Mirantis continually creates tooling to make the process smoother and more automated. Feedback on the documentation is always welcome.
Q: Does the new release support SDN and Contrail?
A: Yes. Currently, the Control field plugin is available for Liberty-compatible release, and Contrail is the Mitaka-compatible version.
Q: The current base OS is Ubuntu 14.04, but are there any plans to upgrade to 16.04?
A: Yes. Operating systems are regularly validated, so 16 is on the roadmap.
Q: With the new release allowing updates to your previously-deployed OpenStack environment, can we also apply a new plugin with Fuel on a deployed environment?
A: Yes, unless it a previous version. For example, with Fuel 9, you can’t deploy a new plugin push deployment to a MOSS 7 environment without having to upgrade the environment itself. However, Fuel can manage multiple versions of Mirantis OpenStack environments.
Q: What is the status on Ironic and VX LAN?
A: Both are supported in 9.0.
Q: Does Murano support deployment of Kubernetes clusters?
A: Yes, absolutely. We do a lot with Kubernetes work, and there’s a new set of announcements coming soon about the work.
Q: What NFV features make Mirantis’ value-add different from others, and how can enterprises benefit from this feature?
A: Mirantis’ value-add is twofold. First, we support all Intel Enhanced Platform Awareness features. Second, we have provisioned for enabling and configuring these features through Fuel. We also support partners like 6WIND, who have DPDK accelerators, and we have Fuel plugins for that. So, we focus on making it easy to operationalize, and that differentiates us.
Q: How can you differentiate Mirantis from services hosted elsewhere, AWS for example?
A: Fundamentally, this compares two different things, a private cloud to a public cloud environment. You will find similarity at the IaaS layer. However, OpenStack is an open system that allows you to choose the components you want. For example, you can add an SDN like Contrail. Thus, in the PaaS, the two deviate considerably. Amazon is prescriptive, choosing the software available to offer customers. Conversely, OpenStack works with a multitude of partners so customers can tailor solutions that work best for them. If they want, for example, Pivotal Cloud Foundry, they can have it. If they want Kubernetes as a container framework, they can have it. If they want a specific database or NoSQL database, they can use Murano and publish that database.
Q: How many nodes are required to deploy OpenStack in Mirantis OpenStack 9.0?
A: Depending on the function, the lower limit is three. If running it virtualized, you could do it all physically on a single machine, but the nodes specifically will be your field master node if you’re using Fuel (you don’t have to use Fuel), which would then deploy to a single controller and a single compute host. This is one of the most minimal deployments if you’re looking at playing with features and practicing deployment, and it means you could conceivably run it on a laptop, though this isn’t advised for running a production deployment. There are instructions for running it in VirtualBox as well.