Sysadmin:AddComputer: Difference between revisions

From Earlham CS Department
Jump to navigation Jump to search
← Older edit
Kay (talk | contribs)
Bureaucrats, nsAppliedGroupsD, nsAppliedGroupsR, nsAppliedGroups_, nsCDCDEL, nsCDC_TalkDEL, nsCS382DEL, nsCS382RO, nsCS382RW, nsCS382_TalkDEL, nsCS382_TalkRO, nsCS382_TalkRW, nsDepartmentDEL, nsDepartmentRW, nsDepartment_Tal, nsFundingDEL, nsFundingRW, nsFunding_TalkDE, nsFunding_TalkRW, nsGradingDEL, nsGradingRW, nsGrading_TalkDE, nsGrading_TalkRW, nsSysadminDEL, nsSysadmin_TalkD, Administrators
959 edits
No edit summary
Craigje (talk | contribs)
administrator, Bureaucrats, Administrators
1,085 edits
mNo edit summary
 
(16 intermediate revisions by 4 users not shown)
Line 1: Line 1:
These are the changes that need to be made if a computer is to be added to the CS network, follow these steps.
Below are instructions for adding a machine to the CS or Cluster network.


== Software ==
Note that if you're ever confused, you can look at another machine and do some "comparative anatomy" to see how certain files should be edited.
Make sure the following packages installed (through ports or through apt):
* vim
* nano
* bash
* ssh
* sudo


=== SSH and Sudo ===
== Install a base OS ==
* Set up sudo to allow members of the admin group to become root.
* Disable root logins via SSH.
* At some point in the future, we may be disabling the root account entirely (Ubuntu style).


== DNS and DHCP ==
Generally, CS machines run Debian and cluster machines run CentOS.
=== DNS ===
* Add the machine's hostname and IP address to /etc/namedb/master/cs.zone (or public.zone for the public network). Make sure to update the serial number at the top of the file, and to end hostnames with a period so that they are FQDN. Also make sure to use an IP address that is not already  taken.
** Add the machine's reverse record to /etc/namedb/master/159.28.230.zone (or 159.28.231.zone for the public zone). The same rules as above apply.
** Restart DNS by sending a SIGHUP to the named process, or using the <tt>rndc reload</tt> command.


'''Note on CNAMES:'''<br />
== Bring up at least one network interface ==
If you want to create a CNAME for foo.public.cs.earlham.edu that is bar.public.cs.earlham.edu, the definition will go into public.zone.  On the other hand, if you wanted bar.cs.earlham.edu to be a CNAME for foo.public.cs.earlham.edu, the CNAME definition will go into cs.zone.


=== DHCP ===
Depending on the OS you install, there's a strong possibility the network interface won't be brought up by default.
* Add the machine to forty-one:/etc/dhcp3/dhcpd.conf. You will need its Ethernet MAC address for this. Make sure to terminate each field with a semicolon.
** Restart dhcpd by running the command /etc/init.d/dhcp3-server restart


== Email ==
== Configure DNS and DHCP ==
* In /etc/aliases or similar, set the outgoing e-mail to root@cs.earlham.edu.  On quark, this automatically forwards to the admin list. We send it to root instead so that we can have "emergency moderation" and stop it going to the list if need be. Or, in case we need to stop going to the list because mailman is down.
 
See [[Sysadmin:DNS & DHCP|this page]] for how to configure the DNS and DHCP server to recognize the machine.
 
Locally, you'll need to edit /etc/resolv.conf (to, e.g., specify your DNS nameserver), the config file for your particular network interface (e.g. on CentOS you may care about /etc/sysconfig/network-scripts/ifcfg-enp1s0f0), and /etc/hosts (to set your own hostname).
 
== Configure LDAP ==
 
Most likely, new servers will be connected to our LDAP database for user account sharing purposes.
 
== Install the base software kit ==
 
Go [[Base software kit|here for that]].

Latest revision as of 16:27, 1 August 2019

Below are instructions for adding a machine to the CS or Cluster network.

Note that if you're ever confused, you can look at another machine and do some "comparative anatomy" to see how certain files should be edited.

Install a base OS

Generally, CS machines run Debian and cluster machines run CentOS.

Bring up at least one network interface

Depending on the OS you install, there's a strong possibility the network interface won't be brought up by default.

Configure DNS and DHCP

See this page for how to configure the DNS and DHCP server to recognize the machine.

Locally, you'll need to edit /etc/resolv.conf (to, e.g., specify your DNS nameserver), the config file for your particular network interface (e.g. on CentOS you may care about /etc/sysconfig/network-scripts/ifcfg-enp1s0f0), and /etc/hosts (to set your own hostname).

Configure LDAP

Most likely, new servers will be connected to our LDAP database for user account sharing purposes.

Install the base software kit

Go here for that.

Retrieved from "https://wiki.cs.earlham.edu/index.php?title=Sysadmin:AddComputer&oldid=17327"