Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,767
    • Issues 44,767
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,329
    • Merge requests 1,329
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #10586
You need to sign in or sign up before continuing.
Closed
Open
Issue created Mar 21, 2019 by Gabriel Mazetto@brodock🔴Maintainer5 of 5 checklist items completed5/5 checklist items

Geo: Allow to enable replication for content in Object Storage

According to our current documentation: https://docs.gitlab.com/ee/administration/geo/replication/object_storage.html#geo-with-object-storage when user setup an object storage with Geo, we disable the replication code, as we assume the Object Storage will be configured to handle that.

That is not always the case, if the user is not using a cloud solution that supports replication, or if they are using a local storage appliance that does not support replication logic.

Even in the case where the user has access to a cloud solution, they may still need to backfill any additional node, when bootstrapping from an existing installation, which is usually not a supported feature from cloud providers.


In order to provide a minimal Object Storage replication functionality we need to make some changes:

  • Cover current download logic with specs (not everything is being tested) !13997 (merged)
  • Add settings to Geo Node to enable/disable syncing files in Object Storage !15139 (merged)
  • Make it possible to download files stored in Object Storage via sync API and upload to another Object Storage !15606 (merged)
  • Remove hard-coded restrictions on all finders to expose both local and remote files (remote means Object Storage) !13997 (merged)
  • Implement a new restriction on finders based on GeoNode settings. !13997 (merged)

Does this MR meet the acceptance criteria?

Edited Oct 02, 2019 by Gabriel Mazetto
Assignee
Assign to
Time tracking