Statistics
| Branch: | Tag: | Revision:

root / daemons @ 3d8548c4

Name Size
ganeti-master 5.1 kB
ganeti-masterd 12.7 kB
ganeti-noded 16.8 kB
ganeti-watcher 12.4 kB

Latest revisions

# Date Author Comment
3d8548c4 07/09/2008 01:34 pm Michael Hanselmann

Make luxi RPC more flexible

- Use constants for dict entries
- Handle exceptions on server side
- Rename client function to CallMethod to match server side naming

Reviewed-by: iustinp
50a3fbb2 07/09/2008 01:34 pm Michael Hanselmann

Instantiate new job queue in master daemon

Reviewed-by: iustinp
195c7f91 07/08/2008 05:42 pm Iustin Pop

Create all SUB_RUN_DIRS in ganeti-noded

Rather than just creating BDEV_CACHE_DIR we loop through the
SUB_RUN_DIRS list and create all its childs.

Reviewed-by: iustinp
26517d45 07/04/2008 07:01 pm Iustin Pop

Fix some issues with the watcher

This patch fixes two bugs:
- the state file is not saved because we use the method for checking
for udpated data
- in two places 'Error' was used instead of 'Exception', which breaks
error handling

Additionally:...
3b316acb 07/03/2008 03:06 pm Iustin Pop

Add custom logging setup for daemons

It's better for daemons if:
- they log only to one log file
- the log level is included
- for debug runs, the filename/line number is included

This patch moves the custom formatter from the watcher to the logging...
cc2bea8b 07/02/2008 02:58 pm Michael Hanselmann

ganeti-masterd: Remove unused locking code

Reviewed-by: iustinp, ultrotter
96cb3986 07/02/2008 02:58 pm Michael Hanselmann

ganeti-masterd: Use logging module

Reviewed-by: ultrotter, iustinp
984f7c32 07/01/2008 03:28 pm Guido Trotter

Context: s/GLM/glm/

Make the GanetiLockManager instance of GanetiContext lowercase

Reviewed-by: imsnah
a478cd7e 07/01/2008 01:43 pm Guido Trotter

Increase the thread size to 5

Now that we use the locking library to make sure running opcodes cannot
step on each other toes we can have a bigger thread size, and
potentially process many opcodes in a parallel manner.

Reviewed-by: iustinp
1c901d13 07/01/2008 01:43 pm Guido Trotter

Processor: pass context in and use it.

The processor used to create a new ConfigWriter when it was initialized.
We now have one in the context, so we'll just recycle it. First of all
we'll pass the context in when creating a new Processor object, then
we'll just use context.cfg, which is granted to be initialized, wherever...

View revisions

Also available in: Atom