Changes between Version 25 and Version 26 of GENIRacksHome/OpenGENIRacks/InstallationGuideJuno

Timestamp:

10/02/15 10:24:03 (9 years ago)

Author:

rrhain@bbn.com

Comment:

--

GENIRacksHome/OpenGENIRacks/InstallationGuideJuno

@@ -175 +175 @@
 ssh-keygen
 }}}
-Then copy the the contents of /home/gram/.ssh/id_rsa.pub of the control node to /home/gram/.ssh/authorized_keys on the network node, and change the permissions of this file as follows:
-{{{
-sudo chmod 600 /home/gram/.ssh/authorized_keys
-}}}
-
-On the network node: 
-
-1. Make sure you have the 10.10.8 interface up as certain pieces of information are placed on the node using ssh and that interface.  Alternately, you can run up to the installation of the /tmp/install/install_operating_system_network.sh on the network node before
-executing the /tmp/install/install_control.sh on the control node. The operating system installation should take care of configuring the needed interface.  Although it is a good idea, if not a requirement for sanity, to check that
-your interfaces are plugged in as you think.  So before the installation, check network connectivity.
-
-
-2. '''Install mysql on the control node'''
-
-{{{
-sudo apt-get install mariadb-server python-mysqldb
-}}}
-
-  - You will be prompted for the password of the mysql admin. Type it in (twice) and remember it: it will be needed in the config.json file for the value of mysql_password.
-
-
-3. '''Install !OpenStack and GRAM on the control, network and compute nodes'''
-
-  - Get the DEBIAN files gram_control.deb, gram_network.deb and gram_compute.deb. 
-  - These packages can be generated from the repository, following instructions from here: http://groups.geni.net/geni/wiki/GENIRacksHome/OpenGENIRacks/SoftwareReleaseNotes
-  - Alternatively, they can be obtained by request from '''gram-dev@bbn.com'''.
-  - Set up the APT repository to read the correct version of juno packages:
-{{{
-sudo apt-get install -y ubuntu-cloud-keyring
-echo deb http://ubuntu-cloud.archive.canonical.com/ubuntu trusty-updates/juno main >> cloudarchive-juno.list
-sudo mv cloudarchive-juno.list /etc/apt/sources.list.d/
-}}}
-  - Update the current repository:
-{{{
-sudo apt-get -y update && sudo apt-get -y dist-upgrade
-}}}
-
-  - Get the gdebi package for direct installation of deb files
-{{{
-sudo apt-get install gdebi-core
-}}}
-  - Install the gram package (where <type> is ''control'', ''network'' or ''compute'' depending on what machine type is being installed):
-{{{
-sudo gdebi gram_<control/network/compute>.deb
-}}}
-
-  - '''Edit /etc/gram/config.json'''. ''NOTE: This is the most critical step of the process. This specifies your passwords, network configurations, so that !OpenStack will be configured properly.'' [See section "Configuring config.json" below for details on the variables in that file]
-
-  - Run the GRAM installation script (where <type> is ''control'' or ''compute'' depending on what machine type is being installed):
-{{{
-sudo /etc/gram/install_gram.sh <control/network/compute>
-}}}
-
-  - Configure the OS and Network. You will lose network connectivity in the step, it is recommended that the following command is run directly on the machine or using the Linux 'screen' program. 
-{{{
-sudo /tmp/install/install_operating_system_[control/network/compute].sh
-}}}
-
-
-  - Configure everything else. Use a ''' root shell '''
-{{{
-/tmp/install/install_[control/network/compute].sh
-}}}
-
-This last command will do a number of things:
-  - Read in all apt dependencies required
-  - Configure the !OpenStack configuration files based on values set in config.json 
-  - Start all !OpenStack services
-  - Start all GRAM services
-
-If something goes wrong (you'll see errors in the output stream), then the scripts it is running are in /tmp/install/install*.sh (install_compute.sh or install_control.sh). You can usually run the commands by hand and get things to work or at least see where things went wrong (often a problem in the configuration file).
-
-  - Create gram ssh public key pair and authorized_hosts file on network node so that commands for gram can be executed without typing in a password
-
-{{{
-ssh-keygen -t rsa -C "gram@bbn.com"
+
+  - Copy gram ssh public key pair and create authorized_hosts file on network node so that commands for gram can be executed without typing in a password.  You might also want to do this on the compute node.
+
+{{{
 ssh gram@networkNode:
 mkdir .ssh
@@ -262 +190 @@
 ssh gram@networkNode ls
 }}}
+
+On the network node: 
+
+1. Make sure you have the 10.10.8 interface up as certain pieces of information are placed on the node using ssh and that interface.  Alternately, you can run up to the installation of the /tmp/install/install_operating_system_network.sh on the network node before
+executing the /tmp/install/install_control.sh on the control node. The operating system installation should take care of configuring the needed interface.  Although it is a good idea, if not a requirement for sanity, to check that
+your interfaces are plugged in as you think.  So before the installation, check network connectivity.
+
+
+2. '''Install mysql on the control node'''
+
+{{{
+sudo apt-get install mariadb-server python-mysqldb
+}}}
+
+  - You will be prompted for the password of the mysql admin. Type it in (twice) and remember it: it will be needed in the config.json file for the value of mysql_password.
+
+
+3. '''Install !OpenStack and GRAM on the control, network and compute nodes'''
+
+  - Get the DEBIAN files gram_control.deb, gram_network.deb and gram_compute.deb. 
+  - These packages can be generated from the repository, following instructions from here: http://groups.geni.net/geni/wiki/GENIRacksHome/OpenGENIRacks/SoftwareReleaseNotes
+  - Alternatively, they can be obtained by request from '''gram-dev@bbn.com'''.
+  - Set up the APT repository to read the correct version of juno packages:
+{{{
+sudo apt-get install -y ubuntu-cloud-keyring
+echo deb http://ubuntu-cloud.archive.canonical.com/ubuntu trusty-updates/juno main >> cloudarchive-juno.list
+sudo mv cloudarchive-juno.list /etc/apt/sources.list.d/
+}}}
+  - Update the current repository:
+{{{
+sudo apt-get -y update && sudo apt-get -y dist-upgrade
+}}}
+
+  - Get the gdebi package for direct installation of deb files
+{{{
+sudo apt-get install gdebi-core
+}}}
+  - Install the gram package (where <type> is ''control'', ''network'' or ''compute'' depending on what machine type is being installed):
+{{{
+sudo gdebi gram_<control/network/compute>.deb
+}}}
+
+  - '''Edit /etc/gram/config.json'''. ''NOTE: This is the most critical step of the process. This specifies your passwords, network configurations, so that !OpenStack will be configured properly.'' [See section "Configuring config.json" below for details on the variables in that file]
+
+  - Run the GRAM installation script (where <type> is ''control'' or ''compute'' depending on what machine type is being installed):
+{{{
+sudo /etc/gram/install_gram.sh <control/network/compute>
+}}}
+
+  - Configure the OS and Network. You will lose network connectivity in the step, it is recommended that the following command is run directly on the machine or using the Linux 'screen' program. 
+{{{
+sudo /tmp/install/install_operating_system_[control/network/compute].sh
+}}}
+
+
+  - Configure everything else. Use a ''' root shell '''
+{{{
+/tmp/install/install_[control/network/compute].sh
+}}}
+
+This last command will do a number of things:
+  - Read in all apt dependencies required
+  - Configure the !OpenStack configuration files based on values set in config.json 
+  - Start all !OpenStack services
+  - Start all GRAM services
+
+If something goes wrong (you'll see errors in the output stream), then the scripts it is running are in /tmp/install/install*.sh (install_compute.sh or install_control.sh). You can usually run the commands by hand and get things to work or at least see where things went wrong (often a problem in the configuration file).