LATEST VERSION: v1.2 - RELEASE NOTES
Pivotal Container Service v1.2

Deploying Ops Manager with NSX-T for PKS

Page last updated:

This topic provides instructions for deploying Ops Manager on VMware vSphere with NSX-T integration for use with PKS.

Note: For security purposes, VMware requires a dedicated instance of Ops Manager for use with PKS. Do not deploy Pivotal Application Service (PAS) on the same instance of Ops Manager as PKS. For more information, see PAS and PKS Deployments with Ops Manager.

Prerequisites

Deploy Ops Manager for PKS

  1. Before starting, refer to the PKS Release Notes for supported Ops Manager versions for PKS. Or, download the Compatiblity Matrix from the Ops Manager download page.
  2. Before starting, refer to the known issues in the PCF Ops Manager Release v2.2 Release Notes or the PCF Ops Manager Release v2.3 Release Notes.
  3. Download the Pivotal Cloud Foundry Ops Manager for vSphere .ova file at Pivotal Network. Use the dropdown menu to select the supported Ops Manager release.

    Ops Manager for vSphere is provided as an OVA file (pcf-vsphere-2.3-build.170.ova, for example) that you import into your vSphere environment. An OVA file is a template for a VM.

    Deploy om 01

  4. Log into vCenter using the vSphere Web Client (FLEX) to deploy the Ops Manager OVA. This can also be done using the using the vSphere Client (HTML5), the OVFTool, or the PowerCLI.

  5. Select the Resource Pool defined for the PKS Management Plane. See Create PKS Management Plane if you have not defined the PKS Management Resource Pool.

  6. Right click the PKS Managment Plane Resource Pool and select Deploy OVF Template.

    Deploy om 02

  7. At the Select template screen, click Browse.

    Deploy om 03

  8. Select the Ops Manager OVA file you downloaded and click Open.

    Deploy om 05

  9. Review template selection and click Next.

    Deploy om 04

  10. At the Select Name and location screen, enter a name for the Ops Manager VM (or use the default name), select the Datacenter object, and click **Next

    Deploy om 06

  11. At the Select a resource screen, select the PKS Management Plane Resource Pool and click Next.

    Deploy om 07

  12. At the Review Details screen, confirm the configuration up to this point and click Next.

    Deploy om 08

  13. At the Select Storage screen, select Thin Provision, choose the desired Datastore, and click Next. For more information about disk formats, see Provisioning a Virtual Disk in vSphere.

    Warning: Ops Manager requires a Director VM with at least 8GB memory.

    Deploy om 09

  14. At the Select Networks screen, if you are using vSphere 6.7, select either the PKS Management T1 Logical Switch that you defined when Creating the PKS Management Plane, or if you are using vSphere 6.5, select a vSS or vDS port-group such as the standard VM Network, and click Next.

    Deploy om 10

    WARNING: With VMware vCenter Server 6.5, when initially deploying the Ops Manager OVA, you cannot connect to an NSX-T logical switch. You must first connect to a vSphere Standard (vSS) or vSphere Distributed Switch (vDS). After the OVA deployment is complete, before powering on the Ops Manager VM, connect the network interface to the NSX-T logical switch. The instructions below describe how to do this. This issue is resolved in VMware vCenter Server 6.7. For more information about this issue, see the VMware Knowledge Base.

  15. At the Customize template screen, enter the following information.

    • Admin Password: A default password for the “ubuntu” user. If you do not enter a password, Ops Manager will not boot up.
    • Custom hostname: The hostname for the Ops Manager VM, for example ops-manager.
    • DNS: One or more DNS servers for the Ops Manager VM to use, for example 10.20.20.1.
    • Default Gateway: The default gateway for Ops Manager to use, for example 10.0.0.1.
    • IP Address: The IP address of the Ops Manager network interface, for example 10.0.0.2 (assuming PKS NAT-mode).
    • NTP Server: The IP address of one or more NTP servers for Ops Manager, for example 10.113.60.176.
    • Netmask: The network mask for Ops Manager, for example, 255.255.255.0. Deploy om 11
  16. Click Next.

  17. At the Ready to complete screen, review the configuration settings and click Finish. This action begins the OVA import and deployment process.

    Deploy om 12

  18. Use the Recent Tasks panel at the bottom of the vCenter dashboard to check the progress of the OVA import and deployment. IF the import or deployment is unsuccessful, check the configuration for errors.

    Deploy om 13

  19. Once the deployment completes successfully, right-click the Ops Manager VM and select Edit Settings.

    Deploy om 14

  20. If you initially selected a vDS or vSS network for the Virtual Hardware > Network adapter 1 setting, change the vNIC connection to use the nsx.LogicalSwitch that is defined for the PKS Management Plane, for example LS-MGMT-PKS. See Create PKS Management Plane if you have not defined the PKS Management T1 Logical Switch and Router.

    Deploy om 15

  21. Right-click the Ops Manager VM and click Power On.

    Deploy om 16

Configure Ops Manager for PKS

  1. Create a DNS entry for the IP address that you used for Ops Manager. You must use this fully qualified domain name when you log into Ops Manager in the Installing Pivotal Cloud Foundry on vSphere topic. Use the routable IP address assigned to Ops Manager.

    Note: Ops Manager security features require you to create a fully qualified domain name to access Ops Manager during the initial configuration.

  2. Navigate to the fully qualified domain of your Ops Manager in a web browser.

    Note: It is normal to experience a brief delay before the interface is accessible while the web server and VM start up.

    Note: If you are using the NAT deployment topology, you will need a DNAT rule that maps the Ops Manager private IP to a routable IP. See Create PKS Management Plane for instructions.

    Deploy om 17

  3. The first time you start Ops Manager, you are required select an authentication system. These instructions use Internal Authentication. See Set Up Ops Manager in the PCF documentation for configuration details for the SAML and LDAP options.

    Deploy om 18

  4. Select Internal Authentication and provide the following information:

    • Username, Password, and Password confirmation to create an Admin user.
    • Decryption passphrase and the Decryption passphrase confirmation. This passphrase encrypts the Ops Manager datastore, and is not recoverable.
    • HTTP proxy or HTTPS proxy, follow the instructions in Configuring Proxy Settings for the BOSH CPI.
  5. Click Setup Authentication. It will take a few minutes to initialize the database.

    Deploy om 19

  6. Log in to Ops Manager with the user name and password you created.

    Deploy om 20

  7. Verify success. You should be able to log in, and you should see the BOSH Director tile is present and ready for configuration, indicated by the orange color.

    Deploy om 21

Next Step

After you complete this procedure, follow the instructions in Generating and Registering the NSX Manager Certificate for PKS.


Please send any feedback you have to pks-feedback@pivotal.io.

Create a pull request or raise an issue on the source for this page in GitHub