| commit | e7f83970d3038211c9f4a4a288a3335f49c32a03 | [log] [tgz] |
|---|---|---|
| author | Gunnar Mills <gmills@us.ibm.com> | Wed Mar 21 11:03:35 2018 -0500 |
| committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | Thu Mar 29 13:44:58 2018 +0000 |
| tree | 06b595b4008af4983cd1e44c4256b60c9ffeeeee | |
| parent | f4d9bc487fa0386d0fb9dcf9131a5961d0f84b59 [diff] |
Move from "Preserve settings" to "Confirm Activation" The "Preserve settings" popup that showed when a user activated an image was not useful and did not do anything. Saving network settings prior to activation is not needed so moved to a "Confirm Activation" modal. This modal will eventually include an "activate BMC firmware and reboot" selection, openbmc/openbmc#3027, for now it only holds the one selection. The "Preserve settings" and now this "Confirm Activation" modal both appear on "server" and "BMC" images, this is a bug that is fixed in a later commit. Tested: Activated an image on a Witherspoon machine. Change-Id: I7176d5a314ea325e6e94606ef07b32786ede64e9 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.