cockpit-devel December 2016

cockpit-devel@lists.fedorahosted.org

6 participants
6 discussions

Weekly meeting
by Marius Vollmer 19 Dec '16

19 Dec '16

======================== #cockpit: weekly meeting ======================== Meeting started by mvollmer at 14:01:17 UTC. The full logs are available at https://meetbot.fedoraproject.org/cockpit/2016-12-19/weekly_meeting.2016-12… . Meeting summary --------------- * Agenda (mvollmer, 14:02:42) * package name change cockpit-shell (mvollmer, 14:06:01) * LINK: https://github.com/cockpit-project/cockpit/pull/5600 has been merged (dperpeet, 14:06:48) * NFS Server COnfiguration (mvollmer, 14:10:57) * LINK: http://knowyourmeme.com/memes/im-going-to-build-my-own-theme-park-with-blac… (mvollmer, 14:35:42) * Firewall configuration (mvollmer, 14:43:47) * LINK: https://github.com/cockpit-project/cockpit/wiki/Feature:-Firewall (andreasn, 14:45:08) * Any other business (mvollmer, 14:52:10) Meeting ended at 14:56:00 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * mvollmer (89) * dperpeet (52) * sgallagh (32) * andreasn (28) * zodbot (6) * bhakti (5) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

ArchLinux development
by Thijs Cramer 15 Dec '16

15 Dec '16

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

2 1

Weekly meeting
by Marius Vollmer 12 Dec '16

12 Dec '16

======================== #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-12-… . 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-11… (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

1 0

Warning message when loading cockpit in Firefox 50.0.2
by Fuji San 06 Dec '16

06 Dec '16

I have these messages when I load cockpit in firefox: http://imgur.com/FUmIlm9 http://imgur.com/yJti27W $ rpm -qa|grep cockpit cockpit-125-1.fc25.x86_64 cockpit-networkmanager-125-1.fc25.noarch cockpit-storaged-125-1.fc25.noarch cockpit-shell-125-1.fc25.noarch cockpit-sosreport-125-1.fc25.noarch cockpit-bridge-125-1.fc25.x86_64 cockpit-doc-125-1.fc25.x86_64 cockpit-ws-125-1.fc25.x86_64 cockpit-docker-125-1.fc25.x86_64

1 0

Cockpit weekly meeting 2016-12-05
by Andreas Nilsson 05 Dec '16

05 Dec '16

=========================================== #cockpit: Cockpit weekly meeting 2016-12-05 =========================================== Meeting started by andreasn at 14:03:41 UTC. The full logs are available at https://meetbot.fedoraproject.org/cockpit/2016-12-05/cockpit_weekly_meeting… . Meeting summary --------------- * Agenda (andreasn, 14:05:04) * Network checkpoints status (andreasn, 14:07:21) * NFS Server (andreasn, 14:40:51) * LINK: https://docs.google.com/document/d/1jLyKsECdHdlKltmHGgf_-iOKj-hj4Qjbh5Zgm7a… (andreasn, 14:41:41) * LINK: https://github.com/cockpit-project/cockpit/wiki/Feature:-NFS-Server (andreasn, 14:41:56) * Open floor (andreasn, 14:48:55) Meeting ended at 14:52:52 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * mvollmer (76) * dperpeet (70) * andreasn (58) * zodbot (5) * larsu (4) * github (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

idea/rfc: device screen in cockpit
by Martin Polednik 03 Dec '16

03 Dec '16

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

6 14

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

cockpit-devel December 2016