Andreas, thanks for that!

So far it makes sense for me.
Tthe covered use-case is really bare minimum anyway - we will definitely need to go farther.

Seems like we agreed on the classification according to [2].

I'm just contemplating positioning the page under the System >> Hardware link.
It might be difficult for newbies to find it. I am not against it - just thinking aloud.
What are the +/- of putting it as a new item in the left-side menu?

Secondly, due to expected amount of devices within single host, I still think we should filter by class.
Either via expandable lists (by class) or by filtering/sorting.

Just to know where we are heading to in follow-ups, what will be future use cases? My vision:

- additional details of a device
    - will be selected upon use-cases
- (un)bind VFIO driver
- configure SR-IOV network cards
- vGPU configuration
- USB bus
- SCSI bus

Marek


On Wed, Dec 13, 2017 at 4:25 PM, Andreas Nilsson <lists@andreasn.se> wrote:
On 2017-11-24 14:17, Andreas Nilsson wrote:
So it would become "As a sysadmin, I need to figure out the address to a
network card, so I can tweak the boot loader of the host, in order to
give a VM direct access to that device"

So I'm still a bit uncertain about the exact goal, but I put this design together, for answering the most basic case of "What devices are on my system".
https://raw.githubusercontent.com/cockpit-project/cockpit-design/2dcca8634b4b0ec5f9ff7254b29cc6578fda0fcd/devices/devices.png
It only does a straight down, simple listing of PCI devices. Let me know what you think!

- Andreas
_______________________________________________
cockpit-devel mailing list -- cockpit-devel@lists.fedorahosted.org
To unsubscribe send an email to cockpit-devel-leave@lists.fedorahosted.org



--

Marek Libra

senior software engineer

Red Hat Czech