Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1512962 - [INFRA] Implement backups for
Summary: [INFRA] Implement backups for
Status: NEW
Alias: None
Product: RDO
Classification: Community
Component: Infrastructure
Version: unspecified
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: trunk
Assignee: Javier Peña
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2017-11-14 14:13 UTC by David Moreau Simard
Modified: 2018-11-28 14:05 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:

Attachments (Terms of Use)

Description David Moreau Simard 2017-11-14 14:13:36 UTC
I suspect it would be hard to back up the actual OpenShift instance (mix of blob storage, etcd, containers, etc.).

What is valuable is really the container images themselves -- the registry can be reinstalled from scratch within 30 minutes if need be.

We could have a small (regular? or openshift?) registry backup instance offsite where we would mirror specifically tagged images (current-tripleo/current-tripleo-rdo).

Skopeo, for example [1] has a feature to easily copy images from a registry to the other.
We should discuss the implementation so that it's as low maintenance as possible.


Comment 1 David Moreau Simard 2017-11-16 21:33:41 UTC
Hmm.. I'm not sure to what extent we need to handle the backups ourselves actually.

We could simply mirror ourselves to DockerHub and fall back to DockerHub in case of outage.

We could push images like described here [1].


Comment 2 Alan Pevec 2018-11-28 14:05:20 UTC
Tracking status in

Note You need to log in before you can comment on or make changes to this bug.