2.1.07 Post build Configuration

Following are the instructions for configuring Sensys in a cluster. This may require root privileges depending on your installation folders.

shell$ vi /opt/open-rcm/etc/orcm-site.xml

Configure node names for aggregator, scheduler and compute nodes to be included in the Sensys cluster. Example:

<?xml version="1.0" encoding="UTF-8" ?>
<configuration>
    <version>3</version>
    <role>RECORD</role>
    <junction>
        <type>cluster</type>
        <name>cluster_name</name>
        <junction>
            <type>row</type>
            <name>row_name</name>
            <junction>
                <type>rack</type>
                <name>rack_name</name>
                <controller>
                     <host>aggregator-hostname</host>
                     <port>55805</port>
                     <aggregator>yes</aggregator>
                </controller>
                <junction>
                     <type>node</type>
                     <name>node_name</name>
                </junction>
            </junction>
        </junction>
    </junction>

    <scheduler>
        <shost>scheduler-hostname</shost>
        <port>55820</port>
    </scheduler>

    <workflows>
        <workflow name = "default_average">
            <step name = "filter">
                <data_group>coretemp</data_group>
            </step>
            <step name = "aggregate">
                <operation>average</operation>
                <db>yes</db>
            </step>
        </workflow>

        <workflow name = "default_threshold">
            <step name = "filter">
                <data_group>coretemp</data_group>
            </step>
            <step name = "threshold">
                <policy>hi|45|warning|syslog</policy>
                <db>yes</db>
            </step>
        </workflow>

        <workflow name = "default_syslog">
            <step name = "filter">
                <data_group>syslog</data_group>
            </step>
            <step name = "genex">
                <severity>crit</severity>
                <db>yes</db>
            </step>
        </workflow>
    </workflows>
</configuration>

NB: This file must be identical across all nodes of the cluster.