| commit | 43a2ed12e55e23b64419cc3493ca75d180e47a16 | [log] [tgz] |
|---|---|---|
| author | Gunnar Mills <gmills@us.ibm.com> | Thu Feb 08 15:42:30 2018 -0600 |
| committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | Fri Feb 23 20:40:49 2018 +0000 |
| tree | 3b00832f27ac71e07c1fad324da9c69b488c6344 | |
| parent | e345cac548dfc846d0630d3cb43ad60d34e1d662 [diff] |
Display the "type" of event log The GUI before displayed the "Severity" of the event log in the name field. It now displays the type. Type is from the "Message" field in the event log. An example of the type is: "xyz.openbmc_project.Software.Version.Error.ManifestFileFailure". This is much more useful than the "Severity" ( e.g. "xyz.openbmc_project.Logging.Entry.Level.Error"). Severity is still displayed in the event log, above the type. Resolves openbmc/openbmc#2875 Change-Id: I10fdf90f6498f49b11a64e2c1e556b9a1c95f7b4 Tested: Running GUI locally Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
TODO: Write a project description
nodejs npm
npm install
npm run-script server
This will run it locally in http://localhost:8080.
https://<bmc-ip> and bypass the secure warning. You will see a JSON response with Login required message.http://localhost:8080. Enter the BMC IP, Username and Password (defaults: root/0penBmc).Now you are logged in.