bmcweb provides an implementation of the Redfish API. This document details the Redfish schemas supported by bmcweb. This document also discusses some of the details of that implementation and different implementations available for certain areas.
The redfish implementation shall pass the Redfish Service Validator with no warnings or errors
The following redfish schemas and fields are targeted for OpenBMC. This is a living document, and these schemas are subject to change.
The latest Redfish schemas can be found here
Fields common to all schemas
- @odata.context
- @odata.id
- @odata.type
- Id
- Name
- AccountService
- CertificateService
- Chassis
- JsonSchemas
- Managers
- RedfishVersion
- SessionService
- Systems
- UUID
- UpdateService
- Description
- ServiceEnabled
- MinpasswordLength
- MaxPasswordLength
- Accounts
- Roles
- Description
- [email protected]
- Members
- Description
- Enabled
- Password
- UserName
- RoleId
- Links/Role
- Description
- [email protected]
- Members
- By default will contain 3 roles, "Administrator", "Operator", and "ReadOnly"
- Description
- IsPredefined
- Will be set to true for all default roles. If the given role is non-default, or has been modified from default, will be marked as false.
- AssignedPrivileges
- For the default roles, the following privileges will be assigned by
default
- Administrator: Login, ConfigureManager, ConfigureUsers, ConfigureSelf, ConfigureComponents
- Operator: Login, ConfigureComponents, ConfigureSelf
- ReadOnly: Login, ConfigureSelf
- For the default roles, the following privileges will be assigned by
default
- [email protected]
- Members
- ChassisType
- Manufacturer
- Model
- SerialNumber
- PartNumber
- PowerState
- Thermal
- Shall be included if component contains temperature sensors, otherwise shall be omitted.
- Power
- Shall be included if component contains voltage/current sensing components, otherwise will be omitted.
Temperatures Fans Redundancy
- MemberId
- Status
- ReadingCelsius
- UpperThresholdNonCritical
- UpperThresholdCritical
- LowerThresholdNonCritical
- LowerThresholdCritical
- MinReadingRange
- MaxReadingRange
threshold fields only present if defined for sensor, otherwise absent
- MemberId
- Status
- Reading
- ReadingUnits
- UpperThresholdNonCritical
- UpperThresholdCritical
- LowerThresholdNonCritical
- LowerThresholdCritical
- MinReadingRange
- MaxReadingRange
- Redundancy
threshold fields only present if defined for sensor, otherwise absent
- MemberId
- RedundancySet
- Mode
- Status
- MinNumNeeded
- MaxNumSupported
PowerControl Voltages PowerSupplies Redundancy
- MemberId
- PowerConsumedWatts
- PowerMetrics/IntervalInMin
- PowerMetrics/MinConsumedWatts
- PowerMetrics/MaxConsumedWatts
- PowerMetrics/AverageConsumedWatts
- RelatedItem
- Should list systems and related chassis
- MemberId
- Status
- ReadingVolts
- UpperThresholdNonCritical
- UpperThresholdCritical
- LowerThresholdNonCritical
- LowerThresholdCritical
- MinReadingRange
- MaxReadingRange
- PhysicalContext
- RelatedItem
- MemberId
- Status
- LininputVoltage
- Model
- manufacturer
- FirmwareVersion
- SerialNumber
- PartNumber
- RelatedItem
- Redundancy
- MemberId
- RedundancySet
- Mode
- Status
- MinNumNeeded
- MaxNumSupported
- Id
- ServiceEnabled
- DeliveryRetryAttempts
- Defaults to 3
- EventTypesForSubscription
- Defaults to "Alert"
- Actions
- Subscriptions
- [email protected]
- Members
- Id
- Destination
- EventTypes
- Context
- OriginResources
- Protocol
- Members
- [email protected]
- Description
- LogServices
- GraphicalConsole
- UUID
- Model
- Links
- PowerState
- FirmwareVersion
- ManagerType
- ServiceEntryPointUUID
- DateTime
- NetworkProtocol
- Actions
- Status
- SerialConsole
- VirtualMedia
- EthernetInterfaces
- Members
- [email protected]
- Description
- Description
- VLAN
- MaxIPv6StaticAddresses
The LogService resource provides properties for monitoring and configuring events for the service or resource to which it is associated.
Within bmcweb, the LogService object resides under the System resource. It tracks all events for the system.
The LogService supports multiple log entry types. bmcweb has support for
the Event
type. This is the new Redfish-defined type.
bmcweb supports two different implementations of the
LogService/EventLog/Entries
URI.
The default implementation uses rsyslog to write Redfish events from the journal to the persistent /var/log/ filesystem. The bmcweb software then looks for these files in /var/log/ and returns the appropriate Redfish EventLog Entries for these. More details on adding events can be found here
The other implementation of EventLog Entries can be enabled by compiling bmcweb
with the -DBMCWEB_ENABLE_REDFISH_DBUS_LOG_ENTRIES=ON
option. This will cause
bmcweb to look to phosphor-logging for any D-Bus log entries. These will
then be translated to Redfish EventLog Entries.
These two implementations do not work together, so choosing one will disable the other.
- Members
- [email protected]
- Description
- Entries
- OverWritePolicy
- Actions
- Status
- DateTime
- MaxNumberOfRecords
- Message
- Created
- EntryType
- Description
- SSDP
- HTTPS
- SSH
- VirtualMedia
- KVMIP
- Status
- Members
- Should support Base, CommonMessages, and EventingMessages
- [email protected]
- Description
- Location
- Description
- [email protected]
- [email protected]
- Languages
- Registry
- Description
- ServiceEnabled
- Status
- SessionTimeout
- Sessions
- Members
- [email protected]
- Description
- Members
- Should support one system
- [email protected]
- Boot
- PartNumber
- IndicatorLED
- UUID
- LogServices
- SystemType
- Manufacturer
- Description
- Model
- Links
- PowerState
- BiosVersion
- Storage
- SerialNumber
- Processors
- ProcessorSummary
- Memory
- Actions
- Status
- EthernetInterfaces
- MemorySummary
- Members
- [email protected]
- Description
- Members
- Should default to one member, named SEL
- [email protected]
- Description
- Members
- [email protected]
- Description
- @odata.nextLink
- MessageArgs
- Severity
- SensorType
- Message
- MessageId
- Created
- EntryCode
- EntryType
- Members
- [email protected]
- MemoryType
- Description
- DeviceLocator
- Oem
- Metrics
- BaseModuleType
- Manufacturer
- MemoryDeviceType
- RankCount
- AllowedSpeedsMHz
- CapacityMiB
- DataWidthBits
- SerialNumber
- OperatingSpeedMhz
- ErrorCorrection
- PartNumber
- Status
- BusWidthBits
- MemoryMedia
- Description
- HealthData
- Members
- Should Support CPU1 and CPU2 for dual socket systems
- [email protected]
- ProcessorArchitecture
- TotalCores
- ProcessorId
- MaxSpeedMHz
- Manufacturer
- Status
- Socket
- InstructionSet
- Model
- ProcessorType
- TotalThreads
- Members
- [email protected]
- Drives
- Links
- SoftwareInventory
- Members
- Should Support BMC, ME, CPLD and BIOS
- [email protected]
- Version
- Updateable