These Ansible scripts can be run from a desktop machine and not from a lab computer.
Visit http://go/skolo-maintenance#heading=h.or4jzu6r2mzn for instructions on how to set up to run these commands.
Runs might fail for a small number of hosts, you can re-run a script for a specific host by passing
--limit (hostname) to the
hosts.yml for all the hosts and groups of hosts you can target when running an Ansible script, as well as for the definitions of broadly scoped variables.
ssh.cfg for the SSH configuration that Ansible uses when running.
eskia_test_machines) in addition to specifying the hostnames of the machines in that group (e.g.
./ssh.cfg if necessary (e.g. new rack or naming convention)
./switchboard/update-authorized-keys.yml to contain the new group of machines, if necessary.
ansible-playbook ./switchboard/update-authorized-keys.yml --limit rack5_linux_eskia or
ansible-playbook ./switchboard/update-authorized-keys.yml --limit skia-e-win-355
./switchboard/foo.yml to describe the roles, (similar to functions) that you want to run for your machines.
--ask-become-pass argument. e.g.
ansible-playbook ./switchboard/eskia.yml --limit skia-i-eskia01 --ask-become-pass