LATEST VERSION: 1.9 - CHANGELOG
Pivotal Cloud Foundry v1.9

Configuring Ops Manager Director on Azure

Page last updated:

This topic describes how to configure the Ops Manager Director for Pivotal Cloud Foundry (PCF) on Azure.

Before you perform the procedures in this topic, you must have completed the procedures in the Preparing to Deploy PCF on Azure topic, and either the Launching an Ops Manager Director Instance with an ARM Template topic or the Launching an Ops Manager Director Instance on Azure without an ARM Template topic.

After you complete the procedures in this topic, follow the instructions in the Deploying Elastic Runtime on Azure topic.

Note: You can also perform the procedures in this topic using the Ops Manager API. For more information, see the Using the Ops Manager API topic.

Step 1: Access Ops Manager

  1. In a web browser, navigate to the fully qualified domain name (FQDN) of Ops Manager that you set up in either the Launching an Ops Manager Director Instance with an ARM Template topic or the Launching an Ops Manager Director Instance on Azure without an ARM Template topic.
  2. When Ops Manager starts for the first time, you must choose one of the following:

    Select authentication

Use an Identity Provider (IdP)

  1. Log in to your IdP console and download the IdP metadata XML. Optionally, if your IdP supports metadata URL, you can copy the metadata URL instead of the XML.

  2. Copy the IdP metadata XML or URL to the Ops Manager Use an Identity Provider log in page. Meta om

    Note: The same IdP metadata URL or XML is applied for the BOSH Director. If you are using a separate IdP for BOSH, copy the metadata XML or URL from that IdP and enter it into the BOSH IdP Metadata text box in the Ops Manager log in page.

  3. Enter your Decryption passphrase. Read the End User License Agreement, and select the checkbox to accept the terms.

  4. Your Ops Manager log in page appears. Enter your username and password. Click Login.

  5. Download your SAML Service Provider metadata (SAML Relying Party metadata) by navigating to the following URLs:

    • 5a. Ops Manager SAML service provider metadata: https://OPS-MAN-FQDN:443/uaa/saml/metadata
    • 5b. BOSH Director SAML service provider metadata: https://BOSH-IP-ADDRESS:8443/saml/metadata

    Note: To retrieve your BOSH-IP-ADDRESS, navigate to the Ops Manager Director tile > Status tab. Record the Ops Manager Director IP address.

  6. Configure your IdP with your SAML Service Provider metadata. Import the Ops Manager SAML provider metadata from Step 5a above to your IdP. If your IdP does not support importing, provide the values below.

    • Single sign on URL: https://OPS-MAN-FQDN:443/uaa/saml/SSO/alias/OPS-MAN-FQDN
    • Audience URI (SP Entity ID): https://OP-MAN-FQDN:443/uaa
    • Name ID: Email Address
    • SAML authentication requests are always signed
  7. Import the BOSH Director SAML provider metadata from Step 5b to your IdP. If the IdP does not support an import, provide the values below.

    • Single sign on URL: https://BOSH-IP:8443/saml/SSO/alias/BOSH-IP
    • Audience URI (SP Entity ID): https://BOSH-IP:8443
    • Name ID: Email Address
    • SAML authentication requests are always signed
  8. Return to the Ops Manager Director tile, and continue with the configuration steps below.

Internal Authentication

  1. When redirected to the Internal Authentication page, you must complete the following steps:

    • Enter a Username, Password, and Password confirmation to create an Admin user.
    • Enter a Decryption passphrase and the Decryption passphrase confirmation. This passphrase encrypts the Ops Manager datastore, and is not recoverable if lost.
    • If you are using an Http proxy or Https proxy, follow these instructions.
    • Read the End User License Agreement, and select the checkbox to accept the terms.
    • Click Setup Authentication.

    Om login

  2. Log in to Ops Manager with the Admin username and password that you created in the previous step.

    Cf login

Step 2: Azure Config Page

  1. Click the Ops Manager Director tile.

    Azure om tile

  2. Select Azure Config.

    Azure config

  3. Complete the following fields with information you obtained in the Preparing to Deploy PCF on Azure topic.

    • Subscription ID: Enter the ID of your Azure subscription.
    • Tenant ID: Enter your TENANT_ID.
    • Application ID: Enter the APPLICATION_ID that you created in the Create an Azure Active Directory Application step of the Preparing to Deploy PCF on Azure topic.
    • Client Secret: Enter your CLIENT_SECRET.
  4. Complete the following fields:

    • Resource Group Name: Enter the name of your resource group, which you exported as the $RESOURCE_GROUP environment variable.
    • BOSH Storage Account Name: Enter the name of your storage account, which you exported as the $STORAGE_NAME environment variable.
    • Deployments Storage Account Name: Enter the base storage name that you used to create your deployment storage accounts, prepended and appended with the wildcard character *. For example, if you created accounts named xyzdeploymentstorage1, xyzdeploymentstorage2, and xyzdeploymentstorage3, enter *deploymentstorage*. Ops Manager requires that you specify an asterisk at both the beginning and the end of the base storage account name.
    • Default Security Group: Enter pcf-nsg.

      Note: The Azure portal sometimes displays the names of resources with incorrect capitalization. Always use the Azure CLI to retrieve the correctly capitalized name of a resource.

  5. For SSH Public Key, copy and paste the contents of your public key in the opsman.pub file. You created this file in either the Launching an Ops Manager Director Instance with an ARM Template topic or the Launching an Ops Manager Director Instance on Azure without an ARM Template topic.

  6. For SSH Private Key, copy and paste the contents of your private key in the opsman file.

  7. Click Save.

Step 3: Director Config Page

  1. Select Director Config.

    Director config

  2. In the NTP Servers (comma delimited) field, enter a comma-separated list of valid NTP servers.

  3. (Optional) Enter your Metrics IP Address if you are Using JMX Bridge.

  4. Select the Enable VM Resurrector Plugin checkbox to enable the Ops Manager Resurrector functionality and increase Elastic Runtime availability.

  5. Select Enable Post Deploy Scripts to run a post-deploy script after deployment. This script allows the job to execute additional commands against a deployment.

  6. Select Recreate all VMs to force BOSH to recreate all VMs on the next deploy. This process does not destroy any persistent disk data.

  7. Select Enable bosh deploy retries if you want Ops Manager to retry failed BOSH operations up to five times.

  8. Select Keep Unreachable Director VMs if you want to preserve Ops Manager Director VMs after a failed deployment for troubleshooting purposes.

  9. (Optional) Select HM Pager Duty Plugin to enable Health Monitor integration with PagerDuty. Director hm pager

    • Service Key: Enter your API service key from PagerDuty.
    • HTTP Proxy: Enter an HTTP proxy for use with PagerDuty.
  10. (Optional) Select HM Email Plugin to enable Health Monitor integration with email. Director hm email

    • Host: Enter your email hostname.
    • Port: Enter your email port number.
    • Domain: Enter your domain.
    • From: Enter the address for the sender.
    • Recipients: Enter comma-separated addresses of intended recipients.
    • Username: Enter the username for your email server.
    • Password: Enter the password password for your email server.
    • Enable TLS: Select this checkbox to enable Transport Layer Security.
  11. For Blobstore Location, Pivotal recommends that you keep Internal selected. Blobstore

  12. For Database Location, Pivotal recommends that you keep Internal selected. Database

  13. Max Threads sets the maximum number of threads that the Ops Manager Director can run simultaneously. Pivotal recommends that you leave the field blank to use the default value unless doing so results in rate limiting or errors on your IaaS.

  14. (Optional) To add a custom URL for your Ops Manager Director, enter a valid hostname in Director Hostname. You can also use this field to configure a load balancer in front of your Ops Manager Director.

  15. Click Save.

Step 4: Create Networks Page

  1. Select Create Networks.

    Create networks

  2. Click Add Network.

  3. Select Enable ICMP checks if you want to enable ICMP on your networks. Ops Manager uses ICMP checks to confirm that components within your network are reachable.

  4. For Name, enter default.

  5. If you want to dynamically provision VMs in this network for use with on-demand services, select the Service Networks checkbox. When the checkbox is selected, Ops Manager does not provision VMs within the specified CIDR range.

  6. To create a subnet, complete the following fields:

    • Azure Network Name: Enter pcf-net/pcf. You can use either the NETWORK-NAME/SUBNET-NAME format or the RESOURCE-GROUP/NETWORK-NAME/SUBNET-NAME format. If you specify a resource group, it must exist under the same subscription ID you provided in the Azure Config page.

      Note: The Azure portal sometimes displays the names of resources with incorrect capitalization. Always use the Azure CLI to retrieve the correctly capitalized name of a resource.

    • CIDR: Enter 10.0.0.0/20.
    • Reserved IP Ranges: Enter the first 9 IP addresses of the subnet. For example, 10.0.0.1-10.0.0.9.
    • DNS: Enter 168.63.129.16.
    • Gateway: Enter the first IP address of the subnet. For example, 10.0.0.1.
  7. Click Save. If you do not have Enable ICMP checks selected, you may see red warnings which you can safely ignore.

Step 5: Assign Networks Page

  1. Select Assign Networks.

    Assign networks

  2. Under Network, select the default network you created from the dropdown menu.

  3. Click Save.

Step 6: Security Page

  1. Select Security.

    Om security

  2. In Trusted Certificates, enter a custom Certificate Authority (CA) certificate to insert into your organization’s certificate trust chain. This feature enables all BOSH-deployed components in your deployment to trust a custom root certificate. If you want to use Docker Trusted Registries for running app instances in Docker containers, use this field to enter the certificate for your private Docker Trusted Registry. See the Using Docker Trusted Registries topic for more information.

  3. Choose Generate passwords or Use default BOSH password. Pivotal recommends that you use the Generate passwords option for greater security.

  4. Click Save. To view your saved Director password, click the Credentials tab.

Step 7: Resource Config Page

  1. Select Resource Config.

    Om resource config

  2. Ensure that the Internet Connected checkboxes are selected for all jobs. This gives all VMs a public IP address that enables outbound Internet access.

    Note: If you want to provision a Network Address Translation (NAT) box to provide Internet connectivity to your VMs instead of providing them with public IP addresses, deselect the Internet Connected checkboxes. Azure offers a managed source NAT (SNAT) service. However, Pivotal does not recommend using this service because Elastic Runtime deployments may fail due to SNAT performance bottlenecks.

  3. Adjust any values as necessary for your deployment. Under the Instances, Persistent Disk Type, and VM Type fields, choose Automatic from the drop-down menu to allocate the recommended resources for the job. If the Persistent Disk Type field reads None, the job does not require persistent disk space.

    Note: If you set a field to Automatic and the recommended resource allocation changes in a future version, Ops Manager automatically uses the updated recommended allocation.

  4. Click Save.

Step 8: Complete the Ops Manager Director Installation

  1. Click Apply Changes. If a red ICMP error message appears and you have disabled ICMP, click Ignore errors and start the install.

  2. Ops Manager Director installs. This may take a few moments. When the installation process successfully completes, the Changes Applied window appears.

  3. Click the Installation Dashboard link to return to the Installation Dashboard.

  4. After you complete this procedure, follow the instructions in the Configuring Elastic Runtime for Azure topic.

Was this helpful?
What can we do to improve?
View the source for this page in GitHub