Changes between Version 39 and Version 40 of GENIExperimenter/ExperimentExample


Ignore:
Timestamp:
08/22/12 16:26:15 (12 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIExperimenter/ExperimentExample

    v39 v40  
    1111If you haven't already configured Omni, please follow [http://trac.gpolab.bbn.com/gcf/wiki/OmniConfigure these configuration instructions].
    1212
    13 The Omni client, is a very simple tool that communicates with Aggregate Managers(AMs) using the [wiki:GeniApi GENI AM API]. In order to specify which AM you would like to talk to, you will have to use the `-a` option of Omni. If you automatically configured Omni then your configuration file contains nicknames for addressing most of GENI AMs. If you manually configured your Omni, them make sure that you added the nicknames from the omni_config.sample file that is under the `gcf` directory. In these examples we will only refer to AMs by their nicknames. If you want to get the full URL please refer to the [attachment:omni_config used configuration file].
     13The Omni client, is a very simple tool that communicates with Aggregate Managers(AMs) using the [wiki:GeniApi GENI AM API]. In order to specify which AM you would like to talk to, you will have to use the `-a` option of Omni. If you automatically configured Omni then your configuration file contains nicknames for addressing most of GENI AMs. If you manually configured your Omni, them make sure that you added the nicknames from the omni_config.sample file that is under the `gcf` directory. In these examples we will only refer to AMs by their nicknames. If you want to get the full URL please refer to the [attachment:omni_config Omni configuration file] used.
    1414
    1515Note: If you are using an Omni version < 1.6.2, then we recommend that you upgrade Omni. If for some reason you can't upgrade Omni and you are having problems following these instructions please [mailto:help@geni.net contact us].