Changes between Version 18 and Version 19 of NeoContainers


Ignore:
Timestamp:
Oct 2, 2015 2:53:22 PM (9 years ago)
Author:
Geoff Lawler
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • NeoContainers

    v18 v19  
    44
    55=== HOWTO run neo-containers ===
     6
     7Note that much of the guts are still on over for these instructions. Much of the guts though are wrapped up in scripts that will themselves be wrapped in a single neo-containers script once everything has been more thoroughly tested.
    68
    791. Checkout the containers repository and switch to the {{{configdb}}} branch:
    … …  
    3436tb-add-node-attribute $c3po containers:image_type vagrant
    3537tb-add-node-attribute $c3po containers:image_name ubuntu/trusty64
    36 tb-add-node-attribute $r2d2 containers:image_url http://scratch/containers/deter_ub1404_64_vb.box
     38tb-add-node-attribute $c3p0 containers:image_url http://scratch/containers/deter_ub1404_64_vb.box
    3739}}}
    3840
    … …  
    5254source tb_compat.tcl
    5355
    54 tb-make-soft-vtype container0 {pc2133 MicroCloud}
     56tb-make-soft-vtype container0 {dl380g3 pc2133 MicroCloud}
    5557set pnode(0000) [$ns node]
    5658tb-set-node-os ${pnode(0000)} PNODE-CONT
    … …  
    6264}}}
    6365
    64 5. Populate the configuration database that runs on {{{chef.isi.deterlab.net}}} by running the database population scripts. (This will automated in the future.) This should be run from a physical node in the experiment. I use {{{pnode-0000}}} in the example below.
     665. Swap in the experiment.
     67
     686. Populate the configuration database that runs on {{{chef.isi.deterlab.net}}} by running the database population scripts. (This will automated in the future.) This should be run from a physical node in the experiment. I use {{{pnode-0000}}} in the example below.
    6569
    6670{{{
    … …  
    7175}}}
    7276
    73 6. Swap in the experiment and wait a long time. There is no great way to tell when the containers are up, unfortunately. Tail the start-cmd output on the {{{config}}} node and look for the "complete" message.
    74 {{{
    75 users: > ssh config.GID.PID
    76 config: > tail -F /local/logs/config_startcmd.out
    77 }}}
    78 
     77At this point, the Chef server and configuration database knows everything it needs to about your experiment and the nodes within it.
     78
     797. Let Chef configure the nodes. Bootstrap and configure the pnodes. To configure/bootstrap the node use the {{{bootstrap_node.sh}}} script. The script needs to know which role the node plays in the experiment. There are currently three roles: {{{pnode}}}, {{{container}}}, and {{{win-container}}}.
     80
     81On your pnodes:
     82{{{
     83> ssh pnode-0000.${EXPID}.${PROJID}
     84> cd [your container repository]
     85> ./bootstrap_node.sh -r pnode
     86}}}
     87
     88The {{{pnode}}} role will spawn the containers and configure them.
     89
     90Once nodes are bootstrapped, simply running {{{sudo chef-client}}} will re-configure the nodes if something should go wrong.
    7991
    8092Fun things to do after the containers are running.