Update policy table for latest release

This provides several updates to the policy table for the latest openbmc
code release. Updates the following:

-updated power supply inventory paths, creating new keys for existing
entries.
-New inventory paths added for GPU entries
-New alerts to call out FSI path errors, instead of previously calling
out the I2C bus
-Add alert for FSI slave detection failure
-Add alerts for missing various defined YAML errors that were previously
missed. This includes the following:
    xyz.openbmc_project.Control.Host.Error.CommandNotSupported
    xyz.openbmc_project.State.Host.Error.SoftOffTimeout
    xyz.openbmc_project.Common.File.Error.Open
    xyz.openbmc_project.Common.File.Error.Seek
    xyz.openbmc_project.Common.File.Error.Write
    xyz.openbmc_project.Common.Device.Error.ReadFailure
    xyz.openbmc_project.Common.Device.Error.WriteFailure
    xyz.openbmc_project.Common.Callout.Error.Device
    xyz.openbmc_project.Common.Callout.Error.GPIO
    xyz.openbmc_project.Common.Callout.Error.IIC
    xyz.openbmc_project.Common.Callout.Error.Inventory
    xyz.openbmc_project.Common.Callout.Error.IPMISensor
    xyz.openbmc_project.Sensor.Threshold.Error.CriticalLow
    xyz.openbmc_project.Led.Mapper.Error.MethodError
    xyz.openbmc_project.Led.Mapper.Error.ObjectNotFoundError
    org.open_power.Host.Access.Error.WriteCFAM
    org.open_power.Host.Access.Error.ReadCFAM
    org.open_power.Proc.FSI.Error.SlaveDetectionFailure
    org.open_power.OCC.Device.Error.OpenFailure
    org.open_power.OCC.Device.Error.ReadFailure
    org.open_power.OCC.Device.Error.WriteFailure
    org.open_power.OCC.Device.Error.ConfigFailure
    org.open_power.OCC.Metrics.Error.Event
    org.open_power.Common.Callout.Error.Procedure
1 file changed
tree: 4c3958493d6da1afb2e2209aebbd8e79e2b46f8a
  1. amboar/
  2. emilyshaffer/
  3. geissonator/
  4. infra/
  5. leiyu/
  6. post-process/
  7. thalerj/
  8. LICENSE
  9. README.md
README.md

The OpenBMC Tools Collection

The goal of this repository is to collect the two-minute hacks you write to automate interactions with OpenBMC systems.

It's highly likely the scripts don't meet your needs - they could be undocumented, dysfunctional, utterly broken, or sometimes casually rm -rf ~. Don't even think about looking for tests.

Repository Rules

  • Always inspect what you will be executing
  • Some hacking on your part is to be expected

You have been warned.

If you're still with us

Then this repository aims to be the default destination for your otherwise un-homed scripts. As such we are setting the bar for submission pretty low, and we aim to make the process as easy as possible:

Sending patches

However you want to send patches, we will probably cope:

What we will do once we have your patches

Look, the rm -rf ~ thing was a joke, we will be keeping an eye on all of you for such shenanigans. But so long as your patches look sane with a cursory glance you can expect them to be applied. To be honest, even Perl will be considered moderately sane.

What you must have in your patches

We don't ask for much, but you need to give us at least a Signed-off-by, and put your work under the Apache 2.0 license. Licensing everything under Apache 2.0 will just hurt our heads less. Lets keep the lawyers off our backs. ^

^ Any exceptions must be accompanied by a LICENSE file in the relevant subdirectory, and be compatible with Apache 2.0. You thought you would get away without any fine print?

How you consume the repository

Probably with difficulty. Don't expect the layout to remain static, or scripts to continue to exist from one commit to the next.