1. 26 Sep, 2016 2 commits
  2. 22 Sep, 2016 8 commits
  3. 21 Sep, 2016 2 commits
  4. 20 Sep, 2016 9 commits
  5. 19 Sep, 2016 3 commits
  6. 15 Sep, 2016 5 commits
  7. 14 Sep, 2016 1 commit
  8. 13 Sep, 2016 3 commits
  9. 12 Sep, 2016 7 commits
    • Mike Hibler's avatar
      Make exports_setup consistent with tmcd w.r.t. NOVIRTNFSMOUNTS. · 7ba4cfd0
      Mike Hibler authored
      Previously, we would not pass the mounts via tmcd but they were still
      exported from fs.
    • Eric Eide's avatar
      Fix typo in help text. · a78faf27
      Eric Eide authored
    • Leigh B Stoller's avatar
      Remove use of evproxy and clusterd; clustering is now built into pubsubd · 49b480c6
      Leigh B Stoller authored
      via the -c and -E/-F options:
      * On normal nodes, we used to use evproxy to capture experiment events
        on ops and forward them to the node local pubsubd (where all local
        agents connect to). Now we restart pubsubd with the -c and a -F option
        that says to subscribe to all events '(EXPT == "pid/eid")' at the
        parent pubsubd on ops (-c event-server).
      * On shared hosts, we used to start kill pubsubd and start clusterd. Now
        we restart pubsubd with just "-c event-server" which causes it to
        subscribe to all events at the parent pubsubd on ops. This is how
        clusterd did it as well.
      Another change is that instead of just kill pubsubd and starting with
      new options, we now write a pubsubd.conf file into /usr/local/etc. The
      rc.d startup files look for this file and source it as a typical .conf
      file and pass the options to pubsubd.
      I added deletion of these file to the prepare script.
    • Leigh B Stoller's avatar
      Add getserviceinfo() which asks tmcd for its subboss setup. This will · a492e5e2
      Leigh B Stoller authored
      eventually be used for pubsubd clustering using subboss, but that is
      a future commit (read: when I have time to get back to it).
    • Leigh B Stoller's avatar
      Switch time=0 program agents to newly added emulab:program-agent · bedf1a8a
      Leigh B Stoller authored
      service, which implements real progrom agents in the CM. See
      commit 760e5d43.
    • Leigh B Stoller's avatar
      Add Emulab program agent support: · 760e5d43
      Leigh B Stoller authored
          <emulab:program-agent name="prog0"
               command="/bin/ls -lt &gt;&amp; /tmp/foo"
      Much like a normal "execute" service, these are event agents instead
      of boot commands (which run on every boot of the node). When onexpstart
      is true, the command is run at event time=0 only. All program agents
      are set up to respond to tevc commands like program agents in an classic
      Emulab experiment.
    • Leigh B Stoller's avatar
      Move event start system startup to after WaitForNodes() returns. It did · 1a0da46f
      Leigh B Stoller authored
      not really matter before, but with new program agent support, we have to
      start it after nodes are "ISUP". This is going to take a little more
      work to get right, not sure if Restart() is going to work right?