3. Redfish Resource Map
A Redfish service, or simply service, is a software or firmware product that implements the protocols, resources, and functions of the Redfish Specification. In many cases, a baseboard management controller (BMC) implements Redfish to provide remote management capabilities of a system.
A service implements resources in the Redfish data model at different URIs. All services support an entry point called the service root. The service root contains references to the supported top-level resource collections and services supported by the implementation. The service root is always located at the URI /redfish/v1/.
Hyperlinks in responses from the service are used to guide clients to other resources in the service. These hyperlinks are represented as @odata.id properties where the value of the property is the URI of the referenced resource.
There are many examples of these hyperlinks in this guide, such as the Redfish Service Root section that shows a sample service root with hyperlinks to the top-level resource collections and services.
Figure 1 shows a simplified resource map for managing a server.
Figure 1
In the previous diagram, there are three commonly used sets of resources for managing a server:
- Chassis (option): Represents the physical view of a container of equipment, which can be a card, a server blade, an enclosure in a rack, an entire rack, or other types of containers.
- Managers: Represents BMCs, enclosure managers, or any other components that manage the infrastructure.
- Systems: Represents the logical view of any subsystem accessible from the host CPU.
The Computer System and Manager (BMC) sections show how users can perform management operations on the previous resources.