1. 17 Apr, 2014 3 commits
  2. 04 Apr, 2014 3 commits
  3. 27 Mar, 2014 1 commit
  4. 26 Mar, 2014 7 commits
  5. 19 Mar, 2014 5 commits
  6. 07 Mar, 2014 1 commit
    • Petr Pudlak's avatar
      Add patching QA configuration files on buildbots · b7630577
      Petr Pudlak authored
      In order to work, it is necessary:
      * Write a JSON Patch to file "qa/qa-patch.json" in a source repository.
        (And be careful not to commit it!) The file must conform to RFC6902
        and describes what changes should be done to the QA JSON
        configuration. This is simple as
         [
           { "op": "add",
             "path": "default",
             "value": false },
           { "op": "add",
             "path": "/tests/instance-add-file",
             "value": true }
         ]
      
      * Install "jsonpatch" and "jsonpointer" modules on the machines QA is
        running on. Either using "easy_install" or as Debian packages using
        "pypi-install".
      
      QA only loads the modules if the patch file is present and non-empty.
      Therefore no changes to buildbots are needed, if the feature is not
      used.
      
      It's advisable to add a git pre-commit hook for the main repository to
      prevent changes to "qa/patch.json", keeping it to "[]". Suggestion for
      such a hook:
      
        # Exit code 1 if the patch file isn't just "[]":
        python -c 'import json, sys; \
          exit(0 if json.load(open("qa/qa-patch.json", "r")) == [] else 1)'
      
      Locally it's possible to tell git not to track changes to the file at
      all (see https://help.github.com/articles/ignoring-files):
      
        git update-index --assume-unchanged qa/qa-patch.json
      
      Cherry-pick of e5398c3a
      
       from stable-2.11.
      Signed-off-by: default avatarPetr Pudlak <pudlak@google.com>
      Signed-off-by: default avatarMichele Tartara <mtartara@google.com>
      Reviewed-by: default avatarJose A. Lopes <jabolopes@google.com>
      b7630577
  7. 29 Jan, 2014 1 commit
  8. 21 Jan, 2014 2 commits
  9. 20 Jan, 2014 1 commit
  10. 16 Dec, 2013 1 commit
  11. 24 Oct, 2013 2 commits
  12. 16 Oct, 2013 1 commit
  13. 11 Oct, 2013 1 commit
  14. 09 Oct, 2013 1 commit
  15. 27 Sep, 2013 1 commit
  16. 25 Sep, 2013 4 commits
  17. 23 Sep, 2013 1 commit
    • Klaus Aehlig's avatar
      Provide PYTHONPATH to burnin · 5d9d1aff
      Klaus Aehlig authored
      
      
      One feature of the new private-module layout is that a python
      script cannot simply 'import ganeti'. The reason is that the
      interfaces to these modules are not stable and hence should not
      be used outside Ganeti. However, this is what the burnin test
      in the qa does. The good news is that we know that the burnin
      script will always be from the same version of ganeti as the
      one we're testing against; so we can simply provide the appropriate
      PYTHONPATH.
      Signed-off-by: default avatarKlaus Aehlig <aehlig@google.com>
      Reviewed-by: default avatarJose Lopes <jabolopes@google.com>
      5d9d1aff
  18. 28 Aug, 2013 2 commits
  19. 27 Aug, 2013 2 commits
    • Helga Velroyen's avatar
      CLI: actually remove the --no-drbd-storage option · 2c88200b
      Helga Velroyen authored
      
      
      This removes the '--no-drbd-storage' option completely
      from the command line interface. The hugepages design
      doc still had a left-over reference to --no-lvm-storage,
      which is removed in this patch as well.
      Signed-off-by: default avatarHelga Velroyen <helgav@google.com>
      Reviewed-by: default avatarThomas Thrainer <thomasth@google.com>
      2c88200b
    • Helga Velroyen's avatar
      cluster init/modify: set helper without DRBD being enabled · 38969795
      Helga Velroyen authored
      
      
      The logic around the DRBD usermode helper so far was that
      setting it was only possible when DRDB was not explicitely
      disabled. This patches changes it in a way that it is
      consistent to how Ganeti handles the volume group name.
      
      Now, the user can specify a DRBD usermode helper independent
      of whether or not DRBD is enabled or not. She will however
      get a warning when she sets a helper without having DRBD
      enabled. The reasoning behind this is that one might want
      to configure a helper while not yet having set up DRBD
      completely or while having DRBD disabled temporarily without
      loosing this piece of configuration.
      
      This change was done earlier in the patch series, because
      I wanted to do the refactoring in two steps, first
      just transforming the original logic from --no-drbd-storage
      to --enabled-disk-templates and if that goes well, adjust
      to the more user-friendly behavior.
      Signed-off-by: default avatarHelga Velroyen <helgav@google.com>
      Reviewed-by: default avatarThomas Thrainer <thomasth@google.com>
      38969795