Bug 1539135

Is there a TripleO support for enabling and configuring This feature?
IS Google cloud backup support encryption ?

Acking OtherQA feature

Avi is correct; this feature needs TripleO support. That effort is not huge, but also not trivial. It should start with a TripleO blueprint, which needs to be submitted soon before the Rocky soft feature freeze.

(In reply to Alan Bishop from comment #10)
> Avi is correct; this feature needs TripleO support. That effort is not huge,
> but also not trivial. It should start with a TripleO blueprint, which needs
> to be submitted soon before the Rocky soft feature freeze.

This was discussed in today's Cinder squad meeting. The focus in OSP-14 is the on  the underlying cinder backup driver, and TripleO support will be delivered in a subsequent release.

New RFE for OSP15 add triple0 support
https://bugzilla.redhat.com/show_bug.cgi?id=1601211

FYI Kim, sure enough hit doc bugs->
https://bugzilla.redhat.com/show_bug.cgi?id=1609554

Gorka, do you have tips on deployment?
Where do I save Google account.json?
Guide suggest /etc/cinder on controller, invalid path once Cinder is dockerized(OSP13).

If under same path (/etc/cinder) but once inside one of Cinder's docker, which docker volume/api/backup..?

Didn't take long, I assume correct path for Google auth json should -> 

/var/lib/config-data/puppet-generated/cinder/etc/cinder/

Gorka (maybe I should ask Alan), 

Deployment issue with yaml, ospd guide's method, something didn't work see #25.

However pasting these[0] directory into cinder.conf
+ restarting volume+backup dockers, I was pleasantly shocked to successfully complete a backup with Google, watched it live on backup.logs :) 

GOOD job dude! 


[0]
#backup_driver=cinder.backup.drivers.swift
backup_driver = cinder.backup.drivers.google
backup_gcs_credential_file=/etc/cinder/gbackup.json
backup_gcs_bucket=mycinderbucket
backup_gcs_project_id=cloudforms-validation
backup_gcs_user_agent=gcscinder

gbackup.json auth file shared with me. 
inside the docker resides on /etc/cinder/gbackup.json

Have any idea, what I did wrong with OSPD guide/yaml instructions?
Or like me you also just added stuff under cinder.conf?

Based on my failed attempt to re-deploy overcloud with Google backup, opened new THT Bug
https://bugzilla.redhat.com/show_bug.cgi?id=1609707

I just replied to the other bug. I think you just have a YAML syntax error, that can be resolved by adding a ':' colon to the lines that start with "DEFAULT/"

(typing this from the Edinburgh bus station)

Yep Alan, adding comment on that bz1609707
 adding a ':' advanced somewhat but still fails to deploy. 

Setting depends on that bz.

Added depends on RFE THT add Google cloud backup driver support. 
https://bugzilla.redhat.com/show_bug.cgi?id=1622504

Verified on:
openstack-cinder-13.0.1-0.20181013185427.31ff628.el7ost.noarch

Test plan passed without a hitch. 

FYI we are still missing THT support see bz1601211.
I had to use a workaround for configuration.
Till we get THTs, test cases are simple to automate, yet deployment is still manual.

Tzach,

When you were testing this, did the GCS driver config stay in place if you did another openstack overcloud deploy command? 

Kim

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:0045