Appendix A. Google Cloud Storage configuration

Procedure

1. Log in to the Google developer console (http://console.developers.google.com) with your Google account.
2. Click the Credentials tab and select Service account key from the Create credentials drop-down menu.
3. In the Create service account key screen, select the service account that you want the Block Storage service to use from the Service account drop-down menu.
4. In the same screen, select JSON from the Key type section and click Create. The browser will then download the key to its default download location.

5. Open the file and note the value of the project_id parameter:

   {
     "type": "service_account",
     "project_id": "*cloud-backup-1370*",
   ...

6. Save a copy of the GCS JSON credentials to /home/stack/templates/Cloud-Backup.json.

   Important

   Name the file Cloud-Backup.json and do not change the file name. This JSON file must be in the same directory location as the cinder-backup-gcs.yaml file that you create as part of the procedure in Section A.2, “Creating cinder-backup-gcs.yaml”.

Procedure

1. Copy the text below, paste it into the new file. Do not make any modifications to the file contents.

   heat_template_version: rocky
   
   description: >
     Post-deployment for configuration cinder-backup to GCS
   
   parameters:
     servers:
       type: json
     DeployIdentifier:
       type: string
   
   resources:
     CinderBackupGcsExtraConfig:
       type: OS::Heat::SoftwareConfig
       properties:
         group: script
         config:
           str_replace:
             template: |
               #!/bin/bash
               GCS_FILE=/var/lib/config-data/puppet-generated/cinder/etc/cinder/Cloud-Backup.json
               HOSTNAME=$(hostname -s)
               for NODE in $(hiera -c /etc/puppet/hiera.yaml cinder_backup_short_node_names | tr -d '[]",'); do
                 if [ $NODE == $HOSTNAME ]; then
                   cat <<EOF > $GCS_FILE
               GCS_JSON_DATA
               EOF
                   chmod 0640 $GCS_FILE
                   chown root:42407 $GCS_FILE
                 fi
               done
             params:
               GCS_JSON_DATA: {get_file: Cloud-Backup.json}
   
     CinderBackupGcsDeployment:
       type: OS::Heat::SoftwareDeploymentGroup
       properties:
         servers:  {get_param: servers}
         config: {get_resource: CinderBackupGcsExtraConfig}
         actions: ['CREATE','UPDATE']
         input_values:
           deploy_identifier: {get_param: DeployIdentifier}

2. Save the file as /home/stack/templates/cinder-backup-gcs.yaml.

Procedure

1. Copy the environment file example below. Retain the white space usage.
2. Paste the content into a new file: /home/stack/templates/cinder-backup-settings.yaml.
3. Change the value for backup_gcs_project_id from cloud-backup-1370 to the project ID listed in the Cloud-Backup.json file.
4. Save the file.

Procedure

1. Log in as the stack user.

2. Deploy the configuration:

   $ openstack overcloud deploy --templates \
   -e /home/stack/templates/cinder-backup-settings.yaml

   Important

   If you passed any extra environment files when you created the overcloud, pass them again here using the -e option to avoid making undesired changes to the overcloud.

3. Restart the cinder-backup service after the deployment finishes.