Changes between Version 17 and Version 18 of GENIRacksHome/InstageniRacks/ConfirmationTestStatus/AdminNewSite


Ignore:
Timestamp:
11/08/12 15:50:14 (7 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIRacksHome/InstageniRacks/ConfirmationTestStatus/AdminNewSite

    v17 v18  
    992. Also Local Admin must join the emulab-ops group, once account was create and membership to emulab-ops was approved proceeded to execute administrative tests.  Note the Utah rack request was submitted at https://boss.utah.geniracks.net/joinproject.php3?target_pid=emulab-ops.
    1010
    11 3. Access to FOAM.utah.genirack.net and !FlowVisor requires more account creation. Also need to document to users the location of the foam password (/opt/foam/etc/foampasswd) and !FlowVisor (/etc/flowvisor/fvpasswd).
     113. Access to FOAM.utah.genirack.net and !FlowVisor requires more account creation.
    1212
    13 4. Access to VM nodes iLO remote access, need to detail how to determine address via web interface, and which ''login ID'' (elabman) and password (/usr/testbed/etc/ilo.pswd) are to be used.
    1413
    1514Note: Found that Utah Rack !FlowVisor uses /home/jbs/fvpasswd.
     
    27262. Local Admin should be told that they can access every VM in the rack, but can only access dedicated nodes (raw-pc) only when they run a sliver on that dedicated node.
    2827
    29 3. There are a multitude of host names for each component in the rack there need to be a list of hostnames provides to the user which documents which hostname is mapped to which address and the role of that definition.
     283. Need to document to Local Admins the location of the foam password (/opt/foam/etc/foampasswd) and !FlowVisor (/etc/flowvisor/fvpasswd).
     29
     304. For Access to VM nodes iLO remote access, need to detail how to determine address via web interface, and which ''login ID'' (elabman) and password (/usr/testbed/etc/ilo.pswd) are to be used.
     31
     32
     335. There are a multitude of hostnames (and network connections) for each component in the rack there need to be a list of hostnames provides to the user which documents which hostname is mapped to which address and the role of that definition.
    3034
    3135For example the following exist on the InstaGENI rack: