Ask Your Question

Mirantis OpenStack vs. Cloud Platform

asked 2017-05-06 16:02:25 -0500

matd gravatar image

With regards to the recent announcement of the Mirantis Cloud Platform (MCP), I'm wondering if anybody caught what would be the future of the Mirantis OpenStack distribution (MOS). Will Mirantis focus on delivering MCP as their (only) cloud based solution, or will they maintain MOS and MCP as a separate products?

edit retag flag offensive close merge delete

3 answers

Sort by ยป oldest newest most voted

answered 2017-05-07 14:10:47 -0500

sgordon gravatar image

updated 2017-05-07 14:11:21 -0500

Disclaimer: I work in product management at Red Hat, I would suggest reaching out to Mirantis directly to ask questions regarding this topic.

Now that we have that out of the way, my understanding is that Mirantis OpenStack continues to be a component of Mirantis Cloud Platform and will not be available separately for new customers, instead you consume it as part of MCP. The name change is the result of the other things being added (primarily StackLight and Kubernetes) as well as the significant changes to the way they are delivering/deploying/managing it (moving away from FUEL towards a CI/CD approach driven by a tool called Drivetrain).

edit flag offensive delete link more

answered 2017-05-08 01:33:45 -0500

sxc731 gravatar image

updated 2017-05-08 01:35:37 -0500

From what I could gather during the introductory webinar sgordon's answer is correct.

It must be noted that whilst MCP retains a component called MOS, it's a completely different beast from the old MOS that used to be provisioned by Fuel/Puppet. I attended Mirantis' OpenStack BCN presentation on the architecture, which also featured a demo, useful for grasping how different - and indeed more advanced/complex - the MCP-provisioned MOS is.

My gut feel: MCP is a giant step in the direction of a much more supportable architecture (I happen to like Salt too, which is used instead of Puppet for provisioning) at the expense of a big uptake in complexity. Having a platform that is indeed upgradable is probably worth a few sacrifices on that front...

There are two important corollaries as far as I am concerned:

  • Old Puppet/Fuel based MOS is being EOLed (though not before 2019 and possibly longer if you have a support contract)
  • Unlike MOS, you cannot just download MCP and take it from a spin - with a view of perhaps enrolling into a support contract with Mirantis once your setup reaches critical mass. The consumption model involves upfront contracting and a minimal period of hand-holding, during which Mirantis mostly operate your platform for you; likely due to aforementioned complexity.

(Sorry for separate answer due to comment size limit)

edit flag offensive delete link more

answered 2017-05-08 14:30:55 -0500

matd gravatar image

Yeah, I'd agree with you both. I got the same impressions after the MCP's initial announcement. I'm wondering how will this reflect to the future of Fuel, since Mirantis is a large contributor. Putting things as CI/CD aside, Fuel is a solid deployment option (IMHO), at least for the initial environment setup.

edit flag offensive delete link more


Yes I agree Fuel is great, particularly in making initial deployment as painless as possible; smth it achieves by (intentionally) restricting deployment options. That said, IMHO the major issue with Fuel (or at least MOS) is that it doesn't support OpenStack upgrades.

sxc731 gravatar imagesxc731 ( 2017-05-09 00:35:17 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2017-05-06 16:02:25 -0500

Seen: 606 times

Last updated: May 08 '17