tree cef7d7434207cffbe18f8b85c006d2edd62310cc
parent cd17b26c893ba9dd1dcb0d56d725f2892c57e125
author Gunnar Mills <gmills@us.ibm.com> 1581024597 -0600
committer Gunnar Mills <gmills@us.ibm.com> 1581102453 +0000

Move Crashdump to OemCrashdump

All other Oem Schemas start with Oem.
This is used by the update_schemas.py to determine an Oem
schema and is a reasonable requirement for Oem schemas.

https://github.com/openbmc/bmcweb/blob/a3268f98f308ca7c8660b1ace44d5b9a40be204b/scripts/update_schemas.py#L43

Tested: Ran the validator against this change on a Witherspoon
        with BMCWEB_ENABLE_REDFISH_CPU_LOG enabled and OemCheck
        true. Validator passed. Might be worth running on a
        system that actually uses BMCWEB_ENABLE_REDFISH_CPU_LOG.

curl -k https://${bmc}/redfish/v1/Systems/system/LogServices/Crashdump
{
  "@odata.context": "/redfish/v1/$metadata#LogService.LogService",
  "@odata.id": "/redfish/v1/Systems/system/LogServices/Crashdump",
  "@odata.type": "#LogService.v1_1_0.LogService",
  "Actions": {
    "#LogService.ClearLog": {
      "target": "/redfish/v1/Systems/system/LogServices/Crashdump/Actions/LogService.ClearLog"
    },
    "Oem": {
      "#Crashdump.OnDemand": {
        "target": "/redfish/v1/Systems/system/LogServices/Crashdump/Actions/Oem/Crashdump.OnDemand"
      }
    }
  },
  "Description": "Oem Crashdump Service",
  "Entries": {
    "@odata.id": "/redfish/v1/Systems/system/LogServices/Crashdump/Entries"
  },
  "Id": "Oem Crashdump",
  "MaxNumberOfRecords": 3,
  "Name": "Open BMC Oem Crashdump Service",
  "OverWritePolicy": "WrapsWhenFull"
}

Change-Id: Iacc11be1284b99c2ed9a6c2ca0a936bd97855afb
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>