Ansible

c3voc - configuration management

git clone git@mng.ber.c3voc.de:cm
vim README.md

Public version of this repository: https://github.com/voc/cm/

To manage hosts with ansible you need to install ansible > 2.3 on your machine. See https://docs.ansible.com/ansible/intro_installation.html for instructions

Syntax validation.

ansible-playbook -i event -l mixers site.yml --syntax-check

Basic ansible call to deploy new config to a specific host.

./ansible-playbook-keepass -u root -i event -l 192.168.122.1 site.yml

Basic ansible call to deploy new config to a set of hosts on an event.

./ansible-playbook-keepass -u voc --sudo -i event -l saal1 site.yml

Also have a look at the 'Usefull combinations' section of this page.

In case you need to do a lot of playbook runs you can also set the password using the following although it is not recommended.

export KEEPASS_PW='…'
./ansible-playbook-keepass … site.yml

What you need:

• install plain debian
• setting hostname to router.lan.c3voc.de
• make sure you have two network interfaces configured with names pbl (public) and int (internal)
• run ansible to deploy config

You have to name the monitoring host monitoring.lan.c3voc.de. After deployment, you have to run check_mk -I && check_mk -O inventory each host.

Have a look into TODO file.

• ansible-doc -l lists all available modules
• ansible-doc $module opens a very helpful knowledge page for a given module
• Documentation Page

• Change nginx config on all relays: --tags nginx,config
• Deploy only streaming website: --tags deploy_website
  • e.g.

./ansible-playbook-keepass –tags deploy_website -i event loadbalancers.yml

• Deploy encoder setting for a conference
  • edit group_vars/all and group_vars/saal*

  • ./ansible-playbook-keepass -i event -u voc --become --become-method=sudo --limit encoder1.lan.c3voc.de --tags encodermode site.yml

  • or

    ./ansible-playbook-keepass -i event -u voc --become --become-method=sudo --limit encoder1.lan.c3voc.de --tags voctomix site.yml

  • or

    ./ansible-playbook-keepass -i event -u voc --become --become-method=sudo -l saal5 --tags voctomix 

• Debug without rerunning working tasks

  • KEEPASS="${KEEPASS}" KEEPASS_PW="${KEEPASS_PW}" python2 `which ansible-playbook` -i event -u voc --become --become-method=sudo -l saal5 --tags voctomix --start-at-task="encoder : create recording script"

Ansible can deploy Encoder-Cubes and Mixer-Notebooks with one of three modes:

• sd-dvswitch was the Default until mid-2016. It runs a mixing-chain around dvswitch and produces sd-video in .dv-files
• hd-direct is more or less what was running on *C3. It only configures the encoder (doesn't need the mixer) and records / streams directly of one of the two decklink mini-recorders in an encoder. It needs a Hardware SDI-Distribution to allow streaming and recording
• hd-voctomix is the new and all-shiny videomixer, running voctocore and sources/sinks on the encoder and voctogui on the mixer

Ansible can transition between all three modes. All three systems are always configured and prepared. Which one should be running can be configured with the encodermode variable in the saal[1-6] groupvars file. Changing that and running ansible with the encodermode-Tag (or without any tag) stops the unnecessary Tasks and starts the required ones. It allows transitioning between dvswitch and voctomix within a minute.