1. 23 Mar, 2010 1 commit
  2. 22 Mar, 2010 1 commit
    • Leigh B Stoller's avatar
      Finish up user deletion. The big visible change is that when a user is · 2965922b
      Leigh B Stoller authored
      deleted, they still remain in the user table with a status of
      "archived", but since all the queries in the system now use uid_idx
      instead of uid, it is safe to reuse a uid since they are no longer
      The reason for not deleting users from the users table is so that the
      stats records can refer to the original record (who was that person
      named "mike"). This is very handy and worth the additional effort it
      has taken.
      There is no way to ressurect a user, but it would not be hard to add.
  3. 03 Mar, 2010 1 commit
  4. 19 Jan, 2010 1 commit
  5. 01 Dec, 2009 1 commit
  6. 30 Nov, 2009 1 commit
  7. 21 Aug, 2009 1 commit
  8. 19 Jul, 2009 1 commit
  9. 29 Jun, 2009 1 commit
  10. 25 Jun, 2009 1 commit
  11. 18 Jun, 2009 2 commits
  12. 09 Jun, 2009 3 commits
  13. 03 Jun, 2009 1 commit
    • Kevin Atkinson's avatar
      Add support for returning more detailed information in the case of a · 340f10a4
      Kevin Atkinson authored
      swap failure in the xmlrpc server.  To use it, the extra option
      "extrainfo" needs to be set to true.  This will cause "value" to be a
      structure (in the XML-RPC sence) with useful information instead of
      just the exit value of the script.  The structure will contain at
      least the following fields:
        cause: "temp", "user", etc
        mesg: more specific error information
        exitval: script return value
        log: activity log
      Note, that value may still be an integer in the case of some other
      failure that is not swap related.
      To support this, the "-X" option was added to swapexp and batchexp
      which will output a RPC-XML method response to stdout when possible.
  14. 28 May, 2009 1 commit
    • Kevin Atkinson's avatar
      Add "-N" option to batchexp/swapexp/endexp to suppress most email to · 649cd68c
      Kevin Atkinson authored
      testbed-ops and the user.  Important email that requires testbed-ops
      attention, such as on a recursive cleanup error, will still be sent.
      In addition mail normally sent to testbed-logs will still be sent.
      Also, add "noemail" option to xmlrpc server methods corresponding to
      those commands, and "-N" option to related commands in script_wrapper.
  15. 07 Jan, 2009 1 commit
  16. 15 Dec, 2008 1 commit
    • Leigh B. Stoller's avatar
      Add a second vlans function, which will eventually replace the · 0a686447
      Leigh B. Stoller authored
      original, but for now the second version is to develop my changes;
      instead of processing the arguments and sending things through on
      the command line, take the blob of xml and send it through to the
      proxy (via a file) and let it convert the xml to a data structure
      (the same data structure that the client inside the elabinelab sent).
      Much easier and less error prone.
  17. 17 Nov, 2008 1 commit
  18. 01 Oct, 2008 1 commit
  19. 15 Aug, 2008 1 commit
  20. 18 Jul, 2008 1 commit
  21. 01 Jul, 2008 1 commit
  22. 26 Jun, 2008 1 commit
  23. 06 Mar, 2008 1 commit
  24. 11 Feb, 2008 1 commit
  25. 16 Nov, 2007 1 commit
  26. 08 Oct, 2007 1 commit
  27. 25 Sep, 2007 1 commit
  28. 24 Sep, 2007 2 commits
  29. 21 Sep, 2007 1 commit
  30. 10 Sep, 2007 1 commit
  31. 07 Sep, 2007 3 commits
  32. 18 Jul, 2007 1 commit
  33. 09 Jul, 2007 1 commit
    • Leigh B. Stoller's avatar
      Checkpoint my cvs interface to the workbench. This first cut uses the · 8371fc79
      Leigh B. Stoller authored
      "rtag" directive to initiate template modify operations. So, to get started
      you do a checkout:
        cvs -d ops.emulab.net:/proj/$pid/templates/XXXXX/cvsrepo checkout XXXXX
      where XXXXX is the part of the guid (10000/1) before the slash. Might try
      and roll all templates into a single project wide repo at some point, to
      avoid the extraneous path stuff, but didn't want to worry that just yet.
      Okay, so have a checkout. You can work along the trunk, doing commits. To
      create a new template (a modify of the existing template), you tag the tree
      using rtag:
        cvs -d ops.emulab.net:/proj/$pid/templates/XXXXX/cvsrepo rtag mytag XXXXX
      A template modify is started at the end, and you should probably wait for
      email before continuing. Eventually I will need to add locking of some
      kind, but I have to do the modify in the background, or else I get deadlock
      cause cvs keeps the repo locked, and the modify also needs to access it.
      Each time you tag along the trunk, you get a modified template, which in
      the history diagram looks like:
        10000/1 --> 10000/2 --> 10000/3 ...
      If you want to branch, say at 10000/2 you can create a branch tag using rtag:
        cvs -d [cut] rtag -r T10000/2 -b mytag2 XXXXX
      You can also use your own tags for -r option, but I also create a TXXXXX/YY
      tag at each template modify, which is easy to remember.
      Then update your sandbox to the new branch, commit changes along that
      branch, and then later use rtag again to initiate a template modify
        cvs update -r mytag2
        cvs commit ...
        cvs -d [cut] rtag -r mytag2 mytag3 XXXXX
      And now the history diagram looks like:
        10000/1 --> 10000/2 --> 10000/3 ...
                      -> 10000/4 ...
      You should be able to mix interaction via the web with interaction via the
      cvs interface. I've tested it, although not extensively.
  34. 31 May, 2007 1 commit