A. MCP is a distributed system of around 100 cloud services, including OpenStack and Kubernetes environments, deployed with DriveTrain (SaltStack/Reclass), with a focus on Day 2 Lifecycle Management (LCM) capabilities (e.g., scaling, updates, etc.). MOS, by contrast, comprises only OpenStack, deployed with Fuel, which also serves as a plugin framework (for OpenStack projects, partner products, etc.). Fuel is focused on Day 1 deployment, and less so on Day 2 LCM.

A. With the general availability of Mirantis Cloud Platform (MCP) 1.0, Mirantis will be closing Technology Partner Program for MOS.

We will be introducing a new program and evolving our processes for partner technology interoperability and deployment automation.

This is now a work-in-progress. Please contact the Mirantis Partner team for updates.

A. With the release of MCP, Mirantis will no longer support partner self-integration efforts for legacy Mirantis OpenStack (MOS), except in fulfillment of current support ticket package obligations, and in special cases. Please contact the Mirantis Partner team with questions.

A. No, they don’t. The MCP Technology Partner Program will be independent and will focus exclusively on MCP technologies and business objectives.

Mirantis is currently working on defining the MCP Technology Partner Program, processes, and partner engagement strategy.

Mirantis will work individually with select partners to transition from MOS Technology Partnership to MCP Technology Partnership.

A. The MCP Technology Partner program is now a work-in-progress. Please fill out this application form to be considered for membership. The Mirantis Partner team will reach out to ask about your products and business, and discuss how your solution might complement Mirantis Cloud Platform.

A. The old Hardware Compatibility program and Hardware Compatibility List (HCL) were relevant to MOS alone.

To identify servers compatible with MCP, we are (temporarily) relying on Ubuntu’s HCL, since we are (presently) using Canonical MaaS (Metal-as-a-Service) for bare metal provisioning and Ubuntu (16.04 for MCP 1.0) as the underlying OS. We are also using the Ceph hardware recommendations as guidance on hardware destined to run as Ceph metadata servers, OSDs, and other components.

A. Existing Fuel plugins will not be directly ported to MCP.

Existing MOS customers will continue receiving support for Fuel as an installer, and for existing Fuel plugins defined in the Fuel Plugin Catalog. However, no further development of Fuel plugins will occur, independent of an existing MOS support contract.

MCP’s Salt-based architecture provides more powerful and flexible ways of extending deployment and lifecycle management functionality that go beyond legacy “plugin” capabilities. This new approach provides a metadata separation between the cloud software and the underlay hardware configuration, treating Infrastructure-as-Code (IaC).

A. We see a straight path from MOS to MCP for applications that run as workloads on MCP core cloud infrastructure (e.g., on OpenStack VMs, Kubernetes-hosted containers, or OpenStack-managed bare metal nodes).

Mirantis will work individually with select partners to facilitate transition. Please contact the Mirantis Partner team for details.

A. At the moment, Mirantis does not offer a straightforward program/transition plan for makers of complex applications (e.g., apps that run on non-cloud-managed bare metal nodes, apps that require customization of MCP control plane or compute nodes) and infrastructure products (e.g., software-defined storage or network technologies requiring driver/plugin integration with OpenStack and/or Kubernetes).

Mirantis will work individually with select partners to enable transition. Please reach out to the Mirantis Partner team for more information.

Mirantis Cloud Platform