1. 16 Jul, 2009 3 commits
  2. 15 Jul, 2009 1 commit
  3. 09 Jul, 2009 1 commit
  4. 07 Jul, 2009 1 commit
  5. 30 Jun, 2009 2 commits
  6. 28 Jun, 2009 1 commit
  7. 11 Jun, 2009 1 commit
    • Leigh B. Stoller's avatar
      Many many changes for supporting shared physical hosts on local · 4de4fcbc
      Leigh B. Stoller authored
      cluster nodes. Not going to try and describe all these changes.
      
      Note that I have not back ported this into the old assign wrapper. We
      move inexorably forward.
      
      Worth mentioning:
      
      * Users get VMs only on shared hosts.
      
      * Multiple experiments from multiple projects can share a node.
      
      * Nodes that are acting as shared hosts are in a holding experiment
        and have a tag in the reserved table. All of the links in the
        experiment are tied together in one giant super vlan. We then
        multipleax over that using our standard mechanisms (veths, vlans,
        whatever).
      
      * Lots of complication in the link setup code for dealing with links
        between a virtual node on a shared node, and a private physical
        node. Requires additional vlans and trunking between those
        interfaces. To make life easier, all of the links in the afore
        mentioned super vlan are trunked in dual mode.
      
      * I had to change Mike's code that does the encap determination, since
        openvz nodes cannot do veth encap. I add some new osfeatures
        (veth-ne, veth-en, and vlans).
      
      * On and on and on ...
      4de4fcbc
  8. 18 May, 2009 1 commit
  9. 04 May, 2009 1 commit
    • Leigh B. Stoller's avatar
      Rob and I talked about regression testing last week, and we decided · e401c0f1
      Leigh B. Stoller authored
      that depending on different versions of assign to find the exact same
      solution on the same top/ptop, is asking for trouble. And in fact, the
      new assign is slightly different and the solutions do not match.
      
      So the idea we came up with is to first run the old version, and then
      fixnode the results for the input to the new version. assign should
      run cleanly and the results will be the same. Then reverse the
      situation and run the new version, then fixnode those results for a
      run of the old version. Then compare all the results.
      e401c0f1
  10. 01 May, 2009 1 commit
  11. 22 Apr, 2009 2 commits
  12. 21 Apr, 2009 1 commit
  13. 20 Apr, 2009 2 commits
  14. 17 Apr, 2009 1 commit
    • Leigh B. Stoller's avatar
      Add a "regression" mode to both the old assign_wrapper and the new · ecb66ab5
      Leigh B. Stoller authored
      mapper wrapper. In regression mode, the wrapper/mapper proceeds
      normally, creating a .vtop file, and then running assign with a fixed
      seed. If the wrapper and the mapper agree on the .vtop file, then the
      solution from assign should be identical.
      
      The wrapper/mapper then proceeds normally, reserving resources and
      making all the DB changes. Needless to say, this has to be on a
      private copy of the database, with all nodes free. Creating that DB
      was a tale in its own right.
      
      At completion, call the existing BackupPhysicalState() function that
      we use in swapmod, and write all the physical tables we have changed
      (just the rows corresponding to the experiment of course). The delete
      all that state, and free the nodes.
      
      If everything is working correctly, those physical tables should be
      identical when created by the mapper or the wrapper.
      
      Of course, its not quite there yet. I have a few things to fix up
      before diff -r produces no results.
      ecb66ab5
  15. 16 Apr, 2009 1 commit
  16. 15 Apr, 2009 1 commit
  17. 13 Apr, 2009 1 commit
  18. 08 Apr, 2009 1 commit
  19. 06 Apr, 2009 1 commit
  20. 03 Apr, 2009 1 commit
  21. 02 Apr, 2009 1 commit
  22. 01 Apr, 2009 1 commit
  23. 24 Mar, 2009 1 commit