1. 27 Mar, 2015 1 commit
  2. 10 Jun, 2014 1 commit
  3. 22 Apr, 2014 1 commit
  4. 24 Jan, 2014 1 commit
  5. 23 Jan, 2014 1 commit
  6. 20 Jan, 2014 1 commit
  7. 13 Jan, 2014 1 commit
  8. 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>
  9. 07 Jan, 2014 1 commit
  10. 16 Dec, 2013 1 commit
  11. 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>
  12. 18 Nov, 2013 1 commit
    • Dimitris Aragiorgis's avatar
      Allow instances to obtain externally reserved IPs · 031d2db1
      Dimitris Aragiorgis authored
      The administrator should be able to assign an externally reserved IP
      to a Ganeti instance manually, if desired. Currently this is not
      supported. External reservations should act as holes in the pool and
      not just as IPs already used by someone outside of Ganeti.
      Automatic allocation with ip=pool will continue to exclude those IPs
      as happens now.
      To allow such functionality the administrator needs to pass explicitly
      the desired IP along with the ``--no-conflicts-check`` option, or else
      an error will be produced as happens now.
      The aforementioned require the following changes:
       - Make IsReserved() to look either in reservations or external ones.
       - Make Reserve() and Release() to use IsReserved() with external
         argument True or False.
       - Pass extra option to ReserveIp() to bypass checking of external reservations
       - Update man pages and design doc for this change.
      Furthermore, a side effect of this patch is that it fixes the
      following problem:
      Currently, one could not mark an IP as external if it was already
      reserved (i.e. belonged to an instance). The code would produce a warning
      and fail silently.
      Fix config_mock.py so that if network and ip is given then reserve it in
      the pool.
      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>
  13. 30 Oct, 2013 1 commit
    • Helga Velroyen's avatar
      Remove FIXME + update man pages wrt iallocator · 708f8301
      Helga Velroyen authored
      This patch removes a FIXME regarding the retrieval
      of the disk template for computation of the cluster
      information for the iallocator. After examining the
      code, I figured out that it is actually a quite
      robust way to just check if the disk template is
      available, in particular with respect to extensions
      of the iallocator.
      In this context, I also updated the man pages of
      the operations that use the iallocator, because so
      far it was not well documented which disk template
      is considered when more than one instance was
      allocated. The situation is not ideal (the default
      disk template is used), but it is still better than
      in 2.9. where only LVM storage was considered.
      With the implementation of storage pools, it would
      make sense to extend the iallocator protocol to
      include storage information for more than one
      Signed-off-by: default avatarHelga Velroyen <helgav@google.com>
      Reviewed-by: default avatarKlaus Aehlig <aehlig@google.com>
  14. 29 Oct, 2013 1 commit
  15. 24 Oct, 2013 2 commits
  16. 02 Oct, 2013 2 commits
  17. 26 Sep, 2013 1 commit
  18. 07 Aug, 2013 1 commit
  19. 06 Aug, 2013 1 commit
  20. 30 Jul, 2013 1 commit
  21. 29 Jul, 2013 1 commit
  22. 18 Jul, 2013 1 commit
  23. 15 Jul, 2013 1 commit
  24. 03 Jul, 2013 1 commit
  25. 25 Jun, 2013 1 commit
  26. 11 Jun, 2013 1 commit
  27. 23 May, 2013 2 commits
  28. 30 Apr, 2013 1 commit
  29. 29 Apr, 2013 1 commit
  30. 17 Apr, 2013 1 commit
  31. 02 Apr, 2013 1 commit
  32. 15 Feb, 2013 2 commits
  33. 04 Feb, 2013 1 commit
  34. 31 Jan, 2013 1 commit
  35. 29 Jan, 2013 1 commit
  36. 16 Jan, 2013 1 commit