Changes between Version 13 and Version 14 of GENIEducation/HyperNets


Ignore:
Timestamp:
08/15/13 15:51:33 (6 years ago)
Author:
shuang@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIEducation/HyperNets

    v13 v14  
    1010 - 4. users' credential will be copied to the hypervisor on registerHyperNet() API call (including ssl private key, will have to change this when "speaks-for" is available ***)
    1111 - 5. build a web page that shows Network Hypervisor server logs: http://andor.gpolab.bbn.com/log/log.html
    12  - 6. concurrent tests: Sarah and I tried to run the same HyperNet package at the same time, reserving resources from both exoGENI and instaGENI. Network Hypervisor is able to handle the XML-RPC calls simultaneously (one does not have to wait until the other finishes)
    13  - 7. An example HyperNet tutorial: http://groups.geni.net/geni/wiki/GENIEducation/SampleAssignments/HyperNetRingDemo
     12 - 6. concurrent tests: Sarah and I tried to run the same !HyperNet package at the same time, reserving resources from both exoGENI and instaGENI. Network Hypervisor is able to handle the XML-RPC calls simultaneously (one does not have to wait until the other finishes)
     13 - 7. An example !HyperNet tutorial: http://groups.geni.net/geni/wiki/GENIEducation/SampleAssignments/HyperNetRingDemo
    1414
    1515== To use a !HyperNet App ==
     
    9191
    9292
     93== !HyperNet Config file ==
     94 - 1. default config file is myConfig.txt, in the same directory of your HyperNet appliance
     95 - 2. by default, it uses "~/.gcf/omni_config" as the omni configuration file (mainly to search for credential files. i.e., ssh keys, ssl certificates and keys)
     96 - 3. by default, it uses pg-utah as the aggregate manager, if users specify to use instaGENI, it uses ig-utah; if users specify to use exoGENI, it uses eg-gpo
     97 - 4. by default, it uses vm as the nodeType (i.e., emulab-openvz for protoGENI and instaGENI AMs, ox-small for exoGENI AMs); user can specify "pc" for protoGENI AMs; or "Xen" for instaGENI AMs; or "xo-medium"/"xo-large" for exoGENI AMs
     98 - 5. "!HyperNetName" is the name of the !HyperNet, we actually pre-pend the username before the !HyperNetName to form the name for the slice in GENI. e.g., username is "shufeng", !HyperNetName is "Ring", then slice name is "shufeng-Ring"
     99 - 6. server is the IP address of the Network Hypervisor service hosing node.
    93100
     101
     102