Changes between Version 30 and Version 31 of GEC13Agenda/ExperimenterWorkflowTutorial/Tutorial

Timestamp:

03/13/12 10:39:42 (13 years ago)

Author:

nriga@bbn.com

Comment:

--

GEC13Agenda/ExperimenterWorkflowTutorial/Tutorial

@@ -90 +90 @@
 After you login, you will see a pop-up window that will ask you which AMs you would like to interact with in this session. First of all unclick the All/None checkbox to uncheck all the AMs. Then make sure that you only check '''bbn-pgeni.cm''' and '''utahemulab.cm''', note that there are AMs with similar names make sure you choose these two. 
 
-[[Image(choose-ams.png, 60%)]]
+[[Image(choose-ams.png, 30%)]]
 
 Now Flack will go behind the scenes and invoke listresources in the selected AMs and populate the map. While Flack is loading the resources you can browse through your personal information by clicking to the button with your username on the left. You will see your credential, your certificate and your ssh keys. 
 
-===Configure Flack to use your account ===
+===Configure Omni to use your account ===
 While Flack is loading the resources let's understand how the same functionality works with Omni. Omni is configured through a text file that is called omni_config. Go back to the terminal window and go under the directory that corresponds to your user 
 {{{
@@ -184 +184 @@
 rm -f ssh/geni_cert_ct.pem
 }}}
+
+ Verify that you have the necessary credential and key files
+     {{{
+     ls ssh |grep geni
+     }}}
+     For gpousr25 the output looks like :
+     {{{
+geni@geni-vm:~/Tutorials/ExptWorkflow/gpousr25$ ls ssh |grep geni
+geni_cert_ct.pem
+geni_cert.pem
+geni_key
+geni_key.pub
+     }}}
+
+   || geni_cert_ct.pem || Cleartext certificate, i.e. does not require any passphrase ||
+   || geni_cert.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 ||
 
 ==== Test configuration ====
@@ -302 +320 @@
 }}}
 
-=== Createslice in Flack ===
-
+=== Createslice and listmyslices in Flack ===
+Now you can switch back to the browser and look at the map of resources. Arguably this is a match better representation of the resources than the text file given back by Omni. 
+Under your username on the left there is a button called createslice. This is how you can create new slices in Flack. Create a new slice called "sliceflack##" based on your username. 
+For example gpousr25 should create a slice called "sliceflack25". An empty canvas should open up and under your username there should be at least this new slice. 
+
+=== Createslice and listmyslice in Omni ===
+In order to do the same thing in Omni, you have to invoke the createslice command. Switch to your terminal window and type 
+{{{
+omni.py createslice sliceomni##
+}}}
+For example user gpousr25 should type :
+{{{
+geni@geni-vm:~/Tutorials/ExptWorkflow/gpousr25$ omni.py createslice sliceomni25
+INFO:omni:Loading config file omni_config
+INFO:omni:Using control framework pgeni
+INFO:omni:Created slice with Name testomni25, URN urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+sliceomni25, Expiration 2012-03-13 20:32:02+00:00
+INFO:omni: ------------------------------------------------------------
+INFO:omni: Completed createslice:
+
+  Options as run:
+                framework: pgeni
+                native: True
+
+  Args: createslice sliceomni25
+
+  Result Summary: Created slice with Name testomni25, URN urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+sliceomni25, Expiration 2012-03-13 20:32:02+00:00
+ 
+INFO:omni: ============================================================
+}}}
+
+In order to see your active slices with Omni, you will have to use the `listmyslices` command. 
+{{{
+omni.py listmyslices gpousr##
+}}}
+
+For user gpousr25, this would look like :
+{{{
+geni@geni-vm:~/Tutorials/ExptWorkflow/gpousr25$ omni.py listmyslices gpousr25
+INFO:omni:Loading config file omni_config
+INFO:omni:Using control framework pgeni
+INFO:omni:User 'gpousr25' has slices: 
+        urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+sliceflack25
+        urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+sliceomni25
+INFO:omni: ------------------------------------------------------------
+INFO:omni: Completed listmyslices:
+
+  Options as run:
+                framework: pgeni
+                native: True
+
+  Args: listmyslices gpousr25
+
+  Result Summary: Found 2 slices for user 'gpousr25'.
+ 
+INFO:omni: ============================================================
+}}}
+
+Notice how you can see the slice that you created with Flack from Omni as well. If you go back to flack and click the reload button that is next to the Slice under your username on the left you will see that the Omni slice will appear there as well. 
+
+=== Createsliver and sliverstatus with Omni ===
 
 == 1. Configure Omni ==
@@ -338 +414 @@
    It will prompt you for the passphrase which should be included on the slip
 that was given to you. 
-   * Verify that you have the necessary credential and key files
-     {{{
-     ls ssh |grep <username>
-     }}}
-     For gpousr21 the output looks like :
-     {{{
-geni@geni-vm:~/omni_tutorial$ ls ssh | grep gpousr21
-gpousr21_cert_ct.pem
-gpousr21_cert.pem
-gpousr21_key
-gpousr21_key.pub
-     }}}
-
-   || gpousr21_cert_ct.pem || Cleartext certificate for gpousr21, i.e. does not
-require any passphrase ||
-   || gpousr21_cert.pem || Encrypted certificate for gpousr21 ||
-   || gpousr21_key || The private key that gpousr21 would use to login to the
-nodes ||
-   || gpousr21_key.pub || The corresponding public key that gpousr21 will ask to
-be loaded to the nodes ||
+   *
 
    * '''Look at the  omni_config'''. Open omni_config. For the tutorial you