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

As a domain user, I can change my storage system credentials and Pulp will migrate my data #3358

Open
bmbouter opened this issue Oct 25, 2022 · 1 comment · May be fixed by #4298
Open

As a domain user, I can change my storage system credentials and Pulp will migrate my data #3358

bmbouter opened this issue Oct 25, 2022 · 1 comment · May be fixed by #4298
Assignees

Comments

@bmbouter
Copy link
Member

bmbouter commented Oct 25, 2022

Motivation

Assume the user is already a domain user. The user needs to migrate data from one storage backend to another. For example:

  • I'm using local filesystem storage and I want to try the cloud cuz it's awesome.
  • I'm using the AWS S3 and I want to try Azure Storage because our company decided to consolidate to Azure
  • I'm using Azure and I want to switch to local filesystem because I realized I'm overpaying

Expectations

  1. Pulp should copy the Artifacts from one storage backend to the other when a user changes their domain storage settings.
  2. Pulp needs to remain online while this occurs.

Technical planning

  • It needs to happen asynchronously in the background as a task.
@ipanova
Copy link
Member

ipanova commented Oct 26, 2022

Thanks for sharing that article, interesting read.

@gerrod3 gerrod3 self-assigned this Aug 16, 2023
gerrod3 added a commit to gerrod3/pulpcore that referenced this issue Aug 17, 2023
gerrod3 added a commit to gerrod3/pulpcore that referenced this issue Aug 17, 2023
gerrod3 added a commit to gerrod3/pulpcore that referenced this issue Aug 17, 2023
gerrod3 added a commit to gerrod3/pulpcore that referenced this issue Aug 17, 2023
gerrod3 added a commit to gerrod3/pulpcore that referenced this issue Aug 17, 2023
gerrod3 added a commit to gerrod3/pulpcore that referenced this issue Aug 18, 2023
gerrod3 added a commit to gerrod3/pulpcore that referenced this issue Aug 18, 2023
gerrod3 added a commit to gerrod3/pulpcore that referenced this issue Aug 18, 2023
gerrod3 added a commit to gerrod3/pulpcore that referenced this issue Aug 23, 2023
gerrod3 added a commit to gerrod3/pulpcore that referenced this issue Aug 23, 2023
gerrod3 added a commit to gerrod3/pulpcore that referenced this issue Aug 23, 2023
gerrod3 added a commit to gerrod3/pulpcore that referenced this issue Aug 25, 2023
gerrod3 added a commit to gerrod3/pulpcore that referenced this issue Aug 25, 2023
gerrod3 added a commit to gerrod3/pulpcore that referenced this issue Aug 28, 2023
gerrod3 added a commit to gerrod3/pulpcore that referenced this issue Aug 30, 2023
gerrod3 added a commit to gerrod3/pulpcore that referenced this issue Apr 24, 2024
gerrod3 added a commit to gerrod3/pulpcore that referenced this issue Apr 24, 2024
gerrod3 added a commit to gerrod3/pulpcore that referenced this issue Apr 24, 2024
gerrod3 added a commit to gerrod3/pulpcore that referenced this issue Apr 24, 2024
gerrod3 added a commit to gerrod3/pulpcore that referenced this issue May 14, 2024
gerrod3 added a commit to gerrod3/pulpcore that referenced this issue May 14, 2024
gerrod3 added a commit to gerrod3/pulpcore that referenced this issue May 14, 2024
gerrod3 added a commit to gerrod3/pulpcore that referenced this issue May 16, 2024
gerrod3 added a commit to gerrod3/pulpcore that referenced this issue May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

4 participants