1. 12 Mar, 2010 10 commits
  2. 11 Mar, 2010 11 commits
  3. 10 Mar, 2010 15 commits
  4. 09 Mar, 2010 4 commits
    • Guido Trotter's avatar
      Clarify cluster nic parameters in install.rst · e721c742
      Guido Trotter authored
      
      
      There were a few outdated options specified there. This patch unifies
      the description under only one section, and updates it.
      Signed-off-by: default avatarGuido Trotter <ultrotter@google.com>
      Reviewed-by: default avatarIustin Pop <iustin@google.com>
      e721c742
    • Iustin Pop's avatar
      Add the auto_promote option to cli and gnt-node · 4c61d894
      Iustin Pop authored
      
      
      This allows one to cleanly set a node offline and promote as needed
      other nodes.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      4c61d894
    • Iustin Pop's avatar
      Rework the node modify for mc-demotion · 601908d0
      Iustin Pop authored
      
      
      The current code in LUSetNodeParms regarding the demotion from master
      candidate role is complicated and duplicates the code in ConfigWriter,
      where such decisions should be made. Furthermore, we still cannot demote
      nodes (not even with force), if other regular nodes exist.
      
      This patch adds a new opcode attribute ‘auto_promote’, and changes the
      decision tree as follows:
      
      - if the node will be set to offline or drained or explicitly demoted
        from master candidate, and this parameter is set, then we lock all
        nodes in ExpandNames()
      - later, in CheckPrereq(), if the node is
        indeed a master candidate, and the future state (as computed via
        GetMasterCandidateStats with the current node in the exception list)
        has fewer nodes than it should, and we didn't lock all nodes, we exit
        with an exception
      - in Exec, if we locked all nodes, we do a AdjustCandidatePool() run, to
        ensure nodes are locked as needed (we do it before updating the node
        to remove a warning, and prevent the situation that if the LU fails
        between these, we're not left with an inconsistent state)
      
      Note that in Exec we run the AdjustCP irrespective of any node state
      change (just based on lock status), so we might simplify the CheckPrereq
      even more by not checking the future state, basically requiring
      auto_promote/lock_all for master candidates, since the case where we
      have more than needed master candidates is rarer; OTOH, this would prevent
      manual promotion ahead of time of another node, which is why I didn't
      choose this way.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      601908d0
    • Iustin Pop's avatar
      Fix node volumes list for stripped volumes · 89e5ab02
      Iustin Pop authored
      
      
      Currently backend.NodeVolumes() drops everything except the first PV,
      thus we get a truncated result. The patch is not the nicest, as Python
      doesn't have a simple `concat' function, so I had to change the list
      comprehension to an explicit loop.
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      89e5ab02