Display reasons for detecting RHEL/OCP in detailed image usage view
Summary
As a Cloud Meter customer, I want to see why Cloud Meter is tracking an image for RHEL and OCP so that I can understand what was found during inspection in case I wish to challenge it.
Mockup screenshot taken on 2018-11-6 from: https://redhat.invisionapp.com/share/UFI078IZVAW#/screens/302986411
Acceptance Criteria
-
Verify that when RHEL is detected, the detailed image usage view includes the list of reasons for detection. - Each
True
reason found is shown with its human-readable explanation. -
False
not-found cases are simply not listed. - Therefore, for example, if 3 of 5 criteria are
True
, user should see three reasons, one for eachTrue
, and nothing about theFalse
ones.
- Each
-
Verify that when OCP is detected, the detailed image usage view includes the list of reasons for detection. -
Verify that when RHEL is not detected, the detailed image usage view simply states that it's not detected. -
Verify that when OCP is not detected, the detailed image usage view simply states that it's not detected. -
Verify that when viewing image details in the UI, cloud access images have a line explaining that it is from cloud access. -
Verify that when viewing image details in the UI, marketplace images have a line explaining that it is from marketplace. -
Docs changes (minimal) are in two different sections: - Data for images in the list view: https://docs.google.com/document/d/1O2vBNGkP8zRLRzdrbWb9C8RpkBDFGpmbImuipmo7HcA/edit#heading=h.fa7d1nu8aeh3
- Flagging an image: https://docs.google.com/document/d/1O2vBNGkP8zRLRzdrbWb9C8RpkBDFGpmbImuipmo7HcA/edit#heading=h.celk5eaed2co
Assumptions and Questions
- This was originally supposed to be part of #55 (closed), but comment #55 (comment 105883811) indicates that this was pulled based on discussion with UX and docs. Do we still want this detailed information? Does something need to change about its display?
- The
/api/v1/image/{id}
API returns bools to indicate the various criteria met during inspection. The front end owns the strings and verbiage for communicating this to users. - The specific phrases aren't documented here, but this is left as an exercise during development to come to a reasonable agreement for them.
- Important note for that discussion: the mockup mentions
uname
but we do not actually useuname
. That probably should say something about the "/etc/release files".
- Important note for that discussion: the mockup mentions
- We are not adding words to explicitly state the negative case. When "not detected" we just show the same text we show now. We simply don't have any bullet list type details to add.
- Because we simply skip inspection of marketplace images, we have no additional information and cannot say anything meaningful about them in the UI.
Edited by Maribeth Pierce