Migrate Spaces to new instance

[AliveDevil]

Description

Currently there is no way of migrating one OCIS installation (with all Spaces included) to another, with a different backend (POSIX -> S3NG, or vice versa).

User Stories

• As a sys-admin, I want to be able to copy spaces verbatim, so that I can migrate data to other storage backends.

Value

• Ease migration between storage backends

Acceptance Criteria

• Migration cli command that copies all blobs from one blobstore into another

Definition of ready

• [ ] Everybody needs to understand the value written in the user story
• [ ] Acceptance criteria have to be defined
• [ ] All dependencies of the user story need to be identified
• [ ] Feature should be seen from an end user perspective
• [ ] Story has to be estimated
• [ ] Story points need to be less than 20

Definition of done

• Functional requirements
  • [ ] Functionality described in the user story works
  • [ ] Acceptance criteria are fulfilled
• Quality
  • [ ] Code review happened
  • [ ] CI is green (that includes new and existing automated tests)
  • [ ] Critical code received unit tests by the developer
• Non-functional requirements
  • [ ] No sonar cloud issues
• Configuration changes
  • [ ] The next branch of the ocis charts is compatible

[micbar]

@butonic @kobergj

As we are currently implementing #9004 , we could easily extend that to download all blobs to the decomposed FS or upload all blobs to the S3 (two way migration).

[kobergj]

This is not really what https://github.com/owncloud/ocis/issues/9004 is for. It is simply checking for consistency, not downloading any blobs.

But we could build a similar command that migrates blobs from one store to another.

[micbar]

But we could build a similar command that migrates blobs from one store to another.

Yes. That is what i meant. But you already did some ground work in reva to export some props to get that done.

[kobergj]

Sounds good :+1:

So the action item would be to create a cli command that copies all blobs from one blobstore into another. Using the new List method on the source blobstore should make this a straightforward task. We will not validate anything, just copy the blobs into the new store.

[AliveDevil]

That would be fine by me, and even more premium than the initial option of just keeping the ids and copying data manually.

[AliveDevil]

Updated entry post. Anything to amend?

[micbar]

@tbsbdr @dragotin we need to squeeze that in.

[micbar]

Added to backlog. Candidate for next sprint.

[butonic]

I am reading this as 'only copy blobs between blobstores' not anything related to metadata, right? The latter would require a Dump and Load mechanism for node metadata.