|Version 12 (modified by 9 years ago) ( diff ),|
Table of Contents
- GENI Site Installation
Base OS installation
- Choose relevant language and keyboard settings
- We expect eth2 is the up-link interface (used to internet access and remote control) and should be interface chosen for installation. It is also expected that eth2 will be connect to a network that will assign it a dhcp address.
- Specify a local USERNAME/PASSWORD combo. Please keep track of this information, it will be required for all setup procedures later on.
- Specify Manual partitioning and partition the disk as follows:
Number Type Size Flags File System Mount Point 1 Primary 20GB Bootable Ext4 / 2 Primary 20GB Ext4 /home 3 Primary 116GB Ext4 /export 4 Primary 4GB Swap
- Leave the http Proxy field empty
- specify NO AUTOMATIC UPDATES. This is important as the auto-update process may break some orbit packages.
- Choose opensssh server in the task selection menu. All other tasks will be installed as seprate packages and do not need to be specified here.
- Answer Yes to installing grub on the local boot disk
- Remove the media (and the drive if needed) and reboot.
- If no explicit instruction is given for a setting, it's safe to assume the default should work.
- This version of Ubuntu does not work well with USB flash disk installations, The best results are with a burned CD/DVD and a USB CD/DVD drive as a the boot medium,refrenced here.
Configure Host Name
A important initial step specifying the hostname of the console. Many of the later services will depend heavily on this name resolution. It is assumed that the general form of the console's fully qualified domain name (FQDN) is console.geni.DOMAIN, where DOMAIN comes from your organization. As an example the DOMAIN for Rutgers is rutgers.edu.
To set the host name edit the follow files (here we assumed that DOMAIN = rutgers.edu):
- /etc/hosts - Local file for name resolution.
127.0.0.1 localhost 127.0.1.1 console.geni.rutgers.edu console # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters
- /etc/hostname - Modify this file to properly resolve the hostname of the machine.
For proper console operation, The console is expected to be connected to 4 Networks. Their respective names and purposes are:
- Data - For experiment traffic, Ideally this is in a separate switch plane to avoid mixing / clobbering control traffic
- CM - Low speed network for soft control of power and terminal output of each node
- Control - Management and control traffic to the Nodes. This network is used for imaging and is needs to be fast. Ideal on a non-blocking switch with good back plane throughput.
- Outside - External access for the console. Mostly for remote control and package updates.
To establish the proper address spaces, we put appropriate rules in the /etc/network/interfaces file. We assume the following mapping of interfaces to subnets:
# This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The Control network interface auto eth3 iface eth3 inet static address 10.1.0.254 netmask 255.255.255.0 broadcast 10.1.0.255 # The Data network interface auto eth0 iface eth0 inet static address 10.2.0.254 netmask 255.255.255.0 broadcast 10.2.0.255 # The CM network interface auto eth1 iface eth1 inet static address 10.3.0.254 netmask 255.255.255.0 broadcast 10.3.0.255 # The primary network interface auto eth2 iface eth2 inet static address 10.50.0.249 netmask 255.255.0.0 gateway 10.50.0.1 dns-nameservers 184.108.40.206
Note: The dns-nameservers is a temporary setting, we'll need to reconfigure the console to resolve against it self once the DNS service is installed
Additional Instructions when using 14.04 instead
Also edit /etc/default/grub, and make sure the lines match the below:
Then run sudo update-grub