commit | e41f0b0bf50c026844c313a63e267c0d3bdafc14 | [log] [tgz] |
---|---|---|
author | Gunnar Mills <gmills@us.ibm.com> | Fri Mar 02 12:16:35 2018 -0600 |
committer | Gunnar Mills <gmills@us.ibm.com> | Mon Mar 05 11:49:46 2018 -0600 |
tree | 895d6b5903c8f3f5f31181d2ad3df9859497e7d2 | |
parent | 607a120a7191c6a8122e747ebcc60c6eae890d85 [diff] |
Remove "Ready" image boot priority arrows Ready images do not have a priority. Priority is for "Active" images to determine which image to boot from. Only images on the GUI that are "Active" or "Functional" (on the GUI we call "Active" images that have the functional association "Functional") should have a Boot Priority. Tested: Verified no priority on Ready images. Change-Id: I5a527ed4bed9d686a746e3759f50fa9bb8b7988a 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.