wiki:dSite/k0Inv
close Warning: Can't synchronize with repository "(default)" (/common/SVN/wimax does not appear to be a Subversion repository.). Look in the Trac log for more information.

Version 5 (modified by ssugrim, 6 years ago) ( diff )

Configure OMF Aggregate Managers

Table of Contents

    At this stage of the install, the console should be resolving DNS information against it self. Make a quick check to ensure that the hostname xmpp can be resolved.

    root@console:/export# host xmpp
    xmpp.geni.rutgers.edu is an alias for consolec.geni.rutgers.edu.
    consolec.geni.rutgers.edu has address 10.1.0.254
    

    If this resolution fails the services begin configured will fail to communicate with the installed openfire service on the console. Consequenctly none of the omf-5.4 calls will work.

    Run the service setup script:

    /usr/sbin/geni_omf_setup
    

    This will configure the following files:

    • TODO list files

    The default image location directory is /var/lib/omf-images-5.4, we're going to re-point this directory to /export/omf-images-5.4 so that we don't run into space constraint issues (This is why we made it a separate partition).

    1. Create target
      mkdir /export/omf-images-5.4
      
    2. Remove the old source
      rmdir /var/lib/omf-images-5.4
      
    3. create a symbolic link
      ln -s /export/omf-images-5.4 /var/lib/omf-images-5.4
      

    Now we can download a copy of the baseline image into our image repository. In the /export/omf-images-5.4 directory and make it world readable.

    wget http://packages.orbit-lab.org/downloads/baseline.ndz
    chmod 666 baseline.ndz
    

    Once these pieces are in place, we should be able to check the node status with:

    omf-5.4 stat -t all
    

    Which should produce output similar to

    INFO NodeHandler: OMF Experiment Controller 5.4 (git 070b00f)
    ...
    INFO Topology: Loaded topology 'system:topo:all'.
    
    Talking to the CMC service, please wait
    -----------------------------------------------
     Node: node1.geni.rutgers.edu   	 State: POWEROFF
     Node: node2.geni.rutgers.edu   	 State: POWEROFF
     Node: node3.geni.rutgers.edu   	 State: POWEROFF
    -----------------------------------------------
    
    INFO EXPERIMENT_DONE: Event triggered. Starting the associated tasks.
    ...
    finished after 0:5
    

    Finally we can load an image onto a node with the following

    omf-5.4 load -t node1.geni.rutgers.edu -i baseline.ndz
    

    If all goes well we will see results similar to the following:

    INFO NodeHandler: OMF Experiment Controller 5.4 (git 070b00f)
    ...
    INFO Topology: Loaded topology 'system:topo:registered'.
    INFO property.resetDelay: resetDelay = 100 (Fixnum)
    INFO Experiment: Resetting resources
    INFO stdlib: Waiting for nodes (Up/Down/Total): 0/1/1 - (still down: node1.geni.rutgers.edu) [0 sec.]
    ...
    INFO stdlib: Waiting for nodes (Up/Down/Total): 0/1/1 - (still down: node1.geni.rutgers.edu) [50 sec.]
    INFO exp: Progress(0/0/1): 0/0/0 min(node1.geni.rutgers.edu)/avg/max (57) - Timeout: 790 sec.
    INFO ALL_UP: Event triggered. Starting the associated tasks.
    INFO exp: Progress(0/0/1): 0/0/0 min(node1.geni.rutgers.edu)/avg/max (57) - Timeout: 780 sec.
    ...
    INFO exp: Progress(0/0/1): 90/90/90 min(node1.geni.rutgers.edu)/avg/max (57) - Timeout: 470 sec.
    INFO exp: Progress(1/0/1): 100/100/100 min()/avg/max (57) - Timeout: 460 sec.
    INFO exp:  ----------------------------- 
    INFO exp:  Imaging Process Done 
    INFO exp:  1 node successfully imaged - Topology saved in '/tmp/pxe_slice-2014-10-25t17.00.49.189-04.00-topo-success.rb'
    INFO exp:  ----------------------------- 
    INFO EXPERIMENT_DONE: Event triggered. Starting the associated tasks.
    INFO NodeHandler: 
    INFO NodeHandler: Shutting down experiment, please wait...
    INFO NodeHandler: 
    INFO NodeHandler: Shutdown flag is set - Turning Off the resources
    INFO run: Experiment pxe_slice-2014-10-25t17.00.49.189-04.00 finished after 6:40
    

    The duration of the installation will depend on the speed of the switches you have installed.

    Note: See TracWiki for help on using the wiki.