| commit | a7bd33761aaf2bd40126a027de85a74e236d6443 | [log] [tgz] |
|---|---|---|
| author | Andrew Geissler <geissonator@yahoo.com> | Wed May 16 16:39:41 2018 -0500 |
| committer | Gunnar Mills <gmills@us.ibm.com> | Wed May 23 13:26:57 2018 +0000 |
| tree | 471118b5fddefb7ab3a8778557f98bbc4d9fae27 | |
| parent | 6bcd6cff96ec88f71b93774418949f765d77411b [diff] |
Only reboot BMC if it is BMC image activation Some internal testing found that when a server image is uploaded and activated, the BMC reboots. This is because the reboot variable defaults to true and it is not manipulated in the server image activate code path, but it shares the common activate image code path with the BMC which look at this variable to determine if it should reboot the BMC. Testing: Verified server image activate did not result in BMC rebooting. Verified when option to reboot BMC after BMC update, that BMC rebooted. Verified when option to not reboot BMC after BMC update, that BMC did not reboot. Resolves openbmc/openbmc#3188 Change-Id: Ib2f6b9cb6af27c11ad0f5c6fc33f161ac3ffa611 Signed-off-by: Andrew Geissler <geissonator@yahoo.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.