pivotal-cf/terraforming-azure

Name: terraforming-azure

Owner: Pivotal Cloud Foundry

Description: use terraform, deploy yourself a pcf

Created: 2016-10-06 19:08:01.0

Updated: 2018-05-18 16:58:10.0

Pushed: 2018-05-18 16:58:08.0

Homepage:

Size: 87

Language: HCL

GitHub Committers

User	Most Recent Commit	# Commits

Other Committers

User	Email	Most Recent Commit	# Commits

README

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?

Will go from zero to having a deployed ops-manager. You'll get networking, a storage account, and a booted ops-manager VM.

Looking to setup a different IAAS

We have other terraform templates to help you!

• aws
• gcp

Prerequisites

 update
 install terraform

Creating An Automation Account

You need an automation account to deploy anything on top of Azure. However, before you can create an automation account you must be able to log into the Azure portal.

First, find your account by running the following commands using the Azure CLI:

e login
e account list

To create the automation account, you need az-automation. You can use brew or go to the releases and get the necessary binary.

 tap genevieve/tap
 install az-automation

Then run:

utomation \
account some-account-id \
identifier-uri http://example.com \
display-name some-display-name \
credential-output-file some-credentials.tfvars

The file created as an output here should include the following:

cription_id = "some-subscription-id"
nt_id       = "some-tenant-id"
nt_id       = "some-client-id"
nt_secret   = "some-client-secret"

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.

cription_id = "some-subscription-id"
nt_id       = "some-tenant-id"
nt_id       = "some-client-id"
nt_secret   = "some-client-secret"

name              = "banana"
short_name        = "banana"
manager_image_uri = "url-to-opsman-image"
tion              = "West US"
suffix            = "some.domain.com"

Variables

• env_name: (required) An arbitrary unique name for namespacing resources
• env_short_name: (required) Used for creating storage accounts. Must be a-z only, no longer than 10 characters
• subscription_id: (required) Azure account subscription id
• tenant_id: (required) Azure account tenant id
• client_id: (required) Azure automation account client id
• client_secret: (required) Azure automation account client secret
• ops_manager_image_uri: (required) URL for an OpsMan image hosted on Azure
• location: (required) Azure location to stand up environment in
• dns_suffix: (required) Domain to add environment subdomain to

Optional

When deploying the isolation segments tile you can optionally route traffic through a separate domain and load balancer by specifying:

• isolation_segment: (default false) Creates a DNS record and load balancer for isolation segment network traffic when set to true.

Running

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

Standing up environment

aform init
aform plan -out=plan
aform apply plan

Tearing down environment

aform destroy