1. 26 Mar, 2014 1 commit
  2. 07 Mar, 2014 4 commits
  3. 24 Jan, 2014 1 commit
  4. 16 Dec, 2013 2 commits
  5. 12 Dec, 2013 1 commit
  6. 05 Dec, 2013 1 commit
  7. 28 Nov, 2013 1 commit
    • Jose A. Lopes's avatar
      Destroy Xen domain only if necessary · 70d8491f
      Jose A. Lopes authored
      
      
      Check if a given Xen domain still exists after a 'xm shutdown' before
      destroying it.  This check is necessary in order to cope with Xen
      domains created with other version of Ganeti, given that an instance
      created in or prior to Ganeti 2.10 will be cleaned up automatically
      and thus calling 'xm destroy' is unnecessary and will lead to an
      error, whereas instances from the more recent versions of Ganeti do
      require 'xm destroy' as it is part of the instance shutdown detection
      feature.
      Signed-off-by: default avatarJose A. Lopes <jabolopes@google.com>
      Reviewed-by: default avatarHrvoje Ribicic <riba@google.com>
      70d8491f
  8. 26 Nov, 2013 1 commit
    • Jose A. Lopes's avatar
      Add Xen paused state as a Ganeti running state · fd201010
      Jose A. Lopes authored
      
      
      The QA test 'TestClusterBurnin' pauses instances and the Xen state
      domain 'paused' was not being handled properly by Ganeti because it
      was not being classified as either a running or shutdown state.  This
      patch adds the 'paused' state to the set of running states by
      extending the function 'ganeti.hypervisor.hv_xen._IsInstanceRunning'
      with the corresponding Xen state string '--p---'.
      
      This fixes the QA test 'TestClusterBurnin'.
      Signed-off-by: default avatarJose A. Lopes <jabolopes@google.com>
      Reviewed-by: default avatarHelga Velroyen <helgav@google.com>
      fd201010
  9. 25 Nov, 2013 3 commits
  10. 14 Nov, 2013 3 commits
  11. 12 Nov, 2013 1 commit
  12. 11 Nov, 2013 1 commit
  13. 24 Oct, 2013 2 commits
  14. 02 Oct, 2013 3 commits
  15. 24 Sep, 2013 1 commit
  16. 28 Aug, 2013 1 commit
  17. 23 Aug, 2013 1 commit
  18. 06 Aug, 2013 1 commit
  19. 18 Jul, 2013 1 commit
  20. 01 Jul, 2013 1 commit
  21. 28 Jun, 2013 1 commit
    • Dimitris Aragiorgis's avatar
      Make NIC setup more flexible in case of Xen · 397b7844
      Dimitris Aragiorgis authored
      
      
      For every NIC write down a file that contains NIC's
      info (MAC, mode, link, network details), that can
      be sourced by any vif script.  The file location is:
      /var/run/ganeti/xen-hypervisor/nic/<domname>/<nicidx>.
      
      This file is created upon cfg file creation and before
      starting the instance and can be sourced by an external
      script. Before file creation ensure that all parent dirs
      exist.
      
      Cleanup NIC dir when removing config files. Upon Xen
      configuration file removal, remove NIC dir as well.
      
      Add new hv param vif_script that allows execution of
      user defined networking script and overrides the one
      xend is configured with in xend-config.sxp
      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>
      397b7844
  22. 13 Jun, 2013 2 commits
    • Thomas Thrainer's avatar
      Index nodes by their UUID · 1c3231aa
      Thomas Thrainer authored
      
      
      No longer index nodes by their name but by their UUID in the cluster
      config. This change changes large parts of the code, as the following
      adjustments were necessary:
       * Change the index key to UUID in the configuration and the
         ConfigWriter, including all methods.
       * Change all cross-references to nodes to use UUID's.
       * External interfaces (command line interface, IAllocator interface,
         hook scripts, etc.) are kept stable.
       * RPC-calls can resolve UUID's as target node arguments, if the RPC
         runner is based on a ConfigWriter instance. The result dictionary is
         presented in the form the nodes are addressed: by UUID if UUID's were
         given, or by name if names were given.
       * Node UUID's are resolved in ExpandNames and then stored in the
         OpCode. This allows to check for node renames if the OpCode is
         reloaded after a cluster restart. This check is currently only done
         for single node parameters.
       * Variable names are renamed to follow the following pattern:
         - Suffix is 'node' or 'nodes': Variable holds Node objects
         - Suffix is 'name' or 'names': Variable holds node names
         - Suffix is 'uuid' or 'uuids': Variable holds node UUID's
       * Tests are adapted.
      Signed-off-by: default avatarThomas Thrainer <thomasth@google.com>
      Reviewed-by: default avatarKlaus Aehlig <aehlig@google.com>
      1c3231aa
    • Helga Velroyen's avatar
      Add cluster name to instance migration RPC · bc0a2284
      Helga Velroyen authored
      
      
      This fixes a 'FIXME' in the xen hypervisor. The instance
      migration requires the cluster's name. This should come
      from the RPC call, but so far was hackishly taken from
      ssconf. Ssconf is intended to be used by scripts only and
      not by the backend itself.
      Signed-off-by: default avatarHelga Velroyen <helgav@google.com>
      Reviewed-by: default avatarThomas Thrainer <thomasth@google.com>
      bc0a2284
  23. 12 Jun, 2013 6 commits