Deploy Ops Manager and Bosh Director

Description

Assumptions

• Docker is installed
• Platform Automation Docker Image has been downloaded from the Pivotal Network and placed in a sibling directory named artifacts
• Ops Manager yaml for GCP has been downloaded from the Pivotal Network and placed in a sibling directory named artifacts
• GCP was paved (terraform)
• A file named terraform-outputs.yml was generated, and resides one directory above the path to this cloned repository, containing references to the resources generated by terraform
• direnv is installed and configured in your shell
• om cli is installed

Steps

1. Import the platform automation docker image into docker

   docker import ../artifacts/platform-automation-image-*.tgz platform-automation-image

2. Run p-automator inside the docker image to create the Ops Manager VM

   docker run -it --rm -v $PWD/..:/workspace -w /workspace/opsman-director platform-automation-image \
     p-automator create-vm \
       --config opsman-config.yml \
       --image-file ../artifacts/ops-manager*.yml \
       --vars-file ../terraform-outputs.yml

3. Configure a .envrc file with these environment variables. Choose a username, password, and decryption passphrase for your new Ops Manager.

   • OM_TARGET (Ops Manager URL)
   • OM_USERNAME (admin is a good choice)
   • OM_PASSWORD
   • OM_DECRYPTION_PASSPHRASE
   • OM_SKIP_SSL_VALIDATION (set it to true if using a self-signed certificate)

   Use envrc.example as a template.

   Make sure to direnv allow before proceeding to the next step.

4. Configure authentication to Ops Manager

   om --env env.yml configure-authentication \
     --decryption-passphrase ${OM_DECRYPTION_PASSPHRASE}

5. Configure the BOSH director

   om --env env.yml configure-director \
     --config director-config.yml \
     --vars-file ../terraform-outputs.yml

6. Provision the bosh director

   om --env env.yml apply-changes \
     --skip-deploy-products