Age | Commit message (Collapse) | Author | Files | Lines |
|
Redfish, the final frontier. These are the voyages of bmcweb. Its
five-year mission: to explore strange new protocols, to seek out new
corner cases and new segmentation faults, to boldly go where no
web-server has gone before.
This commit marks a journey that has taken years, getting a fully
compliant, open source Redfish instance. While there is still quite a
few things to improve, Redfish Protocol Validator passing means that
bmcweb is capable of implementing all the "shall" statements in the
protocol standard that are being tested. A great thanks go out to all
the 173 unique contributors that got it to this point.
Tested: Documentation only.
Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: I786d194c602e4a424f15ddea180da939535e48e9
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I1402cbd84c916792ca2fc0ad0f34db661cbdfa72
|
|
Reformat the repository using the latest from openbmc-build-scripts.
Add the `static/redfish` directory to be ignored by prettier since
these files come from elsewhere and having the ability to do a direct
diff is handy.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I74464d6f97047b4888a591e0d8a4f5ca970ac69e
|
|
"##Abc##" is not a valid syntax. Changed to header level 2.
Signed-off-by: Nan Zhou <nanzhoumails@gmail.com>
Change-Id: I1c52540bd741a65e8fa7d72237bb43a59d120b06
|
|
bmcweb has a number of clients that it interacts with. Many times there
have been questions about what clients are available to test with, and
what the expected level of compatibility is.
This commit attempts to start documenting it. It should not be
considered complete, but aims to start documenting what the expected
level of support one could expect when running the matrix of bmcweb vs
particular clients, and, as we get more evolved, what the status is for
the CI integration of said clients tests.
Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: Ifdb34b951d366a74d7255ce41a6df12532f22b2f
|