Hi there,
although I don't think there is a strong mandate -or policy- to migrate
everything to gitlab just yet, we already have a few repos here and
there. And there is agreement that gitlab in general is beneficial for
us and we should be slowly paying more attention to it as we go.
Naming can be hard, and organizing stuff based on naming can also be
hard. But we already have some kind of "tree" on gitlab. Let me try to
brain dump the mental image I have, and feel free to share / discuss as
required.
Main entry point:
https://gitlab.wikimedia.org/repos/cloud
The repos/cloud group is our main "directory". Everything that resembles
something that WMCS + collabs would maintain as part of the base
services+infra we have should be there. Explicitly excluded are
user-controlled stuff, like Toolforge tool source code etc.
Remember, being under /repos/ gives us some additional features (like
trusted CI runners) and even more /repos/cloud/ already contains some
membership that will be inherited by all child repos.
This group doesn't contain any direct repository, but instead several
subgroups. The only exception is a "wikistats"[1] repo that I'll be
requesting Daniel Zahn to relocate elsewhere.
Child subgroup:
https://gitlab.wikimedia.org/repos/cloud/toolforge
Everything Toolforge, components for k8s, etc.
The only "official" repo here is
https://gitlab.wikimedia.org/repos/cloud/toolforge/ingress-nginx and the
rest are placeholder/tests
Child subgroup:
https://gitlab.wikimedia.org/repos/cloud/cicd
See
https://lists.wikimedia.org/hyperkitty/list/cloud-admin@lists.wikimedia.org…
Child subgroup:
https://gitlab.wikimedia.org/repos/cloud/deb
I just created this the other day to store .deb packaging repos. Created
the first here
https://gitlab.wikimedia.org/repos/cloud/deb/pkg-prometheus-openstack-expor…
I guess we could introduce other subgroups as we go, imagine for example:
* /repos/cloud/vps/
* /repos/cloud/paws/
* /repos/cloud/quarry/
*/ repos/cloud/you_name_it/
Comments welcome.
regards.
[1] https://gitlab.wikimedia.org/repos/cloud/wikistats
--
Arturo Borrero Gonzalez
Site Reliability Engineer
Wikimedia Cloud Services
Wikimedia Foundation
Hi there,
Today 2022-04-06 we're performing some network maintenance operations on
Cloud VPS that could affect all cloud egress/ingress traffic, including
Toolforge. The cuts, if noticeable, should last a few minutes at most.
Some operations were also conducted yesterday (without this email
notice), and some unexpected hiccups occurred. That's why the email today.
regards.
--
Arturo Borrero Gonzalez
Site Reliability Engineer
Wikimedia Cloud Services
Wikimedia Foundation