1. 23 Oct, 2018 1 commit
    • Leigh Stoller's avatar
      New version of the portal monitor that is specific to the Mothership. · 2a5cbb2a
      Leigh Stoller authored
      This version is intended to replace the old autostatus monitor on bas,
      except for monitoring the Mothership itself. We also notify the Slack
      channel like the autostatus version. Driven from the apt_aggregates
      table in the DB, we do the following.
      
      1. fping all the boss nodes.
      
      2. fping all the ops nodes and dboxen. Aside; there are two special
         cases for now, that will eventually come from the database. 1)
         powder wireless aggregates do not have a public ops node, and 2) the
         dboxen are hardwired into a table at the top of the file.
      
      3. Check all the DNS servers. Different from autostatus (which just
         checks that port 53 is listening), we do an actual lookup at the
         server. This is done with dig @ the boss node with recursion turned
         off. At the moment this is serialized test of all the DNS servers,
         might need to change that latter. I've lowered the timeout, and if
         things are operational 99% of the time (which I expect), then this
         will be okay until we get a couple of dozen aggregates to test.
      
         Note that this test is skipped if the boss is not pingable in the
         first step, so in general this test will not be a bottleneck.
      
      4. Check all the CMs with a GetVersion() call. As with the DNS check, we
         skip this if the boss does not ping. This test *is* done in parallel
         using ParRun() since its slower and the most likely to time out when
         the CM is busy. The time out is 20 seconds. This seems to be the best
         balance between too much email and not hanging for too long on any
         one aggregate.
      
      5. Send email and slack notifications. The current loop is every 60
         seconds, and each test has to fail twice in a row before marking a
         test as a failure and sending notification. Also send a 24 hour
         update for anything that is still down.
      
      At the moment, the full set of tests takes 15 seconds on our seven
      aggregates when they are all up. Will need more tuning later, as the
      number of aggregates goes up.
      2a5cbb2a
  2. 01 Oct, 2018 1 commit
    • Leigh Stoller's avatar
      More work on the aggregate monitoring. · 9f3205c9
      Leigh Stoller authored
      1. Split the resource stuff (where we ask for an advertisement and
         process it) into a separate script, since that takes a long time to
         cycle through cause of the size of the ads from the big clusters.
      
      2. On the monitor, distinguish offline (nologins) from actually being
         down.
      
      3. Add a table to store changes in status so we can see over time how
         much time the aggregates are usable.
      9f3205c9
  3. 29 Aug, 2018 1 commit
  4. 08 Aug, 2018 1 commit
    • Leigh Stoller's avatar
      Big set of changes for deferred/scheduled/offline aggregates: · 6f17de73
      Leigh Stoller authored
      * I started out to add just deferred aggregates; those that are offline
        when starting an experiment (and marked in the apt_aggregates table as
        being deferable). When an aggregate is offline, we add an entry to the
        new apt_deferred_aggregates table, and periodically retry to start the
        missing slivers. In order to accomplish this, I split create_instance
        into two scripts, first part to create the instance in the DB, and the
        second (create_slivers) to create slivers for the instance. The daemon
        calls create_slivers for any instances in the deferred table, until
        all deferred aggregates are resolved.
      
        On the UI side, there are various changes to deal with allowing
        experiments to be partially create. For example used to wait till we
        have all the manifests until showing the topology. Now we show the
        topo on the first manifest, and then add them as they come in. Various
        parts of the UI had to change to deal with missing aggregates, I am
        sure I did not get them all.
      
      * And then once I had that, I realized that "scheduled" experiments was
        an "easy" addition, its just a degenerate case of deferred. For this I
        added some new slots to the tables to hold the scheduled start time,
        and added a started stamp so we can distinguish between the time it
        was created and the time it was actually started. Lots of data.
      
        On the UI side, there is a new fourth step on the instantiate page to
        give the user a choice of immediate or scheduled start. I moved the
        experiment duration to this step. I was originally going to add a
        calendar choice for termination, but I did not want to change the
        existing 16 hour max duration policy, yet.
      6f17de73
  5. 09 Jul, 2018 1 commit
  6. 30 Oct, 2017 1 commit
  7. 25 Oct, 2017 2 commits
  8. 12 Nov, 2016 1 commit
  9. 17 Oct, 2016 1 commit
  10. 19 May, 2016 2 commits
  11. 11 Mar, 2016 1 commit
  12. 29 Jan, 2016 2 commits
  13. 27 Jan, 2016 1 commit
  14. 16 Dec, 2015 1 commit
  15. 08 Dec, 2015 1 commit
  16. 12 Feb, 2015 1 commit
  17. 19 Aug, 2014 1 commit
  18. 25 Apr, 2014 1 commit
  19. 19 Feb, 2014 1 commit
  20. 23 Jan, 2014 1 commit
    • Mike Hibler's avatar
      Fire up the lease daemon. · 3bc4b42e
      Mike Hibler authored
      Currently it is configured (hardwired) to run every 15 minutes, even that
      may be too frequent as things don't happen too fast in lease-world.
      3bc4b42e
  21. 28 Aug, 2013 1 commit
  22. 09 Aug, 2013 1 commit
  23. 22 Jul, 2013 1 commit
  24. 26 Sep, 2012 1 commit
  25. 07 Aug, 2012 1 commit
  26. 22 Jun, 2012 1 commit
  27. 15 Mar, 2012 1 commit
  28. 07 Nov, 2011 2 commits
  29. 18 Jan, 2011 1 commit
  30. 11 Jan, 2011 1 commit
    • Mike Hibler's avatar
      More work toward getting this working on subboss. · 8d80301e
      Mike Hibler authored
      More work on the hierarchical configuration for subboss. When doing host-based
      authentication, allow client to pass an explicit host (IP) to the mserver.
      If the mserver is configured to allow it, that IP is used for authenticating
      the request instead of the caller's IP. Add a default ("null") configuration
      so the mserver can operate out-of-the-box with no config file. The goal of
      these two changes is for an mserver instance with the default config and a
      proxy option to serve the needs of a subboss node (i.e., so no explicit
      configuration will be needed).
      8d80301e
  31. 23 Jun, 2010 1 commit
  32. 18 May, 2010 1 commit
  33. 10 May, 2010 1 commit
  34. 22 Dec, 2009 1 commit
  35. 05 Aug, 2009 1 commit
  36. 26 Jan, 2009 1 commit