ArchLinux development
by Thijs Cramer
Hey All,
Recently I've migrated my homeserver from Fedora to ArchLinux. Which
gives me the headache of installing Cockpit (since i like it a lot :)
) on Archlinux.
I've seen the AUR package, but it has an insane amount of dependencies
and i don't understand some of them. (Compiling from source gives the
same dependencies, so the're not wrong...)
Is there some kind of dependency tree/graph for *all* components
needed for compiling Cockpit from source (and maybe why they are
needed) ?
Some of the components that I didn't like that one way or another were
needed as a dependency:
- Cairo
- PCP
- Systemtap
- libmesa
- Qt4
- some LateX stuff
All the help/info is welcome!
- Thijs
7 years, 4 months
Weekly meeting
by Marius Vollmer
========================
#cockpit: weekly meeting
========================
Meeting started by mvollmer at 14:05:49 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/cockpit/2016-12-12/naked_ping.2016-12-1...
.
Meeting summary
---------------
* Agenda (mvollmer, 14:06:05)
* ram disks on Ubuntu (mvollmer, 14:13:40)
* Authorization for privileged actions (mvollmer, 14:18:08)
* LINK: https://github.com/cockpit-project/cockpit/pull/5545 (stefw,
14:21:05)
* LINK: https://github.com/cockpit-project/cockpit/pull/5548 (stefw,
14:21:10)
* LINK:
https://github.com/cockpit-project/cockpit/blob/master/doc/reauthorize.md
(stefw, 14:22:12)
* LINK:
https://cloud.githubusercontent.com/assets/795070/20791780/0524cd4a-b7bf-...
(stefw, 14:25:52)
* Translations (mvollmer, 14:33:07)
* Open floor (mvollmer, 14:55:13)
Meeting ended at 15:04:08 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* stefw (69)
* mvollmer (62)
* petervo (13)
* dperpeet (11)
* zodbot (7)
* github (3)
* cockpitbot (1)
* larsu (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
7 years, 4 months
idea/rfc: device screen in cockpit
by Martin Polednik
Hello,
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
using cockpit.
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,
vports),
* iommu group (possibly clickable to reveal all devices in given
group),
* 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.
Thanks,
mpolednik
7 years, 4 months
