Upgrading BOSH Director on GCP
Page last updated:
This topic describes how to upgrade BOSH Director for Pivotal Platform on Google Cloud Platform (GCP).
Complete the tasks in this topic as part of the Ops Manager upgrade process. For more information, see Upgrading Pivotal Platform.
In this procedure, you create an Ops Manager VM instance to host the upgraded version of Ops Manager. Then, to complete the Ops Manager upgrade, you export your existing Ops Manager installation onto this new VM.
To create an Ops Manager VM instance, do the following tasks:
- Locate the Ops Manager installation file. See Locate the Pivotal Ops Manager Installation File.
- Create a private VM image. See Create a Private VM Image.
- Create the Ops Manager VM. See Create the Ops Manager VM Instance.
To complete the Ops Manager upgrade, you must have your Ops Manager decryption passphrase. You defined this decryption passphrase during the initial installation of Ops Manager.
The Ops Manager installation file includes a filepath to the Ops Manager image. You use this image file to create a private VM image for the new Ops Manager VM.
To locate the Ops Manager installation file, do the following:
Log in to the Pivotal Network, and click on Pivotal Platform Operations Manager.
From the Releases drop-down, select the release for your upgrade.
Select one of the following download files:
- Pivotal Ops Manager for GCP
- Pivotal Ops Manager YAML for GCP
When you click on the download link, your browser downloads or opens the
These documents provide the GCP location of the Ops Manager
.tar.gzinstallation file based on the geographic location of your installation.
Copy the filepath string of the Ops Manager image based on your existing deployment location.
Create a private VM image to use when you create the new Ops Manager VM.
To create a private VM image, do the following:
Log in to the GCP Console.
In the left navigation panel, click Compute Engine, and select Images.
Click Create Image.
Complete the following fields:
- Name: Enter a name that matches the naming convention of your existing Ops Manager image files.
- Encryption: Leave Automatic (recommended) selected.
- Source: Choose Cloud Storage file.
- Cloud Storage file: Paste in the Google Cloud Storage filepath you copied from the PDF or YAML file in the previous task.
Click Create. The file may take a few minutes to import.
Create an Ops Manager VM instance to host the new version of Ops Manager.
To create an Ops Manager VM instance, do the following:
Select the checkbox for the image that you created above.
Click Create Instance.
In the Create an instance form, complete the following fields:
- Name: Enter a name that matches the naming conventions of your existing deployment.
- Zone: Choose a zone from the region of your existing deployment.
Machine type: Click Customize to manually configure the vCPU and memory. An Ops Manager VM instance requires the following minimum specifications:
Machine Spec Minimum Value CPU 2 vCPUs Memory 8 GB
Boot disk: Click Change, then perform the following steps:
- Click Custom images if it is not already selected.
- Select the Boot disk type. If you have an Ops Manager environment with high performance needs, select SSD. As an example, environments used to develop Pivotal Platform tiles may benefit from a higher performing Ops Manager VM boot disk. For most environments, however, you can select Standard.
Set the Size (GB) of the boot disk to the minimum or higher.
Machine Spec Minimum Value Boot disk 100 GB
Select the Ops Manager image you created in the previous step if it is not already selected.
Click Select to save.
Under Identity and API access, choose the Service account you created when you initially installed Pivotal Platform. See Step 1: Set up IAM Service Accounts in Preparing to Deploy Ops Manager on GCP Manually.
Allow HTTP traffic: Only select this checkbox if you selected it in your original Ops Manager VM configuration.
Allow HTTPS traffic: Only select this checkbox if you selected it in your original Ops Manager VM configuration.
Networking: Select the Networking tab, and perform the following steps:
- For Network and Subnetwork, select the network and subnetwork you created when you initially deployed Pivotal Platform. See Step 3: Create a GCP Network with Subnets in Preparing to Deploy Ops Manager on GCP Manually.
- For Network tags, enter any tags that you applied to your original Ops Manager. For example, if you used the
pcf-opsmanagertag to apply the firewall rule you created in Step 5: Create Firewall Rules for the Network, then apply the same tag to this Ops Manager VM.
- For Internal IP, select
Custom. In the Internal IP address field, enter a spare address located within the reserved IP range you configured in your existing BOSH Director as part of Step 5: Create Networks Page. Do not use
10.0.0.1, which is configured for the Gateway.
- For External IP, select New static IP address…. In the next form, enter a name for the static IP. For example,
om-public-ip. Click Reserve. In the External IP drop-down, select the static IP address you just reserved.
Click Create to deploy the new Ops Manager VM. This may take a few moments.
Navigate to your DNS provider, and modify the entry that points a fully qualified domain name (FQDN) to the Ops Manager VM. Replace the original Ops Manager static IP address with the public IP address of the new Ops Manager VM you created in a previous step.
Warning: In order to set up Ops Manager authentication correctly, Pivotal recommends using a Fully Qualified Domain Name (FQDN) to access Ops Manager. Using an ephemeral IP address to access Ops Manager can cause authentication errors upon subsequent access. If you are importing older Ops Manager settings, you must use the FQDN.
After you complete this procedure, continue the upgrade instructions in Upgrading Pivotal Platform topic.
Later on, if you need to SSH into the Ops Manager VM to perform diagnostic troubleshooting, see SSH into Ops Manager.