1. 18 Dec, 2002 1 commit
  2. 16 Dec, 2002 2 commits
  3. 11 Dec, 2002 2 commits
  4. 09 Dec, 2002 1 commit
    • Leigh B. Stoller's avatar
      Ease up permissions check since it always does the right thing; just · ed27821c
      Leigh B. Stoller authored
      force audit mode when a non-admin mucks with another persons account.
      Add check for "webonly" accounts and treat like other users that do
      not get an account on boss/ops.
      Check for users without any project membership, and create account
      with the guest group. This won't actually happen, but I made this
      change in case we decide to give widearea owners a real account.
      I think setgroups should get an equiv change at some point.
      ed27821c
  5. 07 Dec, 2002 1 commit
  6. 06 Dec, 2002 1 commit
    • Leigh B. Stoller's avatar
      Reorg the deleteuser stuff. In the perl script, watch for non-existent · 437b8ebf
      Leigh B. Stoller authored
      accounts and do not die. Also, no longer rename the home dir; just
      leave it where it is; not sure that served any purpose at all.
      Also mark nodes as needing account updates (this requires that the
      group_membership remain intact until after the script runs).
      
      In the php script, also purge the sfskeys table and the new
      widearea_accounts table.
      437b8ebf
  7. 05 Dec, 2002 1 commit
  8. 03 Dec, 2002 1 commit
  9. 22 Nov, 2002 1 commit
  10. 21 Nov, 2002 1 commit
  11. 19 Nov, 2002 1 commit
  12. 14 Nov, 2002 3 commits
    • Shashi Guruprasad's avatar
      011697a7
    • Mac Newbold's avatar
      Add the long-awaited check for nodes that have too many lans/links. For · 4f0c3572
      Mac Newbold authored
      now it is just hardcoded to 4, but could be done from the db too. Gives
      errors like this one, from a topo where node2 and node6 each have 5 links:
      
      *** /usr/testbed/devel/newbold/lib/ns2ir/parse.tcl:
          Too many links/LANs to node node2! Maximum is 4.
      *** /usr/testbed/devel/newbold/lib/ns2ir/parse.tcl:
          Too many links/LANs to node node6! Maximum is 4.
      *** /usr/testbed/devel/newbold/bin/batchexp:
          NS Parse failed!
      4f0c3572
    • Mac Newbold's avatar
      Finally, a check for links that want too much bandwidth. Right now it uses · 5eb5c6ed
      Mac Newbold authored
      the somewhat hacky fail-if-they-want-over-100mbps method, but could in the
      future draw the info from the database or something if it ends up being
      necessary.
      
      Setup Failure(255): Output as follows:
      
      *** /usr/testbed/devel/newbold/lib/ns2ir/parse.tcl:
          Bandwidth requested (150000) exceeds maximum of 100000 kbps!
      *** /usr/testbed/devel/newbold/lib/ns2ir/parse.tcl:
          [run] link0 has only a single node. LANs must have at least 2 nodes in them.
      *** /usr/testbed/devel/newbold/bin/batchexp:
          NS Parse failed!
      5eb5c6ed
  13. 13 Nov, 2002 1 commit
  14. 12 Nov, 2002 1 commit
  15. 10 Nov, 2002 1 commit
  16. 08 Nov, 2002 1 commit
  17. 06 Nov, 2002 2 commits
    • Shashi Guruprasad's avatar
      NSE related changes: · 05bc3bd4
      Shashi Guruprasad authored
        - Fixes the routing problem
        - A new type "sim" has been created but not in the DB. node_types and
          nodes remain unchanged. This will change after we figure out how
          to represent in the DB the local multiple virtnodes in one phynode case
          The frontend tb_compat.tcl adds the sim type and ptopgen associates
          a huge number of sim nodes to all local PCs.
        - All simulated nodes go into one pc untill I finish coding the distributed
          nse case. Also, sim nodes go through assign but with an explicit
          "fix-node" directive in the top file. A random free pc is chosen using
          the avail script in assign_wrapper. If we don't fix node it, assign
          maps sim nodes to multiple phy nodes even when a valid all to one
          mapping is possible.
        - Syntax for nse:
      
         $ns make-simulated {
      
             set simnode1 [$ns node]
             set simnode2 [$ns node]
      
         }
         ...
      
         The old syntax
      
         set nsenode [$ns nsenode]
         $nsenode make-simulated {
         }
      
         is deprecated
      
        - All 38 frontend tests in the testsuite pass
      
        - A new table v2pmap has been added to handle multiple virt nodes to
          one phy node mapping. This is used in "tmcc hostnames" currently.
      
        - The phy node that is picked to run nse is loaded with a custom image
          FBSD45-NSE . This can use the default FBSD kernel if there is a mechanism
          to run at 1000HZ, have options IPFIREWALL_FORWARD and PERFMON turned on.
          The image is in the 'testbed' group. Do not delete this image.
      
        - Static routes now adds routes for the case dst == nexthop. The routing
          graph would be disconnected otherwise and I need to traverse this in
          assign_wrapper for nse. On the client side, such a route is filtered out in
          libsetup.pm
      
        - sim nodes are also correctly visualized
      05bc3bd4
    • Mac Newbold's avatar
      Fix duplicate vname problem. Instead of silently picking something else · a1d69682
      Mac Newbold authored
      for them, fail if they try to use the same vname for two nodes in the expt.
      a1d69682
  18. 05 Nov, 2002 1 commit
  19. 04 Nov, 2002 3 commits
  20. 01 Nov, 2002 3 commits
  21. 31 Oct, 2002 2 commits
  22. 28 Oct, 2002 4 commits
  23. 25 Oct, 2002 1 commit
  24. 24 Oct, 2002 1 commit
    • Leigh B. Stoller's avatar
      Add stuff to update the SFS keys on the fileserver after someone uses · cc1c4e54
      Leigh B. Stoller authored
      the web page to add/delete a key! Nodes were getting updated, but
      the SFS server was not cause there was no program to fire the new keys
      over there.
      
      The operation is currently simple. sfskey_update on boss constructs a
      new sfs_users file. Then it runs sfskey_update.proxy on ops (vis ssh
      of course), and gives it the new file via stdin. The proxy creates the
      .pub version from that file, and then moves the two new files into
      place in /etc/sfs. I employ the same locking stuff that Rob did in
      exports_setup and named_setup to prevent multiple updates from
      stacking up. Not likely, but might as well. Also note that the entire
      file is regenerated. When we get 5000 users this might have to change
      a little bit!
      
      Also changed mkacct slightly. Instead of doing a "sfskey register" on
      ops after generating the new key, just add it to the DB. Then fire off
      an sfskey_update to push the new keys over. Also add a -f flag to
      mkacct for use from the web page to indicate that the user has changed
      his SFS keys. Note that mkacct should probably take a series of flags
      since we have it as a wrapper for several things. Or maybe split all
      this stuff up.
      cc1c4e54
  25. 18 Oct, 2002 3 commits
    • Mac Newbold's avatar
      Small fix for perl oddity. Note to self: Do not expect... · 49003a26
      Mac Newbold authored
      Small fix for perl oddity. Note to self: Do not expect $myhash{TB_CONSTANT_SUB} to work since it evals TB_CONSTANT_SUB as a string unless you force it to be an expression (ie with parens).
      49003a26
    • Mac Newbold's avatar
    • Mac Newbold's avatar
      Merge the newstated branch with the main tree. · 5c961517
      Mac Newbold authored
      Changes to watch out for:
      
      - db calls that change boot info in nodes table are now calls to os_select
      
      - whenever you want to change a node's pxe boot info, or def or next boot
      osids or paths, use os_select.
      
      - when you need to wait for a node to reach some point in the boot process
      (like ISUP), check the state in the database using the lib calls
      
      - Proxydhcp now sends a BOOTING state for each node that it talks to.
      
      - OSs that don't send ISUP will have one generated for them by stated
      either when they ping (if they support ping) or immediately after they get
      to BOOTING.
      
      - States now have timeouts. Actions aren't currently carried out, but they
      will be soon. If you notice problems here, let me know... we're still
      tuning it. (Before all timeouts were set to "none" in the db)
      
      One temporary change:
      
      - While I make our new free node manager daemon (freed), all nodes are
      forced into reloading when they're nfreed and the calls to reset the os
      are disabled (that will move into freed).
      5c961517