1. 13 Feb, 2014 1 commit
  2. 07 Feb, 2014 7 commits
  3. 06 Feb, 2014 1 commit
  4. 04 Feb, 2014 1 commit
  5. 27 Jan, 2014 1 commit
  6. 16 Jan, 2014 1 commit
  7. 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>
      b3cc1646
  8. 17 Dec, 2013 1 commit
  9. 16 Dec, 2013 1 commit
  10. 29 Nov, 2013 1 commit
  11. 26 Nov, 2013 1 commit
  12. 21 Nov, 2013 2 commits
  13. 19 Nov, 2013 1 commit
  14. 29 Oct, 2013 3 commits
  15. 24 Oct, 2013 1 commit
  16. 11 Oct, 2013 1 commit
    • Helga Velroyen's avatar
      Correct properties of the cluster's file storage dir · 5ce621ab
      Helga Velroyen authored
      
      
      This patch does:
      - Rename the haskell opcode parameter
        'pGlobalFileStorageDir' and 'pGlobalSharedfileStorageDir'
        to 'pClusterFileStorageDir' and
        'pClusterSharedfileStorageDir', respectively, because
        the old name was misleading.
      - The two parameters are made optional strings instead of
        non-empty strings. This actually used to be like this
        before, but was accidentally overriden by the switch to
        opcode generation from haskell to python.
      - The ClusterFileStorageDir parameter had to be renamed in
        Haskell to not clash with the FileStorageDir parameter
        of the OpInstanceCreate code.
      Signed-off-by: default avatarHelga Velroyen <helgav@google.com>
      Reviewed-by: default avatarMichele Tartara <mtartara@google.com>
      5ce621ab
  17. 10 Sep, 2013 1 commit
    • Jose A. Lopes's avatar
      Wrap 'Set' in 'ListSet' for the opcodes · 4651c69f
      Jose A. Lopes authored
      
      
      In what Haskell to Python opcodes are concerned, a Haskell 'Set' is
      translated into a Python 'list'.  In other words, currently, opcodes
      that handle sets of parameters are actually handling lists because
      this is how sets are currently encoded.  This patch introduces a new
      type called 'ListSet' that wraps a Haskell 'Set' and it is used to
      represent on the Haskell side a Python 'list' without duplicate
      elements.  This patch also updates the respective opcode parameters
      and updates the opcode tests.
      Signed-off-by: default avatarJose A. Lopes <jabolopes@google.com>
      Reviewed-by: default avatarKlaus Aehlig <aehlig@google.com>
      4651c69f
  18. 08 Aug, 2013 1 commit
    • Jose A. Lopes's avatar
      Fix opcodes and parameters · 5cbf7832
      Jose A. Lopes authored
      
      
      * fix some return types in opcodes and some types and documentation in
        parameters.
      * fix serialization of the default value of the 'name' parameter in
        the opcodes related to tags when tag kind is 'cluster'
      * revert changes to 'pShutdownTimeout'' and its references because the
        master branch tried to fix this inconsistency but was unable to fix
        all the references to this parameter
      Signed-off-by: default avatarJose A. Lopes <jabolopes@google.com>
      Reviewed-by: default avatarThomas Thrainer <thomasth@google.com>
      5cbf7832
  19. 07 Aug, 2013 4 commits
  20. 30 Jul, 2013 1 commit
  21. 29 Jul, 2013 1 commit
  22. 24 Jul, 2013 1 commit
  23. 23 Jul, 2013 1 commit
  24. 15 Jul, 2013 1 commit
  25. 20 Jun, 2013 1 commit
    • Thomas Thrainer's avatar
      Index instances by their UUID · da4a52a3
      Thomas Thrainer authored
      
      
      No longer index instances 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.
       * External interfaces (command line interface, IAllocator interface,
         hook scripts, etc.) are kept stable.
       * Instance UUID's are resolved in ExpandNames and then stored in the
         OpCode. This allows to check for instance renames if the OpCode is
         reloaded after a cluster restart. This check is currently only done
         for single instance parameters.
       * Instance locking unfortunately can't use instances UUID as
         identifiers. The reasons is that new instances (which have no UUID
         yet) have to be locked as well, so the instance name is used.
       * Variable names are renamed to follow the following pattern:
         - Suffix is 'inst' or 'insts': Variable holds Instance objects
         - Suffix is 'name' or 'names': Variable holds Instance names
         - Suffix is 'uuid' or 'uuids': Variable holds Instance UUID's
       * Tests are adapted.
      Signed-off-by: default avatarThomas Thrainer <thomasth@google.com>
      Reviewed-by: default avatarKlaus Aehlig <aehlig@google.com>
      da4a52a3
  26. 13 Jun, 2013 1 commit
    • 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
  27. 04 Jun, 2013 1 commit
  28. 30 Apr, 2013 1 commit