Openebs: Update the design/workflow for S3 Backup/Restore

Created on 13 Apr 2017  路  6Comments  路  Source: openebs/openebs

arevolume arevolumbackup-s3 kindesign summerhack

Most helpful comment

I'd certainly like to pitch in and make this a reality. I have another project where I've come to rely on openEBS.

Kubash

As some future steps there I'd like to setup minio and then get backups running in a kubernetes cronjob

All 6 comments

Feasibility of using the existing longhorn S3 functionality was evaulated and shown to be working. The longhorn replicas where required to be provided with the S3 credentials in a ~.aws/credentials - secret_access_key, access_key_id.

To the backup api should be passed with the bucket url.

Can this be genericized to work witn minio? I see that project as very much akin to this project in many ways and makes a lot of sense in attaining cloud agnosticity. @

Yes @joshuacox Making this work with any S3 interface including minio sounds like the right approach.

I'd certainly like to pitch in and make this a reality. I have another project where I've come to rely on openEBS.

Kubash

As some future steps there I'd like to setup minio and then get backups running in a kubernetes cronjob

This is being worked on by writing OpenEBS plugin to Ark (Valero) https://github.com/heptio/velero

Minio and other S3 compatible storage can be used for backup and restore. Instructions are here under OpenEBS docs https://docs.openebs.io/docs/next/backup.html

Was this page helpful?
0 / 5 - 0 ratings