Over a million developers have joined DZone.

The Cloudcast #152 - How Large does Mirantis Loom Over OpenStack?

DZone 's Guide to

The Cloudcast #152 - How Large does Mirantis Loom Over OpenStack?

· Cloud Zone ·
Free Resource

Download the MP3

Date: July 2, 2014

By: Aaron Delp and Brian Gracely

Description: Brian talks with Adrian Ionel (@adrianionel, CEO of @MirantisIT) about how Mirantis has evolved in the OpenStack community, demand for OpenStack Hybrid Cloud, challenges companies have in deployment and management, and how the European market for OpenStack might be larger and more dynamic than US and Asia market. They also talk about how carriers are embracing OpenStack + NFV for next-generation services and revenues. Music Credit: Nine Inch Nails (www.nin.com)

New OpenStack Certification:
On Demand OpenStack Private Cloud:
Mirantis R&D Office in France:

Topic 1 - Mirantis launched an on-demand private OpenStack cloud. What is it and why did you see a need to offer this? What challenges does OpenStack face that you are trying to solve? Has OpenStack adoption been slower than you expected?

Topic 2 - Mirantis seems to be filling a lot of holes in the industry (integration, products, hosting, consulting, education, certification) while many others seem more specialized. Why has Mirantis chosen this path?

Topic 3 - You recently announced an advanced level OpenStack certification that appears to focus on more in depth operations of OpenStack environments. What are you seeing in the industry that prompted Mirantis to invest in both education and certification in this area?

Topic 4 - Just yesterday it was announced that you will open an office in France. eNovance was recently acquired by Red Hat. Where is Europe (or globally) are you seeing a need for Mirantis services and what types of requests are you getting?
Topic 5 - Can you talk about how you're working with European carriers and where you see NFV fitting into OpenStack?


Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}