control:docs:events: Document modifiers

Modifiers can be used by certain actions to modify the result in a
configurable manner.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I587034ae

control:docs:events: Document modifiers

Modifiers can be used by certain actions to modify the result in a
configurable manner.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I587034ae3c6be8c5ce6c47aba35d9d1e199f0665

show more ...

control:docs:events: Add two more actions

Describe the call_actions_based_on_timer and get_managed_objects
actions.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ie159a9bc14084b9439d8

control:docs:events: Add two more actions

Describe the call_actions_based_on_timer and get_managed_objects
actions.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ie159a9bc14084b9439d8f00b54679591f6c0cd81

show more ...

control:docs:events: Add more actions

Describe the pcie_card_floors, set_request_target_base_with_max, and
set_parameter_from_group_max actions.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Cha

control:docs:events: Add more actions

Describe the pcie_card_floors, set_request_target_base_with_max, and
set_parameter_from_group_max actions.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I18f58846da516ac3ea962e5a0e5e3aa168f46d59

show more ...

control:docs:events: Add more actions

Describe the mapped_floor, set_target_on_missing_owner, and
override_fan_target actions.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ifb7fb14fb

control:docs:events: Add more actions

Describe the mapped_floor, set_target_on_missing_owner, and
override_fan_target actions.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ifb7fb14fbecd2538118282848da29377fe288e2f

show more ...

control:docs:events: Add three more actions

Describe the count_state_floor, count_state_before_target, and
default_floor_on_missing_owner actions.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
C

control:docs:events: Add three more actions

Describe the count_state_floor, count_state_before_target, and
default_floor_on_missing_owner actions.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I77be2a743391b9cbd3033970bca8449da84a395f

show more ...

control:docs:events: Start adding actions

Describe the net_target_increase and net_target_decrease actions.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I7de18b4cad79767079daef3e8a48

control:docs:events: Start adding actions

Describe the net_target_increase and net_target_decrease actions.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I7de18b4cad79767079daef3e8a48e355999a9d4e

show more ...

control:docs:events: Describe triggers

Describe the trigger entries in events.json.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I7158b72f0ebb00714fb8bf28bcda46ff2ffd2e80

control:docs:events: Describe groups

Describe the groups entries in events.json.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I6ab62748f47a3b73106639c404841cecf892a957

control:docs: Create events.md

This describes the events.json file. Only an introduction and example
is added with this commit. Further details will be added in future
commits.

Signed-off-by: Mat

control:docs: Create events.md

This describes the events.json file. Only an introduction and example
is added with this commit. Further details will be added in future
commits.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: If50579d6b26afb979933d4f085cdb21ab14235b2

show more ...

control:docs: create zones.md

This describes the zones.json file.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Id559f4989637d23b842d0a2485785128dedb1107

control:docs: Create groups.md

This describes the groups.json file.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I8cba2159dbd56b0e631dc378ccfc38a6cf9b9a6c

control:docs: Create fans.md

This describes the fans.json file.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Idd206d02d869d5eb35e4ad6b89191bef7452310c

control:docs: Fill in readme sections

Fill in missing sections. Future commits will have the details of the
component JSON files.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I8c021

control:docs: Fill in readme sections

Fill in missing sections. Future commits will have the details of the
component JSON files.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I8c021dd66c4c534b0f782302fe412b0435ac08c3

show more ...

fanctl: Add query_dump cmd to search dump contents

Add a 'query_dump' subcommand to fanctl to assist in looking at the
content of the dump file /tmp/fan_control.json generated by the 'fanctl
dump' c

fanctl: Add query_dump cmd to search dump contents

Add a 'query_dump' subcommand to fanctl to assist in looking at the
content of the dump file /tmp/fan_control.json generated by the 'fanctl
dump' command. This dump file contains the flight recorder as well as
fan control's objects, service, and parameter cache.

The command's output is in JSON.

It has the following parameters:
--section
The section of the dump: objects, parameters, or services

--name
The name of the top level JSON dictionary key to match on.
This can match on substrings, like 'sensors' for all sensors.
Optional - if not provided it matches on every name.

--properties
List of property names to match on.
Geared toward printing property values from the objects cache.
Optional, if not provided the whole JSON objects under the
name is printed.

Examples:

Print the flight recorder:
fanctl query_dump --section flight_recorder
{
"0": "Oct 29 03:41:29.468444: main: Startup"
}

Print the altitude:
fanctl query_dump -s objects -n Altitude -p Value
{
"/xyz/openbmc_project/sensors/altitude/Altitude": {
"Value": 1032.82
}
}

Print all temperatures:
fanctl query_dump -s objects -n sensors/temp -p Value
{
"/xyz/openbmc_project/sensors/temperature/Ambient_Virtual_Temp": {
"Value": 25.0
},
...
}

Print every interface and property of the ambient sensor
fanctl query_dump -s objects -n Ambient
{
... interfaces with their property names and values ...
}

Print every Value property in the cache:
fanctl query_dump -s objects -p Value
{
"/xyz/openbmc_project/sensors/altitude/Altitude": {
"Value": 1032.82
},
"/xyz/openbmc_project/sensors/temperature/Ambient_Virtual_Temp": {
"Value": 25.0
}
}

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: If66a74b432481f337f02813f2e61ae5767a57d1d

show more ...

fanctl: Added README.md

instructions and examples on how to use fanctl, links to fanctl
README.md from the control README.

Change-Id: Ib98f8c33f8be1a3e1600584dfbd38d37360fde5d
Signed-off-by: Mike C

fanctl: Added README.md

instructions and examples on how to use fanctl, links to fanctl
README.md from the control README.

Change-Id: Ib98f8c33f8be1a3e1600584dfbd38d37360fde5d
Signed-off-by: Mike Capps <mikepcapps@gmail.com>

show more ...

monitor: Tie fan FRU functional state with `set_func_on_present`

Only update the fan FRU to functional when the fan FRU has been replaced
or a poweroff->poweron has occured while `set_func_on_presen

monitor: Tie fan FRU functional state with `set_func_on_present`

Only update the fan FRU to functional when the fan FRU has been replaced
or a poweroff->poweron has occured while `set_func_on_present`
configuration is set.

Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Change-Id: I814b29c7d773a403ccf25b8edb9a196528bfb139

show more ...

docs: Update presence GPIO I2C path

Use the shorter /sys/bus/i2c/devices/ path.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I57c1f1175c855cae32d7fd63f778324450b2dc63

monitor: Support set_func_on_present

The set_func_on_present JSON field determines if the fan FRU and rotors
should be set to functional immediately when a fan plug is detected. It
is optional in t

monitor: Support set_func_on_present

The set_func_on_present JSON field determines if the fan FRU and rotors
should be set to functional immediately when a fan plug is detected. It
is optional in the JSON file, and defaults to false if not present.

When this is false, a fan will have to spin back up again before it is
set back to functional, meaning that if the new fan is faulty and never
spins up there may not be another error created. If a faulty fan is
plugged when this setting is true, then an error will be created as soon
as the configuration allows.

In some system configurations, the functional status on the fan FRU may
also control LED status, so setting the FRU to functional on the plug
would also turn off a fault LED, which is a desired behavior in the
systems that do this.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: If1a8e62a7b390e8137353a7ecc423a60df138315

show more ...

monitor: Create count timer

When the method for monitoring fan speeds is set to 'count', which is
when an up/down counter is used determine when a fan should be
considered faulted/nonfunctional, the

monitor: Create count timer

When the method for monitoring fan speeds is set to 'count', which is
when an up/down counter is used determine when a fan should be
considered faulted/nonfunctional, there needs to be some interval at
which the speeds are checked and the count is changed if necessary.
Otherwise, if the checks just happened in the tach changed callback as
they do today, then a fan with a non-changing rotor speed would never
trigger a check.

This commit creates a new timer in the Fan class that is constantly
running when the monitor is active if any of the fan's sensors use this
mode. In the expiration function, the sensors' tach targets will be
compared to their input values and the error count will be
incremented/decremented as was previously happening in the tach changed
callback.

The interval to use is read from a new 'count_interval' property in the
JSON, which defaults to 1 if not present and the count method is
enabled.

The timer is started in the startMonitor function, and stopped when a
power off is detected.

This commit also added some DEBUG journal traces when the counter on a
sensor changes values to help with debugging the new code, and so it can
be enabled on a system if desired by enabling debug level tracing.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I238606e95bb91df93afd6ec7c00bd0577bc603f2

show more ...

docs: Main README updates

Overhaul and update the main README for the package to list all
applications supported and the details of each application at their
current state. Most time was spent on up

docs: Main README updates

Overhaul and update the main README for the package to list all
applications supported and the details of each application at their
current state. Most time was spent on updating/aligning the use of JSON
based configuration since support for YAML configs has been deprecated
and will eventually be removed entirely.

Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Change-Id: Ifc8409261b2f50a77d47ffba46e41f25e3cf2c6c

show more ...

docs:monitor: Fill in the power_off_config attribute details

The `power_off_config` attribute contains a list of power off rules
based on the monitoring state of the fans configured. These power off

docs:monitor: Fill in the power_off_config attribute details

The `power_off_config` attribute contains a list of power off rules
based on the monitoring state of the fans configured. These power off
rules can perform different system power off types to protect a system
that is not able to provide enough cooling due to missing or
nonfunctional fans.

Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Change-Id: Idabaa3a2bb626d3b9048506ed23cd50fb9377f00

show more ...

docs:monitor: Fill in num_nonfunc_rotors_before_error details

The `num_nonfunc_rotors_before_error` attribute contains the number of
fan rotors (sensors) that must be nonfunctional before an error e

docs:monitor: Fill in num_nonfunc_rotors_before_error details

The `num_nonfunc_rotors_before_error` attribute contains the number of
fan rotors (sensors) that must be nonfunctional before an error event
log is created. This defaults to 1, meaning that an error event is
logged when any one of the fan rotors (sensors) being monitored is
nonfunctional.

Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Change-Id: I3294e817c14f1086657861c27c71eb6ad0546f48

show more ...

docs:monitor: Fill in trust group `group` attribute details

The `group` attribute within 'sensor_trust_groups' contains a list of
fan tach sensors to cancel/resume monitoring based on the trust
dete

docs:monitor: Fill in trust group `group` attribute details

The `group` attribute within 'sensor_trust_groups' contains a list of
fan tach sensors to cancel/resume monitoring based on the trust
determination across all members of the group.

Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Change-Id: Ifab450c05b7b8cde234d60b58eff1029ce66f5bb

show more ...

docs:monitor: Fill in trust group class attribute details

The `class` attribute within 'sensor_trust_groups' contains the trust
group determination class implementation to use in determining trust o

docs:monitor: Fill in trust group class attribute details

The `class` attribute within 'sensor_trust_groups' contains the trust
group determination class implementation to use in determining trust of
the fan sensors within the trust group.

Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Change-Id: I52721974a8af61f2bb912751a016dfcd28d824e6

show more ...

docs:monitor: Fill in sensors attribute details

The `sensors` attribute contains a list of sensor objects that make up
the fan enclosure object. The sensors are what's monitored to determine
the fun

docs:monitor: Fill in sensors attribute details

The `sensors` attribute contains a list of sensor objects that make up
the fan enclosure object. The sensors are what's monitored to determine
the functional state of the fan.

Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Change-Id: I9d673efc9ff95d638b9edf68fa0cb45b529657a9

show more ...