1. 24 Apr, 2014 1 commit
  2. 08 Apr, 2014 3 commits
  3. 01 Apr, 2014 1 commit
    • Michele Tartara's avatar
      Upgrade Roman numerals support · 47d2185e
      Michele Tartara authored
      Ganeti prouds itself of its really good retro-compatibility and API stability.
      Some of our users haven't upgraded their hardware in the last 2000 years (one
      century more, one century less) and their Xen-PVM (Parchment and VelluM) does
      not support Arabic numerals yet.
      The already existing support for printing data in Roman numerals had fallen into
      disrepair lately. This patch responds to the request of our most ancient users,
      quickly delivered to us via the "cursus publicus", asking for this fundamental
      functionality to be restored to its old splendour.
      Signed-off-by: default avatarMichele Tartara <mtartara@google.com>
      Reviewed-by: default avatarKlaus Aehlig <aehlig@google.com>
  4. 11 Mar, 2014 2 commits
  5. 05 Mar, 2014 2 commits
  6. 19 Feb, 2014 1 commit
  7. 14 Feb, 2014 1 commit
  8. 13 Feb, 2014 1 commit
  9. 10 Feb, 2014 3 commits
  10. 07 Feb, 2014 4 commits
  11. 06 Feb, 2014 1 commit
  12. 16 Jan, 2014 1 commit
  13. 09 Jan, 2014 1 commit
    • Michele Tartara's avatar
      Improve backwards compatibility of Issue 649 fix · 02a6b50a
      Michele Tartara authored
      Commit e6e4ff4c
       fixed Issue 649 by switching the
      separator for usb_devices from comma to space. That solved the problem with
      the command line, but RAPI was able to work with commas too, so, for backwards
      compatibility we need to keep supporting that as well.
      Also, in order to avoid changing the format of the config file, the default
      internal representation is brought back to being comma-based, and it is changed
      at the interface level (CLI or RAPI) before being passed on.
      Signed-off-by: default avatarMichele Tartara <mtartara@google.com>
      Reviewed-by: default avatarKlaus Aehlig <aehlig@google.com>
  14. 20 Dec, 2013 1 commit
    • Helga Velroyen's avatar
      Verify incoming RPCs against candidate map · b3cc1646
      Helga Velroyen authored
      From this patch on, incoming RPC calls are checked against
      the map of valid master candidate certificates. If no map
      is present, the cluster is assumed to be in
      bootstrap/upgrade mode and compares the incoming call
      against the server certificate. This is necessary, because
      neither at cluster initialization nor at upgrades from
      pre-2.11 versions a candidate map is established yet.
      After an upgrade, the cluster RPC communication continues
      to use the server certificate until the client certificates
      are created and the candidate map is populated using
      'gnt-cluster renew-crypto --new-node-certificates'.
      Note that for updating the master's certificate, a trick
      was necessary. The new certificate is first created under
      a temporary name, then it's digest is updated and
      distributed using the old certificate, because otherwise
      distribution will fail since the nodes don't know the
      new digest yet. Then the certificate is moved to its
      proper location.
      Signed-off-by: default avatarHelga Velroyen <helgav@google.com>
      Reviewed-by: default avatarHrvoje Ribicic <riba@google.com>
  15. 18 Dec, 2013 1 commit
  16. 17 Dec, 2013 2 commits
  17. 29 Nov, 2013 2 commits
  18. 28 Nov, 2013 1 commit
  19. 26 Nov, 2013 3 commits
  20. 21 Nov, 2013 1 commit
    • Dimitris Aragiorgis's avatar
      Introduce --hotplug-if-possible option · 96ed3a3e
      Dimitris Aragiorgis authored
      This will be useful for an external entity using RAPI that
      wants to modify devices of instances.
      The common use case for that is:
      "I want to add a NIC/disk to an instance. If it is running
      then try to hotplug the device. If not, then just add it to config."
      Another use case is that if we are unaware of the instance's
      hypervisor: "I want do add a NIC/disk to an instance and if
      its hypervisor is KVM try to hotplug it."
      For all those cases just print a warning in CheckPrereq() and
      disable any further hotplug related actions (and let
      modifications take place after reboot).
      Add NoHoplugSupport and HotplugIfPossible unittests an modify
      existing by explicitly creating successful RPC results for
      Signed-off-by: default avatarDimitris Aragiorgis <dimara@grnet.gr>
      Signed-off-by: default avatarThomas Thrainer <thomasth@google.com>
      Reviewed-by: default avatarThomas Thrainer <thomasth@google.com>
  21. 14 Nov, 2013 1 commit
  22. 29 Oct, 2013 2 commits
  23. 24 Oct, 2013 2 commits
  24. 17 Oct, 2013 1 commit
  25. 04 Oct, 2013 1 commit
    • Klaus Aehlig's avatar
      Provide means of submitting jobs to a drained queue · 346c3037
      Klaus Aehlig authored
      During an upgrade, the job queue needs to be drained in order to avoid
      new jobs coming to the cluster.  Nevertheless, the upgrade process
      needs to carry out some maintenance, like redistributing the new
      configuration, therefore, this patch provides a means of submitting
      jobs to a drained queue.
      Of course, once the more fine-grained job queue control will be implemented,
      this functionality can be removed.
      Signed-off-by: default avatarKlaus Aehlig <aehlig@google.com>
      Reviewed-by: default avatarJose Lopes <jabolopes@google.com>