summaryrefslogtreecommitdiffstats
path: root/control/example/zones.yaml
blob: 5f3b549b48d71a249db7f54518bd595566d09308 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
#Example fan zone definitions for phosphor-fan-control

#List the properties of the fan zones that are possible in the system.
#The zones may be conditional based on certain conditions, such as
#different chassis types or water cooled models.  The fans themselves
#are not listed in this file.  They are in a separate YAML file so it
#can be machine generated (i.e. from the MRW) if desired.

#The general structure is a list of groups of zones, where a group
#contains both the zones and the conditions required for the zones
#to be valid

#The cooling_profile is used along with the zone number to know
#which fans in the fan yaml belong in this zone instance.  For
#example, a fan may only be in zone 0 if it's the air cooled version
#of the system, but not with the water cooled version.  In that
#case, the fan yaml would have a cooling_profile of 'air' to match
#the zone cooling profile.

#- zone_conditions:
#   - name: [Name of a condition, if any.  Valid names are TBD]
#
#  zones:
#    - zone: [zone number]
#      cooling_profiles:
#        - [cooling profile]
#      initial_speed: [Speed to set the zone to when app starts]

#Example:
#- zone_conditions:
#  - name: air_cooled_chassis
#
#  zones:
#    - zone: 0
#      cooling_profiles:
#      - air
#      - all
#      initial_speed: 10500
#
#- zone_conditions:
#  - name: water_and_air_cooled_chassis
#
#  zones:
#    - zone: 0
#      cooling_profiles:
#      - water
#      - all
#      initial_speed: 4000

OpenPOWER on IntegriCloud