1. 19 Oct, 2005 1 commit
  2. 15 Sep, 2005 1 commit
  3. 14 Sep, 2005 1 commit
    • Mike Hibler's avatar
      Changes related to allowing seperate 'fs' (file server) node. · c53d5827
      Mike Hibler authored
      Entailed new instructions for manual setup as well as integration into
      elabinelab framework.  First, the manual path:
      
      setup.txt, setup-boss.txt, setup-ops.txt and new setup-fs.txt:
          Updated to reflect potential for separate fs node.  The org here
          is a little dicey and could be confusing with ops+fs vs. ops and fs.
          Has not been field tested yet.
      
      */GNUmakefile.in: new fs-install target.
      
      configure, configure.in, defs-*:
          Somewhat unrelated, make min uid/gid to use be a defs setting.
          Also add config of fs-install.in script.
      
      boss-install.in, ops-install.in and new fs-install.in:
          Handle distinct fs node.  If you have one, fs-install is run before
          ops-install.  All scripts rely on the defs file settings of FSNODE
          and USERNODE to determine if the fs node is seperate.
      
      utils/checkquota.in:
          Just return "ok" if quotas are not used (i.e., if defs file FS_WITH_QUOTA
          string is null.
      
      install/ports/emulab-fs:
          Meta ...
      c53d5827
  4. 07 Sep, 2005 1 commit
    • Mike Hibler's avatar
      Inner-elab role changes: · 88926d1c
      Mike Hibler authored
      	'boss' -> 'boss+router'
      	'ops'  -> 'ops+fs'
      	'fs'      (new role)
      	'router'  (new role)
      
      These are in preparation for allowing configurations with split ops and fs
      nodes (and sometime down the road, split boss and router nodes).
      
      This checkin is just the DB state changes along with the scripts that look
      at that state.  The Big One, which actually sets up separate nodes
      automatically, is undergoing more testing but will be Coming Soon.
      88926d1c
  5. 10 Aug, 2005 1 commit
  6. 31 May, 2005 1 commit
  7. 27 May, 2005 1 commit
    • Leigh B. Stoller's avatar
      After rebooting inner experimental nodes, force their eventstate to · e1d0181e
      Leigh B. Stoller authored
      ISUP or else they leave off at SHUTDOWN, which later confuses swapmod
      (tbswap) which waits for them to reach ISUP, but of course they never
      do. This is arguably a misfeature of os_setup, which should probably
      not wait for nodes it didn't reboot, but I want to ponder that change.
      Besides, doing this causes the nodes not to say SHUTDOWN in the web
      interface.
      
      Another change to add there (web interface) is to not say "possibly
      down" for elabinelab nodes.
      e1d0181e
  8. 12 May, 2005 3 commits
    • Leigh B. Stoller's avatar
      Checkpoint the rest of my changes to support swapmod of both ElabInElab and · 6eff9de6
      Leigh B. Stoller authored
      Firewalled experiments (see tbsetup/elabinelab.in for the other stuff).
      
      * To support firewalled experiments, needed to add a new virt_firewalls
        table to split the existing firewalls table up, which included both
        virtual and physical stuff. There are the usual frontend changes and a
        few other things scattered around, including tmcd.c.
      
      * The firewall code in tbswap got some beefing up to support adding and
        deleting nodes from the its special control net vlan. Note that I have
        not made any progress on containment of deleted nodes, just as we do not
        do anything now for teardown (unless its paniced, in which case the
        experiment cannot be modified anyway).
      
      * ptopgen and assign_wrapper got some interesting modifications: Unlike
        regular swapmod, we cannot just tear down all the vlans since that would
        interrupt everything inside the inner elab. Instead, leave the vlans as
        is. The problem is that when assign runs, it can just as easily pick
        different interfaces on the same nodes, which would be a royal pain in
        the ass to deal with! So, ptopgen got a new option (-u) that assign
        wrapper uses to tell ptopgen that it should prune out unused interfaces
        from nodes that are already allocated to the experiment. This is, at
        best, as pathetically gross hack, but it makes sure that all the
        interfaces stay the same across swapmods.
      
      * The unrelated revision of elabinelab has a bunch of new code for adding
        and deleting nodes from the inner elab. Mostly it deals with dhcpd (inner
        and outer, waiting for nodes to reboot, etc). It also deals with updating
        the vlans table in the DB, pruning out any nodes (ports) that are deleted
        but for which there are still interfaces in existing vlans. Said ports
        are them moved back to the default vlan with calls to snmpit. Also under
        another revision a a couple of weeks ago are the web interface changes to
        support the newnode MFS inside an inner Emulab.
      
      * swapexp and endexp got some more checks for firewalled and paniced
        experiments, which were missing.
      6eff9de6
    • Leigh B. Stoller's avatar
      Fix bonehead typo in update query. · 321b4d5d
      Leigh B. Stoller authored
      321b4d5d
    • Leigh B. Stoller's avatar
      Part of my changes to support swapmod of ElabInElab experiments. I needed · 283e27fd
      Leigh B. Stoller authored
      to get this change in cause it also includes some DHCPD conf changes and
      Mike and I were messing each other up.
      
      * The DHCPD change is that instead of using reserved.inner_elab_role
        as the flag to indicate a node should boot inside or outside, I
        added inner_elab_boot, which is a boolean that I set when its
        actually time to do this. This avoids two ElabInElab swapins at the
        same time from messing each other up! Basically avoids the obvious
        race.
      
      * The rest of the changes are for swapmod itself, which are incomplete
        but should be harmless until the rest of the stuff is ready.
      283e27fd
  9. 22 Mar, 2005 1 commit
  10. 09 Feb, 2005 1 commit
  11. 28 Jan, 2005 1 commit
    • 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
        over.
      b2cb72f0
  12. 25 Jan, 2005 1 commit
  13. 19 Jan, 2005 1 commit
    • Leigh B. Stoller's avatar
      Some changes for Mike and Firewalled ElabInElab experiments. I need · 263e2cb3
      Leigh B. Stoller authored
      all of the nodes to boot up normally before I can turn them into an
      inner elab (latter, after os_setup). That cannot happen with the
      firewall rules in place. So, when an experiment is firewalled, reorder
      the boot/wait list and wait for the firewall node first. Once that
      hits ISUP, tell the elabinelab code (-f) option so that it can do what
      it needs, which right now means an ssh over to the firewall node to
      temporarily disable all the rules.
      
      We still need to deal with teardown though.
      263e2cb3
  14. 10 Jan, 2005 1 commit
  15. 22 Dec, 2004 1 commit
  16. 21 Dec, 2004 1 commit
  17. 16 Dec, 2004 1 commit
  18. 09 Dec, 2004 1 commit
    • Leigh B. Stoller's avatar
      When the elabinelab experiment is also firewalled, ssh into the · 12c44d00
      Leigh B. Stoller authored
      firewall node and disable the rules during the inner elab setup, and
      then turn them back on after the inner boss has rebooted. In the case
      that an experiment is to be launched inside, launch the experiment
      async and then turn rules back on. Technically, this should be proxied
      through the firewall instead of directly, but this is okay for now.
      
      As for experiment teardown, I am not doing anything yet since the
      closed firewall lets ssh through, and thats all I need to teardown the
      inner elab.
      
      Also during teardown, if DHCPD cannot be killed on inner boss, then
      skip rest of the steps and return okay so that the rest of experiment
      teardown proceeds (if need be, inner nodes will be power cycled). Not
      being be able to kill DHCPD can happen for lots of reasons (like,
      experiment never setup in the first place).
      12c44d00
  19. 07 Dec, 2004 1 commit
    • Leigh B. Stoller's avatar
      * After rebooting the inner nodes, ssh into the inner boss and run · dd3b8989
      Leigh B. Stoller authored
        utility script to wait for them to reboot and reach PXEWAIT. This
        indicates inner emulab is raelly ready
      
      * When an inner experiment is defined (elabinelab_eid in experiments
        table) fire that experiment off by doing an ssh into inner boss. I
        am currently doing this with -w (wait mode) but eventually will need
        to do it async for experiments in which the control net is turned
        off. Also, not actually swapping experiment in yet since multicast
        and frisbee are still broken inside.
      
      * Add -k mode for cleaning up. The intent of this is to avoid power
        cycling all the nodes cause outer elab cannot reboot or ipod them.
        Goes like this:
      
        * Clear the inner_elab_role for experiment's nodes from the reserved
          table.
      
        * Clear def_boot_osid,next_boot_osid,temp_boot_osid for nodes. This
          is bogus cause os_select whines about doing this, but the point is
          to make sure that all nodes will go into PXEWAIT when they reboot.
          We could have them go into MFS, but thats bound to cause problems
          if inner elab has a lot of nodes (remember, cannot trust what is
          on disk). This needs more thought.
      
        * Regen and restart outer dhcpd. Nodes will become part of outer
          emulab on next boot cycle.
      
        * SSH into inner boss and kill inner DHCPD so that there will not be
          any DHCPD responses on inner control network.
      
        * SSH into inner boss and have it reboot all inner nodes.
      
        * Wait for node to reach PXEWAIT.
      
        The above needs more thought wrt firewalled experiments and isolated
        control network.
      
      * Kill off some old MFS copy code since we now get those direct from
        website.
      dd3b8989
  20. 01 Dec, 2004 2 commits
  21. 17 Nov, 2004 2 commits
  22. 15 Nov, 2004 1 commit
    • Leigh B. Stoller's avatar
      A bunch of ElabInELab changes. · 10b116e0
      Leigh B. Stoller authored
      * snmpit: When ElabInELabis true, use the routines in the new
        snmpit_remote.pm library for setting up and tearing down vlans for an
        experiment. At present, only these two operations are proxied out to
        the outer emulab.
      
      * snmpit_remote.pm: A new little library that uses the XMLPRC server on
        the outer emulab to setup and destroy vlans for an inner experiment.
        This code is used from snmpit (see above).
      
      * snmpit_lib.pm: A couple of minor changes for the server side of the
        proxy operation.
      
      * snmpit.proxy.in: A new perl module that is invoked from the RPC
        server.  This proxy sets up and tears down vlans for an inner elab.
        The basic model is that the container experiment will have lots of
        vlans for various individual experiments running on the inner emulab.
      
      * swapexp: A couple of minor elabinelab hacks.
      
      * tbswap: For elabinelab experiments, reconfig/restart dhcpd when
        tearing down the experiment, and call out to new elabinelab script
        when setting up an elabinelab experiment. There is no provision for
        swapmod at this time.
      
      * elabinelab: A new script to create the inner emulab. Does all kinds of
        gross DB stuff then more gross stuff on the inner ops and boss.
      10b116e0