Configuring BOSH Director on Azure

Page last updated:

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

Prerequisites

See the following sections to prepare for configuring BOSH Director on Azure.

General Prerequisites

Before you perform the procedures in this topic, you must have completed the procedures in the following topics:

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.

Prerequisites for Azure Stack (beta) or Azure Government Cloud

If you are using Azure Stack or Azure Government Cloud, you must set custom VM types for a successful deployment. You can set custom VM types with the Ops Manager API. For more information, see Using the Ops Manager API.

To set custom VM types, see the following information.

Note: Azure Stack is in beta for this release. Pivotal does not recommend using Azure Stack for a production deployment.

For more information, see Azure Stack Support is in Beta for Ops Manager.

  • For Azure Stack (beta): The example below may not have up-to-date VM types. For a current list of supported Azure Stack VM types that you can include in your API call, see Virtual Machine Sizes from the Azure Stack documentation. Include at least one Standard VM type.

  • For Azure Government: See the example curl command below for your list of VM types.

Example Command to Set VM Types
Azure Stack Azure Government
$ curl -k https://YOUR-OPS-MAN-FQDN/api/v0/vm_types -X
PUT -H "Authorization: bearer UAA-ACCESS-TOKEN"
"Content-Type: application/json" -d '{"vm_types":[
{"name":"Standard_DS1_v2","ram":3584,"cpu":1,"ephemeral_disk":51200},
{"name":"Standard_DS2_v2","ram":7168,"cpu":2,"ephemeral_disk":102400},
{"name":"Standard_DS3_v2","ram":14336,"cpu":4,"ephemeral_disk":204800},
{"name":"Standard_DS4_v2","ram":28672,"cpu":8,"ephemeral_disk":409600},
{"name":"Standard_DS5_v2","ram":57344,"cpu":8,"ephemeral_disk":819200},
{"name":"Standard_DS11_v2","ram":14336,"cpu":2,"ephemeral_disk":102400},
{"name":"Standard_DS12_v2","ram":28672,"cpu":4,"ephemeral_disk":204800},
{"name":"Standard_DS13_v2","ram":57344,"cpu":8,"ephemeral_disk":409600},
{"name":"Standard_DS14_v2","ram":114688,"cpu":16,"ephemeral_disk":819200}]}''
$ curl -k https://YOUR-OPS-MAN-FQDN/api/v0/vm_types -X
PUT -H "Authorization: bearer UAA-ACCESS-TOKEN"
"Content-Type: application/json" -d '{"vm_types":[
{"name": "Standard\_D1\_v2", "ram": 3584, "cpu": 1, "ephemeral_disk": 51200 },
{"name": "Standard\_D2\_v2", "ram": 7168, "cpu": 2, "ephemeral_disk": 102400 },
{"name": "Standard\_D3\_v2", "ram": 14336, "cpu": 4, "ephemeral_disk": 204800 },
{"name": "Standard\_D4\_v2", "ram": 28672, "cpu": 8, "ephemeral_disk": 409600 },
{"name": "Standard\_D5\_v2", "ram": 57344, "cpu": 8, "ephemeral_disk": 819200 },
{"name": "Standard\_D11\_v2", "ram": 14336, "cpu": 2, "ephemeral_disk": 102400 },
{"name": "Standard\_D12\_v2", "ram": 28672, "cpu": 4, "ephemeral_disk": 204800 },
{"name": "Standard\_D13\_v2", "ram": 57344, "cpu": 8, "ephemeral_disk": 409600 },
{"name": "Standard\_D14\_v2", "ram": 114688, "cpu": 16, "ephemeral_disk": 819200 },
{"name": "Standard\_F1", "ram": 2048, "cpu": 1, "ephemeral_disk": 16384 },
{"name": "Standard\_F2", "ram": 4096, "cpu": 2, "ephemeral_disk": 32768 },
{"name": "Standard\_F4", "ram": 8192, "cpu": 4, "ephemeral_disk": 65536 },
{"name": "Standard\_F8", "ram": 16384, "cpu": 8,  "ephemeral_disk": 131072}]}'
    

To check that you have successfully set your custom VM types, GET from the /api/v0/vm_types Ops Manager API endpoint.

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 Launching a BOSH Director Instance with an ARM Template or Launching a BOSH Director Instance on Azure without an ARM Template.

  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 use 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 values for the fields listed below. Failure to provide values in these fields results in a 500 error.

    • SAML admin group: Enter the name of the SAML group that contains all Ops Manager administrators.
    • SAML groups attribute: Enter the groups attribute tag name with which you configured the SAML server.
  4. Enter your Decryption passphrase. Read the End User License Agreement, and select the checkbox to accept the terms.

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

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

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

    Note: To retrieve your BOSH-IP-ADDRESS, navigate to the Status tab in the BOSH Director. Record the BOSH Director IP address.

  7. Configure your IdP with your SAML Service Provider metadata. Import the Ops Manager SAML provider metadata from Step 6a 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
  8. Import the BOSH Director SAML provider metadata from Step 6b to your IdP. If the IdP does not support an import, provide the values below.

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

Note: For an example of how to configure SAML integration between Ops Manager and your IdP, see the Configuring Active Directory Federation Services as an Identity Provider topic.

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 the instructions in the Configuring Proxy Settings for the BOSH CPI topic.
    • 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 BOSH 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.
  5. For Cloud Storage Type, select one of the following options based on your Azure VM storage settings.

    • Use Managed Disks: Select this option if you use Azure Managed Disks. See Azure Managed Disks Overview in the Microsoft documentation for more information. For Storage Account Type, select the storage option that corresponds with your Azure subscription. Select Standard_LRS for HDD-based storage or Premium_LRS for SSD-based storage. Azure managed disk
    • Use Storage Accounts: Select this option if you use storage accounts to store your Azure VMs. 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. Storage accounts
  6. (Optional) Enter your Default Security Group. For more information about Network Security Groups, see Filter network traffic with network security groups in Microsoft Azure’s documentation.

    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.

  7. 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 a BOSH Director Instance with an ARM Template topic or the Launching a BOSH Director Instance on Azure without an ARM Template topic.

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

  9. For Azure Environment, select the Azure cloud you want to use. Pivotal recommends Azure Commercial Cloud for most Azure environments.

    Note: If you selected Azure Stack (Beta) or Azure Government Cloud as your Azure environment, you must set custom VM types. For more information, see Prerequisites for Azure Stack or Azure Government Cloud.

Note: Azure Stack is in beta for this release. Pivotal does not recommend using Azure Stack for a production deployment. For more information, see Azure Stack Support is in Beta for Ops Manager.

  1. (Optional) If you selected Azure Stack for your Azure Environment, complete the following Azure Stack-only fields:

    Note: Azure Stack is in beta and not recommended for production use.

    1. For Domain, enter the domain for your Azure Stack deployment. For example, local.azurestack.external.
    2. Enter the URL for your Tenant Management Resource Endpoint.
    3. Enter AzureAD for Authentication.
    4. Enter your Azure Stack Endpoint Prefix. For example management.
    5. Enter your Azure Stack CA Certificate. Azure Stack requires a custom CA certiciate. Copy the certificate from your Azure Stack environment.
  2. 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.

    Note: The NTP server configuration only updates after VM recreation. Ensure that you select the Recreate all VMs checkbox if you modify the value of this field.

  3. Leave the JMX Provider IP Address field blank.

    Note: Starting from PCF v2.0, BOSH-reported component metrics are available in the Loggregator Firehose by default. Therefore, if you continue to use PCF JMX Bridge for consuming them outside of the Firehose, you may receive duplicate data. To prevent this, leave the JMX Provider IP Address field blank. For additional guidance, see BOSH System Metrics Available in Loggregator Firehose.

  4. Leave the Bosh HM Forwarder IP Address field blank.

    Note: Starting from PCF v2.0, BOSH-reported component metrics are available in the Loggregator Firehose by default. Therefore, if you continue to use the BOSH HM Forwarder for consuming them, you may receive duplicate data. To prevent this, leave the Bosh HM Forwarder IP Address field blank. For additional guidance, see BOSH System Metrics Available in Loggregator Firehose.

  5. Select the Enable VM Resurrector Plugin checkbox to enable the Ops Manager Resurrector functionality and increase PAS availability.

  6. 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.

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

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

  9. Select Keep Unreachable Director VMs if you want to preserve BOSH Director VMs after a failed deployment for troubleshooting purposes.

  10. (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.
  11. (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 for your email server.
    • Enable TLS: Select this checkbox to enable Transport Layer Security.
  12. For CredHub Encryption Provider, you can choose whether BOSH CredHub stores its encryption key internally on the BOSH Director and CredHub VM, or in an external hardware security module (HSM). The HSM option is more secure. Before configuring an HSM encryption provider in the Director Config pane, you must follow the procedures and collect information as described in Preparing CredHub HSMs for Configuration.

    Note: After you deploy Ops Manager with an HSM encryption provider, you cannot change BOSH CredHub to store encryption keys internally.

    CredHub Encryption Provider options in the Director Config pane

    • Internal: Select this option for internal CredHub key storage. This option is selected by default and requires no additional configuration.
    • Luna HSM: Select this option to use a SafeNet Luna HSM as your permanent CredHub encryption provider, and fill in the following fields:
      1. Encryption Key Name: Any name to identify the key that the HSM uses to encrypt and decrypt the CredHub data. Changing this key name after you deploy Ops Manager could cause service downtime.
      2. Provider Partition: The partition that stores your encryption key. Changing this partition after you deploy Ops Manager could cause service downtime. For this value and the ones below, use values gathered from Preparing CredHub HSMs for Configuration.
      3. Provider Partition Password
      4. Provider Client Certificate: The certificate that validates the identity of the HSM when CredHub connects as a client.
      5. Provider Client Certificate Private Key
      6. HSM Host Address
      7. HSM Port Address: If you don’t know your port address, enter 1792.
      8. Partition Serial Number
      9. HSM Certificate: The certificate that the HSM presents to CredHub to establish a two-way mTLS connection.

  13. Select a Blobstore Location to either configure the blobstore as an internal server or an external endpoint. Because the internal server is unscalable and less secure, Pivotal recommends you configure an external blobstore.

    Note: After you deploy Ops Manager, you cannot change the blobstore location.

    Blobstore location options in the Director Config pane

    • Internal: Select this option to use an internal blobstore. Ops Manager creates a new VM for blob storage. No additional configuration is required.
    • S3 Compatible Blobstore: Select this option to use an external S3-compatible endpoint. Follow the procedures in Sign up for Amazon S3 and Creating a Bucket from the AWS documentation. When you have created an S3 bucket, complete the following steps:
      1. S3 Endpoint: Navigate to the Regions and Endpoints topic in the AWS documentation. Locate the endpoint for your region in the Amazon Simple Storage Service (S3) table and construct a URL using your region’s endpoint. For example, if you are using the us-west-2 region, the URL you create would be https://s3-us-west-2.amazonaws.com. Enter this URL into the S3 Endpoint field in Ops Manager.
      2. Bucket Name: Enter the name of the S3 bucket.
      3. Access Key and Secret Key: Enter the keys you generated when creating your S3 bucket.
      4. Select V2 Signature or V4 Signature. If you select V4 Signature, enter your Region.

        Note: AWS recommends using Signature Version 4. For more information about AWS S3 Signatures, see the Authenticating Requests documentation.

    • GCS Blobstore: Select this option to use an external Google Cloud Storage (GCS) endpoint. To create a GCS bucket, you will need a GCS account. Then follow the procedures in Creating Storage Buckets. When you have created a GCS bucket, complete the following steps:
      1. Bucket Name: Enter the name of your GCS bucket.
      2. Storage Class: Select the storage class for your GCS bucket. See Storage Classes in the GCP documentation for more information.
      3. Service Account Key: Follow the steps in the Set Up an IAM Service Account section to download a JSON file with a private key. Then enter the contents of the JSON file into the field.

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

    Database

  15. (Optional) Director Workers sets the number of workers available to execute Director tasks. This field defaults to 5.

  16. (Optional) Max Threads sets the maximum number of threads that the BOSH 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.

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

    WARNING: In Ops Manager v2.1.17 and earlier, if you change the Director Hostname after your initial deployment, VMs become unavailable. This causes PCF downtime. To restore VM availability, enable Recreate All VMs and redeploy. This issue is resolved in Ops Manager v2.1.18 and later.

    Director workers

  18. (Optional) Enter your list of comma-separated Excluded Recursors to declare which IP addresses and ports should not be used by the DNS server.

  19. (Optional) To disable BOSH DNS, select the Disable BOSH DNS server for troubleshooting purposes checkbox. For more information about the BOSH DNS service discovery mechanism, see BOSH DNS Service Discovery for Application Containers in the Pivotal Application Service (PAS) Release Notes.

    Breaking Change: Do not disable BOSH DNS without consulting Pivotal Support. For more information about disabling BOSH DNS, see Disabling or Opting Out of BOSH DNS in PCF in the Pivotal Knowledge Base.

  20. (Optional) To set a custom banner that users see when logging in to the Director using SSH, enter text in the Custom SSH Banner field. Disable bosh dns

  21. Click Save.

Step 4: Create Networks Page

In this procedure, you create three networks.

Create the Management Network

  1. Select 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 the name of the network you want to create. For example, Management.

  5. Under Subnets, complete the following fields:

    • Azure Network Name: Enter PCF/Management. 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.4.0/26.
    • Reserved IP Ranges: Enter the first 9 IP addresses of the subnet. For example, 10.0.4.1-10.0.4.9.
    • DNS: Enter 168.63.129.16.
    • Gateway: Enter the first IP address of the subnet. For example, 10.0.4.1. Create networks management
  6. Click Save.

    Note: After you deploy Ops Manager, you add subnets with overlapping AZs to expand your network. For more information on how to configure additional subnets, see Expanding Your Network with Additional Subnets.

Create the PAS Network

  1. Click Add Network.

  2. 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.

  3. For Name, enter the name of the network you want to create. For example, PAS.

  4. Under Subnets, complete the following fields:

    • Azure Network Name: Enter PCF/PAS. 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.12.0/22.
    • Reserved IP Ranges: Enter the first 9 IP addresses of the subnet. For example, 10.0.12.1-10.0.12.9.
    • DNS: Enter 168.63.129.16.
    • Gateway: Enter the first IP address of the subnet. For example, 10.0.12.1. Create networks deployment
  5. Click Save.

Create the Services Network

  1. Click Add Network.

  2. 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.

  3. For Name, enter the name of the network you want to create. For example, Services.

  4. Under Subnets, complete the following fields:

    • Azure Network Name: Enter PCF/Services. 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.8.0/22.
    • Reserved IP Ranges: Enter the first 9 IP addresses of the subnet. For example, 10.0.8.1-10.0.8.9.
    • DNS: Enter 168.63.129.16.
    • Gateway: Enter the first IP address of the subnet. For example, 10.0.8.1. Create networks services
  5. 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 Management network you created from the dropdown menu.

  3. Click Save.

Step 6: Security Page

    1. Select Security. Om security

    2. In Trusted Certificates, enter your custom certificate authority (CA) certificates to insert into your organization’s certificate trust chain. This feature enables all BOSH-deployed components in your deployment to trust custom root certificates.

      To enter multiple certificates, paste your certificates one after the other. For example, format your certificates like the following:

      -----BEGIN CERTIFICATE-----
      ABCDEFGH12345678ABCDEFGH12345678ABCDEFGH12345678AB
      EFGH12345678ABCDEFGH12345678ABCDEFGH12345678ABCDEF
      GH12345678ABCDEFGH12345678ABCDEFGH12345678...
      ------END CERTIFICATE------
      -----BEGIN CERTIFICATE-----
      BCDEFGH12345678ABCDEFGH12345678ABCDEFGH12345678ABB
      EFGH12345678ABCDEFGH12345678ABCDEFGH12345678ABCDEF
      GH12345678ABCDEFGH12345678ABCDEFGH12345678...
      ------END CERTIFICATE------
      -----BEGIN CERTIFICATE-----
      CDEFGH12345678ABCDEFGH12345678ABCDEFGH12345678ABBB
      EFGH12345678ABCDEFGH12345678ABCDEFGH12345678ABCDEF
      GH12345678ABCDEFGH12345678ABCDEFGH12345678...
      ------END CERTIFICATE------

      Note: If you want to use Docker Registries for running app instances in Docker containers, enter the certificate for your private Docker Registry in this field. See Using Docker Registries for more information on running app instances in PAS using Docker Registries.

    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: Syslog Page

  1. Select Syslog. Syslog bosh

  2. (Optional) To send BOSH Director system logs to a remote server, select Yes.

  3. In the Address field, enter the IP address or DNS name for the remote server.

  4. In the Port field, enter the port number that the remote server listens on.

  5. In the Transport Protocol dropdown menu, select TCP, UDP, or RELP. This selection determines which transport protocol is used to send the logs to the remote server.

  6. (Optional) Pivotal strongly recommends that you enable TLS encryption when forwarding logs as they may contain sensitive information. For example, these logs may contain cloud provider credentials. To enable TLS, perform the following steps.

    • In the Permitted Peer field, enter either the name or SHA1 fingerprint of the remote peer.
    • In the SSL Certificate field, enter the SSL certificate for the remote server.
  7. Click Save.

Step 8: Resource Config Page

  1. Select Resource Config.

    Om resource config

  2. Ensure that the Internet Connected checkboxes are deselected for all jobs.

  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: Ops Manager requires a Director VM with at least 8 GB memory.

    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.

    Note: If you install PAS for Windows, provision your Master Compilation Job with at least 100 GB of disk space.

  4. (Optional) For Load Balancers, enter your Azure application gateway name for each associated job. To create an application gateway, follow the procedures in Configure an application gateway for SSL offload by using Azure Resource Manager from the Azure documentation. When you create the application gateway, associate the gateway’s IP with your PCF system domain.

    WARNING: This feature is not recommended for production use. The Azure load balancer does not support an override port in the healthcheck configuration.

  5. Click Save.

Step 9: (Optional) Add Custom VM Extensions

Use the Ops Manager API to add custom properties to your VMs such as associated security groups and load balancers. For more information, see Managing Custom VM Extensions.

Step 10: Complete the BOSH 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. BOSH 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. When Ops Manager finishes deploying, you can optionally deploy BOSH Add-Ons to your system, and then install one or more PCF runtime environments to complete your PCF installation.

What to Do Next

After you complete this procedure, follow the instructions in the Deploying PAS on Azure topic.

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