|
|
| (9 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| {{EquipmentInfobox | | {{EquipmentInfobox |
| |name=Denning <!-- Name of the item. --> | | |name=Denning |
| |image=Hackspace_Unknown.png <!-- Image of the item. Leave with placeholder image if none exists. --> | | |image=Denning-DellOptiplex780.JPG <!-- Image of the item. Leave with placeholder image if none exists. --> |
| |model=Nexcom DNA1110 <!-- Model --> | | |model=Dell Optiplex 780 SFF 4GB Mem / 320GB SATA HD <!-- Model --> |
| |category=Equipment <!-- Main category. Please leave alone to keep item in this category --> | | |category=Equipment <!-- Main category. Please leave alone to keep item in this category --> |
| |subcat=Systems <!-- Sub-category if one exists. Please check main listing to see other categories contained within the main one --> | | |subcat=Systems <!-- Sub-category if one exists. Please check main listing to see other categories contained within the main one --> |
| |status=Good working order <!-- Set to one of; Good working order, Faulty, Out of order, Under construction, Out of consumables, Scrapped, or Unknown --> | | |status=Good working order |
| |consumables=<!-- Any items used up in normal operation, such as; ink, paper, saw-blades, cutting disks, oil, etc.. --> | | |consumables=<!-- Any items used up in normal operation, such as; ink, paper, saw-blades, cutting disks, oil, etc.. --> |
| |accessories=<!-- Any items associated with the equipment but not consumable, such as; drill bits, safety gloves, goggles, etc.. --> | | |accessories=<!-- Any items associated with the equipment but not consumable, such as; drill bits, safety gloves, goggles, etc.. --> |
| Line 11: |
Line 11: |
| |trainlink=Unknown <!-- If training is required, provide a link to training signup or contact page. Otherwise leave blank. --> | | |trainlink=Unknown <!-- If training is required, provide a link to training signup or contact page. Otherwise leave blank. --> |
| |acnode=no | | |acnode=no |
| |owner=LHS <!-- Provide a link to owners members page if other than LHS --> | | |owner=LHS |
| |origin=donation from Tgreer <!-- If via pledge, please link to the completed pledge page on the wiki --> | | |origin=Donation |
| |location= <!-- Floor, room/zone and location within that area --> | | |location=Ground floor, display area <!-- Floor, room/zone and location within that area --> |
| |maintainers=Sysadmin team <!-- If someone is nominated as managing the upkeep of this item, please list them here. No links please; it currently breaks the template. --> | | |maintainers=Sysadmin team <!-- If someone is nominated as managing the upkeep of this item, please list them here. No links please; it currently breaks the template. --> |
| |template_ver=1.1 <!-- Please do not change. Used for tracking out-of-date templates --> | | |template_ver=1.1 <!-- Please do not change. Used for tracking out-of-date templates --> |
| }} | | }} |
|
| |
|
| == Denning ==
| | Denning is is named after [https://en.wikipedia.org/wiki/Peter_J._Denning Peter J Denning], best known for pioneering work in virtual memory, especially for inventing the working-set model for program behaviour, which addressed disk thrashing and became the reference standard for all memory management policies. |
|
| |
|
| Runs the non-vital services that used to run on [[Boole]]. Might get used for other stuff as well. Same hardware as [[Boole]]
| | Same basic Dell Optiplex 780 Quad-Core hardware as [[Bell]] (more detailed hardware configuration there) and now has a nice SSD to use. |
|
| |
|
| Runs the spacefed node for the space (via a freeradius server) and has an LDAP server. the LDAP db is replicated from [[Turing]].
| | Denning provides the following services: |
|
| |
|
| Runs zone minder, see below.
| | * [[Equipment/The_Beast| The Beast Video Game Arcade System]] - emulation, display and control management. |
| | * Provide redundant fun and joy to those who play with The Beast |
|
| |
|
| Also runs [http://www.ansibleworks.com/docs/intro_getting_started.html ansible] for setting up machines in the space.
| | [[File:Thebeastfromtheside.jpg|200px|thumb|left|Look at that beautiful Beast with a Denning Inside]] |
| | | [[File:Thebeast.jpg|400px|thumb|center|Beast Fun is possible using Denning]] |
| == Zoneminder/cctv ==
| |
| | |
| Has an 8 port video capture card in it. It's currently connected to the 3 yard cameras and the rear lobby camera. The other 4 inputs are disabled until we put more cameras up.
| |
| | |
| The card is one of these (or a clone):
| |
| | |
| * http://www.zoneminder.com/wiki/index.php/File:Karta.jpg
| |
| * http://www.zoneminder.com/wiki/index.php/Kodicom_8800
| |
| | |
| The modprobe.d settings I'm using are:
| |
| | |
| <code>
| |
| options i2c-algo-bit bit_test=1
| |
| options tuner debug=1
| |
| options bttv gbuffers=16 card=102,102,102,102,102,102,102,102 radio=0,0,0,0,0,0,0,0 tuner=4,4,4,4,4,4,4,4 audiodev=-1,-1,-1,-1,-1,-1,-1,-1 v4l2=1 bttv_verbose=1 chroma_agc=1 combfilter=2 full_luma_range=1 coring=1
| |
| </code>
| |
| | |
| Each input is configured with:
| |
| | |
| * fps: 10
| |
| * alarm fps: 25
| |
| * palette: BGR24
| |
| * resolution: 640 x 480
| |
| | |
| This might just about work with all 8 inputs, we may have to drop the resolution to 360 x 288
| |
| | |
| The [http://www.zoneminder.com/wiki/index.php/Pico2000 old card].
| |
| | |
| == Issues ==
| |
| | |
| Has only a single mechanical harddrive so vulnerable to data loss.
| |
| | |
| == Ansible procedures ==
| |
| | |
| === using Ansible with a Rasbperry Pi ===
| |
| | |
| <nowiki>
| |
| 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.
| |
| | |
| </nowiki>
| |
| | |
| === Bootstrapping a new machine to a static ip ===
| |
| | |
| <nowiki>
| |
| Login to the new install and find it's ip, make sure you know the root password, or have an sshkey for the root account.
| |
| | |
| Choose a hostname for your new machine.
| |
| | |
| Log in to boole, and as root cd /etc/bind, and edit lan.london.hackspace.org.uk. and 24.31.172.in-addr.arpa. to add your new host, remember the new static ip you choose.
| |
| | |
| There is only a few static ip's left, you may end up needing to shrink the dhcp range and change the dhcpserver config on boole as well.
| |
| | |
| zkt-signer -v -r to sign and push out your changes.
| |
| | |
| Check that the hostname works in fwd and reverse dns.
| |
| | |
| and git commit your changes and log out of boole.
| |
| | |
| on denning edit /etc/ansible/hosts, add:
| |
| | |
| <ip> syslocation="something" lhs_host=<hostname>
| |
| | |
| to at least [lhshosts], you probably want [ldap-clients] as well, and maybe some other sections, depending on what you want.
| |
| | |
| then edit /etc/ansible/lhs/vars/defaults.yml , adding your host and the last octet of the new static ip to the hosts: section
| |
| | |
| now ssh to the host to check that ssh works:
| |
| | |
| ssh root@<ip>
| |
| | |
| You may need to fix old cached pub keys, and/or allowing root to ssh to your new machine with a password ( PermotRootLogin yes in /etc/ssh/sshd_config on the machine you are setting up).
| |
| | |
| Now you can run ansible. This example assumes you are using a password for root
| |
| | |
| cd /etc/ansible
| |
| ansible-playbook -l "<ip>" -k -u root lhs/site.yml
| |
| | |
| and hopefully ansible should run ok and set everything up!
| |
| | |
| Note that ansible will change the root password, hopefully you've got a way to get back in (either you are an admin in ansible, or in the Admins group in ldap, in either case you can login as yourself and then sudo).
| |
| | |
| Now reboot the new machine, it should come back with the static ip. double check that it's right.
| |
| | |
| Now edit /etc/ansible/hosts on denning again and in the entries you added earlier change <ip> to the machines new full hostname.
| |
| | |
| Now run ansible again (needed to fix the snmp config), if it's an ldap client you'll have to use your ldap password - (You could always add your ssh key to your account on the new machine).
| |
| | |
| git commit your changes on denning.
| |
| | |
| and you are done!
| |
| | |
| </nowiki>
| |
| | |
| === Removing an admin ===
| |
| | |
| edit <code>/etc/ansible/lhs/vars/defaults.yml</code>, remove them from users, add them to disable_users, then re-run ansible.
| |
| | |
| == Ansible Troubleshooting ==
| |
| | |
| ; problem, ansible dies in the snmp config cos it can't find a default ipv4 address.
| |
| : fix: make sure the machine has an ipv4 default route
| |
| ; problem, the sshfp stuff just has hostname. rather than hostname.lan.london.hackspace.org.uk.
| |
| : fix: edit /etc/hosts on the effected machine so that both the long and short versions of the hostname are in there.
| |
