Skip to content

Latest commit

 

History

History
313 lines (228 loc) · 13.7 KB

installation.md

File metadata and controls

313 lines (228 loc) · 13.7 KB
Raw

Installing the broker on GCP

The broker service and the GCP brokerpak can be pushed and registered on a foundation running on GCP.

Documentation for broker configuration can be found here.

Requirements

CloudFoundry running on GCP.

The GCP brokerpak services are provisioned with firewall rules that only allow internal connectivity. This allows cf pushed applications access, while denying any public access.

GCP Service Credentials

Set up a GCP Project

  1. Go to the Google Cloud Console and sign up, walking through the setup wizard.
  2. A page then displays with a collection of options. Select "Create Project" option.
  3. Give your project a name and click "Create".
  4. The dashboard for the newly created project will be displayed.

Enable APIs

Enable the following services in APIs and services > Library.

  1. Enable the Google Cloud Resource Manager API
  2. Enable the Google Identity and Access Management (IAM) API
  3. If you want to enable CloudSQL as a service (MySQL and PostgreSQL), enable the CloudSQL API, CloudSQL Admin API, and Service Networking API
  4. If you want to enable BigQuery as a service, enable the BigQuery API
  5. If you want to enable Cloud Storage as a service, enable the Cloud Storage API
  6. If you want to enable Bigtable as a service, enable the Bigtable Admin API
  7. If you want to enable Datastore as a service, enable the Datastore API

Create a root service account

  1. From the GCP console, navigate to IAM & Admin > Service accounts and click Create Service Account.
  2. Enter a Service account name.
  3. In the Project Role dropdown, choose Project > Owner.
  4. Select the checkbox to Furnish a new Private Key, make sure the JSON key type is specified.
  5. Click Save to create the account, key and grant it the owner permission.
  6. Save the automatically downloaded key file to a secure location.

MySQL Database for Broker State

The broker keeps service instance and binding information in a MySQL database.

Binding a MySQL Database

If there is an existing broker in the foundation that can provision a MySQL instance use cf create-service to create a new MySQL instance. Then use cf bind-service to bind that instance to the service broker.

Scripted

Use scripts/gcp-create-mysql-db.sh to create a GCP mysql instance. It will report the DB_HOST (ip address) username, password and db name upon completion.

It requires the gcloud cli be installed.

Manually Provisioning a MySQL Database

The GCP Service Broker stores the state of provisioned resources in a MySQL database. You may use any database compatible with the MySQL protocol. We recommend a second generation GCP CloudSQL instance with automatic backups, high availability and automatic maintenance. The service broker does not require much disk space, but we do recommend an SSD for faster interactions with the broker.

  1. Create new MySQL instance.
  2. CloudSQL Only Make sure that the database can be accessed, add 0.0.0.0/0 as an authorized network.
  3. Run CREATE DATABASE servicebroker;
  4. Run CREATE USER '<username>'@'%' IDENTIFIED BY '<password>';
  5. Run GRANT ALL PRIVILEGES ON servicebroker.* TO '<username>'@'%' WITH GRANT OPTION;
  6. CloudSQL Only (Optional) create SSL certs for the database and save them somewhere secure.

The following configuration parameters will be needed:

  • DB_HOST
  • DB_USERNAME
  • DB_PASSWORD

Set required environment variables

Add these to the env section of manifest.yml

  • GOOGLE_CREDENTIALS - the string version of the credentials file created for the Owner level Service Account.
  • SECURITY_USER_NAME - the username to authenticate broker requests - the same one used in cf create-service-broker.
  • SECURITY_USER_PASSWORD - the password to authenticate broker requests - the same one used in cf create-service-broker.
  • DB_HOST - the host for the database to back the service broker.
  • DB_USERNAME - the database username for the service broker to use.
  • DB_PASSWORD - the database password for the service broker to use.

Create Private Service Connection in GCP

To allow CF applications to connect to service instances created by CSB, follow these instructions to enable private service access to the VPC network that your foundation is running in.

To peer the service network (that mysql and postgres instances are connected to) and your VPC, the following commands need to be run once. Note that the prefix-length (subnet mask) value depends on how many databases are created. If you run out of available IP addresses then consider using a lower number.

VPC_NETWORK_NAME=[the name of your VCP network]
PROJECT=[your GCP project id]
gcloud compute addresses create google-managed-services-mysql-${VPC_NETWORK_NAME} \
    --global \
    --purpose=VPC_PEERING \
    --prefix-length=23 \
    --network=${VPC_NETWORK_NAME} \
    --project=${PROJECT}

gcloud services vpc-peerings connect \
    --service=servicenetworking.googleapis.com \
    --ranges=google-managed-services-mysql-${VPC_NETWORK_NAME} \
    --network=${VPC_NETWORK_NAME} \
    --project=${PROJECT}

if you use scripts/gcp-create-mysql-db.sh to create the mysql metadata database for the broker, these steps are already done.

Authorized Network ID

When using private service connections, the ID for the VPC network must be provided in the authorized_network_id parameter when creating service instances. To get the ID of the given network, use

gcloud compute networks list --filter="name=$GCP_PAS_NETWORK" --uri

where GCP_PAS_NETWORK is the name of the network used when creating the private service network peering above.

Fetch A Broker and GCP Brokerpak

Download a Cloud Service Broker release from https://github.com/cloudfoundry/cloud-service-broker/releases. Find the latest release matching the name pattern vX.X.X. Change filename cloud-service-broker.linux to cloud-service-broker. Add execution permissions chmod +x cloud-service-broker

Download a GCP Brokerpak release from https://github.com/cloudfoundry/csb-brokerpak-gcp/releases. Find the latest release matching the name pattern X.X.X.

Put the cloud-service-broker and gcp-services-X.X.X.brokerpak into the same directory on your workstation.

Create a MySQL instance with GCP broker

If there is an existing GCP broker in the foundation that can provision a MySQL instance use cf create-service to create a new MySQL instance. Then use cf bind-service to bind that instance to the service broker app.

The following command will create a basic MySQL database instance named csb-sql

cf create-service <MySQL_SERVICE_OFFERING_NAME> <PLAN_NAME> csb-sql [-b <SERVICE_BROKER_NAME>]

Build Config File

To avoid putting any sensitive information in environment variables, a config file can be used.

Create a file named config.yml in the same directory the broker and brokerpak have been downloaded to. Its contents should be:

gcp:
  google_credentials: the string version of the credentials file created for the Owner level Service Account
  google_project: Give your project id or name

Add your custom plans to the config.yml file, for example, plans for MySQL

service:
  csb-google-mysql:
    plans: '[{"name":"default","id":"eec62c9b-b25e-4e65-bad5-6b74d90274bf","description":"Default MySQL v8.0 10GB storage","metadata":{"displayName":"default"},"mysql_version":"MYSQL_8_0","storage_gb":10,"tier":"db-n1-standard-2"}]'

Push and Register the Broker

Push the broker as a binary application:

SECURITY_USER_NAME=someusername
SECURITY_USER_PASSWORD=somepassword
APP_NAME=cloud-service-broker

chmod +x cloud-service-broker
cf push "${APP_NAME}" -c './cloud-service-broker serve --config config.yml' -b binary_buildpack --random-route --no-start

Bind the MySQL database and start the service broker:

cf bind-service cloud-service-broker csb-sql
cf start "${APP_NAME}"

Register the service broker:

BROKER_NAME=csb-$USER

cf create-service-broker "${BROKER_NAME}" "${SECURITY_USER_NAME}" "${SECURITY_USER_PASSWORD}" https://$(LANG=EN cf app "${APP_NAME}" | grep 'routes:' | cut -d ':' -f 2 | xargs) --space-scoped || cf update-service-broker "${BROKER_NAME}" "${SECURITY_USER_NAME}" "${SECURITY_USER_PASSWORD}" https://$(LANG=EN cf app "${APP_NAME}" | grep 'routes:' | cut -d ':' -f 2 | xargs)

Once this completes, the output from cf marketplace should include:

csb-google-mysql    default   Default MySQL v8.0 10GB storage
....

Step By Step From a Pre-built Release with a Manually Provisioned MySQL Instance

Fetch a pre-built broker and brokerpak and configure with a manually provisioned MySQL instance.

Requirements and assumptions are the same as above. Follow instructions above to fetch the broker and brokerpak

Create a MySQL Database

It's an exercise for the reader to create a MySQL server somewhere that a cf pushed app can access. The database connection values (hostname, username and password) will be needed in the next step. It is also necessary to create a database named servicebroker within that server (use your favorite tool to connect to the MySQL server and issue CREATE DATABASE servicebroker;).

Build Config File

To avoid putting any sensitive information in environment variables, a config file can be used.

Create a file named config.yml in the same directory the broker and brokerpak have been downloaded to. Its contents should be:

gcp:
  google_credentials: the string version of the credentials file created for the Owner level Service Account
  google_project: Give your project id or name

db:
  host: your mysql host
  password: your mysql password
  user: your mysql username

api:
  user: someusername
  password: somepassword

service:
  csb-google-mysql:
    plans: '[{"name":"default","id":"eec62c9b-b25e-4e65-bad5-6b74d90274bf","description":"Default MySQL v8.0 10GB storage","metadata":{"displayName":"default"},"mysql_version":"MYSQL_8_0","storage_gb":10,"tier":"db-n1-standard-2"}]'

Add your custom plans to the config.yml file, for example, plans for MySQL

Push and Register the Broker, see previous section

Once these steps are complete, the output from cf marketplace should resemble the same as above.

Step By Step From Source with Bound MySQL

Grab the source code, build and deploy.

Requirements

The following tools are needed on your workstation:

The Cloud Service Broker for GCP must be installed in your foundation.

Assumptions

The cf CLI has been used to authenticate with a foundation (cf api and cf login,) and an org and space have been targeted (cf target)

Clone the Repo

The following commands will clone the service broker repository and cd into the resulting directory.

git clone https://github.com/cloudfoundry/cloud-service-broker.git
cd cloud-service-broker

Set Required Environment Variables

Collect the GCP Service Account credentials for your account and set them as environment variables:

export GOOGLE_CREDENTIALS=the string version of the credentials file created for the Owner level Service Account;
export GOOGLE_PROJECT=your google project id

Generate username and password for the broker - Cloud Foundry will use these credentials to authenticate API calls to the service broker.

export SECURITY_USER_NAME=someusername
export SECURITY_USER_PASSWORD=somepassword

Create a MySQL instance

It's an exercise for the reader to create a MySQL server somewhere that a cf pushed app can access. If there is an existing GCP broker in the foundation that can provision a MySQL instance use cf create-service to create a new MySQL instance. Then use cf bind-service to bind that instance to the service broker app.

The following command will create a basic MySQL database instance named csb-sql

cf create-service <MySQL_SERVICE_OFFERING_NAME> <PLAN_NAME> csb-sql [-b <SERVICE_BROKER_NAME>]

Use the Makefile to Deploy the Broker

There is a make target that will build the broker and brokerpak and deploy to and register with Cloud Foundry as a space scoped broker. This will be local and private to the org and space your cf CLI is targeting.

make push-broker

Once these steps are complete, the output from cf marketplace should resemble the same as above.

Uninstalling the Broker

First, make sure there are all service instances created with cf create-service have been destroyed with cf delete-service otherwise removing the broker will fail.

Unregister the Broker

cf delete-service-broker csb-$USER

Uninstall the Broker

cf delete cloud-service-broker