Changes between Version 18 and Version 19 of NikySandbox/TridentCommTut


Ignore:
Timestamp:
05/16/12 22:29:14 (7 years ago)
Author:
nriga@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NikySandbox/TridentCommTut

    v18 v19  
    7676}}}
    7777
    78 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 `[pgeni]` and  `[gpousr##]`.
     78Open 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 `[pgeni]` and  `[<username>]`.
    7979In the pgeni 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.
    8080
    81 In the `[gpousr##]` section, the information need for logging-in to reserved compute resources are provided. It includes you unique URN and a public key that would be uploaded to the hosts that you will reserve during the tutorial.
     81In the `[<username>]` section, the information need for logging-in to reserved compute resources are provided. It includes you unique URN and a public key that would be uploaded to the hosts that you will reserve during the tutorial.
    8282
    8383Another 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 get a chance to provide short descriptive names to the URLs that are easier to memorize and use.
     
    127127   || geni_cert.pem || Cleartext certificate, i.e. does not require any passphrase ||
    128128   || geni_cert_enc.pem || Encrypted certificate  ||
    129    || geni_key || The private key that gpousr25 would use to login to the nodes ||
    130    || geni_key.pub || The corresponding public key that gpousr25 will ask to be loaded to the nodes ||
     129   || geni_key || The private key that you will use to login to the nodes ||
     130   || geni_key.pub || The corresponding public key that will be uploaded to the nodes ||
    131131
    132132== 1c. Test Omni setup ==
     
    184184In order to see your active slices with Omni, you will have to use the `listmyslices` command.
    185185{{{
    186 omni.py listmyslices gpousr##
    187 }}}
    188 
    189 The output looks like :
    190 {{{
    191 geni@geni-vm:~$ omni.py listmyslices inki
    192 INFO:omni:Loading config file /home/geni/.gcf/omni_config
    193 INFO:omni:Using control framework pg
    194 INFO:omni:User 'inki' has slice(s):
    195         urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+testclemson
    196         urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+gponox
    197         urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+inkislice
    198 INFO:omni: ------------------------------------------------------------
    199 INFO:omni: Completed listmyslices:
    200 
    201   Options as run:
    202                 framework: pg
    203                 native: True
    204 
    205   Args: listmyslices inki
    206 
    207   Result Summary: Found 3 slice(s) for user 'inki'.
    208  
    209 INFO:omni: ============================================================
    210 geni@geni-vm:~$ ]
    211 }}}
     186omni.py listmyslices <username>
     187}}}
     188
     189You should see the slice that you created through Flack.
    212190
    213191=== Omni Scripting ===
    214192
    215 After reserving the nodes, you are ready to login. When reserving !PlanetLab resources, using a ProtoGENI clearinghouse, the login name that should be used to access the nodes is ''''not'''' the username. The login is listed as part of the sliverstatus call. For common functionality like this that is expected to be used often, omni gives you the capability of writing scripts and including omni as a library.
    216 Under the /home/geni/gcf directory there is a folder 'examples' that includes example python scripts that use Omni. One script that is available is the
    217 ''readyToLogin.py'' script that will return the exact command for logging-in to your nodes.
    218 {{{
    219 readyToLogin -a <AM_NICKNAME> sliceomni##
     193After reserving the nodes, you are ready to login. The login name and port are listed as part of the sliverstatus call. For common functionality like this that is expected to be used often, omni gives you the capability of writing scripts and including omni as a library.
     194Omni comes with a set of examples (under gcf/examples). One script that is available is the ''readyToLogin.py'' script that will return the exact command for logging-in to the nodes in your sliver.
     195{{{
     196readyToLogin -a pg-utah <slicename>
    220197}}}
    221198