Automated installation
From Wikitech
A more recent set of instructions on how to build new servers is at Build a new server.
We have an automated installation system for Ubuntu server, using the Ubuntu installer and preseeding.
Contents |
How to install a server
Information needed
- MAC Address
- Internal or external based host (IE: bast1001.wikimedia.org or mw1001.eqiad.wmnet)
- Network Port
Some of the above may already be listed in the requisite puppet files if the server is being reinstalled, as opposed to a brand new installation.
System Install
- Ensure the server is in the netboot.cfg file located in /srv/autoinstall/netboot.cfg on brewster in the correct section.
- If your box is part of a cluster, then add it to corresponding range otherwise the common install will be used.
- Systems with no entry in netboot.cfg merely have the installer prompt for partitioning information.
- Add the host to the dhcpd configuration file on brewster found in /etc/dhcpd/ and restart dhcpd.
- Please do note there is one configuration file per system baud rate on serial. Please put the system you wish to install in the proper file.
- Connect through the management interface of your new host, power on the server, and netboot the box (e.g. hit F-12 during bootup if it's a Dell).
- There are far more detailed instructions on how to interact with the remote management interfaces at Remote_management
If all works well, you should pull down an automated install from zwinger and lots of magical things will transpire until you get to the partitioning screen.
- Follow the guidelines at partitioning on how best to slice up the disks.
- After the install, ensure the system can use puppet for basic updates. DO NOT PUSH NEW SYSTEMS INTO THE CLUSTER WITHOUT PUPPET WORKING!
Outstanding issues
- Partitioning
- mcelog
- security.ubuntu.com
- SSH keys repository
- Grub PXE booting
- Automatic setting of root password
Problems
My host turned on through the management interface but got no dhcp lease
- Check /var/log/dhcpd.log on brewster to see if the hosts request was ever received.
- If it wasn't then there might be a link issue between the two hosts.
- If it is there then pay attention to the error message. A message of no leases available can mean many things.
- Check the mac address in dhcpd configuration to make sure you entered in the right address.
- Make sure you have set the proper vlan on the switch that your new host is connected to.
- The installer complains about a bad mirror.
- First, check if you don't have a syntax error in the preseed files, e.g. missing 'echo' in netboot.cfg
- This is also sometimes caused by Squid on brewster acting up. Squid is used for ALL apt requests in the installer, because the installer needs to reach external hosts like security.ubuntu.com. After the install, only internal hosts use it, and only for apt mirrors not on our own network.
- Check /var/spool/squid/cache.log for clues.
- If that's not it, try a new rsync:
# su -s /bin/sh mirror /usr/local/sbin/update-ubuntu-mirror
