Equipment/Boole: Difference between revisions
From London Hackspace Wiki
(ansible brain dump.) |
(add model info) |
||
| Line 2: | Line 2: | ||
|name=Boole <!-- Name of the item. --> | |name=Boole <!-- Name of the item. --> | ||
|image=Hackspace_Unknown.png <!-- Image of the item. Leave with placeholder image if none exists. --> | |image=Hackspace_Unknown.png <!-- Image of the item. Leave with placeholder image if none exists. --> | ||
|model= | |model=Nexcom DNA1110 <!-- 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 --> | ||
| Line 17: | Line 17: | ||
|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 --> | ||
}} | }} | ||
A 1U Intel Atom machine in the rack in the basement. | A 1U Intel Atom machine in the rack in the basement, specs etc [http://www.nexcom.com/Products/network-and-communication-solutions/desktop-appliance/desktop-appliance/communication-gateway-dna-1110# here] | ||
Is our core router, has both FTTC lines connected to it. DHCP and DNS server. Runs the spacefed node for the space and is an ldap server. | Is our core router, has both FTTC lines connected to it. DHCP and DNS server. Runs the spacefed node for the space and is an ldap server. | ||
Revision as of 12:27, 20 October 2013
| Boole | |
|---|---|
 | |
| Model | Nexcom DNA1110 |
| Sub-category | Systems |
| Status | Good working order |
| Training requirement | yes |
| Training link | Unknown |
| ACnode | no |
| Owner | LHS |
| Origin | donation from Tgreer |
| Location | Basement rack. |
| Maintainers | Sysadmin team |
A 1U Intel Atom machine in the rack in the basement, specs etc here
Is our core router, has both FTTC lines connected to it. DHCP and DNS server. Runs the spacefed node for the space and is an ldap server.
Also a netboot server, provides:
- Diskless i386 and amd64 debian wheezy
- Rescue and Install for debian wheezy.
- partition magic
- memtest
- dban
- Voyage (a minimised debian disto that can run from readonly media) Warning : the Voyage auto install kernsl will reformat things they are booted on without prompting.
Also runs ansible for setting up machines in the space.
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
log into boole with ssh keys forwarded
add hostname to dns
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
ansible -v -s -u pi -k -m command -a "apt-get -y install python-apt" "hostname*"
ansible-playbook -u pi -s -k -l "perlman*" 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.
