Tooling to move projects between shards

https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/4578 added multiple repository storage paths. Now, for EE users we want to provide a way to move projects between shards.

@pcarranza proposed a rake task to which you would provide project ids and a shard name that would do the moving of those projects.

Later we want to have a configuration to do it directly from the UI, maybe on the Edit Project page (thoughts on this, @jschatz1?)

mentioned in issue #583 (closed)

Reassigned to @eReGeBe

Started branch 759-tooling-to-move-projects-between-shards

mentioned in merge request !533 (merged)

@eReGeBe Second part not critical, admins usually live in the darkness of a black console.

What matters and should be discussed as part of the product is the fact that we need to lock the repo so nothing gets pushed to it.

@eReGeBe @pcarranza I honestly don't think that project owners should be able to move the projects between shards. I think only admins should worry about the black box, so to say.

I agree @JobV this is a feature for system administrators, not project administrators.

Milestone changed to %8.11

Status changed to closed by merge request !533 (merged)

What's the reasoning for having this on EE only? It seems like this should be on CE as well or multiple repository storage paths should only be supported on EE.

@bbodenmiller more relevant for organizations that have more than 100 users, see https://about.gitlab.com/about/#stewardship

We decided to add multiple repository storage paths to both to prevent CE and EE diverging too much.

I agree the usefulness of multiple repository storage paths is reduced if you can't move repo's. However we did use multiple repository storage paths without being able to move. But in that case it is more of a short term fix than a long term one.