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
- data source: sysfs
- make use of backward-compatible lspci for data preprocessing (especially
manipulation with HW database)
- monitor for changes by listening kernel uevents
Follow-ups will lead to [3] scope:
- for pci, active actions are allowed for selected device classes, one PR
per each:
- (un)bind VFIO driver
- configure SR-IOV network cards
- vGPU configuration
- additional view by Driver
- What devices is the driver bound to?
- additional view by IOMMU Groups
- For server fine-tuning, what devices are within single IOMMU Group?
- support for other buses, i.e. USB or SCSI
- their views are independent on each other due to fundamental differences
Please let me know your thoughts.
Thanks,
Marek
[1] https://github.com/cockpit-project/cockpit/pull/5523
[2] http://pci-ids.ucw.cz/
[3]
https://github.com/cockpit-project/cockpit/wiki/Feature:-Hardware-Devices
--
Marek Libra
senior software engineer
Red Hat Czech
<https://www.redhat.com>
http://cockpit-project.org/blog/cockpit-158.html
Cockpit is the modern Linux admin interface. We release regularly. Here
are the release notes from version 158.
Add check boxes for common NFS mount options
--------------------------------------------
Setting up an NFS mount point on the Storage page now offers check boxes for
the most common mount options: "Mount at boot" and "Mount read only". Other
arbitrary options can still be given in the "Custom" input line, as before.
Screenshot: http://cockpit-project.org/images/storage-nfs-option-checkboxes.png
Clarify Software Update status if only security updates are available
---------------------------------------------------------------------
In that case the status message is now "n security fixes" instead of
"n updates, including n security fixes".
Create self-signed certificates with SubjectAltName
---------------------------------------------------
When connecting to Cockpit through SSL (https://...) without explicitly
configuring a certificate, Cockpit generates a self-signed one. This
certificate now has a `SubjectAltName:` field that is valid for
localhost/127.0.0.1. Some browsers, like Chromium, require this field to accept
a certificate for an SSL connection.
This allows administrators or users to import Cockpit's certificate into the
system oder user certificate database so that web browsers can connect to
Cockpit without SSL errors:
openssl s_client -connect 127.0.0.1:9090 < /dev/null | \
sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p' > /tmp/cert.pem
certutil -d sql:$HOME/.pki/nssdb -A -t "TC,C,P" -n cockpit -i /tmp/cert.pem
Get it
------
You can get Cockpit here:
http://cockpit-project.org/running.html
Cockpit 158 is available in Fedora 27:
https://bodhi.fedoraproject.org/updates/cockpit-158-1.fc27
Or download the tarball here:
https://github.com/cockpit-project/cockpit/releases/tag/158
Take care,
Martin Pitt
Hi,
I have some mockup screen regarding cockpit enhancement.Please review it
and give some suggestion to make it useful.
Below is the google doc link:
https://docs.google.com/document/d/11sJ89ylKfyNRgFh_JCKoPa1TX2Wmd6XTlpm4TQf…
Attached pdf file as well incase screens are not visible properly.
Thanks,
Gobinda Das
9019047912
We are currently developing internally a new functionality for the "logs" plugin. We need a way to filter the log list by unit, something like this:
https://netsmarttech.com/web/image/6894
Is it interesting for you that we submit a PR in the oficial cockpit repository for that ?