Create virtual host configuration API for GitLab Pages

Rename API::Internal class to API::Internal::Base gitlab-foss!32617 (merged)
Extract Workhorse <-> GitLab JWT authentication to make it reusable gitlab-foss!32623 (merged)
Add skeleton Pages internal API gitlab-foss!32732 (merged)
Add support for custom domains to the Pages internal API gitlab-foss!32735 (merged)
Add support for namespaces to Pages internal API !17197 (merged)
Migrate Pages metadata on-demand !17204 (merged)
Background migration to migrate Pages metadata !17993 (merged)
omnibus-gitlab: Generate and symlink gitlab_pages_shared_secret omnibus-gitlab!3705 (merged)

mentioned in commit gitlab-foss@5d1d5942

mentioned in commit gitlab-foss@e529360f

mentioned in commit gitlab-foss@eb914571

mentioned in commit gitlab-foss@ba73aef8

This item has now missed %12.3 and is being moved to %12.4 where it can be wrapped up. @darbyfrey this was another one waiting on maintainer review.

changed milestone to %12.4

added missed-deliverable missed:12.3 labels

@jlenny would this be considered a direction item?

I don't think so @ogolowinski. Doesn't seem particularly high visibility.

mentioned in commit gitlab-foss@54aa07d8

mentioned in commit gitlab-foss@d5de8b6e

mentioned in commit gitlab-foss@66c8b7ac

mentioned in commit gitlab-foss@b1dc49c9

mentioned in commit b7110a59

mentioned in merge request !17197 (merged)

mentioned in commit f2ba88ed

mentioned in commit 456e1527

mentioned in merge request !17204 (merged)

mentioned in commit c1bbc5c7

mentioned in commit 7a7868cc

mentioned in commit b63e87a8

mentioned in commit 0e10dadd

mentioned in commit 151a2b25

mentioned in commit c4008f6d

mentioned in commit ef7ca36f

mentioned in commit 3a0ae19a

mentioned in issue #33106

mentioned in commit 7a1294d6

mentioned in commit 817c140e

mentioned in commit 043df9b4

mentioned in merge request !17993 (merged)

mentioned in commit 1e569fb0

mentioned in commit 8442a947

mentioned in commit gitlab-pages@f640b996

mentioned in commit b89a9909

mentioned in commit 75b18413

mentioned in commit 1bfe53a0

added typefeature label

mentioned in commit 4b7bffd9

mentioned in commit 748829de

@ogolowinski In !17993 (merged) we introduced background migration. According to https://docs.gitlab.com/ee/development/background_migrations.html#when-to-use-background-migrations we need to announce it in the monthly release post along with an estimate of how long it will take to complete.

This is done in the Important notes on upgrading section - https://about.gitlab.com/handbook/marketing/blog/release-posts/#important-notes-on-upgrading.

Here is the text we need to include:

To help with the larger migrations we have introduced background migrations for this release. Background migrations are Sidekiq jobs that will run asynchronously. For GitLab.com these migrations took around 36 hours to complete, and no side effects were expected nor present.

To find the approximate time it will take to complete these migrations on your instance run the following command from a Rails console: (Project.count.to_f / 300_000).ceil. You can check the status of background migrations by running this command from a Rails console: Sidekiq::Queue.new('background_migration').size.

Let me know if you have any questions or if there's anything else I can help with.

/cc @darbyfrey

assigned to @ogolowinski

@jlenny Where should this go in the blog post? Also, should I mark it direction ?

@ogolowinski reading the description I can't tell what this actually does from a customer facing standpoint, so not sure. It sounds like maybe it's a backend thing so no, that wouldn't be included.

@jlenny please refer to Kras's comment above #28781 (comment 230957914) There is a migration involved

@ogolowinski it goes in the important notes for upgrading section as @krasio mentioned. Someone in the #release-post channel can help with how to edit that part. There's no need to mark this direction to include it there, though we should probably groom the description of this issue to be complete.

@krasio This will affect self managed customers , correct?

@ogolowinski Yes but need to have significant number of projects in order to make this migration take more than few minutes.

changed milestone to %12.5

added missed:12.4 label

@darbyfrey this has missed 12.4? If so, I need to remove the upgrade notes from the blog post, from what I understood GitLab.com has already migrated. @krasio can you confirm?

@ogolowinski This is issue turned out bigger than we thought so I've been working on it in smaller chunks, you can see the progress here - #28781 (comment 217282591). So the issue itself as a whole is not going to make it for %12.4 but the migration from the blog post announcement will be there (and was already deployed to GitLab.com).

@ogolowinski to add to @krasio's comment, there is one MR still is review that is preventing this issue from being fully closed. Aside from the migration, these changes won't have any customer impact in this release. Please keep the upgrade notes in the release post.

mentioned in commit omnibus-gitlab@1a6ae80f

mentioned in commit omnibus-gitlab@1c762b60

mentioned in merge request omnibus-gitlab!3705 (merged)

changed the description

mentioned in commit omnibus-gitlab@f19c4cf6

mentioned in commit Dalahro/gitlab@4d1a3d31

mentioned in commit gitlab-pages@313ed9f5

mentioned in merge request gitlab-pages!198 (merged)

mentioned in commit gitlab-pages@1821232a

mentioned in commit gitlab-pages@e4daad77

mentioned in commit omnibus-gitlab@f379fa83

This is almost there, we have the API built and released but last related MR (omnibus-gitlab!3705 (merged)) needs to wait for gitlab-pages!198 (merged) to be released for Pages so that we can safely merge.

@krasio gitlab-pages!198 (merged) has been merged, is omnibus-gitlab!3705 (merged) in the queue?

Yes, it is but we have to wait for gitlab-pages!198 (merged) to be released first - omnibus-gitlab!3705 (comment 241177076).

Assigning @jmeshell who is the PM for this area.

assigned to @jmeshell and unassigned @ogolowinski

mentioned in merge request !19928 (merged)

added missed:12.5 label

changed milestone to %12.6

removed 1 deleted label

marked the checklist item omnibus-gitlab: Generate and symlink gitlab_pages_shared_secret omnibus-gitlab!3705 (merged) as completed

Last piece was merged - omnibus-gitlab!3705 (merged).

The API is still behind a feature flag but I am going to close this issue now.

closed

added workflowproduction label and removed workflowin review label

mentioned in commit 2b8d2300

mentioned in issue #39172 (closed)

mentioned in commit 7ac4d9f7

mentioned in merge request !21529 (merged)

mentioned in commit 8a9f5880

mentioned in commit db0e44e6

mentioned in commit cd6ba78a

mentioned in commit ba907f05

mentioned in issue gl-retrospectives/release#16 (closed)

mentioned in commit 7816adee

added grouprelease [DEPRECATED] label and removed 1 deleted label

Create virtual host configuration API for GitLab Pages

Description

Proposal

Links / references

Designs

Child items ...

Activity