Differences

This shows you the differences between two versions of the page.

--- c3tracker:setup [2025/09/19 21:01] – andi
+++ c3tracker:setup [2025/10/01 08:49] (current) – kunsi
@@ Line 23: / Line 23: @@
   Processing.Path.Outro           /video/intros/camp2023/outro.ts
-  Publishing.Upload.SkipSlaves    speedy,tweety,blade1,blade2,blade3,blade4
+  Publishing.Upload.SkipSlaves    minion254-1,minion254-2,minion254-3,minion254-4
   Publishing.UploadTarget         releasing.c3voc.de:/video/encoded/camp2023/
   Publishing.Tags                 <additional tags>
@@ Line 44: / Line 44: @@
 === Worker Filter Examples
+  # get all non-master tickets
   EncodingProfile.IsMaster=no
+  # get all master tickets
   EncodingProfile.IsMaster=yes
+  # get all recording tickets
   EncodingProfile.IsMaster=
+  # get all tickets in this room.
   Fahrplan.Room=Servus.at Lab
 Please note that the conditions in the "project to worker group" filter are currently always evaluated with logical OR.
 Specifying a property with an empty value, which is often done for `EncodingProfile.IsMaster`, will match if this property does not exist at all on a ticket. So for `EncodingProfile.IsMaster`, specifying an empty filter will match on recording tickets which never have this property.
+{{.:pasted:20250919-215601.png}}
 == Pipeline setup during event
@@ Line 100: / Line 110: @@
   sudo systemctl start rsync-from-encoder@encoderX.lan.c3voc.de
-Then, start tracker workers on storage:
+If you use a minion as storage machine, you have start the tracker manually (on storage.lan.c3voc.de they are started by default):
+  sudo systemctl start crs-worker.target
+which starts
+- crs-recording-scheduler (A)
+- crs-mount4cut.service   (B)
+- crs-cut-postprocessor   (C)
+- crs-encoding0, crs-encoding1 (D)
+- crs-postencoding        (E)
+- crs-postprocessing      (F)
-  `sudo systemctl start crs-worker.target` (only needed if you don't use `storage.lan.c3voc.de` - worker scripts get started automatically)
 ==== Minion setup
-To allow the encoding workers to do their job, they need to mount the storage first: `sudo crs-mount <storage location>`
+To allow get additional release encoding workers on the (other) minions, you need to connect to these an mount the storage machine first:
+  ssh minionX.lan.c3voc.de
+  sudo crs-mount <storage location>
+After mounting, you can start the tracker encoding workers:
-After mounting, you can start the tracker encoding workers: `sudo systemctl start crs-encoding.service`
+  sudo systemctl start crs-encoding0.service
-The minion VMs running inside our event colo case automatically mount `storage.lan.c3voc.de` via cifs and start their worker scripts. You usually do not need to touch them.
+The virtual minion's living in [[hardware:server-case|event colo case]] automatically mount `storage.lan.c3voc.de` via CIFS and start their worker scripts. You usually do not need to touch them.
@@ Line 118: / Line 143: @@
 At small events, when all talks are finished for today, you can use the recording encoder PCs to encode master MP4 files.
-First: Stop voctocore:
+First – stop voctocore:
   sudo systemctl stop voctomix2-voctocore