12 | | For GENI Experiment Example defined above, the following omni_config settings were used: |
13 | | |
14 | | {{{ |
15 | | [omni] |
16 | | default_cf = gpo-pg |
17 | | users = lnevers |
18 | | |
19 | | # ---------- Users ---------- |
20 | | [lnevers] |
21 | | urn = urn:publicid:IDN+pgeni.gpolab.bbn.com+user+lnevers |
22 | | keys = ~/.ssh/id_rsa.pub |
23 | | |
24 | | # ---------- Frameworks ---------- |
25 | | # GPO ProtoGENI |
26 | | [gpo-pg] |
27 | | type = pg |
28 | | ch = https://www.emulab.net:443/protogeni/xmlrpc/ch |
29 | | sa = https://www.pgeni.gpolab.bbn.com:443/protogeni/xmlrpc/sa |
30 | | cert = ~/.ssl/pgeni/encrypted-cleartext.pem |
31 | | key = ~/.ssl/pgeni/encrypted-cleartext.pem |
32 | | verbose=false |
33 | | |
34 | | # Utah ProtoGENI |
35 | | [utah-pg] |
36 | | type = pg |
37 | | ch = https://www.emulab.net:443/protogeni/xmlrpc/ch |
38 | | sa = https://www.emulab.net:443/protogeni/xmlrpc/sa |
39 | | cert = ~/.ssl/protogeni/encrypted-cleartext.pem |
40 | | key = ~/.ssl/protogeni/encrypted-cleartext.pem |
41 | | |
42 | | # PlanetLab |
43 | | [plc] |
44 | | type=sfa |
45 | | authority=plc.bbn |
46 | | user=plc.bbn.lnevers |
47 | | cert=~/.gcf/planetlab/plc.bbn.lnevers.gid |
48 | | key=~/.gcf/planetlab/lnevers.pkey |
49 | | registry=http://www.planet-lab.org:12345 |
50 | | slicemgr=http://www.planet-lab.org:12347 |
51 | | }}} |
52 | | |
53 | | The above configuration is specific to the experiment captured in this page. Note, the pgeni framework definition includes the Utah Emulab clearinghouse, which is the only clearinghouse for ProtoGENI aggregates. For additional configuration details please see the [http://trac.gpolab.bbn.com/gcf/wiki/Omni Omni] page for more details. The omni_configuration parameters shown define the following: [[BR]] |
54 | | || '''Parameter''' || ''' Use''' || |
55 | | || default_cf|| Default Clearinghouse and credentials used if not specified on the command line. || |
56 | | || users|| users setting used when reserving slices. || |
57 | | || urn|| The username URN, see how to determine [wiki:GENIExperimenter/ExperimentCredentials#DetermineyourURN your URN] || |
58 | | || keys|| A comma separated list of public ssh key, that are already uploaded to the Clearinghouse and will be uploaded to nodes by omni tools || |
59 | | || type|| Clearinghouse/credentials type "pg" indicates ProtoGENI, "sfa" indicates PlanetLab || |
60 | | || ch|| ProtoGENI Clearinghouse URL. || |
61 | | || sa|| Slice Authority URL. || |
62 | | || cert|| Location of your SSL encrypted certificate (contains both a certificate and a private key). || |
63 | | || key|| Location of your SSL encrypted private key (contains both a certificate and a private key), or SSH private key for PlanetLab || |
64 | | |
| 13 | Note: 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]. |
68 | | With the GPO ProtoGENI setting defined as shown in the omni_config above, you can get a list of available resources from each of the other 2 aggregates. |
69 | | |
70 | | Note: These instructions use Omni options available in v1.3 and later. Starting with Omni 1.3, 'native' format RSpecs are the default, and 'omnispecs' are deprecated though still available. Additionally, verbose output like the Advertisement RSpec from List Resources is saved to a file using the {{{-o}}} option. Finally, these instructions show the use of the {{{-t}}} option to request RSpecs in a particular format. For earlier versions of omni, you should (a) include the {{{-n}}} argument, (b) re-direct output to a file (''>'') instead of the -o option, and (c) use PG V0.2 RSpecs at Emulab and SFA format RSpecs at PlanetLab. |
| 17 | With your Omni is configured with your GENI credentials, you can get a list of available resources from each of the other 2 aggregates. |
| 18 | |