Changes between Version 24 and Version 25 of GENIExperimenter/Tutorials/SystematicExprCaseStudy/InstallSoftwareQuagga


Ignore:
Timestamp:
07/11/16 17:20:15 (8 years ago)
Author:
pjayanth@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIExperimenter/Tutorials/SystematicExprCaseStudy/InstallSoftwareQuagga

    v24 v25  
    211211<tr>
    212212<td><img src="http://trac.gpolab.bbn.com/gcf/raw-attachment/wiki/Graphics/stock_notes.png" width="40" height="40" alt="Note"></td>
    213 <td> The custom image with Quagga pre-installed is available for use by any InstaGENI aggregate by using the url <b>https://www.utahddc.geniracks.net/image_metadata.php?uuid=570dc911-2f2b-11e6-9a79-000099989701/b>. This will allow you to skip the customization in Step 2 when using this newly defined custom image. </td></tr></table>
     213<td> The custom image with Quagga pre-installed is available for use by any InstaGENI aggregate by using the url <b>https://www.utahddc.geniracks.net/image_metadata.php?uuid=570dc911-2f2b-11e6-9a79-000099989701</b>. This will allow you to skip the customization in Step 2 when using this newly defined custom image. </td></tr></table>
    214214  </li>
    215215</ol>
     
    233233= 4. Verify InstaGENI Custom Image =
    234234
    235 Unfortunately when a custom image is created, the user account `quagga` and the group account `quaggavty` are deleted. Thus we need a script which recreates these accounts and assigns the required permissions to these accounts. the script for the `quagga` image used in this tutorial is available at http://pcvm2-33.genirack.nyu.edu/install-script.tar.gz .
     235Unfortunately when a custom image is created, the user account `quagga` and the group account `quaggavty` are deleted. Thus we need a script which recreates these accounts and assigns the required permissions to these accounts. The script for the `quagga` image used in this tutorial is available at http://pcvm2-33.genirack.nyu.edu/install-script.tar.gz .
    236236
    237237Now let's load the custom image created in Step 3 by requesting a new VM that uses that image: