DEPRECATION

This repo is going to be archived. The terraform templates that should be used for deploying an Ops Manager, PAS and/or PKS, can be found at https://github.com/pivotal/paving No PRs or Issues will be responded to here.

Terraforming OpenStack

How Does One Use This?

Please note that the master branch is generally unstable. If you are looking for something "tested", please consume one of our releases.

What Does This Do?

You will get a booted ops-manager VM plus some networking.

Looking to setup a different IAAS?

• aws
• azure
• gcp
• vsphere

Prerequisites

You will need terraform:

brew update
brew install terraform

Are you using Platform Automation?

Be sure to skip the creation of the Ops Manager VM. Do not include flavor_name and set ops_manager_image = "" in your vars. If you create your Ops Manager using terraform, you will not be able to manage it with Platform Automation.

Deployment of the infrastructure is still required.

Var File

Copy the stub content below into a file called terraform.tfvars and put it in the root of this project.

These vars will be used when you run terraform apply.

You should fill in the stub values with the correct content.

env_name = ""
project = ""
username = ""
password = ""
region = ""
az = ""
auth_url = ""
external_network_name = ""
internal_cidr = ""
ops_manager_image = "/path/to/pcf-openstack-2.1-build.214.raw"
keypair = ""
key = <<KEY
-----BEGIN RSA PRIVATE KEY-----
-----END RSA PRIVATE KEY-----
KEY

Var Details

• env_name: (required) An arbitrary unique name for namespacing resources.
• project: (required) The name of the tenant (Identity v2) or project (Identity v3) to login with.
• username: (required) The username to login with.
• password: (required) The password to login with.
• region: (required) The region of the OpenStack cloud to use.
• auth_url: (required) The identity authentication url.
• domain: (optional) The name of the domain to scope to (Identity v3). Defaults to default.
• external_network_name: (required) The name of the external network.
• internal_cidr: (required) CIDR representing the IP range for the subnet.
• flavor_name: (optional) The name of the desired flavor for the Ops Manager instance. Defaults to m1.large.
• ops_manager_image: (required) The local file path to the raw image to boot the Ops Manager instance.
• key: (required) The contents of the client private key file for SSL client authentication.
• keypair: (required) The name of an existing key pair to put on the Ops Manager instance.
• optional_ops_manager: (optional) Set to 1 to deploy a second Ops Manager instance. Defaults to 0.
• optional_ops_manager_image: (optional) The local file path to the raw image to boot the second Ops Manager instance. Defaults to to "".

Running

Note: please make sure you have created the terraform.tfvars file above as mentioned.

Standing up environment

terraform init
terraform plan -out=plan
terraform apply plan

Tearing down environment

Note: This will only destroy resources deployed by Terraform. You will need to clean up anything deployed on top of that infrastructure yourself (e.g. by running om delete-installation)

terraform destroy