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. As with all projects, the items mentioned on this page are subject to change or delay. The development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.
StatusAuthorsCoachDRIsOwning StageCreated
proposed -

This document is a work-in-progress and represents a very early state of the Cells design. Significant aspects are not documented, though we expect to add them in the future. This is one possible architecture for Cells, and we intend to contrast this with alternatives before deciding which approach to implement. This documentation will be kept even if we decide not to implement this so that we can document the reasons for not choosing this approach.

Cells: Admin Area

In our Cells architecture proposal we plan to share all admin related tables in GitLab. This allows simpler management of all Cells in one interface and reduces the risk of settings diverging in different Cells. This introduces challenges with admin pages that allow you to manage data that will be spread across all Cells.

1. Definition

There are consequences for admin pages that contain data that spans “the whole instance” as the Admin pages may be served by any Cell or possibly just 1 cell. There are already many parts of the Admin interface that will have data that spans many cells. For example lists of all Groups, Projects, Topics, Jobs, Analytics, Applications and more. There are also administrative monitoring capabilities in the Admin page that will span many cells such as the “Background Jobs” and “Background Migrations” pages.

2. Data flow

3. Proposal

We will need to decide how to handle these exceptions with a few possible options:

  1. Move all these pages out into a dedicated per-cell Admin section. Probably the URL will need to be routable to a single Cell like /cells/<cell_id>/admin, then we can display this data per Cell. These pages will be distinct from other Admin pages which control settings that are shared across all Cells. We will also need to consider how this impacts self-managed customers and whether, or not, this should be visible for single-cell instances of GitLab.
  2. Build some aggregation interfaces for this data so that it can be fetched from all Cells and presented in a single UI. This may be beneficial to an administrator that needs to see and filter all data at a glance, especially when they don’t know which Cell the data is on. The downside, however, is that building this kind of aggregation is very tricky when all the Cells are designed to be totally independent, and it does also enforce more strict requirements on compatibility between Cells.

4. Evaluation

4.1. Pros

4.2. Cons