Bug #1903914 adds support for storing cinder backups on an S3 server. This RFE adds TripleO support for deploying the S3 backup driver via the director.
Hi, I verified the fix with the DCI component RHOS-17.1-RHEL-9-20230329.n.1. Environment file used for the deployment: --- (dci171e1r1) [stack@dci171e1d ~]$ cat templates/cinder-backup-settings.yaml resource_registry: OS::TripleO::Services::CinderBackup: /usr/share/openstack-tripleo-heat-templates/deployment/cinder/cinder-backup-pacemaker-puppet.yaml # Use cinder-backup-active-active.yaml for non-pcmk managed implementation # parameter_defaults: CinderBackupCompressionAlgorithm: zstd CinderBackupBackend: s3 CinderBackupS3EndpointUrl: http://192.168.1.1:9000 CinderBackupS3AccessKey: xxxxxxxx CinderBackupS3SecretKey: xxxxxxxx CinderBackupS3Bucket: testbucket --- The backup volume data is stored in the s3. --- (dci171e1r1) [stack@dci171e1d heat-stack-files]$ openstack volume backup create testvol --name testbk +-------+--------------------------------------+ | Field | Value | +-------+--------------------------------------+ | id | 466d0669-5fe6-4d72-974a-92f3e521bacc | | name | testbk | +-------+--------------------------------------+ (dci171e1r1) [stack@dci171e1d ~]$ mc admin info mclocal ● 192.168.1.1:9000 Uptime: 21 hours Version: 2023-03-24T21:41:23Z Network: 1/1 OK Drives: 1/1 OK Pool: 1 Pools: 1st, Erasure sets: 1, Drives per erasure set: 1 2.3 MiB Used, 1 Bucket, 23 Objects 1 drive online, 0 drives offline (dci171e1r1) [stack@dci171e1d ~]$ mc ls mclocal/testbucket/volume_fb94e062-c6bb-4bc7-bc9a-9a99befc13c5/20230331180416/ [2023-03-31 14:04:17 EDT] 3.0KiB STANDARD az_nova_backup_466d0669-5fe6-4d72-974a-92f3e521bacc-00001 [2023-03-31 14:04:17 EDT] 1.6KiB STANDARD az_nova_backup_466d0669-5fe6-4d72-974a-92f3e521bacc-00002 [2023-03-31 14:04:18 EDT] 1.6KiB STANDARD az_nova_backup_466d0669-5fe6-4d72-974a-92f3e521bacc-00003 [2023-03-31 14:04:18 EDT] 1.6KiB STANDARD az_nova_backup_466d0669-5fe6-4d72-974a-92f3e521bacc-00004 [2023-03-31 14:04:19 EDT] 1.6KiB STANDARD az_nova_backup_466d0669-5fe6-4d72-974a-92f3e521bacc-00005 [2023-03-31 14:04:19 EDT] 2.0KiB STANDARD az_nova_backup_466d0669-5fe6-4d72-974a-92f3e521bacc-00006 [2023-03-31 14:04:19 EDT] 1.6KiB STANDARD az_nova_backup_466d0669-5fe6-4d72-974a-92f3e521bacc-00007 [2023-03-31 14:04:20 EDT] 1.6KiB STANDARD az_nova_backup_466d0669-5fe6-4d72-974a-92f3e521bacc-00008 [2023-03-31 14:04:20 EDT] 1.6KiB STANDARD az_nova_backup_466d0669-5fe6-4d72-974a-92f3e521bacc-00009 [2023-03-31 14:04:21 EDT] 1.6KiB STANDARD az_nova_backup_466d0669-5fe6-4d72-974a-92f3e521bacc-00010 [2023-03-31 14:04:21 EDT] 8.8KiB STANDARD az_nova_backup_466d0669-5fe6-4d72-974a-92f3e521bacc-00011 [2023-03-31 14:04:21 EDT] 1.6KiB STANDARD az_nova_backup_466d0669-5fe6-4d72-974a-92f3e521bacc-00012 [2023-03-31 14:04:22 EDT] 1.6KiB STANDARD az_nova_backup_466d0669-5fe6-4d72-974a-92f3e521bacc-00013 [2023-03-31 14:04:22 EDT] 1.6KiB STANDARD az_nova_backup_466d0669-5fe6-4d72-974a-92f3e521bacc-00014 [2023-03-31 14:04:23 EDT] 1.6KiB STANDARD az_nova_backup_466d0669-5fe6-4d72-974a-92f3e521bacc-00015 [2023-03-31 14:04:23 EDT] 2.0KiB STANDARD az_nova_backup_466d0669-5fe6-4d72-974a-92f3e521bacc-00016 [2023-03-31 14:04:24 EDT] 1.6KiB STANDARD az_nova_backup_466d0669-5fe6-4d72-974a-92f3e521bacc-00017 [2023-03-31 14:04:24 EDT] 1.6KiB STANDARD az_nova_backup_466d0669-5fe6-4d72-974a-92f3e521bacc-00018 [2023-03-31 14:04:24 EDT] 1.6KiB STANDARD az_nova_backup_466d0669-5fe6-4d72-974a-92f3e521bacc-00019 [2023-03-31 14:04:25 EDT] 1.6KiB STANDARD az_nova_backup_466d0669-5fe6-4d72-974a-92f3e521bacc-00020 [2023-03-31 14:04:25 EDT] 930B STANDARD az_nova_backup_466d0669-5fe6-4d72-974a-92f3e521bacc-00021 [2023-03-31 14:04:25 EDT] 8.1KiB STANDARD az_nova_backup_466d0669-5fe6-4d72-974a-92f3e521bacc_metadata [2023-03-31 14:04:25 EDT] 2.3MiB STANDARD az_nova_backup_466d0669-5fe6-4d72-974a-92f3e521bacc_sha256file --- Thank you for providing the fix! Best regards, Yusuke Okada
Director can set the parameters required to configure cinder-backup with S3 (and also the compression method). The parameters are: CinderBackupBackend: 's3' CinderBackupS3EndpointUrl: 'http://urlofthes3server' CinderBackupS3AccessKey: 'some_access_key' CinderBackupS3SecretKey: 'some_secret_key' CinderBackupS3Bucket: 'some_bucket' CinderBackupCompressionAlgorithm: 'zstd' Those are translated to cinder.conf as: backup_s3_endpoint_url=http://urlofthes3server backup_s3_store_access_key=some_access_key backup_s3_store_secret_key=some_secret_key backup_s3_store_bucket=some_bucket backup_driver=cinder.backup.drivers.s3.S3BackupDriver backup_compression_algorithm=zstd --- openstack-tripleo-heat-templates-14.3.1-1.20230428140957.004ef6e.el9ost puppet-cinder-18.5.2-1.20230127000858.6aa60e7.el9ost.noarch puppet-tripleo-14.2.3-1.20230323230826.d0c3708.el9ost.noarch
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 (Release of components for Red Hat OpenStack Platform 17.1 (Wallaby)), 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-2023:4577