Difference between revisions of "Sysadmin"

From Earlham CS Department
Jump to navigation Jump to search
m (Machines and Brief Descriptions of Services)
 
(249 intermediate revisions by 15 users not shown)
Line 1: Line 1:
== '''Introducing our 3D printers:''' ==
+
This is the hub for the CS sysadmins on the wiki.
  
 +
= Overview =
  
{|style="margin: 0 auto;"
+
[https://docs.google.com/drawings/d/1XaULz5IxXV_BZQjrko3QJ8wV5aXsSTYcSWxxT49OyZk/edit If you're visually inclined, we have a colorful and easy-to-edit map of our servers here!]
|[[File:MakerBot.jpg|thumb|300px|MakerBot]]
 
|[[File:Robo_3D.jpg|thumb|300px|Robo 3D]]
 
|[[File:Taz_LulzBot.jpg|thumb|300px|Taz Lulzbot]]
 
|}
 
  
== '''Printing instructions:''' ==
+
== Server room ==
  
=== '''Desiging your own 3D model:''' ===
+
Our servers are in Noyes, the science building that predates the CST. For general information about the server room and how to use it, check out [[Sysadmin:Server Room|this page]].
  
Software: OpenSCAD
+
Columns: machine name, IPs, type (virtual, metal), purpose, dies, cores, RAM
  
Cheat Sheet: http://www.openscad.org/cheatsheet/index.html
+
== Compute Resources ==
  
After creating your own 3D model follow this steps:
+
[https://wiki.cs.earlham.edu/index.php/Sysadmin:Computer_Resources Machines and VMs related information here!]
* Render and compile your code by pressing F6
 
* Export the design as .stl
 
* If the file is in your own computer, move the file(name.stl) to the Mac found in Turing lab(CST 222)
 
  
=== '''Overhang / Supports''' ===
+
== Network ==
  
Software: Meshmixer
+
We have two network fabrics linking the machines together. There are three subdomains.
  
Once you import a pre-existing model:
+
=== 10 Gb ===
* Use the align tool under the Edit tab to place model on bed
 
* Use the overhang tool under the Analysis tab to generate supports for the model
 
* Export as " *.stl " when finished
 
  
=== '''Instructions on how to use the 3D printers:''' ===
+
We have 10Gb fabric to mount files over NFS. Machines with 10Gb support have an IP address in the class C range 10.10.10.0/24 and we want to add DNS to these addresses.
  
==== '''Robo R1+ 3D Printer''' ====
+
=== 1 Gb (cluster, cs) ===
  
Software for the printer: MatterControl
+
We have two class C subnets on the 1Gb fabric: 159.28.22.0/24 (CS) and 159.28.23.0/24 (cluster). This means we have double the IP addresses on the 1Gb fabric that we have on the 10Gb fabric.
  
Printing from an SD card:
+
Any user accessing *.cluster.earlham.edu and *.cs.earlham.edu is making calls on a 1Gb network.
*Insert a microSD card into the Mac and get rid of any files in it.
 
*Open MatterControl and drag your .stl file into the QUEUE section of the application.
 
*On the top-left section, click on “Select Printer.” Select “Robo 3D TM Turing” in the window that pops out.  
 
*Towards the bottom of the QUEUE section, you will find a “Queue” button. Click on it to get a list.
 
*On the list, below GCode, select “Export to Folder or SD Card.” Click on the microSD card under “Devices” in the side panel and click on “Export”
 
*Now, in Finder, browse to the microSD card and rename the file you just exported as “auto0.g” (auto zero dot g). Choose “Use.g” if a prompt appears.
 
*Then, safely remove the microSD card from the Mac and insert it into the Robo 3D printer.
 
*Prep the build plate using one the following:
 
**Glue Stick
 
**Vinyl Sheeting
 
**Hairspray
 
:Apply whichever product on the surface of the build plate enough to cover the surface you will be printing on.                                                             
 
*Turn the printer on. Your print will start after about 5 minutes.
 
*After the print is over, wait for the temperature to cool down and carefully remove the 3D printed object from the build plate.
 
*Clean the build plate.
 
  
Printing from the computer:
+
=== Intra-cluster fabrics ===
*Open MatterControl and drag your .stl file into the QUEUE section of the application.
 
*On the top-left section, click on “Select Printer.” Select “Robo 3D TM Turing” in the window that pops out.
 
*Under "Settings" ensure that the correct material is selected.
 
*Under "Controls" an offset of 0.9 typically shows the best results.
 
*Pre-heat the extruder and bed on the same page.
 
*Alternatively, near the top center of the screen, an extruder temperature and a bed temperature will be shown, mouse over and click "pre-heat" for both.
 
*Prep the build plate using one the following:
 
**Glue Stick
 
**Vinyl Sheeting
 
**Hairspray
 
*Click print once the printer has heated up.
 
*After the print is over, wait for the temperature to cool down and carefully remove the 3D printed object from the build plate.
 
*Clean the build plate.
 
  
==== '''Taz Lulzbot 3D Printer''' ====
+
The layout cluster has an Infiniband infrastructure. Wachowski has only a 1Gb infrastructure.
Software for the printer: Cura
 
  
Steps to follow in order to print:
+
== Power ==
*Insert a microSD card into the Mac.
 
*Open Cura and press “Load Model” to upload the stl file you want to print.
 
*Right click “Control” and select the “Save gcode” and then choose the SDcard under the “Devices” panel.
 
*Make sure the Taz 3D Printer is turned on.
 
*Safely eject the sdCard from the Mac and insert it into Taz Printer (on left side of the LCD screen)
 
**Make sure the SD card has the pins facing towards you when insert it
 
*Back on the LCD screen, rotate the knob counter-clockwise to decrease the print speed to ~50%
 
*Press the knob, scroll down by rotating the knob clockwise and select “Temperature”.
 
*Select “Custom Temp” and set the "Nozzle" to 240 and "Bed" to 64
 
*After a few seconds, the LCD will display the info screen again and the printer will start heating up. Wait until the temperatures reach 240C and 64C.
 
*In the info screen, press the knob again. Scroll down and select “Print from SD” Select your file and it will start printing right away.
 
*Once the printing has finished, wait for the bed to cool down and carefully remove the 3D printed object.
 
  
==== '''MakerBot 3D Printer''' ====
+
We have a backup power supply, with batteries last upgraded in 2019 (?). We’ve had a few outages since then and power has held up well.
Software for the printer: ReplicatorG
 
  
Steps to follow in order to print:
+
== HVAC ==
*Insert a microSD card into the Mac.
+
 
*Open ReplicatorG, drag and drop your stl file into application screen.  
+
HVAC systems are static and are largely managed by Facilities.
*Adjust your model if you need to.
+
 
*Select “Generate GCode” on the bottom right.
+
[[Topology|See full topology diagrams here.]]
*Make sure the values are set as shown in the image below and then select “Generate GCode”
+
 
:[[File:Replicator_values.png|thumb|250px|center]]
+
[[Sysadmin:Layers of abstraction for filesystems|A word about what's happening between files and the drives they live on.]]
*If prompted with an “Acceleration Warning” select “OK”
+
 
*Wait until it generates the gcode.
+
= New sysadmins =
*After the file is generated go to the gcode tab and modify the numbers on the lines M104 should be 230 and M109 should be 128, i.e.:
+
 
:M104 S230 T1 (set extruder temperature) M109 S128 T1 (set HBP  temperature)
+
These pages will be helpful for you if you're just starting in the group:
:Make sure to save it by pressing “Command + S”.
+
 
*Select “Build to file using SD Card” as shown in the image below. Select the microSD card and make sure to save it as “.x3g” format.
+
* [[Sysadmin:New Sysadmins | Welcoming a new sysadmin ]]
:[[File:Build_from_sd.png|thumb|300px|center]]
+
* [[Sysadmin:Troubleshooting|General troubleshooting tips for admins]]
*Wait until it is done building and then safely eject the sdCard from the Mac and insert it into the MakerBot. Note: You can find the sdCard slot as shown in the image below:
+
* [[Sandbox Notes|Sandbox Notes]]
:[[File:MakerBot-slot.jpg|thumb|300px|center]]
+
* [[Password managers]]
*Turn on the printer.
+
* [[Server safety]]
*Select “Build from SD” and then using the arrows scroll down to your file.
+
* [https://code.cs.earlham.edu/sysadmin/ticket-tracker Ticket tracking for current projects]
*The printer will start heating up and once it finishes heating up, it will start printing.
+
 
*Once the printing has finished, wait for the bed to cool down and carefully remove the 3D printed object.
+
Note: you'll need to log in with wiki credentials to see most Sysadmin pages.
 +
 
 +
= Additional information =
 +
 
 +
These pages contain a lot of the most important information about our systems and how we operate.
 +
 
 +
===Handy Tools===
 +
* [http://monitor.cluster.earlham.edu:8088/packages Porter's Package Explorer]
 +
 
 +
===Technical docs===
 +
 
 +
* [https://code.cs.earlham.edu/sysadmin/ticket-tracker Ticket tracking for current projects]
 +
* [[Server safety]]
 +
* [[Sysadmin:Backup|Backup]]
 +
* [[Sysadmin:Monitoring | Monitoring ]]
 +
* [[Sysadmin:SSH|SSH info relevant to admins]]
 +
* [[Sysadmin:User Management | User Management]] and [[Sysadmin:LDAP|LDAP]] generally
 +
* [[Sysadmin:Jupyterhub Notebook Server|Jupyterhub]] and [[Nbgrader notes|NBGrader]]
 +
* [[Sysadmin:MailStack|Email service]]
 +
* [[Sysadmin:XenDocs | Xen Server]]
 +
* [[Sysadmin:NFS|Network File System (NFS)]]
 +
* [[Sysadmin:Web Servers|Web Servers and Websites]]
 +
* [[Sysadmin:Services:Databases|Databases]]
 +
* [[Sysadmin:DNS & DHCP|DNS and DHCP]]
 +
* [[Sysadmin:AWS|AWS]]
 +
* [[Bash_start_up_script|Bash startup scripts]]
 +
* [[Sysadmin:VirtualBox | VirtualBox]]
 +
* [[X Applications]]
 +
* [[Sysadmin:Services:ClusterOverview|Cluster Overview]] and [[Sysadmin:Ccg-admin|additional details]]
 +
* [[Sysadmin:Firewall|Firewall]] running on babbage.cs.e.e
 +
* [[Sysadmin:Setting_up_Lovelace_Lab_Machines|Setting up Lab Machines]]
 +
 
 +
===Common tasks===
 +
* [[Sysadmin:Recurring Tasks | Recurring tasks - e.g. software updates, hardware replacements]]
 +
* [[Sysadmin:Contacting all users|Contacting all users]]
 +
* [[Reset password]]
 +
* [[Sysadmin:Software installation | Software installation]]
 +
* [[Modules | Installing software under modules ]]  
 +
* [[Sysadmin:AddComputer|Add a computer to CS or cluster domains]]
 +
* [[Senior projects|Supporting senior projects]]
 +
* [[ShutdownProcedure|How to do a planned shutdown and reboot of the system]]
 +
** [[Sysadmin:TestingServices | Testing services]] (after a reboot, upgrade, change in the phase of the moon, etc.)
 +
* [[Sysadmin:Upgrading SSL Certificate | Upgrading SSL Certificates ]]
 +
* [[Sysadmin:Launch at startup|Launch a process at startup]]
 +
* [[Sysadmin:Psql-setup | setup psql for cs430 students]]
 +
 
 +
===Group and institution information===
 +
* [[Sysadmin:CS-ITS Interoperability|Working with ITS]]
 +
* [[Sysadmin:Recurring spending | Recurring spending ]]
 +
* [[Sysadmin:SlackAndGitLab | Slack and GitLab integration]]

Latest revision as of 08:32, 20 March 2024

This is the hub for the CS sysadmins on the wiki.

Overview

If you're visually inclined, we have a colorful and easy-to-edit map of our servers here!

Server room

Our servers are in Noyes, the science building that predates the CST. For general information about the server room and how to use it, check out this page.

Columns: machine name, IPs, type (virtual, metal), purpose, dies, cores, RAM

Compute Resources

Machines and VMs related information here!

Network

We have two network fabrics linking the machines together. There are three subdomains.

10 Gb

We have 10Gb fabric to mount files over NFS. Machines with 10Gb support have an IP address in the class C range 10.10.10.0/24 and we want to add DNS to these addresses.

1 Gb (cluster, cs)

We have two class C subnets on the 1Gb fabric: 159.28.22.0/24 (CS) and 159.28.23.0/24 (cluster). This means we have double the IP addresses on the 1Gb fabric that we have on the 10Gb fabric.

Any user accessing *.cluster.earlham.edu and *.cs.earlham.edu is making calls on a 1Gb network.

Intra-cluster fabrics

The layout cluster has an Infiniband infrastructure. Wachowski has only a 1Gb infrastructure.

Power

We have a backup power supply, with batteries last upgraded in 2019 (?). We’ve had a few outages since then and power has held up well.

HVAC

HVAC systems are static and are largely managed by Facilities.

See full topology diagrams here.

A word about what's happening between files and the drives they live on.

New sysadmins

These pages will be helpful for you if you're just starting in the group:

Note: you'll need to log in with wiki credentials to see most Sysadmin pages.

Additional information

These pages contain a lot of the most important information about our systems and how we operate.

Handy Tools

Technical docs

Common tasks

Group and institution information