## Reference For [Cell 1.0](https://gitlab.com/groups/gitlab-org/-/epics/12383) we need to create some proof of concepts so that we validate that that our [proposal](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/139519) is achievable. ## Status Check [main epic](https://gitlab.com/groups/gitlab-org/-/epics/12383#status) ## Accessing the PoC **Please read https://gitlab.com/groups/gitlab-org/-/epics/12474#note_1763724687 (internal link)** Any questions around the PoC ask @sxuereb / @OmarQunsulGitlab / [#g_tenant-scale](https://gitlab.enterprise.slack.com/archives/C01TQ838Y3T) 1. To log in visit https://gitlab.steveazz.xyz/ 1. Login Cell 1 1. Admin `username`: `root` 1. Admin `password`: [1password](https://handbook.gitlab.com/handbook/security/password-guidelines/) > Engineering > Cell 1.0 Poc > cell-1 (password) 1. Login Cell 2 1. Open the browser javascript console and run `document.cookie = 'cell_2=true;path=/;domain=gitlab.steveazz.xyz'` to force cell-2 logging 1. Refresh browser 1. Admin `username`: `cell_2_root` 1. Admin `password`: [1password](https://handbook.gitlab.com/handbook/security/password-guidelines/) > Engineering > Cell 1.0 Poc > cell-2 (password) ### What happens when something is broken The PoC is very broken, and there are [things](#things-we-know-that-are-broken) we know are broken. Comment on this epic and link to an issue specifying that it's broken and start investigating if this is related to the PoC or the feature is broken. #### Things we know that are broken - Admin settings are not automatically synced, if you update in `cell-1` you have to do the same in `cell-2` - Emails are not configured - API requests using the `Authorization: Bearer` header isn't supported yet. Use the `PRIVATE-TOKEN` format instead, see [this](https://gitlab.com/groups/gitlab-org/-/epics/12474#note_1755425140) for example. - JWT token-based requests aren't redirected correctly. - Registration is disabled for security reasons. - We don't use any secrets tokens for staging/development at the moment to keep the security risk low on these machines. ### Testing Ultimate/Premium features The cells PoC now runs as a SaaS instance, not self-managed. You should create a new top-level group for your testing in the Cells PoC. By default, this group will be a free group and have no access to premium or ultimate features. Go to Admin Area -> Groups, and find your newly created group. Press Edit, and under "Plan" set the value to either Premium, or Ultimate. This will allow that namespace to have access to the required licenced features. ### CI Runners The PoC doesn't come with a Runner installer you'll have to [register](https://docs.gitlab.com/runner/register/) one yourself and run it so you have full control over what you do. ### Feature Flags You can use the [feature flags API](https://docs.gitlab.com/ee/api/features.html) to enable/disable feature flags. ## E2E test results by stage We have issues create by stage to track the problems found by running the E2E test suites against the cell PoC. [Issue tracking details of the test runs](https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/2399). | Stage | | ----- | | [Manage](https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/2442) | | [Plan](https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/2413) | | [Create](https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/2412) | | [Verify](https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/2419) | | [Package](https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/2437) | | [Release](https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/2438) | | [Govern](https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/2414) | | [Monitor](https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/2445) | | [Data Stores](https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/2417) | | [Analytics](https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/2418) | | [Fulfillment](https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/2451) | | [Systems](https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/2452) | | [Configure](https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/2457) | ## Results - Global Service PoC :point_right: [demo](https://gitlab.com/gitlab-org/gitlab/-/issues/444346#note_1855508454) - PoCs for Cell 1.0 to enable the rest of the engineering department to test their workflows.