This guide describes how to install VMware Tanzu Operations Manager (Ops Manager) on OpenStack with VMware Tanzu Application Service for VMs (TAS for VMs).
OpenStack is a cloud operating system that controls large pools of compute, storage, and networking resources throughout a datacenter. For guidance on OpenStack service credential management, see Open Stack Security Documents below.
These documents provide a general reference for OpenStack service credential management.
This section describes the requirements for installing Ops Manager on OpenStack, including general requirements for installing Ops Manager with Ops Manager and TAS for VMs as well as OpenStack requirements.
Note: You can install Ops Manager on OpenStack with the TAS for VMs runtime. The VMware Tanzu Kubernetes Grid Integrated Edition (TKGI) runtime is not supported for OpenStack. For more information about TAS for VMs, see TAS for VMs Components. For more information about TKGI, see the TKGI documentation.
For TAS for VMs-specific resource requirements, see TAS for VMs Resource Requirements.
The following are OpenStack requirements for deploying Ops Manager:
Ops Manager is supported on the OpenStack Ocata, Pike, Queens, Rocky, and Stein releases. OpenStack is a collection of inter-operable components and requires general OpenStack expertise to troubleshoot issues that may occur when installing Ops Manager on particular releases and distributions. To verify that your OpenStack platform is compatible with Ops Manager, use the OpenStack Validator tool. To access the OpenStack Validator tool, see CF OpenStack Validator on GitHub.
VMware recommends granting complete access to the OpenStack logs to the operator managing the Ops Manager installation process.
For OpenStack accounts for Ops Manager, VMware recommends following the principle of least privilege by scoping privileges to the most restrictive permissions possible for a given role.
You must have a dedicated OpenStack project, formerly known as an OpenStack tenant.
You must have Keystone access to the dedicated OpenStack project, including the following:
PrimaryProjectfor the user must be the project you want to use to deploy Ops Manager. For more information, see Manage projects and users in the OpenStack documentation.
You must have the ability to do the following in OpenStack:
The following are resource requirements for the dedicated OpenStack project:
Nova or Neutron networking with floating IP support
Note: By default, TAS for VMs deploys the number of VM instances required to run a highly available configuration of Ops Manager. If you are deploying a test or sandbox Ops Manager that does not require HA, then you can scale down the number of instances in your deployment. For information about the number of instances required to run a minimal, non-HA Ops Manager deployment, see Scaling TAS for VMs.
The following are requirements for the OpenStack Cinder back end:
The following are requirements for using an Overlay Network with VXLAN or GRE Protocols:
Note: If you are using IPsec, your resource usage will increase by approximately 36 bytes. For details, including information about setting correct MTU values, see Installing IPsec in the IPsec documentation.
To install Ops Manager on OpenStack with the TAS for VMs runtime:
Deploy Ops Manager. For more information, see Deploying Ops Manager on OpenStack.
Configure BOSH Director on OpenStack. For more information, see Configuring BOSH Director on OpenStack.
After completing the procedures above, configure a runtime.
For information about installing and configuring a runtime, see Configuring TAS for VMs.