I have an idea for cockpit, but before thinking it further, I'm
interested in hearing your opinions. I am oVirt developer mostly
dealing with system stuff and this is something that could be useful
in virtualization while also providing utility for administrators
The idea is about new tab/plugin (not sure of the terminology) called
'devices', that would allow access to (hardware) devices as exposed by
sysfs. The interface could be similar to 'Services' tab/plugin,
showing a list of device names created from their physical location,
similarly to libvirt's nodedev-list.
After clicking on the name, new screen would be presented, showing
additional information such as
* physical address,
* driver in use,
* special capabilities (SR-IOV numvfs and totalvfs, NPIV max_vports,
* iommu group (possibly clickable to reveal all devices in given
* vendor, vendor id, product, product id.
Additionally, it makes sense to allow some basic operations:
* unbinding from host driver, binding it to specific one (useful for
local vfio-pci testing),
* reattaching it back (one use case is that
oVirt does not reattach devices automatically due to possible
issues, needs user intervention),
* setting numvfs, vports,
* ... ?
Do you find ideas above reasonable for cockpit? It is mostly in idea
phase, and builds on development and requirements of oVirt. I
personally believe that this could be useful for broader audience.
I'd like to inform you there is a new feature in ABRT.
Now, it's is possible to report problems into systemd journal.
If some problem occurs, abrt sends a catalog message into systemd
journal with some details about the problem (e.g. truncated backtrace, reason, ...)
and also some information how to analyse the problem via abrt etc..
Content of catalog messages for each problem type can be configured,
the following wiki page  shows the default formatting of catalog messages.
For better understanding, I've created a video with examples .
After i log in to cockpit web ui using firefox, the page remaines empty (white).
Sometimes I get a warning message "Unresponsive script" saying:
"A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue.
Script: https:// server:9090/cockpit/$3..../shell/bundle.js:29"
I do not have this problem when I use Opera browser.
The Ideals of Cockpit  says that "Users of Cockpit should feel they
are interacting with the underlying Server OS, not with Cockpit." so we
took extra care to make sure Cockpit is not something that is directly
visible to the end user.
Peter Volpe is currently working on integration between ManageIQ and
The idea is that you can get an overview of a cluster in ManageIQ, but
then dive in, by clicking a button, to a particular node by and
administer that with Cockpit.
Initially the button was labeled "Cockpit", so we had to come up with a
better label. Peter, me, Stef and Ben discussed this back and forth a
bit with the ManageIQ designers, and settled on "Access Web Console" in
(I am fully aware that this wording is a very tempting bike-shed to
paint, but it's also consistent with how other ways of interacting with
the server is called across several products.)
Apparently there is something similar in oVirt, so Fabian Deutch was
kind enough to quickly fix that up and have it say "Web Console" as well.
Since I think this is something that will come up more in the future, as
we integrate Cockpit with more products, I thought it would be a good
idea to set up a wiki page with general guidance on how to refer to
Cockpit from another UI.
These are only the initial recommendations, and there is probably a ton
of wrinkles to this, so I am pretty sure the document will evolve over time.