|Status||Good working order|
|Origin||donation from Tgreer|
Runs zone minder and has a not very good 4 port TV capture card in it, currently connected to the 3 yard cameras and the rear lobby camera.
Also a netboot server, provides:
- Diskless i386 and amd64 debian wheezy
- Rescue and Install for debian wheezy.
- partition magic
- Voyage (a minimised debian disto that can run from readonly media) Warning : the Voyage auto install kernel will reformat things they are booted on without prompting.
Also runs ansible for setting up machines in the space.
Has only a single mechanical harddrive so vulnerable to data loss.
using Ansible with a Rasbperry Pi
dd raspbian image (use the 02-09 one to avoid usb issues) boot pi watch dhcp logs on boole ssh pi@ip passwd: raspberry sudo raspi-config update it expand filesystem change password boot to console advanced options -> hostname cd /etc/network edit interfaces to get a static ip reboot on boole: add hostname to fwd and rev. dns, don't forget to commit your changes. log into denning with ssh keys forwarded add hostname to /etc/ansible/hosts in both the [lhshosts] and [rpis] sections, and [doorbot] if it's a doorbot, make the syslocation="something sensible" then: if it's a replacement for an old machine then: ssh-keygen -R hostname ssh-keygen -R hostname.lan.london.hackspace.org.uk ssh-keygen -R ipv4 address (?) ssh-keygen -R ipv6 address (?) then: cd /etc/ansible install python-apt which ansible needs: ansible -vvv -u pi -k -s -m command -a "apt-get -y install python-apt" "hostname" Then run it ansible-playbook -u pi -s -k -l "hostname" lhs/site.yml The 2nd one will add our users, ssh keys, packages, etc etc. notes: not sure how resolv.conf gets setup, I thought having: iface eth0 inet static [...] dns-nameservers 172.31.24.2 dns-search lan.london.hackspace.org.uk Would sort it, but maybe that dosn't and we got lucky from dhcp? The dns stuff in /etc/network/interfaces appears to be bogus and resolv.conf needs to be done manually, add to ansible.