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.
On 06/20/2016 08:44 AM, Stef Walter wrote:
> On 02.06.2016 17:13, Josh Berkus wrote:
>> So because of my conference schedule in June, I'm trying to get the demo
>> atomic cluster for Summit kitted out sooner rather than later.
>> For that reason, I'd like to know:
>> 1. What do you want to demo on it? You're welcome to install any
>> version of Cockpit you can install in a container, with the caveat that
>> it needs to be loaded ahead of time.
> Sorry for the delayed response. Is that an Atomic Host cluster? Is there
> still time? If so, could you preload 'atomic run rhel7/cockpit-ws' on them?
I'll be rebuilding the cluster.
However, I need some help making both cockpit/ws and cockpit/kubernetes
work properly on the cluster, when can I get some assistance from you guys?
Also, isn't there a cockpit intereface for Commissaire? Where do I get
Red Hat OSAS
(any opinions are my own)
So because of my conference schedule in June, I'm trying to get the demo
atomic cluster for Summit kitted out sooner rather than later.
For that reason, I'd like to know:
1. What do you want to demo on it? You're welcome to install any
version of Cockpit you can install in a container, with the caveat that
it needs to be loaded ahead of time.
2. What days/times will you not be available during Summit?
Red Hat OSAS
I've set up Cockpit/Kubernetes on a new atomic cluster, but I can't log
into it. I've tried both the standard password, and various system
users, and can't log in.
Where is it getting auth credentials from?
Red Hat OSAS
so I had a first go at adding network teaming support to Cockpit:
The current code doesn't expose _any_ configuration settings for a team,
because the defaults are perfect!
At least, that's my working assumption right now. :-)
If you use teams, what settings to do you have to change? Can you see a
way to improve teamd itself so that you could just use the default