welcome: please sign in

Diff for "InstallationProcedure/CommonInstallSteps"

Differences between revisions 5 and 7 (spanning 2 versions)
⇤ ← Revision 5 as of 2012-12-30 21:33:18 →
Size: 2355
Editor: ClintonEbadi
Comment: mail
← Revision 7 as of 2014-04-29 05:10:29 → ⇥
Size: 2488
Editor: ClintonEbadi
Comment: no need to use dc_other_hostnames
Deletions are marked like this. Additions are marked like this.
Line 37: Line 37:
 * `update-exim4.conf.conf`: Add to `dc_other_hostnames` and `dc_relay_nets`  * `update-exim4.conf.conf`: Add to `dc_relay_nets`
Line 41: Line 41:
Add machine server key to Kerberos: Add the server key to Kerberos. At the `kadmin` console (`$SERVER` is the fully qualified domain name):
Line 43: Line 43:
 * SetupNewMachines#ConfigureSSHServer {{{
add_principal -randkey host/$SERVER@HCOOP.NET
}}}
Line 45: Line 47:
 * Sync keytabs in `create-user`
 * Create `WebNode` for portal		 Update `create-user` to synchronize keytabs to the new node if applicable.
Line 48: Line 49:
Create `WebNode` for portal according to [[DaemonAdmin/Portal]]

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.

Enable mail routing by adding to exim configuration on the mail server (unless Bug 939 has been fixed, in which case update this documentation with the domtool managed procedure). In the exim config directory:

  • update-exim4.conf.conf: Add to dc_relay_nets

  • conf.d/main/01_exim4-config_listmacrosdefs.conf: Add to unix_domains

  • Run update-exim4.conf

Add the server key to Kerberos. At the kadmin console ($SERVER is the fully qualified domain name): 

add_principal -randkey host/$SERVER@HCOOP.NET

Update create-user to synchronize keytabs to the new node if applicable.

Create WebNode for portal according to DaemonAdmin/Portal

CategorySystemAdministration

InstallationProcedure/CommonInstallSteps (last edited 2020-07-19 21:49:28 by ClintonEbadi)