- Mar 20, 2009
-
-
Iustin Pop authored
-
Iustin Pop authored
-
Iustin Pop authored
-
Iustin Pop authored
-
Iustin Pop authored
This will enhance the ‘dist’ rule by skipping unneeded files.
-
Iustin Pop authored
The modules are moved from the ‘top’ namespace to ‘Ganeti.HTools’, in compliance with standard practices.
-
- Mar 16, 2009
-
-
Iustin Pop authored
-
- Mar 14, 2009
-
-
Iustin Pop authored
This patch moves the version string creation into a function in Utils which shows some more information.
-
Iustin Pop authored
A new man page and typos fixed in hbal.1.
-
Iustin Pop authored
-
Iustin Pop authored
This patch adds a -V, --version command line option that shows the program version and also updates the hn1 usage string (similar to hbal).
-
Iustin Pop authored
This just reorders some functions for a more logical ordering.
-
Iustin Pop authored
This patch changes the solution list to include a step counter so that it's more clear these are successive steps (in a definite order), and not just an unordered list of changes.
-
Iustin Pop authored
This patch changes the gnt-instance failover to migrate, and fixes a bug in the formatting of commands.
-
Iustin Pop authored
This patch added a verbose output and changed the output so that by default it is less verbose and more clear.
-
Iustin Pop authored
This patch adds a new instance move, FailoverAndReplace, which promotes the old secondary to primary and then uses a new secondary node. This is the last move that we can do within the limitations of one node changed per move.
-
- Mar 13, 2009
-
-
Iustin Pop authored
-
Iustin Pop authored
This patch moves the formatting of the command list to Cluster.hs and enhances it with separator messages between the steps.
-
Iustin Pop authored
This patch adds a new replace secondary and failover move (equals to “r:x f”), which can improve the solution (since we are testing more options at each step).
-
Iustin Pop authored
Aligned the comments in Instance.hs
-
Iustin Pop authored
Currently hbal does multiple rounds, stopping when a rounds doesn't bring improvements. With the recent changes to not remove instances from the candidate list, this is obsolete as the first round will always run to the end of the improvements. This patch changes this so that the Cluster.checkMove function doesn't recurse, but just computes the next best move (as its docstring says). This means we can actually incrementally compute and print the solution, and this is needed as otherwise an instance could move twice and the second time it needs the current placement to compute the exact command line and operation needed for the move.
-
Iustin Pop authored
This abstracts the individual placement solution so that it can be used independently.
-
- Mar 12, 2009
-
-
Iustin Pop authored
The current code restricts each instance to one move per round. This is bad, as an computation restarted in the middle of the solution will have a different set of instances to work and will thus lead to a different end-solution. Once this is applied, further rounds are not possible since the first round will have tried all instances at its end. As such, the removal of the rounds feature will be next. The code adds a hard-coded 100 moves limit, which for big clusters is actually small.
-
Iustin Pop authored
This prints the total memory/disk and also adds a header.
-
Iustin Pop authored
This is to keep in style with the other memory variables.
-
Iustin Pop authored
This is useful and not easy to compute otherwise.
-
Iustin Pop authored
This patch attempts to embed the VCS id in binaries, based on the way other projects seem to do this.
-
- Mar 11, 2009
-
-
Iustin Pop authored
This removes obsolete entries from the clean rule and adds the hbal binary.
-
Iustin Pop authored
Since for a very many N+1 failures in a cluster, we could actually degrade the N1 CV by making a node N+1 compliant, we need to make sure this value only decreases when fixing non-compliant nodes. The easiest way is to compute the N+1 score as a percentage of failed nodes, with the caveat that the domain of values might not be fully compatible with the other scores. It is still [0, 1] but does not vary like the others.
-
Iustin Pop authored
This patch adds two new variables to the cluster score: - variance of the failN1 attribute - variance of the reserved memory percentage The variance of the failN1 helps make the cluster N+1 happy, whereas the reserved memory percentage helps balance the unused memory for redundancy on the nodes.
-
Iustin Pop authored
This patch adds the node attribute “reserved memory percentage” that is derived from the maximum reserved memory for a node and its total memory. This will be useful for enhancing the balancing algorithm.
-
Iustin Pop authored
This patch adds a score variable to the placement type, so we can record the changes in the cluster CV for later display. This gives visibility in the decrease of the parameters and can show which are the most important steps to perform (out of the full move list).
-
Iustin Pop authored
This patch adds printing the initial and final cluster coefficients in hn1 too, to better understand the found solution.
-
- Mar 10, 2009
-
-
Iustin Pop authored
This patch removes the primary/secondary instance lists from the node status and also removes the tabbed formatting with explicit width formatting.
-
Iustin Pop authored
This patch makes the tabular solution list nicer, by changing from tabs to explicit widths.
-
Iustin Pop authored
Learned how multi-line string literals work in Haskell :)
-
- Mar 09, 2009
-
-
Iustin Pop authored
-
Iustin Pop authored
This patch automatically removes the longest common (domain, i.e. starting with a dot) suffix from the node and instance names. This gives a much clearer display, and this format is compatible with the way Ganeti accepts shortened names.
-
Iustin Pop authored
Based on the node changes, we remove the N+1 check and only show a warning instead.
-
Iustin Pop authored
Currently, we fail a new instance placement if the new node status is not N+1 compliant. This means that an allocation on an already N+1 failed node still fails, even though (conceptually) we're not worse than before. This patch changes this model to fail the allocation *only* if the node was N+1 compliant before. This allows balancing to work on non-N+1 happy clusters, with the caveat that they probably won't be N+1 happy at the end. Since we skip N+1 check in some cases, we add a new “failHealth” check that verifies the node still has strict positive free memory and disk space.
-