source: trunk/UPGRADE @ 414

Last change on this file since 414 was 414, checked in by bastiaans, 13 years ago

CHANGELOG:

  • updated

UPGRADE:

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