Equipment/Landin: Difference between revisions

From London Hackspace Wiki

no edit summary
m (blinking formatting.)
No edit summary
 
(23 intermediate revisions by 3 users not shown)
Line 5: Line 5:
|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
|status=Operational
|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 12: Line 12:
|acnode=no
|acnode=no
|owner=LHS
|owner=LHS
|origin=Donation
|origin=Donation from kraptv
|location=Basement rack <!-- Floor, room/zone and location within that area -->
|location=first floor comms room<!-- 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 -->
Line 24: Line 24:


= Info =
= Info =
* IP: 10.20.20.10
* IP: 10.0.20.10
* DNS: landin.london.hackspace.org.uk
* DNS: landin.london.hackspace.org.uk
* Access: LDAP
* Access: LDAP


= Stats =
= Stats =
Landin is a Xyratex HS-1235T (OEM platform for IBM XIV, Dell Compellent, LaCie 12Big, Pure FA-300, and others - note also NetApp disk trays such as DS4243 and other Xyratex OEM users fit as well)
Landin is a Xyratex HS-1235T (OEM storage server platform for IBM XIV, Dell Compellent, LaCie 12Big, Pure FA-300, and several others others - compatibility with various branded disk trays such as NetApp DS4243 and other Xyratex OEM customers mentioned above fit in the array as well)


Note that the <span style="color:red"> power button</span> is just to the inside-front-left (just around the corner from the front-facing LED status lights)
Note that the <span style="color:red"> power button</span> is just to the inside-front-left (just around the corner from the front-facing LED status lights)
Line 39: Line 39:
* [https://www.servethehome.com/lsi-sas-2008-raid-controller-hba-information/ Avago LSI SAS2008 SAS PCIe JBOD Controller] with the following ZFS disk configuration:  
* [https://www.servethehome.com/lsi-sas-2008-raid-controller-hba-information/ Avago LSI SAS2008 SAS PCIe JBOD Controller] with the following ZFS disk configuration:  
** 12-drive ([https://www.hgst.com/sites/default/files/resources/Ultrastar_A7K1000_final_DS.pdf 1TB HGST HUA721010KLA330]) single-pool RAIDZ2 (10TB usable) mounted as /peter
** 12-drive ([https://www.hgst.com/sites/default/files/resources/Ultrastar_A7K1000_final_DS.pdf 1TB HGST HUA721010KLA330]) single-pool RAIDZ2 (10TB usable) mounted as /peter
== Documentation ==
* [[File:HS-1235T-ATX_Quick_Reference_Sheet.pdf]] - Xyratex HS-1235T Kontron Motherboard Quick Reference Sheet (Slot speeds, etc.)
* [[File:User_Manual_12big_Rack_Storage_Server_EN.pdf]] - System User Manual
* [[File:Quick_Install_Guide_12big_Rack_Storage_Server_EN.pdf]] - Xyratex HS-1235T Quick Install Guide (LaCie Branding)


= Build Notes =
= Build Notes =
# These are the notes for the build of Landin (and its functional twin Blanton)
# These are the notes for the build of Landin (and its functional twin [[Equipment/Blanton|Blanton]])
# HW config and notes here: https://wiki.london.hackspace.org.uk/view/Equipment/Landin
# HW config and notes here: https://wiki.london.hackspace.org.uk/view/Equipment/Landin


Line 96: Line 101:


===Proxmox setup===
===Proxmox setup===
We installed Debian Stretch (Debian 9.4.0 at the time) and then followed the [https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Stretch Install Proxmox VE on Debian Stretch] documentation.  After that we needed to install the upgraded the ZFS ZED Daemon via apt-get and upgrade our zpool version as well.
# We'll probably just edit LDAP users to be in that group rather than complicate things with local-remote overlays!
# We'll probably just edit LDAP users to be in that group rather than complicate things with local-remote overlays!
# libvirt:x:113: and libvirt-qemu:x:64055:
# libvirt:x:113: and libvirt-qemu:x:64055:
Line 152: Line 160:


=== Networks ===
=== Networks ===
 
* '''bond0''' LACP group of 4 gigabit ethernet interfaces, tagged with VLANs
* '''vmbr0''' - Standard Linux Bridge, bridged to enp2s0. Think of it like an internal switch. Any VM attached to this bridge is effectively attached to the LAN that Landin is connected to.
==== Bridges ====
* '''vmbr0''' - Standard Linux Bridge, bridged to bond0.20. Think of it like an internal switch. Any VM attached to this bridge is effectively attached to the Servers VLAN
* '''vmbr1''' - Standard Linux Bridge, bridged to bond0.30. This is for the cctv network - you probably don't want this one!
* '''vmbr2''' - Standard Linux Bridge, bridged to bond0.10. This is for the management network - you probably don't want this one!


= Current VMs =
= Current VMs =
=== Chomsky ===
=== Chomsky ===
Chomsky is a General purpose system for LHS member usage ( [[IRC|IRC client use]], [[Robonaut]], shell interaction, http://hack.rs/ URL & forwards, light programming tasks, etc.).
* If you are a current London Hackspace member and would like to login to Chomsky, please create and  [https://london.hackspace.org.uk/members/ldap.php enable your LDAP login here].
* Once your LDAP login has been created, use your ssh client and account details to connect to <span style="color: blue;">chomsky.hack.rs</span>.  (We also resolve internally to <span style="color: blue;">chomsky.lan.london.hackspace.org.uk</span>)
* If you have a software package you'd like installed on the system, please engage with any of the maintainers via [[IRC]] or the [[mailing list]] and we'll do the best to accommodate you.


=== ACserver ===
=== ACserver ===


=== Adminstuff ===
=== Adminstuff ===
* Adminstuff serves network admin bits that were original on retired physical host [[denning]], now running Ansible, apt-cacher-ng, tftpboot + pxeboot stuff, NFS server for diskless booting via [[Netboot]].
==== apt-cacher-ng ====


==== apt-cacher-ng ====
Should you want to leverage our local cache for installing the latest Debian/Ubuntu/Raspbian, you can leverage our local proxy.
 
Simply specify '''http://adminstuff.lan.london.hackspace.org.uk:3142''' or have the line
  Acquire::http::Proxy "http://adminstuff.lan.london.hackspace.org.uk:3142/";
 
in something like /etc/apt/apt.conf.d/proxy.conf
 
Remember to delete this file if you take your computer off of the Hackspace network!


==== Redmine ====
==== Redmine ====
Line 169: Line 193:


=== Services ===
=== Services ===
* apt-mirror / apt-cacher-ng (we probably only want one of these)
* TFTP Serving for PXE Boot Support
=== Scheduled Services ===
We use our reasonably equipped data storage and bandwidth to our advantage, especially when synchronising new Ubuntu and Debian variants.
* '''apt-mirror''' syncing at 4AM every morning the following Debian and Debian-derived repositories:
  Debian Unstable main contrib non-free
  Debian Stable main contrib non-free
  Debian Stretch main contrib non-free
  Ubuntu 16.04 main restricted universe multiverse
  UBUNTU 18.04 main restricted universe multiverse
  Raspbian jessie main contrib non-free rpi
  Raspbian stretch main contrib non-free rpi
* ZFS Scrubbing for Data Health & Verification


= How to: =
= How to: =
Line 175: Line 216:
==== Via the web interface ====
==== Via the web interface ====


# Go to to https://landin.london.hackspace.org.uk:8006
# Go to to https://landin.lan.london.hackspace.org.uk:8006
# Login with your LDAP credentials
# Login with your LDAP credentials
# Click Create VM in the top right corner
# Click Create VM in the top right corner
# In the general tab, set the name and check "start at boot"  
# In the general tab, click advanced in the lower right corner and then set the name and check "start at boot"  
# In the OS tab, select your desired ISO image in the drop down list and configure the parameters for the guest OS
# In the OS tab, select your desired ISO image in the drop down list and configure the parameters for the guest OS
# In the Storage tab, select a SCSI device, select the storage to the "peter" zpool and entered your desired disk size. Check advanced and also check the "discard" box (Important for thin provisioning)
# In the Storage tab, select a SCSI device, select the storage to the "peter" zpool and entered your desired disk size. Check advanced and also check the "discard" box (Important for thin provisioning)
Line 195: Line 236:
# Create the VM <pre>qm create [ID] --name [NAME] -cdrom [PATH TO ISO] --memory [RAM] --cores [CORES] --net0 [INTERFACE] --scsi0 [LOCATION,SIZE]</pre>
# Create the VM <pre>qm create [ID] --name [NAME] -cdrom [PATH TO ISO] --memory [RAM] --cores [CORES] --net0 [INTERFACE] --scsi0 [LOCATION,SIZE]</pre>
# Example of a Debian VM with a single core, 512MB of RAM, 10G HDD and connected to the "Bridge" interface <pre>qm create 104 --name "qm-test" --cdrom /var/lib/vz/template/iso/debian-9.4.0-amd64-netinst.iso --memory 512 --cores 1 --net0 "virtio,bridge=vmbr0" --scsi0 "file=peter:10,discard=on,size=10G"</pre>
# Example of a Debian VM with a single core, 512MB of RAM, 10G HDD and connected to the "Bridge" interface <pre>qm create 104 --name "qm-test" --cdrom /var/lib/vz/template/iso/debian-9.4.0-amd64-netinst.iso --memory 512 --cores 1 --net0 "virtio,bridge=vmbr0" --scsi0 "file=peter:10,discard=on,size=10G"</pre>
==== From an existing disk image ====
Create a VM from the cli or web as above, no need to start it. Then delete it's disk from the hardware config.
Then follow this: http://dae.me/blog/2340/how-to-add-an-existing-virtual-disk-to-proxmox/
If the old vm image is stored on ZFS then you'll need to set the disk cache used by proxmox to `writeback`
Once the disk appears in the proxmox UI you can add it to the vm and activate it (? Can't quite remember how I did it, but the cache thing is the main thing to know)
==== Notes ====
There is an apt-cacher-ng setup on landin running on port 10.0.20.10:3142
Netbooting should work now, the tftp server and files are on the adminstuff VM. There is a Debian Stretch installer with a preseed config that sets up ssh keys for root for some of the admins.


=== RAID Status and How to Blink a Light and Replace a Drive ====
=== RAID Status and How to Blink a Light and Replace a Drive ====
Line 203: Line 260:
* Very likely you want to see how ZFS sees the drives.  This command should suffice:
* Very likely you want to see how ZFS sees the drives.  This command should suffice:
   # zpool status -v
   # zpool status -v
* You can check the list of hardware connected to the array via the LSI (Avago/Broadcom) utility <pre>sas2ircu</pre>
* You can check the list of hardware connected to the array via the LSI (Avago/Broadcom) utility '''sas2ircu'''
   # sas2ircu 0 display
   # sas2ircu 0 display
(you'll want to pipe this to less or a text file to scroll through the various notes.
(you'll want to pipe this to less or a text file to scroll through the various notes.
* Maybe you want to run through <pre>smartctl</pre> and see whether any of the disks are in a pre-fail state. Try a shell script like this:
* Maybe you want to run through '''smartctl''' and see whether any of the disks are in a pre-fail state. Try a shell script like this:
   for i in {a..o}; do
   for i in {a..o}; do
       echo "Disk sd$i" $SN $MD
       echo "Disk sd$i" $SN $MD
118

edits