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.
New to cockpit - a co-worker mentioned it last week and it seems pretty nifty. I'm curious if it's a good fit for a project of mine.
I want to host Open Bazaar servers (https://openbazaar.org/). I'd _like_ to give my users access a GUI as 'a' user to run a limited set of functions such as ..
* start / stop a service
* look at a log file
* run a predefined set of API calls using CURL
* run a predefined script to backup a database
Is Cockpit a good fit?
I would like to hear your opinion on adding Virtual Machine status and management capability to the Cockpit.
I've already played with this idea for some time. It lead me to a plugin providing such a functionality, but with dependency on the oVirt (VDSM).
- lists all VMs running on the host,
- displays some charts, statistics and other VM details
- plus allows set of actions on them (so far basic - shutdown, restart, console, but can grow).
With optional access to oVirt's engine, additional cluster-related functionality is made accessible:
- list of VMs in a cluster,
- VM run,
- click-through to other cockpit running particular VM
In hindsight, there might be a better approach in contributing VM status&management to the Cockpit upstream, alongside with recent Docker or Kubernetes.
As a starting point, a list of running VMs will be displayed and basic set of actions provided.
Vision: implement in the Cockpit
- similar functionality as is recently done for the desktop's virt-manager but with the benefit of revising the User Experience
- allow monitoring&management of cluster VMs, if the host is part of any
This feature would be libvirt-based, not VDSM - so no additional dependencies for Cockpit.
The VDSM would be preferred service provider, if *optionally* installed on the host.
Similar for oVirt's engine - if accessible then cluster-related functionality is provided (i.e. cluster VMs list, managed VM migration, run a VM "in a cluster", cockpit's VM detail click-through, etc.).
Benefit for users: support for VM management out of the box with layered access to functionality as more advanced VM management tools are installed on a host
Please share your ideas.
Currently a package with a "name"(in manifest.json) causes the package loading
logic from various package directories to fail. Instead of the
first one (ie: ~/.local/share/cockpit) being used, the
last instance of a package will be used (ie: /usr/share/cockpit)
A fix will be running the following command-
sudo rm -rf /usr/share/cockpit/realmd
PR associated with the issue-
Good news! The project ideas for Cockpit have been updated on the Fedora
- Cockpit support for systemd timers
- OStree Repositories in Cockpit
- OStree Rebases in Cockpit
- Setup a FreeIPA server in Cockpit using Rolekit
The 2016 student application window is March 14th to 25th (source:
Google Summer of Code website http://g.co/gso).
If you're a student, you're welcome to hack on Cockpit, make some
contributions and apply to the program!