1 | Most Job Monarch releases (and their configs) should be backwards compatible with |
---|
2 | previous version. However, should there be any changes that has significant effect on the |
---|
3 | operation, tips and suggestions will be given here. |
---|
4 | |
---|
5 | 0.2 -> 0.3 |
---|
6 | ============ |
---|
7 | |
---|
8 | web) |
---|
9 | * Now supports per-cluster specific settings |
---|
10 | |
---|
11 | This enables you to override any setting of the webfrontend's conf.php on a per-cluster basis. |
---|
12 | You can also specify a different sql database per cluster this way, of specify cluster image |
---|
13 | hostname parsing (see below). |
---|
14 | |
---|
15 | You can do this by including separate conf files as follows: |
---|
16 | |
---|
17 | $CLUSTER_CONFS["My Cluster"] = "/path/to/clusterconf/mycluster.php"; |
---|
18 | |
---|
19 | * Now supports parsing hostname location for building the ClusterImage as seen on the overview |
---|
20 | |
---|
21 | This enables you to graphically display your cluster as it might be physically located in the racks |
---|
22 | or computer floor, assuming that this is part of the hostname somehow. |
---|
23 | |
---|
24 | If for example, your hosts are named: r<racknumber>n<nodenumber> |
---|
25 | |
---|
26 | You can configure the webfrontend to parse racknumber as a X coordinate and nodenumber as Y coordinate. |
---|
27 | |
---|
28 | Since your Grid/Cluster hostnames will probably be different per-cluster, you will probably only want to |
---|
29 | configure this using a cluster-specific config file, as mentioned above. |
---|
30 | |
---|
31 | Then you can create the following configuration options that will specify from which position in the hostname |
---|
32 | the X and Y coordinate will be parsed: |
---|
33 | |
---|
34 | <?php |
---|
35 | // |
---|
36 | $SORTBY_HOSTNAME = "r{x}n{y}.mydomain.tld"; |
---|
37 | $SORT_ORDER = "asc"; |
---|
38 | |
---|
39 | $SORT_XLABEL = "rack"; |
---|
40 | $SORT_YLABEL = "node"; |
---|
41 | ?> |
---|
42 | |
---|
43 | jobmond) |
---|
44 | * Now supports native Gmetric support, without the use of any external libraries or binaries. |
---|
45 | |
---|
46 | This enables jobmond to transmit it's data much faster and efficient. To make use of this, you |
---|
47 | have to set where jobmond should send it's metric's to. This is defined in jobmond.conf: |
---|
48 | |
---|
49 | # Target of Gmetric's: where should we report to |
---|
50 | # (usually: your udp_send_channel from gmond) |
---|
51 | # |
---|
52 | # Syntax: <ip>:<port> |
---|
53 | # |
---|
54 | GMETRIC_TARGET : 239.2.11.71:8649 |
---|
55 | |
---|
56 | Should you choose not to configure this, jobmond will fail back to it's old binary style submission |
---|
57 | of Gmetric's using Ganglia. |
---|
58 | |
---|
59 | * Now supports the use of syslog for errors. |
---|
60 | |
---|
61 | Should jobmond by freak accident crash, you can find in the syslog why this happened. |
---|
62 | |
---|
63 | To configure this you have to enable it in your jobmond.conf: |
---|
64 | |
---|
65 | |
---|
66 | # Enable logging to syslog? |
---|
67 | # |
---|
68 | USE_SYSLOG : 1 |
---|
69 | |
---|
70 | # What level msg'es should be logged to syslog? |
---|
71 | # |
---|
72 | # usually: lvl 0 (errors) |
---|
73 | # |
---|
74 | SYSLOG_LEVEL : 0 |
---|
75 | |
---|
76 | # Which facility to use in syslog |
---|
77 | # |
---|
78 | # Known: |
---|
79 | # KERN, USER, MAIL, DAEMON, AUTH, LPR, |
---|
80 | # NEWS, UUCP, CRON and LOCAL0 through LOCAL7 |
---|
81 | # |
---|
82 | SYSLOG_FACILITY : DAEMON |
---|
83 | |
---|
84 | jobarchived) |
---|
85 | |
---|
86 | - Now supports the py-rrdtool library, in stead of rrd pipes. |
---|
87 | |
---|
88 | This enables Jobarchived to write it's archive to disk MUCH MUCH faster and efficient than before. |
---|
89 | It's HIGHLY RECOMMENDED to do this, since this will increase performance significantly! |
---|
90 | |
---|
91 | To make use of this, simply install the 'py-rrdtool' Python module as mentioned in the README. |
---|
92 | Jobarchived will automatically detect that py-rrdtool is available and make use of it. |
---|
93 | |
---|
94 | Should you choose not to install it, Jobarchived fails back to it's old rrd pipe based writing of data. |
---|
95 | |
---|