Before proceeding with the AutomatedSystemInstall new nodes must be added to HCoop's infrastructure.

1. Network

After deciding on the host name through a poll of the members:

1. Allocate an addresses from the free list on IpAddresses (and update the page!)

2. Using the peer1 request portal, add a reverse dns mapping to the hostname
   • You cannot install the machine until the reverse dns mapping has been created; various services rely on the rdns mapping to behave correctly.

3. Add basic node information to DomTool config

   1. Edit /afs/hcoop.net/common/etc/domtool/lib/hcoop.dtl and add definition for HOSTNAME_ip

   2. Edit /afs/hcoop.net/user/h/hc/hcoop/.domtool/hcoop.net to add a DNS entry for $HOST.hcoop.net, using HOSTNAME_ip

   3. Apply DomTool configuration (run DOMTOOL_USER=hcoop domtool hcoop.net)

   4. Synchronize DomTool library with source code git repository

2. Documentation

Add the machine to the Hardware page. KernelVirtualMachines go into a sub-section of their current physical node. Note any relevant information such as the resources available for the node, intended purpose, etc.

Make sure the machine is listed on the IpAddresses page.

After install, update the notes with any quirks of the install (ideally: none, but reality is a work in progress).

3. Add to Infrastructure

To control the node with DomTool minimally:

• Add to Config.nodeIps

• Add to Config.Firewall.firewallNodes

If you are configuring the node for a specific purpose, you'll need to add it to more configuration. See the DomTool documentation where it exists.

Prepare DomTool for deployment: DomTool/Installation.

• Add to Kerberos SetupNewMachines#ConfigureSSHServer

• Add to relay_domains on mail hub

• Sync keytabs in create-user

• Create WebNode for portal

CategorySystemAdministration