Changes between Version 18 and Version 19 of NikySandbox/TridentCommTut

Timestamp:

05/16/12 22:29:14 (12 years ago)

Author:

nriga@bbn.com

Comment:

--

NikySandbox/TridentCommTut

@@ -76 +76 @@
 }}}
 
-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##]`.
+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  `[<username>]`.
 In 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. 
 
-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. 
+In 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. 
 
 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 get a chance to provide short descriptive names to the URLs that are easier to memorize and use. 
@@ -127 +127 @@
    || geni_cert.pem || Cleartext certificate, i.e. does not require any passphrase ||
    || geni_cert_enc.pem || Encrypted certificate  ||
-   || geni_key || The private key that gpousr25 would use to login to the nodes ||
-   || geni_key.pub || The corresponding public key that gpousr25 will ask to be loaded to the nodes ||
+   || geni_key || The private key that you will use to login to the nodes ||
+   || geni_key.pub || The corresponding public key that will be uploaded to the nodes ||
 
 == 1c. Test Omni setup ==
@@ -184 +184 @@
 In order to see your active slices with Omni, you will have to use the `listmyslices` command. 
 {{{
-omni.py listmyslices gpousr##
-}}}
-
-The output looks like :
-{{{
-geni@geni-vm:~$ omni.py listmyslices inki
-INFO:omni:Loading config file /home/geni/.gcf/omni_config
-INFO:omni:Using control framework pg
-INFO:omni:User 'inki' has slice(s): 
-        urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+testclemson
-        urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+gponox
-        urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+inkislice
-INFO:omni: ------------------------------------------------------------
-INFO:omni: Completed listmyslices:
-
-  Options as run:
-                framework: pg
-                native: True
-
-  Args: listmyslices inki
-
-  Result Summary: Found 3 slice(s) for user 'inki'.
- 
-INFO:omni: ============================================================
-geni@geni-vm:~$ ]
-}}}
+omni.py listmyslices <username>
+}}}
+
+You should see the slice that you created through Flack. 
 
 === Omni Scripting ===
 
-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. 
-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
-''readyToLogin.py'' script that will return the exact command for logging-in to your nodes. 
-{{{
-readyToLogin -a <AM_NICKNAME> sliceomni##
+After 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. 
+Omni 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.
+{{{
+readyToLogin -a pg-utah <slicename>
 }}}