Changes between Version 13 and Version 14 of GENIExperimenter/Tutorials/HelloOmni


Ignore:
Timestamp:
11/15/12 11:09:20 (7 years ago)
Author:
nriga@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIExperimenter/Tutorials/HelloOmni

    v13 v14  
    4444geni_cert_enc.pem  geni_cert.pem
    4545     }}}
    46 
    47 == 1a. Look around the omni_config file -- Optional ==
    48 Open the file `~/.gcf/omni_config` using either vim or emacs. Close to the top of the file you will see two parameters called `default_cf` and `users`. Your username should be at least listed in the user section. Look for the sections in the file that are named `[pg]` and  `[<username>]`.
    49 
    50 In the `[<username>]` section, the information need for logging-in to reserved compute resources are provided. It includes your unique user URN and a public key that would be uploaded to the hosts that you reserve.
    51 
    52 In the `[pg]` section you configure Omni to use your personal information. The cert and the key attribute point to files that we have manually downloaded from pgeni.gpolab.bbn.com. This is equivalent to the Download action of Flack.
    53 
    54 Another interesting section to look at is the `[aggregate-nicknames]` sections. Flack already knows the URL for all the AMs and present you a list of AMs to choose from using a short, descriptive name. In Omni a user is required to pass the URL for each call to the GENI AM API. In this section the user gets a chance to provide short descriptive names to the URLs that are easier to memorize and use.
     46   || geni_cert.pem || Cleartext certificate, i.e. does not require any passphrase ||
     47   || geni_cert_enc.pem || Encrypted certificate  ||
     48   || geni_key || The private key that you will use to login to the nodes ||
     49   || geni_key.pub || The corresponding public key that will be uploaded to the nodes ||
     50   '''Note:''' Depending on the setup of your host you might see more files listed above.
     51
     52   5.  '''Optional - Look around the omni_config file '''
     53   Open the file `~/.gcf/omni_config` using either vim or emacs. Close to the top of the file you will see two parameters called `default_cf` and `users`. Your username should be at least listed in the user section. Look for the sections in the file that are named `[pg]` and  `[<username>]`.
     54   
     55   In the `[<username>]` section, the information need for logging-in to reserved compute resources are provided. It includes your unique user URN and a public key that would be uploaded to the hosts that you reserve.
     56
     57   In the `[pg]` section you configure Omni to use your personal information. The cert and the key attribute point to files that we have manually downloaded from pgeni.gpolab.bbn.com. This is equivalent to the Download action of Flack.
     58
     59   Another interesting section to look at is the `[aggregate-nicknames]` sections. Flack already knows the URL for all the AMs and present you a list of AMs to choose from using a short, descriptive name. In Omni a user is required to pass the URL for each call to the GENI AM API. In this section the user gets a chance to provide short descriptive names to the URLs that are easier to memorize and use.
    5560
    5661= 2. Clear the passphrase from your cert =