Skip to content

rjain-pivotal/gcp-concourse

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Customer0 PCF+GCP Concourse Pipeline

Pre_Reqs & Instructions for POC Deployment via Concourse

  1. Create a Service Account with "Editor" Role on the target GCP Project
  • Non POC versions of the pipeline will support sep Terraform & Opsman Service accounts
  • ENABLE your GCP Compute API here
  • ENABLE your GCP Storage API here
  • ENABLE your GCP SQL API here
  • ENABLE your GCP DNS API here
  • ENABLE your GCP Cloud Resource Manager API here
  • ENABLE & Create GCP Storage Interoperability Tokens here here
  1. Create a Concourse instance with public access for downloads. Look here for vagrant instructions if an ephemeral concourse instance is desired.

  2. git clone this repo

  3. EDIT!!! ci/c0-gcp-concourse-poc-params.yml and replace all variables/parameters you will want for your concourse individual pipeline run

    • The sample pipeline params file includes 2 params that set the major/minor versions of OpsMan & ERT that will be pulled. They will typically default to the latest RC/GA avail tiles.
      opsman_major_minor_version: '1\.9\..*'
      ert_major_minor_version: '1\.9\..*'
      
  4. AFTER!!! Completing Step 4 above ... log into concourse & create the pipeline.

(this command syntax assumes you are at the root of your repo)

  • fly -t [YOUR CONCOURSE TARGET] set-pipeline -p c0-gcp-concourse-base -c ci/c0-gcp-concourse-poc.yml -l ci/c0-gcp-concourse-poc-params.yml
  1. Un-pause the pipeline
  2. Run the init-env job manually, you will need to review the output and record it for the DNS records that must then be made resolvable BEFORE!!! continuing to the next step:
  • Example:
==============================================================================================
This gcp_pcf_terraform_template has an 'Init' set of terraform that has pre-created IPs...
==============================================================================================
Activated service account credentials for: [[email protected]]
Updated property [core/project].
Updated property [compute/region].
You have now deployed Public IPs to GCP that must be resolvable to:
----------------------------------------------------------------------------------------------
*.sys.gcp-poc.customer0.net == 130.211.9.202
*.cfapps.gcp-poc.customer0.net == 130.211.9.202
ssh.sys.gcp-poc.customer0.net == 146.148.58.174
doppler.sys.gcp-poc.customer0.net == 146.148.58.174
loggregator.sys.gcp-poc.customer0.net == 146.148.58.174
tcp.gcp-poc.customer0.net == 104.198.241.71
opsman.gcp-poc.customer0.net == 104.154.98.48
----------------------------------------------------------------------------------------------

[DEPLOY]. AFTER!!! Completing Step 7 above ... Run the deploy-iaas job manually, if valid values were passed, a successful ERT deployment on GCP will be the result.

Added Stop and Start Scripts

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Shell 56.6%
  • HCL 43.4%