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>
1 file changed
tree: 895d6b5903c8f3f5f31181d2ad3df9859497e7d2
  1. app/
  2. gulp_tasks/
  3. .babelrc
  4. .gitignore
  5. bower.json
  6. gulp-options.js
  7. gulpfile.js
  8. karma.conf.js
  9. LICENSE
  10. package.json
  11. postcss.config.js
  12. README.md
  13. sonar-project.properties
  14. webpack.config.js
README.md

openbmc

UX Design repo for OpenBMC

OpenBMC

TODO: Write a project description

Requirement

nodejs npm

Installation

npm install

Running

npm run-script server

This will run it locally in http://localhost:8080.

Example Usage with OpenBMC

  1. Browse to https://<bmc-ip> and bypass the secure warning. You will see a JSON response with Login required message.
  2. In the same session, navigate to http://localhost:8080. Enter the BMC IP, Username and Password (defaults: root/0penBmc).

Now you are logged in.