- Oct 20, 2011
-
-
Guido Trotter authored
Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Guido Trotter authored
The rename is not needed either, since we're not adding more code as of now. This reverts commit 57ca011e. Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Guido Trotter authored
We discussed that this is not needed right now, and it breaks existing functionality and unittests. This reverts commit 6915fe26. Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Guido Trotter authored
In python 2.7 the ovf unittests fail because OVFReader expects ElementTree.parse() of an erroneous document to throw an xml.parsers.expat.ExpatError while instead it throws an ElementTree.ParseError. The solution is to "except" for both errors, with the catch that ParseError didn't exist before, so we need to define it locally and get it from the module if it exists, while leaving it set to "None" (thus catching no exception) if it does not. Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Agata Murawska <agatamurawska@google.com>
-
- Oct 18, 2011
-
-
Guido Trotter authored
* devel-2.5: Revert "rapi.client.ModifyNode should PUT rather than POST" - also fix the actual call, which was merged as PUT in master by mistake. Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Guido Trotter authored
This was a mistake on my side because ModifyGroup and ModifyInstance were PUT, and I was not aware of the discussion and the rationale why this one had to be POST. This reverts commit 55ef0cf6. Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Guido Trotter authored
* devel-2.5: Revert "Added SPICE TLS option and related cert paths" Revert "Implementation of TLS-protected SPICE connections" Revert "Updated man pages with new SPICE TLS options" Revert "Add tls_ciphers and use_vdagent options" Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Guido Trotter authored
This reverts commit bfe86c76. This commit will be readded on master. Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Guido Trotter authored
This reverts commit b6267745. This commit will be readded on master. Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Guido Trotter authored
This reverts commit b8a10435. This commit will be readded on master. Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Guido Trotter authored
This reverts commit 3e40b587. This commit will be readded on master. Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Guido Trotter authored
* devel-2.5: rapi.client.ModifyNode should PUT rather than POST Fix RAPI node modify client and server calls xen: changes to facilitate "xl" support (xen 4.1) xen: abstract instance config file naming Abstract xen's 'xm' command as a constant Fix RAPI documentation build rapi: Allow auto-promotion on node role change rapi: Add resource for modifying node opcodes: Add comment to *SetParams result description Conflicts: lib/rapi/client.py - both functions stay, remove one empty line lib/rapi/rlib2.py - convert new function to 2.6 rapi style test/ganeti.rapi.client_unittest.py - both tests stay, trivial Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Guido Trotter authored
This was caught (albeit in a sibylline manner) by unittests on master which are not present in 2.5. Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
René Nussbaumer <rn@google.com>
-
Guido Trotter authored
rapi.client.ModifyNode accepts a "group" and not a "node" param. (this bug is invisible but still not nice) rlib2.R_2_nodes_name_modify submits the opcode with instance_name rather than node_name as a param. This would break the call. Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
- Oct 17, 2011
-
-
Guido Trotter authored
- Copy the xl config file, in case there's any - Start instances by config file, not name (also xm compatible) - Start paused domains with -p and not --paused (also xm compatible) - Add a fixme for migration (changes are not xm compatible) Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Guido Trotter authored
Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Guido Trotter authored
Signed-off-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Michael Hanselmann authored
- Split code using ctypes directly into a helper class - Don't load “libc.so.6”, but use handle for main program instead (see comment in code) - Clarify comment on errno with older ctypes versions - Rename unittest since it can't be used for other functions (modifies process environment at runtime) - Add boolean return value for “Mlockall” These changes are leftovers from some experiments with ctypes. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Michael Hanselmann authored
Renaming so that more code using ctypes could be added to the same file. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
- Oct 14, 2011
-
-
Iustin Pop authored
I am currently able to run a 2-node virtual cluster on my machine, with a very ad-hoc setup. But the results show clearly that this is doable, and that given the right tools, setting up such a cluster will be quite easy. Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Guido Trotter <ultrotter@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Iustin Pop authored
This improves devnotes.rst with some tricks for Haskell development, and additionally it does two Makefile improvements: - properly document lib/_vcsversion.py as a requirement for Constants.hs (but do not require rebuild when updated) - move HEXTRA at the end of the GHC invocation, so any command line options will indeed override the built-in ones (especially -osuf) Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Iustin Pop authored
This moves the checking of results from the allocation functions to a separate function, so that we have less code duplication. It also does a bit of simplification in the printing functions. Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Iustin Pop authored
The node offline/mcpu is identical to hbal's setNodesStatus, so let's move that to CLI.hs and reuse it in hspace (also, rename it and drop one 's'). Also, the check for the number of nodes is obsolete, as we compute that from the disk template. The patch does a bit of other small cleanups. Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Iustin Pop authored
Both iterateAlloc and tieredAlloc share the same signature, but it's not documented nor exported (needed for refactoring). Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Iustin Pop authored
The logic is not entirely correct—the new Query interface exports the field status, and we don't use that yet. But the new code should be more readable. Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Guido Trotter <ultrotter@google.com>
-
Iustin Pop authored
This partially undoes commit 92678b3c, more specifically it removes the Store data type and the associated code, since all Luxi arguments are now lists. Furthermore, since the qfilter field on Query is complex (it's actually a tree structure), and we don't support it, turn it into a plain () type, which always gets encoded as JSNull ('null'), so that we can remove the optional field handling from Luxi (all fields are always required). Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
- Oct 13, 2011
-
-
Michael Hanselmann authored
*mumble* Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Michael Hanselmann authored
Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Michael Hanselmann authored
A separate patch will add “auto-promote” through “/2/nodes/[node_name]/role”. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Michael Hanselmann authored
Explicitely say that the second element of the tuple is the new value. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Michael Hanselmann authored
The “constants” module is a bit special in the sense that we don't want to export random stuff from it. This unittest checks the naming convention and removes imported modules from the module's namespace. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Michael Hanselmann authored
This patch removes all remains of the HTTP client pool. Newly added unittests provide 96% coverage on http.client. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Michael Hanselmann authored
The HTTP pool is no longer used. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
- Oct 12, 2011
-
-
Michael Hanselmann authored
* devel-2.5: rpc: Disable HTTP client pool and reduce memory consumption Preserve bridge MTU in KVM ifup script hail: Fix result for node evacuation Fix assertion error on unclean master shutdown Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Iustin Pop authored
Currently, we get a luxi Client, then parse the filter, then execute the query. If parsing the filter fails, we connected to the masterd needlessly. Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Michael Hanselmann authored
* stable-2.5: rpc: Disable HTTP client pool and reduce memory consumption hail: Fix result for node evacuation Fix assertion error on unclean master shutdown Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Iustin Pop authored
Currently, we have 4 types of arguments in LUXI calls: - most common, a list of values - a single argument that is sent as a list of one element - a single argument that is sent by itself - a dictionary (only Query and QueryFields) This inconsistency makes it not only harder to auto-generate the HTools LUXI interface, but also in general to check the arguments and (if we ever want to do it) auto-generate the Python LUXI client. Compare this with the node daemon, which uses consistently a list for its arguments, and even with way more changes over time had no issues with extending the interface. In case we want to extend a call, there are two options: - preferred: add a new call, keep the old one unchanged - possible: add further parameters to the current argument list The patch against HTools will follow—sending separately as the Python changes are very clear by themselves. Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Iustin Pop authored
We currently use 'filter' as the OpCode, QueryRequest and RAPI field name for representing a query filter. However, since 'filter' is a built-in function, we actually have to use filter_ throughout the code in order to not override the built-in function. This patch simply goes and does a global sed over the code. Due to the fact that the RAPI interface already exposed this field, we add compatibility code for now which handles both forms. Signed-off-by:
Iustin Pop <iustin@google.com> Reviewed-by:
Michael Hanselmann <hansmi@google.com>
-
Michael Hanselmann authored
* devel-2.4: rpc: Disable HTTP client pool and reduce memory consumption Fix assertion error on unclean master shutdown Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-
Michael Hanselmann authored
We noticed that “ganeti-masterd” can use large amounts of memory, especially on large clusters. Measurements showed a single PycURL client using about 500 kB of heap memory (the actual usage depends on versions, build options and settings). The RPC client uses a per-thread HTTP client pool with one client per node. At this time there are 41 non-main threads (25 for the job queue and 16 for client requests). This means the HTTP client pools use a lot of memory (ca. 200 MB for 10 nodes, ca. 1 GB for 50 nodes). This patch disables the per-thread HTTP client pool. No cleanup of unused code is done. That will be done in the master branch only. Signed-off-by:
Michael Hanselmann <hansmi@google.com> Reviewed-by:
Iustin Pop <iustin@google.com>
-