Tag and Prioritise more issues

16 files changed, 106 insertions, 4 deletions

diff --git a/topics/systems/bbb.gmi b/topics/systems/bbb.gmi
index 9ef54a3..73582e6 100644
--- a/topics/systems/bbb.gmi
+++ b/topics/systems/bbb.gmi
@@ -1,4 +1,9 @@
-# BBB
+# BigBlueButton
+
+## Tags
+
+* type: documentation
+* keywords: BigBlueButton
 
 ## BASH script to install BigBlueButton in 30 minutes. 
 
diff --git a/topics/systems/ci-cd.gmi b/topics/systems/ci-cd.gmi
index cc12069..a5e00b6 100644
--- a/topics/systems/ci-cd.gmi
+++ b/topics/systems/ci-cd.gmi
@@ -13,7 +13,10 @@ deployment cycle to help with quick iteration of the code.
 ## Tags
 
 * assigned: bonfacem, fredm, efraimf, aruni
-* deployment
+* keywords: deployment, CI, CD, testing
+* status: in progress
+* priority: high
+* type: enhancement
 
 ## Tasks
 
diff --git a/topics/systems/decommission-machines.gmi b/topics/systems/decommission-machines.gmi
index 92614ad..496f23f 100644
--- a/topics/systems/decommission-machines.gmi
+++ b/topics/systems/decommission-machines.gmi
@@ -3,6 +3,10 @@
 # Tags
 
 * assigned: pjotrp, arthurc, dana
+* priority: high
+* keywords: systems
+* type: system administration
+* status: unclear
 
 # Tasks
 
diff --git a/topics/systems/gn1-time-machines.gmi b/topics/systems/gn1-time-machines.gmi
index 1154a5e..0029016 100644
--- a/topics/systems/gn1-time-machines.gmi
+++ b/topics/systems/gn1-time-machines.gmi
@@ -39,6 +39,10 @@ so you can see all the different versions. The matching code bases should be the
 ## Tags
 
 * assigned: pjotrp, efraimf
+* priority: high
+* status: unclear
+* type: system administration
+* keywords: systems
 
 ## Tasks
 
diff --git a/topics/systems/letsencrypt.gmi b/topics/systems/letsencrypt.gmi
index feb4f48..bafae55 100644
--- a/topics/systems/letsencrypt.gmi
+++ b/topics/systems/letsencrypt.gmi
@@ -3,7 +3,9 @@
 ## Tags
 
 * assigned: pjotr
-* bug
+* type: bug
+* priority: critical
+* status: completed, done, closed
 
 ## Tasks
 
diff --git a/topics/systems/machine-room.gmi b/topics/systems/machine-room.gmi
index d75883a..28d9921 100644
--- a/topics/systems/machine-room.gmi
+++ b/topics/systems/machine-room.gmi
@@ -3,6 +3,10 @@
 ## Tags
 
 * assign: pjotrp, dana
+* type: system administration
+* priority: high
+* keywords: systems
+* status: unclear
 
 ## Tasks
 
diff --git a/topics/systems/mariadb/ProbeData.gmi b/topics/systems/mariadb/ProbeData.gmi
index b613784..c339571 100644
--- a/topics/systems/mariadb/ProbeData.gmi
+++ b/topics/systems/mariadb/ProbeData.gmi
@@ -1,4 +1,14 @@
+# ProbeData
 
+## Tags
+
+* assigned: pjotrp, aruni
+* status: unclear
+* priority: medium
+* type: enhancement
+* keywords: database, mariadb, innodb, ProbeData
+
+## Description
 
 Probe level data is used to examine the correlation structure among the
 N probes that have the same nominal target. Sometimes several probes
diff --git a/topics/systems/mariadb/ProbeSE.gmi b/topics/systems/mariadb/ProbeSE.gmi
index f9aa670..2c36514 100644
--- a/topics/systems/mariadb/ProbeSE.gmi
+++ b/topics/systems/mariadb/ProbeSE.gmi
@@ -1,3 +1,15 @@
+# ProbeSE
+
+## Tags
+
+* assigned: pjotrp
+* status: unclear
+* priority: medium
+* type: enhancement
+* keywords: database, mariadb, innodb, ProbeSE
+
+## Description
+
 Zach pointed out that ProbeSE is used on GN1 with
 
 => http://gn1.genenetwork.org/webqtl/main.py?FormID=showProbeInfo&database=HC_M2_0606_P&ProbeSetID=1427571_at&CellID=None&RISet=BXD&incparentsf1=ON
diff --git a/topics/systems/mariadb/ProbeSetData.gmi b/topics/systems/mariadb/ProbeSetData.gmi
index 63e7912..672b64c 100644
--- a/topics/systems/mariadb/ProbeSetData.gmi
+++ b/topics/systems/mariadb/ProbeSetData.gmi
@@ -1,5 +1,15 @@
 # ProbeSetData
 
+## Tags
+
+* assigned: pjotrp
+* status: unclear
+* priority: medium
+* type: enhancement
+* keywords: database, mariadb, innodb
+
+## Description
+
 This is by far the largest table (~200Gb). I need to add disk space to be able to host it on the NVME and move stuff around. Final move is GN2 code and we have over 400Gb free.
 
 This time I failed porting to InnoDB. Next time:
diff --git a/topics/systems/mariadb/ProbeSetXRef.gmi b/topics/systems/mariadb/ProbeSetXRef.gmi
index d8981a5..cdf08f4 100644
--- a/topics/systems/mariadb/ProbeSetXRef.gmi
+++ b/topics/systems/mariadb/ProbeSetXRef.gmi
@@ -1,3 +1,13 @@
+# ProbeSetXRef
+
+## Tags
+
+* keywords: ProbeSetXRef, database, mariadb, innodb
+* type: enhancement, documentation
+* assigned: pjotrp
+* status: unclear
+* priority: medium
+
 ## Table ProbeSetXRef
 
 Juggling indexes and transforming to InnoDB led to a massive speed increase for typical ProbeSetXRef queries. Global search for brca2 went down from 13s to 4s! Try
diff --git a/topics/systems/mariadb/cleanup.gmi b/topics/systems/mariadb/cleanup.gmi
index c034fbc..0639e40 100644
--- a/topics/systems/mariadb/cleanup.gmi
+++ b/topics/systems/mariadb/cleanup.gmi
@@ -1,4 +1,14 @@
+# Clean Up
 
+## Tags
+
+* assigned: pjotrp, robw
+* status: unclear
+* priority: unclear
+* type: database administration
+* keywords: database, mariadb
+
+## Description
 
 Find all larger tables
 
diff --git a/topics/systems/mariadb/mariadb.gmi b/topics/systems/mariadb/mariadb.gmi
index c2c927b..0cbd0e7 100644
--- a/topics/systems/mariadb/mariadb.gmi
+++ b/topics/systems/mariadb/mariadb.gmi
@@ -4,7 +4,8 @@ Here we capture some common actions
 
 ## Tags
 
-* info
+* type: info, documentation
+* keywords: mariadb, systems
 
 ## Check the transaction logs
 
diff --git a/topics/systems/mariadb/move-to-innodb.gmi b/topics/systems/mariadb/move-to-innodb.gmi
index b29173e..134a50a 100644
--- a/topics/systems/mariadb/move-to-innodb.gmi
+++ b/topics/systems/mariadb/move-to-innodb.gmi
@@ -1,3 +1,5 @@
+# MariaDB: Move to InnoDB Engine
+
 We are going to move from myisam to innodb. Penguin2 has been happily running innodb for some time.
 
 Main problem are fulltext columns, the text from Trello is captured below. This is for the following tables
@@ -581,3 +583,12 @@ On Penguin2 we are already runing ProbeSetData as
 ```
 
 which is pretty massive! It includes the index, which is 180G, so the difference is not that great. Also we should try a 4kb page size. Also make sure to enable innodb_file_per_table.
+
+
+## Tags
+
+* assigned: pjotr
+* type: enhancement, documentation
+* status: unclear
+* priority: medium
+* keywords: database, mariadb, innodb
diff --git a/topics/systems/octopus.gmi b/topics/systems/octopus.gmi
index 0929a65..1420865 100644
--- a/topics/systems/octopus.gmi
+++ b/topics/systems/octopus.gmi
@@ -3,6 +3,10 @@
 # Tags
 
 * assigned: pjotrp, efraimf, erikg
+* priority: high
+* status: completed, closed
+* type: system administration
+* keywords: systems, octopus
 
 # Tasks
 
diff --git a/topics/systems/reboot-tux01-tux02.gmi b/topics/systems/reboot-tux01-tux02.gmi
index afed594..3186a0d 100644
--- a/topics/systems/reboot-tux01-tux02.gmi
+++ b/topics/systems/reboot-tux01-tux02.gmi
@@ -44,3 +44,11 @@ The Linux kernel shows some fixes that are not on Tux01 yet
 => https://lkml.org/lkml/2021/2/17/970
 
 In our case a simple reboot worked, fortunately.
+
+## Tags
+
+* assigned: pjotrp
+* status: unclear
+* priority: medium
+* type: system administration
+* keywords: systems, tux01, tux02, production
diff --git a/topics/systems/tux02-production.gmi b/topics/systems/tux02-production.gmi
index 3a0a3c7..0b698ab 100644
--- a/topics/systems/tux02-production.gmi
+++ b/topics/systems/tux02-production.gmi
@@ -5,6 +5,10 @@ We are going to move production to tux02 - tux01 will be the staging machine. Th
 ## Tags
 
 * assigned: pjotrp
+* status: in progress
+* priority: medium
+* type: system administration
+* keywords: systems, tux02, production
 
 ## Tasks