| #
649268a5 |
| 13-Feb-2023 |
Gunnar Mills <gmills@us.ibm.com> |
power-recovery: Add Content-Type
From https://www.w3.org/Protocols/rfc2616/rfc2616-sec7.html#sec7.2.1:
Any HTTP/1.1 message containing an entity-body SHOULD include a
Content-Type header field defin
power-recovery: Add Content-Type
From https://www.w3.org/Protocols/rfc2616/rfc2616-sec7.html#sec7.2.1:
Any HTTP/1.1 message containing an entity-body SHOULD include a
Content-Type header field defining the media type of that body.
Redfish also mentions this "In HTTP messages, the media type is
specified in the Content-Type header."
bmcweb is attempting to validate content-type header,
https://gerrit.openbmc.org/c/openbmc/bmcweb/+/59941.
Change-Id: Ie020df1fd3b46ba1dad9720be5c8b384a77d7d7e
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
show more ...
|
| #
f4febd00 |
| 08-Dec-2022 |
Patrick Williams <patrick@stwcx.xyz> |
prettier: re-format
Prettier is enabled in openbmc-build-scripts on Markdown, JSON, and YAML
files to have consistent formatting for these file types. Re-run the
formatter on the whole repository.
prettier: re-format
Prettier is enabled in openbmc-build-scripts on Markdown, JSON, and YAML
files to have consistent formatting for these file types. Re-run the
formatter on the whole repository.
Change-Id: I35ec9c19ae581e4dd00b515c1bba3a9c1862eeb1
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
show more ...
|
| #
cdf04a3e |
| 01-Jun-2022 |
NodeMan97 <corey.hardesty@icloud.com> |
Proposal for chassis 'obmc-chassis-blackout@.target'
Some OpenBMC systems have services they need run after a system blackout
occurs. This design change proposes a new target to coordinate these
ser
Proposal for chassis 'obmc-chassis-blackout@.target'
Some OpenBMC systems have services they need run after a system blackout
occurs. This design change proposes a new target to coordinate these
services.
Signed-off-by: Corey Hardesty <corey.hardesty@icloud.com>
Change-Id: I7798b758a539bfae408ddf1d8422b144fcaf7a34
show more ...
|
| #
6ac6f3df |
| 28-Apr-2022 |
Patrick Williams <patrick@stwcx.xyz> |
designs: remove 'Primary Assignee'
In almost all cases this was the same individual as the author or not
filled in. Nobody seems to know what this means in the context of
OpenBMC, so we dropped it
designs: remove 'Primary Assignee'
In almost all cases this was the same individual as the author or not
filled in. Nobody seems to know what this means in the context of
OpenBMC, so we dropped it from the design template. Clean up all the
existing designs to remove them.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I01309f0b63d1e0c53fb596521595c5f39f365301
show more ...
|
| #
fd991943 |
| 11-Apr-2022 |
George Keishing <gkeishin@in.ibm.com> |
Fix typo and misspell in documentation
Change-Id: I5432c28ece0332ea99a665009547c13efe8e9dd1
Signed-off-by: George Keishing <gkeishin@in.ibm.com>
|
| #
8ec6cb41 |
| 25-Oct-2021 |
Andrew Geissler <geissonator@yahoo.com> |
power-recovery: uninterruptible power supplies
Add a section on handling a UPS and the requirements around it
Change-Id: I5ff93de04bb8b5b321686adaac318f9c03e7f8b5
Signed-off-by:
power-recovery: uninterruptible power supplies
Add a section on handling a UPS and the requirements around it
Change-Id: I5ff93de04bb8b5b321686adaac318f9c03e7f8b5
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
show more ...
|
| #
e67c779e |
| 20-Oct-2021 |
Andrew Geissler <geissonator@yahoo.com> |
power-recovery: handling of brownout conditions
A brownout condition is when a system has enough power for the BMC but
not the rest of the hardware in the chassis. This design update
power-recovery: handling of brownout conditions
A brownout condition is when a system has enough power for the BMC but
not the rest of the hardware in the chassis. This design update
addresses how the BMC firmware will handle this scenario.
Change-Id: I7173f44e3a605ef317a2165595a43cf8906d7f87
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
show more ...
|
| #
f3d60e3d |
| 13-Oct-2021 |
Andrew Geissler <geissonator@yahoo.com> |
power-recovery: bmc and system recovery paths
Provide a mechanism for the power recovery software to not run in
situations where a user has manually intervened to try and recover the
power-recovery: bmc and system recovery paths
Provide a mechanism for the power recovery software to not run in
situations where a user has manually intervened to try and recover the
system.
For example, if a system is unresponsive and a user manually resets
it in some way (for example via a pin hole reset), then do not run
the power recovery logic. This allows the user to manually work with
the system to debug and not worry about it automatically doing things
on them.
Change-Id: I3bead46df5d7ad4344d47affc066c7e36379e0db
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
show more ...
|
| #
de77feb6 |
| 12-Oct-2021 |
Andrew Geissler <geissonator@yahoo.com> |
power-recovery: auto power on feature
This commit documents what is already in place within OpenBMC with
respect to BMC support for auto power on functions. This document is
being wr
power-recovery: auto power on feature
This commit documents what is already in place within OpenBMC with
respect to BMC support for auto power on functions. This document is
being written post-mortem so that it can be built upon for proposed new
functions in this area.
Change-Id: I0d5dcbb8b4e53aac81cb714df6d863e171f41b45
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
show more ...
|