Speed up Pages initialization time by using configuration API

Description

Once the Pages configuration API is in place it will be necessary to update gitlab-pages to load its configuration from the API instead of the filesystem. This should be done in a way that will allow support for both implementations (API and config file) for a period of time. Shipping two versions of the binary with Omnibus has been considered as an approach.

This will bring the time of pages configuration update from ~30 minutes to almost instant in gitlab.com, including:

1. time for the project to be visible for the first time
2. adding new domains
3. adding SSL certificates

• Add configurable timeout

Proposal

This work has already started in this MR, finishing up that work will complete this issue.

Links / references

Related Epic: &1316 (closed)

added devopsrelease [DEPRECATED] + 1 deleted label

added to epic &1316 (closed)

mentioned in epic &1316 (closed)

mentioned in issue #62332 (closed)

added Category:Pages label

mentioned in issue gitlab-pages#161 (closed)

changed milestone to %12.3

added [deprecated] Accepting merge requests label

Setting ~"group::release management" based on ~"pages".

Setting ~"group::release management" based on ~"pages".

added 1 deleted label

added Deliverable label

assigned to @krasio

removed [deprecated] Accepting merge requests label

Does this change anything for our users or is it more of a ~backstage item?

@jlenny it will bring the time of pages configuration update from ~30 minutes to almost instant in gitlab.com, including:

1. time for the project to be visible for the first time
2. adding new domains
3. adding SSL certificates

Wow, ok that's definitely worth mentioning!

added direction label

changed the description

mentioned in issue #65304 (closed)

mentioned in issue #42949 (moved)

changed title from Update gitlab-pages to use that API for virtual host configuration to Speed up Pages initialization time by using configuration API

@cstasik if you have time, it's not urgent but it would be nice to rewrite this issue description in terms of value. At the moment it starts with technical details and gets to the value, but it would be more clear to users I think if it was inverted.

added workflowin dev label

changed the description

Added

• Add configurable timeout

per discussion

Hey!

GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current gitlab-ce repository will become a read-only mirror, without any proprietary code. All development is moved to the current gitlab-ee repository, which we will rename to just gitlab in the coming weeks. As part of this migration, issues will be moved to the current gitlab-ee project.

If you have any questions about all of this, please ask them in our dedicated FAQ issue.

https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

You can also find more information here:

• https://gitlab.com/gitlab-org/gitlab-ee/issues/13304
• https://about.gitlab.com/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/

Frequently Asked Questions

For an up to date list of questions and answers, please take a look at https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

What will we do with the repository names?

https://gitlab.com/gitlab-org/gitlab-ee/ will become https://gitlab.com/gitlab-org/gitlab, and https://gitlab.com/gitlab-org/gitlab-ce will become https://gitlab.com/gitlab-org/gitlab-foss.

Why rename gitlab-ce to gitlab-foss?

Using "gitlab" and "gitlab-ce" would be confusing, so we decided to rename gitlab-ce to gitlab-foss to make the purpose of this FOSS repository more clear

I created a merge requests for CE, and this got closed. What do I need to do?

You will need to create a merge request at https://gitlab.com/gitlab-org/gitlab-ee/. This link will eventually redirect to https://gitlab.com/gitlab-org/gitlab.

How does the licensing work in this new setup?

Everything in the ee/ directory is proprietary. Everything else is free and open source software. If your merge request does not change anything in the ee/ directory, the process of contributing changes is the same as when using the gitlab-ce repository.

Will you accept merge requests on the gitlab-ce/gitlab-foss project after it has been renamed?

No. Merge requests submitted to this project will be closed automatically.

Will I still be able to view old issues and merge requests in gitlab-ce/gitlab-foss?

Yes.

How will this affect users of GitLab CE using Omnibus?

No changes will be necessary, as the packages built remain the same.

How will this affect users of GitLab CE that build from source?

Once the project has been renamed, you will need to change your Git remotes to use this new URL. GitLab will take care of redirecting Git operations so there is no hard deadline, but we recommend doing this as soon as the projects have been renamed.

Where can I see a timeline of the remaining steps?

https://gitlab.com/gitlab-org/gitlab-ee/issues/13304

Will community contributions submitted to the new "gitlab" repository be available in the new gitlab-foss repository?

Yes, these changes will be synced to gitlab-foss automatically, several times per day.

locked this issue

mentioned in epic &1737

removed milestone

Issues describing what needs to be done in Pages:

• gitlab-pages#253 (closed)
• gitlab-pages#254 (closed)