1. 09 Aug, 2013 9 commits
    • Leigh B Stoller's avatar
      Pass -w option to newnode ... · 5377df38
      Leigh B Stoller authored
    • Leigh B Stoller's avatar
      Add option to use from web, to turn off script mode and revert · d7a3790c
      Leigh B Stoller authored
      to normal newnode mode.
    • Leigh B Stoller's avatar
      Also run named_setup. · ba174ea0
      Leigh B Stoller authored
    • Leigh B Stoller's avatar
      A lot of changes for use on privately purchased InstaGeni Racks. · 9019197f
      Leigh B Stoller authored
      The GPO purchased racks all look the same so we can add the new
      nodes statically from the XML file that HP sends us.
      Well, for the UEN rack and other privately purchased racks, we do not
      have any of that info, and so we have to figure things out ourselves.
      We could use the standard newnode route without modification, but that
      is a realy pain, say on a 33 node rack where the nodes land in any
      order and you have no idea what the corresponding ilo is.
      So I whacked this script to run from a data file we generate, which
      contains the two bits of info from the top of the node (ilo passwd and
      the ilo hostname), and the IPs we want to assign to the node and the
      corresponding ilo.
      So after turning all the nodes on and they checkin as usual, we run
      this script with the -r option, which looks at the dhcpd.lease file to
      find out what IP is which ILO, and the it asks each ilo via XMLRPC for
      its hosts daya, which includes the ethernet MACs. I use that to find
      the corresponding node in the leases file. Now I reorder the new_nodes
      table so that pc1 is at the bottom and pcNN is at the top.
      Now go back to the web interface and add all of the nodes.
      Then run this script again (no -r), which will create all of the
      management interfaces in the DB, reset the ilo, and then do the
      normal initilo stuff for each node (boot order, password change, ssh
      keys, etc).
      Presto, done.
    • Leigh B Stoller's avatar
      Create an ssh config file for root, for ssh to switches. · 354c2ea7
      Leigh B Stoller authored
      I figure out how to get the switches to do ssh login, so not
      you can just do "sudo ssh procurve1" instead of telnet.
    • Leigh B Stoller's avatar
      Add option to reset the ilo so that it reboots. Capture license key · b81402d7
      Leigh B Stoller authored
      from control node.
    • Leigh B Stoller's avatar
    • Leigh B Stoller's avatar
      pygrub really wants the active partition set, otherwise it · 05583576
      Leigh B Stoller authored
      fumbles around in an infinite loop.
    • Leigh B Stoller's avatar
      I added two new actions to PerformOperationalAction, which appear to · cfd1974a
      Leigh B Stoller authored
      work fine when the nodes are behaving themselves.
      1) geni_update_users: Takes a slice credential and a keys argument. Can
        only be invoked when the sliver is in the started/geni_ready state.
        Moves the slice to the geni_updating_users state until all of the
        nodes have completed the update, at which time the sliver moves back
        to started/geni_ready.
      2) geni_updating_users_cancel: We can assume that some nodes will be whacky
        and will not perform the update when told to. This cancels the
        update and moves the sliver back to started/geni_ready.
      A couple of notes:
      * The current emulab node update time is about three minutes; the
        sliver is in this new state for that time and cannot be restarted or
        stopped. It can of course be deleted.
      * Should we allow restart while in the updating phase? We could, but
        then I need more bookkeeping.
      * Some nodes might not be running the watch dog, or might not even be
        an emulab image, so the operation will never end, not until
        canceled. I could add a timeout, but that will require a monitor or
        adding DB state to store the start time.
  2. 08 Aug, 2013 2 commits
  3. 06 Aug, 2013 1 commit
  4. 31 Jul, 2013 1 commit
  5. 30 Jul, 2013 20 commits
  6. 24 Jul, 2013 6 commits
  7. 23 Jul, 2013 1 commit