1. 14 Oct, 2016 1 commit
    • Leigh Stoller's avatar
      Attempt to address the problem described in issue #166; that nodes fail · 5d7164b3
      Leigh Stoller authored
      to go from PXEBOOTING (pxewakeup) to actually booting, but we do not
      know that for a really long time cause we send a BOOTING event from
      bootinfo right after PXEBOOTING, since that was the only place to hook
      it in. Well Mike discovered the "on commit" support in dhcpd, and so
      that is what we are going to use now. Note that uboot nodes have been
      using on commit, now all nodes will when BOOTINFO_EVENTS=0.
      
      Mike's reportboot program is now a daemon, renamed to report_daemon.
      The original reportboot program is a little script that writes the
      arguments from dhcpd to a unix socket to be picked up by the daemon,
      which does the original work of mapping the IP/Mac to a node id and
      sending an event. The code has also been modified to run on a subboss
      using the same node mapping given to to dhcpd, reconstituted as DBM
      file by subboss_dhcpd_makeconf.
      
      The reason for using a daemon this way is so that we do not hang up
      dhcpd in case we cannot get to the event system. The unix domain
      socket will give us some amount of buffering, but I suspect that any
      event problem will eat that space up quickly, and I will be back to
      revisit this (probably want reportboot to not block on its write
      to the socket).
      
      pxeboot changed to not send PXEBOOTING or BOOTING when
      BOOTINFO_EVENTS=0.
      5d7164b3
  2. 15 Apr, 2010 1 commit
    • Ryan Jackson's avatar
      Various subboss-related bits · 3d95a752
      Ryan Jackson authored
      - Add support for new tmcd dhcpdconf command to watchdog
      - Fix dhcpd.conf template so that ddns-update-style is set to none
      - Pull some utility functions from boss's libtestbed.pm into the client
        libtestbed.pm for use by subboss_dhcpd_makeconf and daemon_wrapper.
      - Add stuff to simplify getting control interface IP address.
      3d95a752
  3. 24 Feb, 2010 1 commit
    • Ryan Jackson's avatar
      Add node attribute for specifying bootinfo server · ed105035
      Ryan Jackson authored
      Add the bootinfo_server attribute for specifying the bootinfo server the
      node should use during the boot process.  If not specified the node will
      default to trying the tftp server and dhcp server, in that order.
      
      PXE vendor option 128 is used to communicate this to the NBP. Options
      128-254 are available for NBP-specific use according to the PXE spec, so
      we're safe using it.
      ed105035
  4. 16 Jul, 2007 1 commit
  5. 26 Oct, 2004 1 commit
  6. 30 Sep, 2004 1 commit
  7. 01 Apr, 2004 1 commit
  8. 13 Jan, 2004 1 commit
  9. 12 Jan, 2004 1 commit
  10. 09 Jan, 2004 1 commit
  11. 01 Apr, 2003 1 commit
  12. 27 Mar, 2003 1 commit
  13. 23 Jan, 2002 1 commit
  14. 15 Jan, 2002 1 commit