1. 04 Aug, 2014 7 commits
    • Kirk Webb's avatar
      Don't look at expt state when modifying dhcpd.conf for external managment. · 055485ea
      Kirk Webb authored
      For externally managed experiments, don't consider the current state of
      the experiment.  If a node is reserved to the experiment, period, then its
      entry needs to be disabled in dhcp.  Otherwise the next time dhcp_makeconf
      runs, any already active externally managed experiments will revert to Emulab
      dhcp.
      055485ea
    • Kirk Webb's avatar
      Argh - fix typo. · 270ee757
      Kirk Webb authored
      270ee757
    • Kirk Webb's avatar
      Merge branch 'external-management' · 5b7f0a09
      Kirk Webb authored
      5b7f0a09
    • Kirk Webb's avatar
      Cache external management state for experiments in dhcpd_makeconf. · bf929ce1
      Kirk Webb authored
      Don't look it up for each and every node...
      bf929ce1
    • Kirk Webb's avatar
      Send "BOOTING" event after rebooting externally managed nodes. · bc207167
      Kirk Webb authored
      Also quiet down the EmulabFeatures library where we are using it
      to detect external management.  Too many "checking for feature ..."
      messages.
      bc207167
    • Kirk Webb's avatar
      Make disabling of dhcp for external managment look like elab-in-elab case. · b6956f3d
      Kirk Webb authored
      Leaving the node entries in the dhcpd.conf file, but setting them to
      be ignored is better.  Cuts out "no free leases" log messages and is
      less confusing for people looking through the config file.
      
      Sprinkle a few comments around in dhcpd_makeconf
      b6956f3d
    • Kirk Webb's avatar
      Add support for disabling dhcp for an experiment/user/group · ca561d42
      Kirk Webb authored
      In support of the collaboration effort with CHPC, I've added a check
      and actions for a new feature, ExternalNodeManagment.  When swapping in,
      the swapper, group, and experiment are checked for the feature.  Since
      there doesn't appear to be a way to ask for an experiment feature in the
      parser, I'm punting for now and just letting the experiment inherit this
      feature from the user and/or project/group.
      
      The effect of this feature is that nodes will be omitted from the
      dhcpd.conf file when allocated to a marked experiment, and put back
      in when freed from that experiment.
      
      We will also use this feature to force nodes to reboot even when they
      are in PXEWAIT during the OS setup phase.  Ultimately the point is for
      something else to take over the boot process and manage the experiment's
      nodes for the duration of the experiment.
      ca561d42
  2. 01 Aug, 2014 1 commit
  3. 31 Jul, 2014 18 commits
  4. 30 Jul, 2014 5 commits
  5. 29 Jul, 2014 1 commit
  6. 28 Jul, 2014 8 commits