Architecture and Installation Overview

Page last updated:

This guide describes how to design an Ops Manager deployment and install it with VMware Tanzu Application Service for VMs (TAS for VMs) or VMware Enterprise PKS (PKS) runtime on an IaaS.

For Architects and Operators

If you are designing and installing an Ops Manager deployment, you have one or both of the following roles:

  • Architects design an Ops Manager deployment. They know the IaaS to which they intend to deploy it and what other relevant resources they have. In their design, they consider needs for the platform’s capacity, availability, security, geography, budget, and other factors. If they do not install Ops Manager themselves, they provide the architectural specifications to whoever does.

  • Operators run an Ops Manager platform, keep it up-to-date, monitor its health and performance, and fix any problems. They may also install the platform, or perform “Day 2” configurations that expand its functionality and integrate it with external systems.

This guide helps people in both roles create an Ops Manager deployment that does what they want. The contents of this guide follow the phases of a typical Ops Manager planning and installation effort.

Planning and Installation Overview

Ops Manager and its runtimes, such as VMware Tanzu Application Service for VMs (TAS for VMs), comprise a suite of products. This suite can run on various IaaSes. Planning and installing an Ops Manager platform means building layers from the bottom up, starting with the details of your IaaS and ending with “Day 2” configurations that you perform on an installed and running Ops Manager deployment.

The typical planning and installation process is:

  1. Plan

    • Review the requirements for your IaaS:
    • See the Reference Architecture for your IaaS.
    • Assess your platform needs, including capacity, availability, container support, host OS, resource isolation, and geographical distribution. Discuss with your VMware contact.
  2. Deploy BOSH and Ops Manager Installation Dashboard

    • BOSH is an open-source tool that lets you run software systems in the cloud.
      • BOSH and its IaaS-specific Cloud Provider Interfaces (CPIs) are what enable Ops Manager to run on multiple IaaSes.
      • See Deploying with BOSH for a description of how BOSH deploys cloud software.
    • The Ops Manager Installation Dashboard is a graphical interface that deploys with BOSH. Ops Manager works with the BOSH Director to manage, configure, and upgrade Ops Manager products such as TAS for VMs, VMware Enterprise PKS (PKS), and Ops Manager services and partner products.
      • The Ops Manager UI represents products as tiles with multiple configuration panes that let you input or select configuration values needed for the product.
      • Ops Manager generates BOSH manifests containing the user-supplied configuration values, and sends them to the BOSH Director.
      • After you install Ops Manager and BOSH, you use the Ops Manager UI or API to deploy almost all Ops Manager products.
    • Deploying Ops Manager installs both BOSH and Ops Manager with a single procedure. Some IaaSes allow you to install BOSH and Ops Manager using Terraform instead of installing manually.
  3. Install Runtimes

    • VMware Tanzu Application Service for VMs (TAS for VMs) lets developers develop and manage cloud-native apps and software services.
      • TAS for VMs is based on the Cloud Foundry Foundation’s open-source Application Runtime (formerly Elastic Runtime) project.
    • VMware Enterprise PKS (PKS) uses BOSH to run and manage Kubernetes container clusters.
      • PKS is based on the Cloud Foundry Foundation’s open-source Container Runtime (formerly Kubo) project.
    • Isolation Segment lets a single TAS for VMs deployment run apps from separate, isolated pools of computing, routing, and logging resources.
      • Operators replicate and configure a Isolation Segment tile for each new resource pool they want to create.
      • You must install TAS for VMs before you can install Isolation Segment.
    • VMware Tanzu Application Service for VMs [Windows] (TAS for VMs [Windows]) enables TAS for VMs to manage Windows Server 2016 (1709) stemcells hosting .NET apps, and can also be replicated to create multiple isolated resource pools.
      • Operators replicate and configure a TAS for VMs [Windows] tile for each new resource pool they want to create.
      • You must install TAS for VMs before you can install TAS for VMs [Windows].
    • VMware Tanzu Application Service for VMs [Small Footprint] is an alternative to TAS for VMs that uses far fewer VMs than TAS for VMs but has limitations.
  4. Day 2 Configurations

    • Day 2 configurations set up internal operations and external integrations on a running Ops Manager platform.
      • Examples include front end configuration, user accounts, logging and monitoring, internal security, and container and stemcell images.
  5. Install Services

    • Install software services for developers to use in their apps.
      • Services include the databases, caches, and message brokers that stateless cloud apps rely on to save information.
      • Installing and managing software services on Ops Manager is an ongoing process, and is covered in the Operator Guide.

Guide Contents

This guide follows this bottom-up progression:

After installing Ops Manager, Operators install the software services that developers use in their apps. These Ops Manager services include the databases, caches, and message brokers that stateless cloud apps rely on to save information.

Installing and managing software services on Ops Manager is an ongoing process, and is covered in the Operator Guide.

The Operator Guide explains how to maintain a running Ops Manager platform, including monitoring, tuning, troubleshooting, and upgrading.

Getting Started with TAS for VMs gives a high-level overview of how TAS for VMs works and explains how you can try a simple deployment on your own local machine.