On 22.11.2017 06:31, Andreas Nilsson wrote:
On 2017-10-19 11:44, Marek Libra wrote:
> Hi,
>
> I would like to renew the effort on Host Devices for Cockpit [1].
>
> To move forward, let's implement it step by step while opening brand
> new PR picking just a subset of the already implemented functionality
> [1] while adjusted to generally acceptable form.
>
> Initial implementation would meet:
> - PCI support only
> - initially read-only: just the List of devices by their Class
> (according to [2])
> - example: by Audio device, Ethernet Controller, etc
Hi, and sorry it took a while before I replied.
I agree that this is a good initial scope, and it's better to start
small and grow it as we go.
I went over a bunch of internal support tickets regarding hardware
detection. One common problem seems to be to figure if a slot is used or
not, and what network card is using what slot. I must admit I'm having
the same issue with my own wardrobe server. I literary would need to
open it and look today. I have no idea exactly how to parse the cli
commands.
So what do you think about this use case: "As a sysadmin, I want to know
if my server has the capability for another network card."
(and the more detailed version)
"John needs to spin up a new VM to host a database. He expect the
network traffic to the VM to be rather heavy, so he wants to dedicate a
network card just for this VM. Problem is that all the network cards in
the server are already in use by other VMs. He will have to buy a new
card for that, but the server is in the server room, in the basement of
the other office building, and he would rather not run over there and
open the machine to find out.
Hence he wants to check it remotely, but he's not seasoned enough with
Linux to know what CLI command to use, or how to use it."
These are good use cases. I'll imagine we'll tackle them after the
initial basic support is in? Getting the initial support for something
in, allows others to then contribute more easily.
Stef