migtools / mig-ui

Openshift Migration UI
Apache License 2.0
10 stars 31 forks source link

UI needs to differentiate VSL from BSL in replication repository #443

Open dymurray opened 5 years ago

dymurray commented 5 years ago

When a user creates a replication repository in the UI, we create a migstorage object that has a backupStorageConfig and a volumeSnapshotConfig in the spec. We fill out the volumeSnapshotConfig and backupStorageConfig details using information from a single form. This means that whatever credentials I specify in the Replication Repository, the created secret will be used for both configurations. This causes problems when using Minio, as I enter information that is only relevant for an S3 storage endpoint, and nothing to do with volume snapshots. Currently, configuring minio in the replication repository and then trying a migration will fail since the VSL validation will error out.

When creating a replication repository, the user needs the option to either use the same set of credentials/region information for the VSL, or they should be able to configure it separately.

jwmatthews commented 5 years ago

As an example....

I may be running OpenShift on Bare Metal and I am doing a migration to another bare metal cluster. I want to use NooBaa for S3 storage and I have no intentions to use VSL as all of my PV data will use Restic and go to the configured BSL.

I would set data for BSL and nothing for VSL

eriknelson commented 4 years ago

It's not clear to me how important this is for our use-cases right now. We should bring this up on a scrum call to determine.