Cells
Status: Experiment
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
Configuration | Default value | Description |
---|---|---|
cell.id
| nil
| Unique integer identifier for the cell in a cluster. For use when the instance is part of a cell cluster. |
database.skip_sequence_alteration
| false
| When 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.enabled
| false
| When true , enables the topology service client to connect to the topology service, which is required to be considered a cell.
|
topology_service.address
| nil
| Address and port of the topology service. |
topology_service.ca_file
| nil
| Path to the CA certificate file for secure communication. |
topology_service.certificate_file
| nil
| Path to the client certificate file. |
topology_service.private_key_file
| nil
| Path to the private key file. |
Related configuration
For information on how to configure other components of the cells architecture, see: