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


Ignore:
Timestamp:
03/13/12 10:39:42 (7 years ago)
Author:
nriga@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEC13Agenda/ExperimenterWorkflowTutorial/Tutorial

    v30 v31  
    9090After 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.
    9191
    92 [[Image(choose-ams.png, 60%)]]
     92[[Image(choose-ams.png, 30%)]]
    9393
    9494Now 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.
    9595
    96 ===Configure Flack to use your account ===
     96===Configure Omni to use your account ===
    9797While 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
    9898{{{
     
    184184rm -f ssh/geni_cert_ct.pem
    185185}}}
     186
     187 Verify that you have the necessary credential and key files
     188     {{{
     189     ls ssh |grep geni
     190     }}}
     191     For gpousr25 the output looks like :
     192     {{{
     193geni@geni-vm:~/Tutorials/ExptWorkflow/gpousr25$ ls ssh |grep geni
     194geni_cert_ct.pem
     195geni_cert.pem
     196geni_key
     197geni_key.pub
     198     }}}
     199
     200   || geni_cert_ct.pem || Cleartext certificate, i.e. does not require any passphrase ||
     201   || geni_cert.pem || Encrypted certificate  ||
     202   || geni_key || The private key that gpousr25 would use to login to the nodes ||
     203   || geni_key.pub || The corresponding public key that gpousr25 will ask to be loaded to the nodes ||
    186204
    187205==== Test configuration ====
     
    302320}}}
    303321
    304 === Createslice in Flack ===
    305 
     322=== Createslice and listmyslices in Flack ===
     323Now 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.
     324Under 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.
     325For 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.
     326
     327=== Createslice and listmyslice in Omni ===
     328In order to do the same thing in Omni, you have to invoke the createslice command. Switch to your terminal window and type
     329{{{
     330omni.py createslice sliceomni##
     331}}}
     332For example user gpousr25 should type :
     333{{{
     334geni@geni-vm:~/Tutorials/ExptWorkflow/gpousr25$ omni.py createslice sliceomni25
     335INFO:omni:Loading config file omni_config
     336INFO:omni:Using control framework pgeni
     337INFO: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
     338INFO:omni: ------------------------------------------------------------
     339INFO:omni: Completed createslice:
     340
     341  Options as run:
     342                framework: pgeni
     343                native: True
     344
     345  Args: createslice sliceomni25
     346
     347  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
     348 
     349INFO:omni: ============================================================
     350}}}
     351
     352In order to see your active slices with Omni, you will have to use the `listmyslices` command.
     353{{{
     354omni.py listmyslices gpousr##
     355}}}
     356
     357For user gpousr25, this would look like :
     358{{{
     359geni@geni-vm:~/Tutorials/ExptWorkflow/gpousr25$ omni.py listmyslices gpousr25
     360INFO:omni:Loading config file omni_config
     361INFO:omni:Using control framework pgeni
     362INFO:omni:User 'gpousr25' has slices:
     363        urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+sliceflack25
     364        urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+sliceomni25
     365INFO:omni: ------------------------------------------------------------
     366INFO:omni: Completed listmyslices:
     367
     368  Options as run:
     369                framework: pgeni
     370                native: True
     371
     372  Args: listmyslices gpousr25
     373
     374  Result Summary: Found 2 slices for user 'gpousr25'.
     375 
     376INFO:omni: ============================================================
     377}}}
     378
     379Notice 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.
     380
     381=== Createsliver and sliverstatus with Omni ===
    306382
    307383== 1. Configure Omni ==
     
    338414   It will prompt you for the passphrase which should be included on the slip
    339415that was given to you.
    340    * Verify that you have the necessary credential and key files
    341      {{{
    342      ls ssh |grep <username>
    343      }}}
    344      For gpousr21 the output looks like :
    345      {{{
    346 geni@geni-vm:~/omni_tutorial$ ls ssh | grep gpousr21
    347 gpousr21_cert_ct.pem
    348 gpousr21_cert.pem
    349 gpousr21_key
    350 gpousr21_key.pub
    351      }}}
    352 
    353    || gpousr21_cert_ct.pem || Cleartext certificate for gpousr21, i.e. does not
    354 require any passphrase ||
    355    || gpousr21_cert.pem || Encrypted certificate for gpousr21 ||
    356    || gpousr21_key || The private key that gpousr21 would use to login to the
    357 nodes ||
    358    || gpousr21_key.pub || The corresponding public key that gpousr21 will ask to
    359 be loaded to the nodes ||
     416   *
    360417
    361418   * '''Look at the  omni_config'''. Open omni_config. For the tutorial you