forked from openbmc/bmcweb
-
Notifications
You must be signed in to change notification settings - Fork 0
systems.hpp - initial multi-host implementation #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
mox669
wants to merge
5
commits into
master
Choose a base branch
from
dev/multi-host-impl
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2b0ba60
to
af944a1
Compare
pointbazaar
reviewed
Feb 27, 2024
af944a1
to
ea01c9b
Compare
28045c1
to
d5b9425
Compare
d5b9425
to
d60c35a
Compare
2e50134
to
c885511
Compare
411fc52
to
54989b9
Compare
f6e954f
to
6571777
Compare
f61d23d
to
f39febd
Compare
b7badaa
to
994603c
Compare
d63b2a8
to
b1c1668
Compare
6a03e58
to
4687e93
Compare
184619e
to
66981d7
Compare
Add support for multi-host GET, POST and PATCH request handling under the /redfish/v1/Systems/{computerSystemId}/ redfish resource. The change implements the getComputerSystemIndex function which leverages the xyz.openbmc_project.ManagedHost interface to retrieve the index corresponding to the host the request was made for, when on a multi-host machine. On single-host the index always defaults to 0. It is not the perfect solution, but it is a starting point to introduce multi-host support to bmcweb, allowing for power control, via redfish and in general something we can build from. More efficient ways of doing things are already discussed, but will need more time to design properly. The implementation relies on the experimental-redfish-multi-computer-system meson flag to give bmcweb an indication, whether it is running on single- or multi-host and to drop unsupported redfish resources for the time being. All multi-host supported redfish URIs can be found in this listing: https://gerrit.openbmc.org/c/openbmc/bmcweb/+/76118 Tested: GET route has been tested with redfish service validator in qemu for the romulus and yosemite4 machine. Validator passed, no regression observed. POST route has been manually tested in web-ui on single-host hardware. All possible power controls worked as expected. For multi-host this was tested manually with curl in qemu. After requesting the expected changes have been observed on dbus. PATCH route has been requested via curl manually both on multi- and single-host for every property, that this patch implements. After each request the expected change has been observed on dbus. Change-Id: I67c17c3dd7a354fa9a2ebbc56d4def7a7e788909 Signed-off-by: Oliver Brewka <oliver.brewka@9elements.com>
Add support for multi-host to get a valid collection upon requesting /redfish/v1/Systems/{computerSystemId}/LogServices/ redfish resource. All multi-host supported redfish URIs can be found in this listing: https://gerrit.openbmc.org/c/openbmc/bmcweb/+/76118 Tested: Redfish service validation succeeded on romulus and yosemite4. In addition the route has been curled to see if the correct collection is returned. Change-Id: Ic01cdfb18e1c219bf1fc2e0343a45d8ca5d4fa0a Signed-off-by: Oliver Brewka <oliver.brewka@9elements.com>
Add support for multi-host for all GET and POST method requests under /redfish/v1/Systems/{computerSystemId}/LogServices/PostCodes/ redfish resource. Tested: Redfish-service-validation passes on single-host machine as well as on yv4 in qemu. Every postcode entry is displayed in web-ui on single-host and shown in the curl output when requested on yv4 qemu. POST has been tested on single-host hardware inside web-ui and yv4 qemu machine with curl. (Postcodes have been copied over to the qemu machine manually from a single-host machine). No regressions observed. The postcode dir for the specific host is cleared successfully on both single- and multi-host machine after the POST. Change-Id: Ie04cb160a1f2756a04be68e6675a6cecc5f09117 Signed-off-by: Oliver Brewka <oliver.brewka@9elements.com>
Add support for multi-host for all GET and POST method requests under /redfish/v1/Systems/{computerSystemId}/LogServices/HostLogger/ redfish resource. Testing: TBD Change-Id: I026be8106f2accbb77d8d40749f502f3162ad04b Signed-off-by: Oliver Brewka <oliver.brewka@9elements.com>
This change adds multi-host support in manager.hpp. Mainly returning all valid redfish links for the ManagerForServers array. In addition we opt out of calling getMainChassisId when on multi-host. Needs more clarification what exactly should be returned for that, if anything. Testing: TBD Change-Id: Ia73cabc23cd87128a59df5c7b16af0bf87462925 Signed-off-by: Oliver Brewka <oliver.brewka@9elements.com>
66981d7
to
4efbfb7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
BMCWEB multi-host imple 8000 mentation
In order to support class 1 multi-host server configurations (i.e. yosemite v3, 1 BMC, N hosts), this change enables bmcweb to gather information on multiple available hosts and handle the information accordingly.
The implementation is based on an already taken - and now abondened - effort from earlier this year as can be seen on gerrit:
The current changes are only a subset of the patches to come, to fully implement multi host support.
Reviewing
The bmcweb devs wrote a document on common errors. Since I am new to cpp, I might misunderstood or unintentionally ignored one or two of these common errors. Might be good to have a look at the document and have it ready for reviewing.
Testing
NOTE: real hardware testing hasn't been performed yet!
Changes were tested in QEMU with the romulus image by IBM. After successful compilation of bmcweb on local machine,
the resulting patch file has been appended to the yocto build system in
meta-ibm/meta-romulus/recipes-phosphor/interfaces/bmcweb
.In general, all Redfish routes touched by the change need to be tested - for both - single-host- and multi-host-configuration to ensure that we don't break the single-host configuration. This means, we have to test the implementation twice (enabling/ disabling -Dexperimental-redfish-multi-computer-system in bmcweb_%.bbappend).
In order to automate this process to some extend, the
scripts/test-all-routes.sh
curls every route for you, and stores the response in a file that you have to specify as argument to the script. Afterwards you have to compare the response to the expected output:Expected response
Expected response single host
Expected response multi host
Response of local testing in QEMU
Response single host
GET /redfish/v1/Systems
GET /redfish/v1/Systems/system
GET /redfish/v1/Systems/system0
GET /redfish/v1/Systems/system1
GET /redfish/v/fileSystems/sysem0
GET /redfish/v1/Systems/foobar
GET /redfish/v1/Systems/system/ResetActionInfo
GET /redfish/v1/Systems/system0/ResetActionInfo
GET /redfish/v1/Systems/system1/ResetActionInfo
GET /redfish/v1/Systems/sysem0/ResetActionInfo
GET /redfish/v1/Systems/foobar/ResetActionInfo
POST /redfish/v1/Systems/system/Actions/ComputerSystem.Reset
POST /redfish/v1/Systems/system0/Actions/ComputerSystem.Reset
POST /redfish/v1/Systems/system1/Actions/ComputerSystem.Reset
POST /redfish/v1/Systems/sysem0/Actions/ComputerSystem.Reset
POST /redfish/v1/Systems/foobar/Actions/ComputerSystem.Reset
Response multi host
GET /redfish/v1/SystemsGET /redfish/v1/Systems/system
GET /redfish/v1/Systems/system0
GET /redfish/v1/Systems/system1
GET /redfish/v/fileSystems/sysem0
GET /redfish/v1/Systems/foobar
GET /redfish/v1/Systems/system0/ResetActionInfo
GET /redfish/v1/Systems/system1/ResetActionInfo
GET /redfish/v1/Systems/sysem0/ResetActionInfo
GET /redfish/v1/Systems/foobar/ResetActionInfo
POST /redfish/v1/Systems/system/Actions/ComputerSystem.Reset
POST /redfish/v1/Systems/system0/Actions/ComputerSystem.Reset
POST /redfish/v1/Systems/system1/Actions/ComputerSystem.Reset
POST /redfish/v1/Systems/sysem0/Actions/ComputerSystem.Reset
POST /redfish/v1/Systems/foobar/Actions/ComputerSystem.Reset