Installation Overview

Page last updated:

This topic provides an overview of how to install and configure Ops Manager and app runtimes.

Installation Sequence

Ops Manager, app runtimes, and associated products can run on multiple IaaSes. Planning and installing Ops Manager and app runtimes 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 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 requirements, including capacity, availability, container support, host OS, resource isolation, and geographical distribution. Discuss with your VMware contact.
  2. Deploy BOSH and Ops Manager

    • 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.
    • Ops Manager is a graphical dashboard that deploys with BOSH. Ops Manager works with the BOSH Director to manage, configure, and upgrade products such as VMware Tanzu Application Service for VMs (TAS for VMs), VMware Tanzu Kubernetes Grid Integrated Edition (TKGI), and services and partner products.
      • Ops Manager 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.
    • A single procedure deploys both BOSH and Ops Manager.
  3. (Optional) Deploy IPsec BOSH Add-on

    • IPsec encrypts IP data to secure network traffic.
    • If IPsec is required for security compliance, deploy it before you install runtimes.
    • IPsec is deployed with BOSH rather than as an Ops Manager tile.
  4. 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 Tanzu Kubernetes Grid Integrated Edition (TKGI) uses BOSH to run and manage Kubernetes container clusters.
      • TKGI 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 an 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].
    • Small Footprint TAS for VMs is an alternative to TAS for VMs that uses far fewer VMs than TAS for VMs but has limitations.
  5. Day 2 Configurations

    • Day 2 configurations set up internal operations and external integrations on a running deployment.
      • Examples include front-end configuration, user accounts, logging and monitoring, internal security, and container and stemcell images.
  6. 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 Ops Manager Operator Guide.

Deploying with BOSH

The following describes how you can use BOSH to run software in the cloud:

  1. To use BOSH, you create a manifest .yml file that specifies your software system’s component processes, the VMs they run on, how they communicate, and anything else they need.

  2. The BOSH command-line interface (CLI) or API sends the manifest to the BOSH Director, BOSH’s executive process.

  3. The BOSH Director provisions what it needs from the IaaS, deploys your software to run in the cloud, and heals automatically when VMs go down.

  4. BOSH CLI and API commands let you control BOSH-managed processes and allocate or release IaaS resources.

Backing Up

Monitoring, Logging, and Troubleshooting