Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2020-10-29 | Use correct type for Dbus sensor interface in IPMI sensors YAML files | Konstantin Aladyshev | 1 | -21/+21 | |
Dbus sensor interface 'xyz.openbmc_project.Sensor.Value' migrated from int to double. Therefore all old 'int64_t' types in "*-ipmi-sensor*.yaml" files for this interface should be changed to 'double'. (From meta-ibm rev: c769f790e14b9caa4fc842dc1e2035378de6ae60) Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com> Change-Id: Id8e164203541550eb19301ca429702cbf7d4b2f8 Signed-off-by: Andrew Geissler <geissonator@yahoo.com> | |||||
2020-01-17 | meta-palmetto: Fix issues found by HW CI | Lei YU | 1 | -1/+1 | |
HW CI on Palmetto trigers two issues: 1. The case to verify occ active fails because it was using the last character of `cpux` for occ, e.g. cpu0 -> occ0. Palmetto had an incorrect inventory path of `cpu`, which results in `occu`, and it becomes an incorrect path, and the case gets a 404 error while trying to get the OCC active state. 2. The case to get https://$bmc/ fails, it's expecting HTTP 200 OK resonse, but got a 401 error. This is because webui is not built into Palmetto, so there is no page, and bmcweb returns 401 for such case. Fix the above cases. Tested: Verify the HW CI succeeds on Palmetto: python3 -m robot -v OPENBMC_HOST:palmetto --argumentfile \ test_lists/HW_CI --exclude Verify_Redfish_Host_PowerOn --include \ Verify_Redfish_Host_PowerOn_No_Check_Watts redfish tests (From meta-ibm rev: 4ac52cb28db30f89bdfd23ab1614f71b65dfdceb) Signed-off-by: Lei YU <mine260309@gmail.com> Change-Id: Ifd102f167cfa4d83769fb055b883e4c214a27b9a Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com> | |||||
2019-06-13 | meta-ibm: palmetto: new YAML config recipe | Brad Bishop | 3 | -0/+1364 | |
YAML configuration files exist scattered throughout the OpenBMC tree and how they are used is controlled with layers dependencies of virtuals and preferred providers. Most of the time the above scheme is very difficult to comprehend. This patch continues a re-thinking of that approach towards a more centralized scheme. Specifically this patch implements a single YAML config recipe for the Palmetto systems. The logic contained in the recipe was pulled from all over the OpenBMC tree - the ability to comprehend how the different YAML files are generated and consumed should be greatly eased. One notable detail - unlike the upstream recipes, palmetto-yaml-config is a target recipe and as such enables MACHINE based overrides. YAML files were copied from different locations in the tree, and run through a styling application (pyyaml dump(load(yaml))): phosphor-ipmi-fru-properties-native:extra-properties.yaml -> palmetto-yaml-config:palmetto-ipmi-fru-properties.yaml phosphor-ipmi-sensor-inventory-native:config.yaml -> palmetto-yaml-config:palmetto-ipmi-sensors.yaml phosphor-ipmi-inventory-map-native:config.yaml -> palmetto-yaml-config:palmetto-ipmi-fru.yaml (From meta-ibm rev: 70eb689af4a1b27d5cdcca1acdff8d27329c6808) Change-Id: I0f26e60db3caf66cbb2ec6d2ad0a053617eee50e Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com> |