Platform9 Managed OpenStack (PMO) is a SaaS-Managed OpenStack offering that enables you to create an agile private cloud deployment on your infrastructure that is fully automated and highly scalable. PMO deploys, manages, upgrades, and monitors your OpenStack cloud on your infrastructure located on-premises, in colocations or at the edge. PMO simplifies all aspects of operating a virtualized private cloud environment at scale by remotely managing and monitoring every component of your private cloud deployment.
PMO is deployed using a unique and powerful Software-as-a-Service model, where a cloud hosted management plane remotely deploys, manages, monitors and upgrades your OpenStack private cloud environment on your on-premises infrastructure, including your servers, storage, networking. This deployment model enables us to guarantee 24x7x365 SLA for your virtualized environment.
PMO is made up of core OpenStack components including: Nova, Neutron, Ironic, Glance, Cinder, Heat and Keystone, building the foundation to run an effective private cloud.
As a cloud administrator or a self-service user, you can set up and interact with various components of PMO through the Clarity SaaS portal, with zero knowledge of OpenStack, or OpenStack CLI commands. With a few simple clicks, your Platform9 dashboard starts offering visibility into your infrastructure across compute, storage, network, and existing workloads — and your OpenStack cloud is live. And as a Platform9 cloud administrator, you can configure and manage OpenStack resources that are to be used by self-service users, with Clarity.
PMO is a SaaS-managed virtualization offering that’s designed to help you make use of all the benefits of OpenStack, while ensuring you can run large scale, production ready, multi-cluster deployments of virtualization that meet your business SLA.
When we create a new deployment of PMO for you or your organization, it consists of following key components:
Read more: https://platform9.com/docs/openstack-docs/openstack/introduction-architecture
With Platform9 Managed OpenStack (PMO), any user, including developers, are able to quickly and easily build Virtual Machine (VM) instances. Platform9 also enables developers to launch multi-tier applications that are composed of multiple VMs with a single click.
Platform9 Managed OpenStack supports live migration on KVM. The VM or application downtime during a live migration is very small or negligible. Live migration is performed in the following scenarios.
PMO provides out of the box HA, with automatic VM restart on host failure, ensuring minimal downtime for critical workloads. HA is enabled by pf9-hamgr service for node failure detection using consul. PMO utilizes Masakari for host evacuation once failure is detected. Refer here for more information on the VM HA architecture in PMO.
PMO supports sign in with Single Sign-on (SSO) Credentials. You can sign in to PMO by using Identity Access Management (IAM) solutions like Okta, OneLogin, and Microsoft Active Directory Federation Services.
If your organization is using one of the above-mentioned IAM solutions for single sign-on to all web-based applications, you can use the IAM single sign-on (SSO) credentials to sign in to Clarity. SSO must be enabled on your account for you to be able to log in using IAM credentials.
With SSO integration, you no longer need to create individual username and password based accounts for your Platform9 Managed OpenStack users. This allows for easier integration across groups of users and different organizations in your environment, since users maintain a single login and password across various tools in the environment, including Platform9 Managed OpenStack.
PMO Networking enables the use of Software Defined Networks (SDN) enabling an administrator to define complex, virtual network topologies using VLAN / overlay networking (GRE/VXLAN), and isolated L3 domains within the OpenStack environment.
A typical Neutron-enabled environment requires either having one or more hosts configured as the network nodes, or having Distributed Virtual Routing (DVR) configured across all your hypervisors. In a configuration that uses dedicated network nodes, the node serves as the egress point for north-south traffic for the cloud. The node also provides layer 3 routing between tenant networks created in PMO.
PMO enables virtual firewalls via security groups that consist of a set of rules to control the inbound network traffic and outbound network traffic. When the security group is associated with or assigned to an instance, it controls the inbound network traffic to the instance and outbound network traffic from the instance. You can create a security group to control TCP, UDP and ICMP traffic.
PMO has features to configure GPUs and Accelerator cards passthrough and support for virtual GPUs.
GPUs and Accelerator cards installed on your PMO hosts can be passed through entirely or as virtual devices to virtual machines running in your PMO cloud. Any card that is capable of functioning as virtual GPU or passthrough or both via applicable drivers on the upstream OpenStack version ‘Rocky’ and later versions of OpenStack will function in PMO as well on supported hypervisor types.