Page MenuHomePhabricator

Jelto (jwodstrcil)
User

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Thursday

  • Clear sailing ahead.

User Details

User Since
Jun 7 2021, 7:25 AM (56 w, 1 d)
Availability
Available
LDAP User
Jelto
MediaWiki User
JWodstrcil (WMF) [ Global Accounts ]

Recent Activity

Today

Jelto added a comment to T311241: DNS/networking not working on Trusted Runners.

I run the script in repos/releng/gitlab-trusted-runner/ manually:

Tue, Jul 5, 3:20 PM · serviceops, serviceops-collab, GitLab (CI & Job Runners)
Jelto added a comment to T311241: DNS/networking not working on Trusted Runners.

currently the issue here is not DNS anymore.

but it is now: 'This job is stuck because you don't have any active runners online or available with any of these tags assigned to them: protected '

even though we see the de-registered and re-registered runner tagged as protected

Tue, Jul 5, 2:54 PM · serviceops, serviceops-collab, GitLab (CI & Job Runners)
Jelto added a comment to T274463: Backups for GitLab.

unfortunately just noticed an Icinga alert for gitlab1003 (nothing mails us about this, that's just if you happen to log at web UI for some reason)

Tue, Jul 5, 10:15 AM · serviceops-collab, GitLab (Infrastructure), serviceops, Data-Persistence-Backup, Patch-For-Review, User-brennen
Jelto added a comment to T295793: Support services VIPs with not marked as VIP in Netbox.

gitlab1001 and gitlab2001 will be decommissioned soon in T307142. So regarding GitLab this should be resolved soon.

Tue, Jul 5, 7:23 AM · Wikimedia-Mailing-lists, serviceops, Infrastructure-Foundations, SRE-tools

Thu, Jun 23

Jelto updated subscribers of T311241: DNS/networking not working on Trusted Runners.
Thu, Jun 23, 3:42 PM · serviceops, serviceops-collab, GitLab (CI & Job Runners)
Jelto created T311241: DNS/networking not working on Trusted Runners.
Thu, Jun 23, 3:05 PM · serviceops, serviceops-collab, GitLab (CI & Job Runners)

Wed, Jun 22

Jelto added a comment to T310593: Experiencing pipeline failure due to disk-space issues.

Docker cache is cleaned every 24h on GitLab Runner nodes now. So failing jobs due to full docker volume should happen less frequent.

Wed, Jun 22, 9:36 AM · Data-Engineering, GitLab
Jelto added a comment to T310535: GitLab runners: allowed_images patterns need to be loosened to include subdirectories.

I can confirm, pipeline works again for me. Re-configuring the Cloud Runners was block because of a failing pipeline. But this works again and Cloud Runner are using the new double star config now.

Wed, Jun 22, 8:59 AM · User-brennen, Release-Engineering-Team, GitLab (CI & Job Runners)

Mon, Jun 20

Jelto added a comment to T307142: bring new gitlab hardware servers into production.

@Arnoldokoth @Dzahn what's missing to also check

Mon, Jun 20, 9:11 AM · Patch-For-Review, GitLab (Infrastructure), serviceops

Fri, Jun 10

Jelto added a comment to T310265: Reduce usage of public IPv4 addresses on GitLab hosts.

First and foremost though, the reason why gitlab has all public IPs is because we were trying to emulate the gerrit setup. And gerrit has public IPs and is not behind LVS because we wanted it that way. We wanted to be able to still use Gerrit and merge changes even if the caching layer is down for some reason.

Fri, Jun 10, 12:43 PM · GitLab (Infrastructure), serviceops

Thu, Jun 9

Jelto triaged T310265: Reduce usage of public IPv4 addresses on GitLab hosts as Medium priority.
Thu, Jun 9, 11:39 AM · GitLab (Infrastructure), serviceops
Jelto created T310265: Reduce usage of public IPv4 addresses on GitLab hosts.
Thu, Jun 9, 11:39 AM · GitLab (Infrastructure), serviceops

Wed, Jun 8

Jelto changed the status of T296713: Document and test failover for GitLab and GitLab Replica from Open to In Progress.

We gathered some experience regarding failover when migrating GitLab to the new physical hosts in T307142.

Wed, Jun 8, 2:33 PM · GitLab (Infrastructure)
Jelto reopened T297411: Migrate gitlab-test instance to puppet as "Open".

puppet runs on the test instance gitlab-prod-1001 fail with

Wed, Jun 8, 12:05 PM · Patch-For-Review, serviceops, GitLab (Infrastructure)

Jun 3 2022

Jelto added a comment to T307142: bring new gitlab hardware servers into production.

...
One rsync job failed on the old production host gitlab1001. I'll take a closer look. I assume that's a timer/resource which is not managed by puppet anymore.

Jun 3 2022, 3:12 PM · Patch-For-Review, GitLab (Infrastructure), serviceops
Jelto added a comment to T274463: Backups for GitLab.

After migrating to new hosts (T307142) we got a bacula alert about backups on gitlab1001 (the old production machine):

Jun 3 2022, 3:07 PM · serviceops-collab, GitLab (Infrastructure), serviceops, Data-Persistence-Backup, Patch-For-Review, User-brennen
Jelto updated the task description for T307142: bring new gitlab hardware servers into production.
Jun 3 2022, 8:51 AM · Patch-For-Review, GitLab (Infrastructure), serviceops
Jelto added a comment to T307142: bring new gitlab hardware servers into production.

...
I'll check bacula tomorrow for new backups of gitlab1004 and make sure the replicas synced properly.

Jun 3 2022, 8:51 AM · Patch-For-Review, GitLab (Infrastructure), serviceops

Jun 2 2022

Jelto added a comment to T307142: bring new gitlab hardware servers into production.

Migration of production GitLab from gitlab1001 to gitlab1004 was successful. Downtime was around 65 minutes.

Jun 2 2022, 4:49 PM · Patch-For-Review, GitLab (Infrastructure), serviceops

Jun 1 2022

Jelto updated the task description for T307142: bring new gitlab hardware servers into production.
Jun 1 2022, 2:53 PM · Patch-For-Review, GitLab (Infrastructure), serviceops

May 31 2022

Jelto updated subscribers of T307142: bring new gitlab hardware servers into production.

Checklist for gitlab migation from gitlab1001 to gitlab1004:

May 31 2022, 4:32 PM · Patch-For-Review, GitLab (Infrastructure), serviceops
Jelto added a comment to T307142: bring new gitlab hardware servers into production.

Checklist for todays gitlab-replica migation from gitlab2001 to gitlab1003:

May 31 2022, 12:14 PM · Patch-For-Review, GitLab (Infrastructure), serviceops

May 30 2022

Jelto added a comment to T307142: bring new gitlab hardware servers into production.

gitlab1003 and gitlab1004 are configured as GitLab replicas now and are serving https://gitlab-replica-new.wikimedia.org/ and https://gitlab-new.wikimedia.org/.

May 30 2022, 1:03 PM · Patch-For-Review, GitLab (Infrastructure), serviceops
Jelto updated the task description for T307142: bring new gitlab hardware servers into production.
May 30 2022, 11:52 AM · Patch-For-Review, GitLab (Infrastructure), serviceops
Jelto added a comment to T274463: Backups for GitLab.

Backup size decreased after cleanup of big projects. Thanks again to @brennen and @Dzahn for finding and coordinating this!
We are down from 50GB to 10GB for one backup. That also means disk pressure on the backup volume decreased a lot (see disk usage over time dashboard).

May 30 2022, 9:29 AM · serviceops-collab, GitLab (Infrastructure), serviceops, Data-Persistence-Backup, Patch-For-Review, User-brennen

May 27 2022

Jelto updated the task description for T307142: bring new gitlab hardware servers into production.
May 27 2022, 1:39 PM · Patch-For-Review, GitLab (Infrastructure), serviceops
Jelto updated the task description for T307142: bring new gitlab hardware servers into production.
May 27 2022, 1:26 PM · Patch-For-Review, GitLab (Infrastructure), serviceops
Jelto updated the task description for T307142: bring new gitlab hardware servers into production.
May 27 2022, 12:46 PM · Patch-For-Review, GitLab (Infrastructure), serviceops
Jelto updated the task description for T307142: bring new gitlab hardware servers into production.
May 27 2022, 11:39 AM · Patch-For-Review, GitLab (Infrastructure), serviceops
Jelto updated the task description for T307142: bring new gitlab hardware servers into production.
May 27 2022, 10:13 AM · Patch-For-Review, GitLab (Infrastructure), serviceops
Jelto updated the task description for T307142: bring new gitlab hardware servers into production.
May 27 2022, 10:11 AM · Patch-For-Review, GitLab (Infrastructure), serviceops

May 23 2022

Jelto triaged T308089: gitlab-restore: version detection fail / restore fail as Medium priority.

So it did succeed, good! Not sure about that internal API error though.

May 23 2022, 1:59 PM · serviceops, Patch-For-Review, GitLab (Infrastructure)
Jelto updated the task description for T307142: bring new gitlab hardware servers into production.
May 23 2022, 12:35 PM · Patch-For-Review, GitLab (Infrastructure), serviceops
Jelto changed the status of T307142: bring new gitlab hardware servers into production from Open to In Progress.

@Dzahn thanks for testing the partman config! I'm happy it worked first time!

May 23 2022, 12:32 PM · Patch-For-Review, GitLab (Infrastructure), serviceops

May 20 2022

Jelto added a comment to T308380: 2022-05-14 Databases.

Queries involved in the issue during the first phase (wikidata): https://logstash.wikimedia.org/goto/feefd185271bdccfda06da231c09bfe1
Queries involved in the issue during the second phase (ruwiki): https://logstash.wikimedia.org/goto/5d3c2846f8ca3c41748e067d00260ba9

May 20 2022, 11:20 AM · Patch-For-Review, Wikimedia-production-error, DBA, Wikimedia-Incident

May 19 2022

Jelto updated the task description for T307142: bring new gitlab hardware servers into production.
May 19 2022, 6:30 PM · Patch-For-Review, GitLab (Infrastructure), serviceops
Jelto added a comment to T307142: bring new gitlab hardware servers into production.

I solved the installation/puppet issues with gitlab1003. The gitlab-ce package was installed and login using CAS/IDP worked. Synced backups for the backup-restore cycle were also present already.

May 19 2022, 1:01 PM · Patch-For-Review, GitLab (Infrastructure), serviceops

May 17 2022

Jelto updated the task description for T295481: Setup GitLab Runner in trusted environment.
May 17 2022, 12:16 PM · Patch-For-Review, GitLab (CI & Job Runners), SecTeam-Processed, Release-Engineering-Team (Radar), Security-Team, serviceops
Jelto added a comment to T295481: Setup GitLab Runner in trusted environment.
  1. Trusted Runner automation and access request
May 17 2022, 12:14 PM · Patch-For-Review, GitLab (CI & Job Runners), SecTeam-Processed, Release-Engineering-Team (Radar), Security-Team, serviceops
Jelto added a comment to T295481: Setup GitLab Runner in trusted environment.
May 17 2022, 12:04 PM · Patch-For-Review, GitLab (CI & Job Runners), SecTeam-Processed, Release-Engineering-Team (Radar), Security-Team, serviceops

May 12 2022

Jelto reopened T308089: gitlab-restore: version detection fail / restore fail as "Open".

Reopening, puma still fails to stop:

May 12 2022, 9:05 AM · serviceops, Patch-For-Review, GitLab (Infrastructure)

May 11 2022

Dzahn awarded T308089: gitlab-restore: version detection fail / restore fail a Barnstar token.
May 11 2022, 3:52 PM · serviceops, Patch-For-Review, GitLab (Infrastructure)
Jelto closed T308089: gitlab-restore: version detection fail / restore fail as Resolved.

Thanks for opening the task!

May 11 2022, 1:18 PM · serviceops, Patch-For-Review, GitLab (Infrastructure)

May 10 2022

Jelto added a comment to T297426: Provision untrusted instance-wide GitLab job runners to handle user-level projects and merge requests from forks.

@thcipriani I added some more open topics to the description. Can you take a look? I would like to know what is needed from your perspective until Cloud Runners can be available instance wide.

May 10 2022, 3:37 PM · User-brennen, Release-Engineering-Team (Next), GitLab (CI & Job Runners)
Jelto updated the task description for T297426: Provision untrusted instance-wide GitLab job runners to handle user-level projects and merge requests from forks.
May 10 2022, 3:35 PM · User-brennen, Release-Engineering-Team (Next), GitLab (CI & Job Runners)
Jelto added a comment to T307255: move mw241[2-9].codfw.wmnet into production.

After yesterdays incident mw2412 got depooled again to restore the state before the incident (see SAL). I'm going to adjust this and pool mw2412 again. This host is ready for production similar to the other hosts of mw241[2-9].

May 10 2022, 12:24 PM · serviceops

May 9 2022

Jelto updated the task description for T307142: bring new gitlab hardware servers into production.
May 9 2022, 12:49 PM · Patch-For-Review, GitLab (Infrastructure), serviceops
Jelto closed T307255: move mw241[2-9].codfw.wmnet into production as Resolved.

Maybe you got confused by the stale files there that we should remove for the non-https LVSes?

May 9 2022, 11:07 AM · serviceops
Jelto updated the task description for T307255: move mw241[2-9].codfw.wmnet into production.
May 9 2022, 11:06 AM · serviceops
Jelto added a comment to T307255: move mw241[2-9].codfw.wmnet into production.

mw241[2-9] where pooled in an incident this morning (accidentally depool and pool of codfw datacenter) . I run a scap pull on all machines to make sure they are up to date.

May 9 2022, 9:23 AM · serviceops

May 6 2022

Jelto added a comment to T297426: Provision untrusted instance-wide GitLab job runners to handle user-level projects and merge requests from forks.

I added more restrictive CPU and memory limits to the Cloud Runner configuration (0.1 CPU and 200Mi Memory). I also set the timeout for jobs to 300s which is the minimum.

May 6 2022, 12:45 PM · User-brennen, Release-Engineering-Team (Next), GitLab (CI & Job Runners)

May 4 2022

Jelto added a comment to T307541: Establish image trust system for GitLab/Blubber.

That's related to T295481.

May 4 2022, 1:32 PM · GitLab (Project Migration), Release-Engineering-Team (GitLab-a-thon 🦊)
Jelto added a comment to T297426: Provision untrusted instance-wide GitLab job runners to handle user-level projects and merge requests from forks.

https://gitlab.wikimedia.org/repos/releng/gitlab-cloud-runner has CI for provisioning the managed Kubernetes cluster and setup of Kubernetes Runner now. Thats mostly done using Terraform and Helm. So we have working Cloud Runners with autoscaling (min 1 and max 2 nodes).

May 4 2022, 1:27 PM · User-brennen, Release-Engineering-Team (Next), GitLab (CI & Job Runners)

May 3 2022

Jelto updated the task description for T307142: bring new gitlab hardware servers into production.
May 3 2022, 3:06 PM · Patch-For-Review, GitLab (Infrastructure), serviceops
Jelto claimed T307142: bring new gitlab hardware servers into production.

I would suggest to treat gitlab-runner hosts a little different. For the Runner hosts we can basically can apply the puppet role, add data to Hiera and remove the old ganeti VMs.

May 3 2022, 2:56 PM · Patch-For-Review, GitLab (Infrastructure), serviceops
Jelto added a comment to T297426: Provision untrusted instance-wide GitLab job runners to handle user-level projects and merge requests from forks.

We have a k8s cluster on Digital Ocean that we're using to prove the viability of ^ model. We talked it over with ServiceOps and WMCS and that's a good path for the time-being if everything seems to work correctly. In future, we'll continually evaluate whether a third party cloud is the right place to run this.

May 3 2022, 8:38 AM · User-brennen, Release-Engineering-Team (Next), GitLab (CI & Job Runners)

May 2 2022

Jelto awarded T306823: mw2286 stuck after reboot a Like token.
May 2 2022, 3:52 PM · SRE, ops-codfw, DC-Ops
Jelto awarded T307103: mw1323 stuck after reboot a Like token.
May 2 2022, 9:15 AM · SRE, ops-eqiad, DC-Ops

Apr 28 2022

Jelto created T307103: mw1323 stuck after reboot.
Apr 28 2022, 1:17 PM · SRE, ops-eqiad, DC-Ops

Apr 25 2022

Jelto created T306823: mw2286 stuck after reboot.
Apr 25 2022, 5:22 PM · SRE, ops-codfw, DC-Ops

Apr 19 2022

Jelto closed T293833: Add concurrent parameter to profile::gitlab::runner as Resolved.

This has been implemented in https://gerrit.wikimedia.org/r/732093, I'm closing this task.

Apr 19 2022, 9:03 AM · GitLab (CI & Job Runners), Release-Engineering-Team (Doing)
Jelto updated the task description for T295481: Setup GitLab Runner in trusted environment.
Apr 19 2022, 8:31 AM · Patch-For-Review, GitLab (CI & Job Runners), SecTeam-Processed, Release-Engineering-Team (Radar), Security-Team, serviceops
Jelto updated the task description for T297659: upgrade gitlab-runners to bullseye.
Apr 19 2022, 8:20 AM · Patch-For-Review, GitLab (CI & Job Runners), serviceops
Jelto added a comment to T297659: upgrade gitlab-runners to bullseye.

@Jelto All the (non-protected) prod runners are upgraded. Now I was just wondering about the 2 protected runners. They are paused. Should I try upgrading those as well?

Apr 19 2022, 8:19 AM · Patch-For-Review, GitLab (CI & Job Runners), serviceops
Jelto added a comment to T274463: Backups for GitLab.

[...]
BTW, restores directly to a different host are possible, although a bit cumbersome at the moment (because encryption reasons). We want to make this easier in the future.

Apr 19 2022, 8:10 AM · serviceops-collab, GitLab (Infrastructure), serviceops, Data-Persistence-Backup, Patch-For-Review, User-brennen
Jelto added a comment to T287117: Establish a routine GitLab deployment / update window.

We discussed in last ITC meeting that a dedicated GitLab update and maintenance window is not needed now. The last downtimes for updates and maintenance lasted between 2 to 5 minutes and were announced some hours ahead. With current usage of GitLab we agreed that this is not an issue. Also a fixed window would slow down progress on infrastructure tasks around GitLab because we have to wait for the next window.

Apr 19 2022, 8:10 AM · GitLab (Administration, Settings & Policy), User-brennen, Release-Engineering-Team (Next)

Apr 8 2022

Jelto added a comment to T305058: Security Issue Access Request for Jelto.

I have access now, thanks a lot!

Apr 8 2022, 12:36 PM · SecTeam-Processed, Security-Team, Security
Jelto awarded T297659: upgrade gitlab-runners to bullseye a Like token.
Apr 8 2022, 10:31 AM · Patch-For-Review, GitLab (CI & Job Runners), serviceops
Jelto added a comment to T297659: upgrade gitlab-runners to bullseye.

I like the idea of putting the bullseye runner runner-1020 into the gitlab-runners project. That reduces overhead around the puppet and hiera configuration.

Apr 8 2022, 10:24 AM · Patch-For-Review, GitLab (CI & Job Runners), serviceops

Apr 7 2022

Jelto reopened T305058: Security Issue Access Request for Jelto as "Open".

Thanks for the quick help! However I still have problems accessing some task. For example I can not access T304938, which is marked as security.

Apr 7 2022, 9:33 AM · SecTeam-Processed, Security-Team, Security

Apr 6 2022

Jelto added a comment to T274463: Backups for GitLab.

Backup is present in bacula for the new folder structure:

Apr 6 2022, 11:59 AM · serviceops-collab, GitLab (Infrastructure), serviceops, Data-Persistence-Backup, Patch-For-Review, User-brennen

Apr 5 2022

Jelto added a comment to T274463: Backups for GitLab.

Mentioned in SAL (#wikimedia-operations) [2022-04-05T00:32:47Z] <mutante> gitlab.wikimedia.org was down because gitlab1001 ran out of disk space. ran 'apt-get clean' to free 13G which made it recover... T274463 - <+icinga-wm> RECOVERY - Gitlab HTTPS healthcheck on gitlab.wikimedia.org is OK

Apr 5 2022, 7:23 PM · serviceops-collab, GitLab (Infrastructure), serviceops, Data-Persistence-Backup, Patch-For-Review, User-brennen

Apr 4 2022

Jelto added a comment to T274463: Backups for GitLab.

@Jelto @Arnoldokoth See above. I added a new disk to gitlab2001 and gitlab1001. On gitlab2001 I have also done the other necessary steps to actually use it, while I have left gitlab1001 untouched so far.

  • created virtual disk on ganeti level
  • rebooted on ganeti level (not enough to boot on machine level)
  • ran into the bug with the host not coming back, exactly like the other day, fixed interface name again
  • created partition table
  • created partition
  • created file system, ext4
  • created /mnt/gitlab-backup
  • mounted on /mnt/gitlab-backup
  • used blkid to get UUID of new partition
  • edited /etc/fstab and inserted "UUID=c5235682-ac21-46a9-85ee-9603f694a6a4 /mnt/gitlab-backup ext4 errors=remount-ro 0 2" (0 = no dumping, 2 = no fsck unlike the root file system)
  • rebooted to check if it survices the reboot and gets auto-mounted, it does.

There is now this:

/dev/vdb1        98G   61M   93G   1% /mnt/gitlab-backup

And now backups could be switched from /srv/gitlab-backup to /mnt/gitlab-backup.

And then we would have to do those steps above also for gitlab1001.

Apr 4 2022, 10:47 AM · serviceops-collab, GitLab (Infrastructure), serviceops, Data-Persistence-Backup, Patch-For-Review, User-brennen

Mar 30 2022

Jelto closed T304622: GitLab minor version upgrade: 14.9.x as Resolved.

@Arnoldokoth and I updated production instance gitlab1001 and gitlab-runners successfully.

Mar 30 2022, 5:05 PM · Patch-For-Review, serviceops, GitLab (Infrastructure)
Jelto created T305058: Security Issue Access Request for Jelto.
Mar 30 2022, 12:48 PM · SecTeam-Processed, Security-Team, Security

Mar 29 2022

Jelto added a comment to T304622: GitLab minor version upgrade: 14.9.x.

@Arnoldokoth and I updated the test instance gitlab-prod-1001.devtools.eqiad1.wikimedia.cloud and the replica gitlab2001.wikimedia.org to gitlab-ce 14.9.1-ce.0.

Mar 29 2022, 4:14 PM · Patch-For-Review, serviceops, GitLab (Infrastructure)

Mar 28 2022

Jelto added a comment to T304622: GitLab minor version upgrade: 14.9.x.

This will happen tomorrow/Tuesday due to scheduling conflicts.

Mar 28 2022, 2:58 PM · Patch-For-Review, serviceops, GitLab (Infrastructure)

Mar 25 2022

brennen awarded T304622: GitLab minor version upgrade: 14.9.x a Like token.
Mar 25 2022, 4:01 PM · Patch-For-Review, serviceops, GitLab (Infrastructure)
Jelto added a comment to T304622: GitLab minor version upgrade: 14.9.x.

@Arnoldokoth and I will do the upgrade of GitLab + Runners on Monday after 4pm UTC.

Mar 25 2022, 8:34 AM · Patch-For-Review, serviceops, GitLab (Infrastructure)

Mar 24 2022

Jelto triaged T304622: GitLab minor version upgrade: 14.9.x as Medium priority.
Mar 24 2022, 4:09 PM · Patch-For-Review, serviceops, GitLab (Infrastructure)
Jelto created T304622: GitLab minor version upgrade: 14.9.x.
Mar 24 2022, 4:09 PM · Patch-For-Review, serviceops, GitLab (Infrastructure)
Jelto updated the task description for T295481: Setup GitLab Runner in trusted environment.
Mar 24 2022, 3:34 PM · Patch-For-Review, GitLab (CI & Job Runners), SecTeam-Processed, Release-Engineering-Team (Radar), Security-Team, serviceops

Mar 23 2022

Jelto updated the task description for T304491: Standardize Debian package builds on GitLab CI.
Mar 23 2022, 11:25 AM · GitLab (CI & Job Runners), serviceops
Jelto added a comment to T295481: Setup GitLab Runner in trusted environment.

I mirrored wmf-sre-laptop to GitLab and created a very basic proof-of-concept CI to build the Debian package on Trusted Runners. The current implementation has limitations and is not complete. I created T304491 to further discuss the whole topic of Debian package builds on GitLab CI, as this is a bit out of scope for this task.

Mar 23 2022, 10:25 AM · Patch-For-Review, GitLab (CI & Job Runners), SecTeam-Processed, Release-Engineering-Team (Radar), Security-Team, serviceops
Jelto updated the task description for T295481: Setup GitLab Runner in trusted environment.
Mar 23 2022, 10:18 AM · Patch-For-Review, GitLab (CI & Job Runners), SecTeam-Processed, Release-Engineering-Team (Radar), Security-Team, serviceops
Jelto created T304491: Standardize Debian package builds on GitLab CI.
Mar 23 2022, 10:17 AM · GitLab (CI & Job Runners), serviceops

Mar 15 2022

Jelto updated the task description for T295481: Setup GitLab Runner in trusted environment.
Mar 15 2022, 12:58 PM · Patch-For-Review, GitLab (CI & Job Runners), SecTeam-Processed, Release-Engineering-Team (Radar), Security-Team, serviceops

Mar 9 2022

Jelto updated the task description for T295481: Setup GitLab Runner in trusted environment.
Mar 9 2022, 2:19 PM · Patch-For-Review, GitLab (CI & Job Runners), SecTeam-Processed, Release-Engineering-Team (Radar), Security-Team, serviceops
Jelto updated the task description for T295481: Setup GitLab Runner in trusted environment.
Mar 9 2022, 10:58 AM · Patch-For-Review, GitLab (CI & Job Runners), SecTeam-Processed, Release-Engineering-Team (Radar), Security-Team, serviceops

Mar 3 2022

Jelto closed T297411: Migrate gitlab-test instance to puppet as Resolved.

I created a dedicated task to automate the test instance creation: T302976

Mar 3 2022, 1:32 PM · Patch-For-Review, serviceops, GitLab (Infrastructure)
Jelto updated the task description for T297411: Migrate gitlab-test instance to puppet.
Mar 3 2022, 1:24 PM · Patch-For-Review, serviceops, GitLab (Infrastructure)
Jelto triaged T302976: Automate setup of GitLab test instance as Low priority.
Mar 3 2022, 1:23 PM · serviceops, GitLab (Infrastructure)
Jelto created T302976: Automate setup of GitLab test instance.
Mar 3 2022, 1:23 PM · serviceops, GitLab (Infrastructure)

Mar 2 2022

Jelto updated subscribers of T297411: Migrate gitlab-test instance to puppet.

With the help of @Majavah the correct configuration of private and public/floating IP was found. https and cloning over SSH works now. Thanks again!

Mar 2 2022, 10:19 AM · Patch-For-Review, serviceops, GitLab (Infrastructure)
Jelto closed T302803: Create additional network port in project devtools as Resolved.

The keepalived VIP configuration was not clear for me from looking at the horizon interface.

Mar 2 2022, 8:54 AM · GitLab (Infrastructure), Cloud-VPS (Project-requests)
Jelto closed T302803: Create additional network port in project devtools, a subtask of T297411: Migrate gitlab-test instance to puppet, as Resolved.
Mar 2 2022, 8:53 AM · Patch-For-Review, serviceops, GitLab (Infrastructure)
Jelto reopened T302803: Create additional network port in project devtools as "Open".

Thanks a lot for setting up the additional port! I can confirm that the port is present in Horizon Interface.

Mar 2 2022, 8:10 AM · GitLab (Infrastructure), Cloud-VPS (Project-requests)
Jelto reopened T302803: Create additional network port in project devtools, a subtask of T297411: Migrate gitlab-test instance to puppet, as Open.
Mar 2 2022, 8:10 AM · Patch-For-Review, serviceops, GitLab (Infrastructure)

Mar 1 2022

Jelto added a comment to T297411: Migrate gitlab-test instance to puppet.

SSH access to the test instance is not working because of different networking behavior on WMCS/VPS. The public floating IP ("service ip") is NATed to the VM. So we can not bind on this address directly.
I requested a second networking port in T302803 and hope we can map/NAT the floating IP to this second port to replicate the production configuration (with NGINX and git SSH daemon listening on a different address).

Mar 1 2022, 1:53 PM · Patch-For-Review, serviceops, GitLab (Infrastructure)
Jelto added a parent task for T302803: Create additional network port in project devtools: T297411: Migrate gitlab-test instance to puppet.
Mar 1 2022, 1:48 PM · GitLab (Infrastructure), Cloud-VPS (Project-requests)