GitLab

before using it!

help nodes in reload_pending get sucked into reloading faster. If it
doesn't do enough, we'll need to do more batching of stuff, so we get some
parallelism in os_load instead of forcing it to serialize by calling
os_load one node at a time.

I was tempted to nuke all the stuff that was in there from the netdisk
reload type, but decided not to. It won't be too long (relatively
speaking) before we have freed, the new "free node manager" that will
replace/supersede our current reload_daemon anyway.

a temporary class for testing new images.

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.

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.

Also made the image and osid shared so that it works for any emulab user
who swaps in an experiment. Before this, swapping an nse expt would have
failed but since no uses it, we never had any problem!

set the login shell to /sbin/login. Minor complications for preserving
the existing shell of users on both boss/ops, but no big deal.

simulated nodes.

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!

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!

tests completely.

  - 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

for them, fail if they try to use the same vname for two nodes in the expt.

was sending incorrect params, and os_select had a bad regexp that was
causing failures prematurely.

after assign

experiment. Also -v vname1,vname2,etc for supplying a list of vnames
instead of a prefix. Vname list must have right number of entries. If you
pick vnames that are already in use, it picks new ones for you.

Update reload_daemon with corresponding changes to those in os_load. Quick cleanup to deactivate the bitrotted netdisk stuff.

Add some logging. Some nodes are mysteriously getting set to the wrong op_modes and hopefully this will help me figure out when, how and why it is happening.

However, we have a situation in which the user gets approved in a
subgroup before the main group; this causes all kinds of headaches.

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.

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).

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).