1. 19 May, 2014 1 commit
  2. 16 May, 2014 1 commit
  3. 08 May, 2014 2 commits
  4. 15 Apr, 2014 2 commits
  5. 27 Mar, 2014 1 commit
  6. 26 Mar, 2014 1 commit
  7. 19 Feb, 2014 1 commit
    • Helga Velroyen's avatar
      Make hbal deal with no-LVM storage space properly · 3daaab6c
      Helga Velroyen authored
      
      
      Since 2.6, hbal crashes when used on a cluster where no
      LVM storage is enabled at all. The problem is that it
      always queries for fields that only sometimes make
      sense for certain types of storage. This patch will
      make it fall-back to a default value if those fields
      are not returned by a query. This way it will simply
      disregard the space information in its calculation
      which is the best we can do in this situation, because
      not all storage types support space reporting.
      Signed-off-by: default avatarHelga Velroyen <helgav@google.com>
      Reviewed-by: default avatarKlaus Aehlig <aehlig@google.com>
      3daaab6c
  8. 13 Feb, 2014 2 commits
  9. 10 Feb, 2014 1 commit
  10. 07 Feb, 2014 1 commit
    • Hrvoje Ribicic's avatar
      Allow classic queries to use either names or UUIDs · 13ef1fa5
      Hrvoje Ribicic authored
      
      
      When UUIDs are used in CLI commands, such addressing of objects fails
      or succeeds inconsistently across object types. Worse yet, some calls
      do not fail, but simply return no result. This is due to the way the
      classical queries are handled in the Haskell code - a filter is built,
      checking if the names match. If the names do not match, but the object
      can still be retrieved through UUID, the query is successful, but there
      is nothing to return.
      
      This patch remedies the situation by extending the filter into an or
      clause checking for either name or uuid. For objects that have no uuid
      field, the name is reused, making the filter equivalent to the old one.
      
      Works towards resolving issue 703.
      Signed-off-by: default avatarHrvoje Ribicic <riba@google.com>
      Reviewed-by: default avatarKlaus Aehlig <aehlig@google.com>
      13ef1fa5
  11. 28 Jan, 2014 1 commit
  12. 20 Jan, 2014 1 commit
  13. 16 Dec, 2013 1 commit
  14. 12 Dec, 2013 1 commit
  15. 04 Dec, 2013 2 commits
  16. 27 Nov, 2013 1 commit
  17. 26 Nov, 2013 1 commit
  18. 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
      call_hotplug_supported.
      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>
      96ed3a3e
  19. 18 Nov, 2013 1 commit
  20. 14 Nov, 2013 3 commits
  21. 08 Nov, 2013 10 commits
  22. 06 Nov, 2013 1 commit
  23. 04 Nov, 2013 2 commits
  24. 30 Oct, 2013 1 commit