1. 22 Aug, 2011 4 commits
  2. 19 Aug, 2011 5 commits
  3. 17 Aug, 2011 11 commits
  4. 16 Aug, 2011 10 commits
  5. 15 Aug, 2011 2 commits
  6. 14 Aug, 2011 1 commit
  7. 13 Aug, 2011 1 commit
  8. 12 Aug, 2011 6 commits
    • Mike Hibler's avatar
    • Leigh B Stoller's avatar
      Do not run the precheck on empty testbed, if the reason for failure is · c04c9828
      Leigh B Stoller authored
      failure to allocate nodes; obviously the top mapped.
    • Leigh B Stoller's avatar
    • Leigh B Stoller's avatar
      When generating a new ssl certificate, allow reuse of existing private · 5ccc258a
      Leigh B Stoller authored
      key so that existing delegations are not invalidated. In general this
      is fine if the key has not been compromised. User has a choice, with
      the check box.
    • Leigh B Stoller's avatar
    • Leigh B Stoller's avatar
      Lets make it easier to manage pre reservations (Mike, this was Rob's · 261c2a1a
      Leigh B Stoller authored
      New script and table to manage node pre reservations. Lets just look
      at the script.
      To create a reservation:
          myboss> wap prereserve -t pc850 testbed 2
          Node reservation request for 2 nodes has been created.
      To see the reservation status for testbed
          myboss> wap prereserve -i testbed
          Project         Cnt (Cur)  Creator    When               Pri Types
          testbed         1 (1)      stoller    2011-08-12 12:39:07 0   pc850
          which says 1 node is pending and 1 node has already been
      To clear the above reservation request (and optionally, clean
      reserved_pid from the nodes table).
          myboss> wap prereserve -c -r testbed
          The -r is optional, otherwise just the reservation request is
          cleared, and nodes continue to be pre-reserved to the project.
      To see a list of all reservation requests:
          myboss> wap prereserve -l
      So, when a node is released in nfree, we look at the reservation
      status for the node and any pending reservation requests.
      1. If the node has a reserved_pid and that request is still pending
         (still in the table), nothing is changed.
      2. If the node has a reserved_pid, but the request has been cleared
         from the pending table, then clear reserved_pid.
      3. If reserved_pid is null, and there are pending requests, then pick
         the highest priority, most recent dated, request, and set
         reserved_pid to that project.
      * -n <pri> - is how you set a priority. Lowest is zero, choose a
        higher number if you want this reservation request to be considered
        before others. In a tie, look at the date of creation, and use the
      * -t <typelist> - a comma separated list of types you want to
        consider. Types are considered in order, but not in the fancy way
        you might imagine.