Cells

  • Offering: GitLab.com
  • Status: Experiment

This feature is available for administrators of GitLab.com only. This feature is not available for GitLab Self-Managed or GitLab Dedicated instances.

This page contains information related to upcoming products, features, and functionality. It is important to note that the information presented is for informational purposes only. Please do not rely on this information for purchasing or planning purposes. The development, release, and timing of any products, features, or functionality may be subject to change or delay and remain at the sole discretion of GitLab Inc.

Cells 1.0 is in development. For more information about the state of cell development, see epic 12383.

This page explains how to configure the GitLab Rails console for cell functionality. For more information on the proposed design and terminology, see the design document for Cells.

Configuration

The cells related configuration in config/gitlab.yml is in this format:

  cell:
    id: 1
    database:
      skip_sequence_alteration: false
    topology_service:
      enabled: true
      address: topology-service.gitlab.example.com:443
      ca_file: /home/git/gitlab/config/topology-service-ca.pem
      certificate_file: /home/git/gitlab/config/topology-service-cert.pem
      private_key_file: /home/git/gitlab/config/topology-service-key.pem
ConfigurationDefault valueDescription
cell.idnilUnique integer identifier for the cell in a cluster. For use when the instance is part of a cell cluster.
database.skip_sequence_alterationfalseWhen true, skips database sequence alteration for the cell. Enable for the legacy cell (cell-1) before the monolith cell is available for use, being tracked in this epic: Phase 6: Monolith Cell.
topology_service.enabledfalseWhen true, enables the topology service client to connect to the topology service, which is required to be considered a cell.
topology_service.addressnilAddress and port of the topology service.
topology_service.ca_filenilPath to the CA certificate file for secure communication.
topology_service.certificate_filenilPath to the client certificate file.
topology_service.private_key_filenilPath to the private key file.

For information on how to configure other components of the cells architecture, see:

  1. Topology service configuration
  2. HTTP router configuration