Hide Forgot
+++ This bug was initially created as a clone of Bug #1404319 +++ Description of problem: Fetch "lstopo" PNG image per hardware node (from swift), and display it to the UI user for him to learn the NUMA topology (core count, PCI IDs, NUMA alignment). This is required for advanced Ceph, HCI and NFV deployments. The admin mus be 100% sure of the PCI IDs and the Numa node number, CPU core count, etc, before writing the installation YAML parameters. This should be displayed in the NODES tab of the Director UI, as a clickable option to see the autodiscovered hardware layout, only available after the node has been Introspected (maybe the button is added next to the "introspect nodes" button) Once the button is clicked, for only one node at a time, the UI will download from swift the PNG (see Bug #1404319 for the precise location/name) and display the image to the user, either as a pop-up/dropdown or as a download action. Example: https://www.open-mpi.org/projects/hwloc/lstopo/images/2XeonE5v3.v1.11.png
The graphical representation of the NUMA info collected in the introspection JSON (as defined in https://bugzilla.redhat.com/show_bug.cgi?id=1384848), which is stored in Swift, will have to be dealt in a very different manner than showing a PNG image. We'll followup with Anandeep and the UI team as the flow will require fetching info from Mistral (according to the devs) and of course Swift (for the actual JSON download), then rendering the JSON in the UI in a manner than a person can read the information they require. Quite different flow than fetching a PNG So let's close this RFE and wait until OSP11 gets NUMA info in the JSON, then by OSP12 we can expect to display that info in the UI