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.
Github now has a "rebase and merge" button which does exactly what we
have been doing manually so far.
I think we can just use it. Differences compared to our old way are:
- We don't get any opportunity to add the "Reviewed-By" line, but we
can use the "Commit" field instead that is shown by "git log
--format=full" and also by Github.
- Github now says "Merged" instead of "Closed".
- It's less work.
I have closed two PRs with that button: #5079 and #5084.
I'll update our Workflow document, OK?
Meeting started by mvollmer at 13:05:02 UTC. The full logs are available
* Agenda (mvollmer, 13:06:27)
* network manager capabilities (mvollmer, 13:10:53)
* more better storage layouts (mvollmer, 13:12:52)
* any other business (mvollmer, 13:20:19)
Meeting ended at 13:22:43 UTC.
Action Items, by person
People Present (lines said)
* mvollmer (28)
* zodbot (6)
* dperpeet (6)
* larsu (2)
* github (1)
* petervo (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
Yesterday several of us (roughly the top contributors  to Cockpit)
discussed removing the '0.x' from the Cockpit version number.
The plan is from here on out to just go with integer versions, starting
with version '118' following version '0.117'.
Cockpit releases weekly. Some versions of Linux distributions closely
track that weekly release. Other choose particular releases to include,
based on features and other criteria.
, as well as backwards compatible transport protocol. I hope to post
more documentation about these guarantees soon.
I'm having trouble adding a host to cockpit.
It was already listed in cockpit but then I reinstalled fedora on it,
removed the host from cockpit and now I get the following message when I
try to add it again:
Incorrect Host Key
The key of *myhost.mydomain* does not match the key previously in use.
Unless this machine was recently replaced, it is likely that someone is
trying to attack your connection to this machine.
How can I solve this?