1. 28 Jan, 2005 7 commits
    • Leigh B. Stoller's avatar
    • Leigh B. Stoller's avatar
      Add destination coords to the nodes table for robots. · be79278b
      Leigh B. Stoller authored
      	alter table nodes add destination_x float NOT NULL default '0';
      	alter table nodes add destination_y float NOT NULL default '0';
      Unlike other coords, these are meters and translated to pixels
      later when displayed (trying to head in the right direction ...)
    • Timothy Stack's avatar
    • Leigh B. Stoller's avatar
      * Look for latest rc.mkelab in /usr/testbed/etc, but allow override by · b2cb72f0
      Leigh B. Stoller authored
        looking for /proj/$pid/exp/$eid/rc.mkelab. This file constantly
        changes, so its convenient to just copy it over (since it is the
        script that drives inner emulab creation).
      * No longer copy over rc.inelab; let it get installed when the inner
        boss/ops is created, from the testbed source tree that gets copied
    • Leigh B. Stoller's avatar
      Changes to elabinelab setup. The source code for inner boss/ops no · 03cf92cb
      Leigh B. Stoller authored
      longer comes from the project directory (really, my source directory
      in the various projects). Instead, the source code comes from one of
      two places:
      * Using fetch on the inner ops and boss, make a special request to the
        outer webserver to return a tarball, currently stored in
        /usr/testbed/src, and created by toplevel makefile target "elabinelab".
        So, in your object tree (preferably one that is pure, without any of your
        own hacks) run "make elabinelab" and it will create the tarfile for you.
        The tarball is returned only to elabinelab experiments providing the
        experiment secret key (a variant of the existing spewrpmtar file stuff).
      * Using the standard tarfile install command, albiet indrectly cause of how
        we hide all of the elabinelab NS goo. So, in your NS file you can do:
      	tb-elab-in-elab 1
      	set ::TBCOMPAT::elabinelab_source_tarfile \
        Which will arrange for this tarfile to be installed in /usr/src, and then
        copied to the approriate place later when inner boss and inner ops are
        setup. The tarfile should be created in the top of your testbed source
        tree. This is given preference over method 1 above.
      XXX Currently the tarfile is unpacked in /usr/src cause install-tarfile
      does not create the target directory. As soon as we have new images, I'll
      move this unpacking to a more suitable place.
    • Leigh B. Stoller's avatar
      Create the directory where the tarfile is to be unpacked. Not sure why · c3d2b2d8
      Leigh B. Stoller authored
      this was never done ... I guess no one uses tarfiles much.
    • Leigh B. Stoller's avatar
  2. 27 Jan, 2005 25 commits
  3. 26 Jan, 2005 8 commits