[Git][qa/jenkins.debian.net][master] init: some infrastructure plan

Holger Levsen (@holger) gitlab at salsa.debian.org
Tue Mar 19 10:53:54 GMT 2024



Holger Levsen pushed to branch master at Debian QA / jenkins.debian.net


Commits:
c7f714f5 by Holger Levsen at 2024-03-19T11:53:33+01:00
init: some infrastructure plan

Signed-off-by: Holger Levsen <holger at layer-acht.org>

- - - - -


1 changed file:

- + TODO.infrastructure


Changes:

=====================================
TODO.infrastructure
=====================================
@@ -0,0 +1,52 @@
+infomaniak
+----------
+define ressources & nodes
+free memory: FIXME
+free cores: FIXME
+free hdd space: FIXME
+free sdd space: FIXME
+
+ionos
+-----
+free memory: 47gb
+free cores: 13
+free hdd space: 150gb
+free sdd space: 1800gb
+
+ordered todo
+------------
+fix all FIXMEs and answer all question marks
+shutdown ionos3 at fkb free 2 cores & 24gb ram & 272gb hdd
+shutdown ionos3 at fra free 2 cores & 4gb ram & 150gb sdd
+setup ionos4 as proxy for fkb, needs 2 core, 6gb ram, 128gb hdd (8 swap, 20 system, 100 /var/spool/squid)
+setup ionos14 as proxy for fra, needs 2 core, 6gb ram, 128gb hdd (8 swap, 20 system, 100 /var/spool/squid)
+	or put proxies on sdd?
+shutdown proxies on ionos1 and ionos10, use squid on ionos4+6
+mv jenkins:/dev/mapper/reproducible-userContent to SDD, free 700gb hdd space
+	increase to 1tb?
+mv jenkins:/dev/vda1 to SDD, free 500gb hdd space
+	increase to 640gb? more partitions?
+is /srv/workspace on jenkins on tmpfs (with 100gb size) really a good idea, especially with / on sdd?
+document codethink out-of-band access
+document infomaniak setup
+setup new infomanika nodes, FIXME: needs a plan
+setup ionos8 as www2.r-b.o
+	website.git
+	source-date-epoch-spec.git
+	tests.r-b.o data?
+point snapshot.r-b.o to rebuilder-snapshot.d.n?
+upload python-ionoscloud to bookworm-backports?
+improve ionos naming scheme so the datacenter becomes visible and whether its running in the future or not?
+	 ionos151 - fkb/5/future
+	 ionos050 - fra/5/today
+   or the other way round:
+	 ionos050 - today/5/fkb
+	 ionos151 - future/5/fra
+   i like the 2nd variant, because: if $hostname =="ionox1*" then $future
+   downside: we loose munin history. plus side: we dont rename jenkins, so meh, and we can introduce subdomain views in munin too
+move openwrt & netbsd & coreboot builds on different hosts than the ones building archlinux
+   make it so that *either* openwrt, coreboot or netbsd is built
+	FIXME: this needs a plan
+split this on several hosts: 
+	osuosl3-amd64: Debian live-builds / Debian bootstrap jobs / debian-janitor / mmdebstrap-jenkins jobs / openqa.d.n workers
+	FIXME: this needs a plan



View it on GitLab: https://salsa.debian.org/qa/jenkins.debian.net/-/commit/c7f714f5e43136147ec2f385b50605080ac7a6d0

-- 
View it on GitLab: https://salsa.debian.org/qa/jenkins.debian.net/-/commit/c7f714f5e43136147ec2f385b50605080ac7a6d0
You're receiving this email because of your account on salsa.debian.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/qa-jenkins-scm/attachments/20240319/0581248f/attachment-0001.htm>


More information about the Qa-jenkins-scm mailing list