Skip to content

Commit 12cdd09

Browse files
authored
Merge pull request #2387 from hpe-dev-incubator/cms/blog/why-is-redfish®-different-from-other-rest-apis-part-2
Update Blog “why-is-redfish®-different-from-other-rest-apis-part-2”
2 parents f7a69e6 + 43284bd commit 12cdd09

File tree

1 file changed

+14
-12
lines changed

1 file changed

+14
-12
lines changed

content/blog/why-is-redfish®-different-from-other-rest-apis-part-2.md

Lines changed: 14 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,9 @@ tags:
88
- ilo-restful-api
99
- Redfish
1010
---
11-
<style> li { font-size: 27px; line-height: 33px; max-width: none; } </style>
11+
<style> li { font-size: 27px; line-height: 33px; max-width: none; } </style>
12+
13+
<style> figcaption {font-size: 15px; line-height: 33px; max-width: none;} </style>
1214

1315
## Introduction
1416

@@ -30,13 +32,13 @@ To address these cases and others, Redfish offers the concept of **Actions**. Th
3032

3133
![Computer system actions](/img/fig1-descriptionactionreset.png "Computer system actions")
3234

33-
Figure 1: Computer system actions
35+
_<figcaption>Figure 1: Computer system actions</figcaption>_
3436

3537
Figure 2 shows the graceful restart action of a server with its destination (target URI) and its payload as well as the payload of the response (`Success`).
3638

3739
![System reset action](/img/fig2-resetaction.png "System reset action")
3840

39-
Figure 2: System reset action
41+
_<figcaption>Figure 2: System reset action</figcaption>_
4042

4143
The precise description of possible actions in the main body of GET responses allows Redfish clients to carry out checks to avoid sending erroneous requests, thereby avoiding the creating of unwanted network traffic.
4244

@@ -56,7 +58,7 @@ The exhaustive list of registers that can be used to subscribe to events is retu
5658

5759
![Enumeration of prefixes available for event subscriptions](/img/fig3-registryprefixes.png "Enumeration of prefixes available for event subscriptions")
5860

59-
Figure 3: Enumeration of prefixes available for event subscriptions
61+
_<figcaption>Figure 3: Enumeration of prefixes available for event subscriptions</figcaption>_
6062

6163
### How to subscribe to events?
6264

@@ -68,19 +70,19 @@ Figure 4 is an example of subscribing to events generated by storage components
6870

6971
![Event subscription](/img/fig4-eventsubscription.png "Event subscription")
7072

71-
Figure 4: Event subscription
73+
_<figcaption>Figure 4: Event subscription</figcaption>_
7274

7375
The collection of subscriptions received by the BMC can be found at the URI: `/redfish/v1/EventService/Subscriptions` (Figure 5).
7476

7577
![Subscription collection](/img/fig5-eventcollection.png "Subscription collection")
7678

77-
Figure 5: Subscription collection
79+
_<figcaption>Figure 5: Subscription collection</figcaption>_
7880

7981
The event service also allows you to easily test the subscriptions by creating a test action to `/redfish/v1/EventService/Actions/EventService.SubmitTestEvent` with, in its body, the first part of the `MessageId` property correctly populated so that the test event is sent to the correct system (Figure 6).
8082

8183
![Test event](/img/fig6-testevent.png "Test event")
8284

83-
Figure 6: Test event
85+
_<figcaption>Figure 6: Test event</figcaption>_
8486

8587
## The Telemetry service
8688

@@ -94,7 +96,7 @@ The telemetry entry point is at `/redfish/v1/TelemetryService` and has the follo
9496

9597
![ Metric report definition](/img/fig7-metricreportdefinition.png " Metric report definition")
9698

97-
Figure 7: Metric report definition
99+
_<figcaption>Figure 7: Metric report definition</figcaption>_
98100

99101
The model shown above is both powerful and extremely flexible. It allows you to:
100102

@@ -109,7 +111,7 @@ The telemetry service offers undeniable advantages and flexibility. Unfortunatel
109111

110112
![Telemetry event subscription](/img/fig8-souscriptionrapporttelemetrie.png "Telemetry event subscription")
111113

112-
Figure 8: Telemetry event subscription
114+
_<figcaption>Figure 8: Telemetry event subscription</figcaption>_
113115

114116
## Additional components integration
115117

@@ -121,7 +123,7 @@ Figure 9 explains the communication between a Redfish client and an add-on card.
121123

122124
![Offload Redfish processing to device](/img/fig9-pldm4rde.png "Offload Redfish processing to device")
123125

124-
Figure 9: Offload Redfish processing to device
126+
_<figcaption>Figure 9: Offload Redfish processing to device</figcaption>_
125127

126128
### PLDM for RDE
127129

@@ -145,7 +147,7 @@ Very quickly after the publication of the first version of Redfish in 2015, the
145147

146148
![ Link to Swordfish® URL](/img/fig10-swordfishschema.png " Link to Swordfish® URL")
147149

148-
Figure 10: Link to Swordfish URL
150+
_<figcaption>Figure 10: Link to Swordfish URL</figcaption>_
149151

150152
## Security and component integrity
151153

@@ -159,7 +161,7 @@ The operating system and BMC integrity measurements can be retrieved from the Tr
159161

160162
![SPDM configuration](/img/fig11-spdmconfiguration.png "SPDM configuration")
161163

162-
Figure 11: SPDM configuration
164+
_<figcaption>Figure 11: SPDM configuration</figcaption>_
163165

164166
## What about the future ?
165167

0 commit comments

Comments
 (0)