Bug 1659888
Summary: | Not a good idea to store undercloud backups in Swift | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Dan Macpherson <dmacpher> |
Component: | python-tripleoclient | Assignee: | Juan Badia Payno <jbadiapa> |
Status: | CLOSED WONTFIX | QA Contact: | Gurenko Alex <agurenko> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 13.0 (Queens) | CC: | aschultz, beth.white, hbrock, jbadiapa, jbuchta, jslagle, mburns, rmccabe, tdunnon |
Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-03-09 14:56:30 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Dan Macpherson
2018-12-17 06:33:20 UTC
I feel that this is more related to user action than to the swift system. Probably changing the default would be enough. What would be the default action? The exponential backup problem seems bad but it seems like the correct behaviour if you want a backup of your backup these things happen. (In reply to Adriano Petrich from comment #1) > I feel that this is more related to user action than to the swift system. > Probably changing the default would be enough. What would be the default > action? When you say "default action", are we talking about mistral actions? If so, the relevant actions are: * tripleo.undercloud.create_file_system_backup, which maps to class CreateFileSystemBackup in tripleo-common -- this creates the filesystem backup, including the swift objects * tripleo.undercloud.upload_backup_to_swift which maps to class UploadUndercloudBackupToSwift in tripleo-common -- this saves the resulting backup to swift So might need to change the component of this BZ to tripleo-common > The exponential backup problem seems bad but it seems like the correct > behaviour if you want a backup of your backup these things happen. It seems a little redundant and impractical to backup a backup and then upload it to the same location as the original backup. I'm not sure why anyone would want this to be standard behaviour. Agreed in all counts. When I said the default action it was bad semantics. I meant should the default be store to disk? because that is already an intermediary step. What could be done is that uploading to swift and deleting the temporary directory be an optional step. The new backups would not contain the previous ones if they are not in swift and the backup dir is outside the regular folders to be backupped. Pretty much. Ideally you'd want store the backup in a location not included in the filesystem backup to avoid the exponential backup size. We are moving all the backup and restore feature to use ReaR. With the use of ReaR as our main method of backup and recovery this bug will be closed. |