Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft: Support for multiple BSLs/Clouds #47

Merged
merged 4 commits into from
Nov 15, 2022
Merged

Conversation

Lirt
Copy link
Owner

@Lirt Lirt commented Nov 10, 2022

If we specify multiple clouds for example into clouds.yaml file, we need to have a way how to pick which cloud to use for specific backup. For this we can set cloud name into BackupStorageLocation or VolumeSnapshotLocation and plugin will pick which cloud to use for authentication and further operations.

Signed-off-by: Ondrej Vasko ondrej.vaskoo@gmail.com

@Lirt Lirt self-assigned this Nov 10, 2022
@Lirt Lirt changed the title Use cloud name from configuration Draft: Use cloud name from configuration Nov 10, 2022
@Lirt Lirt marked this pull request as draft November 10, 2022 12:43
@Lirt Lirt force-pushed the use-cloud-from-configuration branch from 82a80b7 to cc12a6b Compare November 10, 2022 12:58
If we specify multiple clouds for example into clouds.yaml file, we need
to have a way how to pick which cloud to use for specific backup. For
this we can set cloud name into BackupStorageLocation or
VolumeSnapshotLocation and plugin will pick which cloud to use for
authentication and further operations.

Signed-off-by: Ondrej Vasko <ondrej.vaskoo@gmail.com>
@Lirt
Copy link
Owner Author

Lirt commented Nov 11, 2022

This PR is currently blocked by issue vmware-tanzu/velero#5582.

Edit: The issue was in the code. I had to create new provider and client in every Init() request from Velero

@Lirt Lirt force-pushed the use-cloud-from-configuration branch from cc12a6b to 6e4d3b9 Compare November 11, 2022 00:23
When using multiple backupstoragelocations velero switches between them
executing various operations from plugin interface. In case we skip
reauthentication velero can use old provider client and service client
while in correct case it should authenticate again using another cloud
ID

Signed-off-by: Ondrej Vasko <ondrej.vaskoo@gmail.com>
@Lirt Lirt force-pushed the use-cloud-from-configuration branch from 15d649c to 0854b09 Compare November 11, 2022 11:47
@Lirt Lirt changed the title Draft: Use cloud name from configuration Draft: Support for multiple BSLs/Clouds Nov 12, 2022
Signed-off-by: Ondrej Vasko <ondrej.vaskoo@gmail.com>
@Lirt Lirt force-pushed the use-cloud-from-configuration branch from ebbf804 to e3f6cfa Compare November 12, 2022 12:46
Signed-off-by: Ondrej Vasko <ondrej.vaskoo@gmail.com>
@Lirt Lirt marked this pull request as ready for review November 15, 2022 09:54
@Lirt Lirt merged commit d9fc7f3 into master Nov 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant