cockpit-devel April 2016

cockpit-devel@lists.fedorahosted.org

7 participants
11 discussions

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

Feature Suggestion: Send syslog to external log management tool
by Eduardo Hernacki 09 May '16

09 May '16

Hello! Since I haven't seen another place to put it, I'd like to make a feature suggestion in this list... Based on the growing demand for log management and big data, I think it would be interesting if Cockpit could provide a method to configure log shipping to an external log management tool. It could also include Docker and Kubernetes container logs as well... This would avoid the need to manually configure rsyslog or another log collector to ship syslogs. What do you guys think? Regards, Eduardo Hernacki

4 4

Cockpit 0.104
by Stef Walter 29 Apr '16

29 Apr '16

A summary of the Cockpit weekly release. There’s a new release every week. Here are the highlights from this weeks 0.104 release. Kubernetes iSCSI Volumes ------------------------ Peter added support for iSCSI Kubernetes Volumes in the Cockpit Cluster dashboard. When you have container pods that need to store data somewhere, it's now real easy to configure use an iSCSI initiator. Take a look: Demo: https://www.youtube.com/embed/ytNGsIDYNSQ Change: https://github.com/cockpit-project/cockpit/pull/4252 Listing View Expansion ---------------------- Andreas, Dominik, and I worked on a better listing view pattern. In Cockpit we like to give admins the option to expand data inline, and compare it between multiple entries on the same page. But after feedback from the Patternfly folks we added an explicit expander to do this. Demo: https://www.youtube.com/embed/myXr_hnr5Jg Change: https://trello.com/c/w6HNguFl/294-0-104-new-listing-designs Tagging Docker Images in the Registry ------------------------------------- The Atomic Registry and Openshift Registry support mirroring images from another image registry such as the Docker Hub. When the images are mirrored, they are copied and available in your own registry. Cockpit now has support for telling the registry which specific tags you'd like to mirror. And Aaron is adding support for various mirroring options as well. Demo: https://www.youtube.com/embed/MJzqob5AYI8 Change: https://github.com/cockpit-project/cockpit/pull/4268 From the Future --------------- Marius has a working proof of concept that lets you configure where Docker stores container and image data on its host. Take a look at the demo below. Marius adds disks to the container storage pool: Demo: https://www.youtube.com/embed/9YiG4AY6HeY Get it ------ You can get Cockpit here: http://cockpit-project.org/running.html Cockpit 0.104 is available in Fedora 24: https://bodhi.fedoraproject.org/updates/cockpit-0.104-1.fc24 Or download the tarball here: https://github.com/cockpit-project/cockpit/releases/tag/0.104 Take care, Stef

1 0

Cockpit weekly meeting 2016-04-25
by Andreas Nilsson 25 Apr '16

25 Apr '16

=========================================== #cockpit: Cockpit weekly meeting 2016-04-25 =========================================== Meeting started by andreasn at 13:04:09 UTC. The full logs are available at https://meetbot.fedoraproject.org/cockpit/2016-04-25/cockpit_weekly_meeting… . Meeting summary --------------- * Agenda (andreasn, 13:04:48) * React Playground (andreasn, 13:09:25) * listing pattern updates (andreasn, 13:18:01) * google summer of code (andreasn, 13:24:00) * Open Floor (andreasn, 13:30:39) Meeting ended at 13:38:00 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * dperpeet (56) * andreasn (29) * larsu (18) * zodbot (7) * petervo (5) * sgallagh (3) * mulhern (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Cockpit 0.103
by Stef Walter 21 Apr '16

21 Apr '16

A summary of the Cockpit weekly release. There’s a new release every week. Here are the highlights from this weeks 0.103 release. Kubernetes Connection Configuration ----------------------------------- When a Kubernetes client wants to access the API of the cluster, it looks for a "kubeconfig" file to tell it how to find the cluster and how to authenticate when accessing the API. The usual location for this file is in the current user's home directory at the ```~/.kube/config``` file path. If that doesn't exist, then usually the cluster isn't available. This applies to both clients like the ```kubectl``` command as well as Cockpit's cluster dashboard. Cockpit can now prompt for this information, and build this file for you. If it doesn't exist, then there's a helpful "Troubleshoot" button to help get this configuration in place. Demo: https://www.youtube.com/embed/WSh7wYhAXrA Change: https://github.com/cockpit-project/cockpit/pull/4207 Upload each Release to an Ubuntu PPA ------------------------------------ Each weekly release of Cockpit is now uploaded to an Ubuntu PPA. Here's how to make use of it: sudo add-apt-repository ppa:cockpit-project/cockpit sudo apt-get update sudo apt-get install cockpit Change: https://github.com/cockpit-project/cockpituous/pull/30 Remove jQuery Usage from cockpit.js API --------------------------------------- As part of stabilizing the internals of Cockpit, we removed jQuery usage from the cockpit.js file. [The javascript API itself](http://cockpit-project.org/guide/latest/api-base1.html) hasn't changed, but this change helps to help keep a stable API in the future. Change: https://github.com/cockpit-project/cockpit/pull/4203 Get it ------ You can get Cockpit here: http://cockpit-project.org/running.html Cockpit 0.103 is available in Fedora 24: https://bodhi.fedoraproject.org/updates/cockpit-0.103-1.fc24 Or download the tarball here: https://github.com/cockpit-project/cockpit/releases/tag/0.103 Take care, Stef

2 1

Weekly meeting 2016-04-18
by Andreas Nilsson 18 Apr '16

18 Apr '16

=========================================== #cockpit: Cockpit weekly meeting 2016-04-18 =========================================== Meeting started by andreasn at 13:01:06 UTC. The full logs are available at https://meetbot.fedoraproject.org/cockpit/2016-04-18/cockpit_weekly_meeting… . Meeting summary --------------- * Agenda (andreasn, 13:02:20) * list pattern (andreasn, 13:05:54) * LINK: https://raw.githubusercontent.com/cockpit-project/cockpit-design/master/pat… (andreasn, 13:06:49) * removing jquery from cockpit.js (andreasn, 13:22:24) * Patternfly update (andreasn, 13:29:07) * Ubuntu PPA packages (andreasn, 13:31:37) * Open Floor (andreasn, 13:37:00) Meeting ended at 13:44:11 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * stefw (56) * dperpeet (52) * andreasn (35) * mvollmer (22) * larsu (11) * zodbot (8) * github (4) * mulhern (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Cockpit 0.102 with Docker Restart Policy
by Stef Walter 14 Apr '16

14 Apr '16

A summary of the Cockpit weekly release. There’s a new release every week. Here are the highlights from this weeks 0.102 release. Docker Restart Policy --------------------- When running a Docker container in Cockpit, you can now set the restart policy, so when the docker daemon restarts the containers will be restarted too. Justin Robertson contributed this feature. Take a look. Demo: https://www.youtube.com/watch?v=8YYHui-FQco Change: https://github.com/cockpit-project/cockpit/pull/4172 Single Dialog for Creating Logical Volumes ------------------------------------------ The storage interface in Cockpit now has a single combined dialog when creating logical volumes. This is a first tiny step towards advanced LVM2 features such as RAID layouts and caches. The dialog will get more fields and more interesting behavior as we implement more of the features offered by LVM2, such as the various RAID levels, as indicated by the hidden options for the "Purpose" and "Layout" fields. Screenshot: http://stef.thewalter.net/images/cockpit-logical-volume-one-dialog.png Change: https://github.com/cockpit-project/cockpit/pull/4027 Storage interface now available on Debian ----------------------------------------- The storage interface in Cockpit has been enabled and built on Debian. The storaged API is now available on Debian too. Change: https://github.com/cockpit-project/cockpit/pull/4112 Don't Distribute jshint due to License -------------------------------------- We stopped distributing jshint or requiring it as a build dependency due to its controversial license. Change: https://github.com/cockpit-project/cockpit/pull/4165 Get it ------ You can get Cockpit here: http://cockpit-project.org/running.html Cockpit 0.102 is available in Fedora 24: https://bodhi.fedoraproject.org/updates/cockpit-0.102-1.fc24 Or download the tarball here: https://github.com/cockpit-project/cockpit/releases/tag/0.102 Take care, Stef

1 0

Problem connecting on an ipa client
by Fuji San 11 Apr '16

11 Apr '16

Hello, I have several Freeipa clients and a Freeipa server (4.2.4-1.fc23). 3 of them are causing trouble. No user can log into them either through lightdm or via ssh from another desktop. Here user *smith* is trying to connect to amelia from doe's account: [doe@nina ~] $ ssh smith@amelia smith@amelia's password: Permission denied, please try again. smith@amelia's password: Permission denied, please try again. smith@amelia's password: packet_write_wait: Connection to UNKNOWN port 0: Broken pipe Below are some logs when user '*smith*' is trying to log in on desktop 'amelia', one of those 3 desktops: And user '*smith*' has no problem loging in other desktops. User '*smith*' will eventually be able to login later today without me doing anything to fix this. Any idea how I can fix this problem? Thank you Best regards, Fuji ---------------------------------------- # systemctl status sshd.service ● sshd.service - OpenSSH server daemon Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2016-04-08 08:08:30 CEST; 3 days ago Docs: man:sshd(8) man:sshd_config(5) Process: 1337 ExecStart=/usr/sbin/sshd $OPTIONS (code=exited, status=0/SUCCESS) Main PID: 1344 (sshd) CGroup: /system.slice/sshd.service └─1344 /usr/sbin/sshd Apr 11 08:27:29 amelia.opera sshd[5007]: Connection closed by 10.0.21.200 port 49700 [preauth] Apr 11 08:51:21 amelia.opera sshd[5707]: error: AuthorizedKeysCommand /usr/bin/sss_ssh_authorizedkeys root failed, status 1 Apr 11 08:51:21 amelia.opera sshd[5707]: error: AuthorizedKeysCommand /usr/bin/sss_ssh_authorizedkeys root failed, status 1 Apr 11 08:51:21 amelia.opera sshd[5707]: Accepted publickey for root from 10.0.21.200 port 50798 ssh2: RSA SHA256:kur/vJcNV6ksMFGaMzN9eqhBUMertS7cvRZqU64dMCk Apr 11 08:52:30 amelia.opera sshd[5791]: pam_sss(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=10.0.21.200 user=*smith* Apr 11 08:52:30 amelia.opera sshd[5791]: pam_sss(sshd:auth): received for user *smith*: 4 (System error) Apr 11 08:52:30 amelia.opera sshd[5791]: Failed password for *smith* from 10.0.21.200 port 50830 ssh2 Apr 11 09:04:26 amelia.opera sshd[6924]: pam_sss(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=10.0.21.200 user=*smith* Apr 11 09:04:26 amelia.opera sshd[6924]: pam_sss(sshd:auth): received for user *smith*: 4 (System error) Apr 11 09:04:26 amelia.opera sshd[6924]: Failed password for *smith* from 10.0.21.200 port 51440 ssh2 Apr 11 09:05:03 amelia.opera sshd[6924]: pam_sss(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=10.0.21.200 user=*smith* Apr 11 09:05:03 amelia.opera sshd[6924]: pam_sss(sshd:auth): received for user *smith*: 4 (System error) Apr 11 09:05:03 amelia.opera sshd[6924]: pam_reauthorize: couldn't set permissions on kernel key: reauthorize/secret/*smith*: Permission denied Apr 11 09:05:03 amelia.opera sshd[6924]: Failed password for *smith* from 10.0.21.200 port 51440 ssh2 ---------------------------------------- in /var/log/secure: Apr 11 08:50:54 amelia lightdm: pam_sss(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=*smith* Apr 11 08:50:54 amelia lightdm: pam_sss(lightdm:auth): received for user *smith*: 4 (System error) Apr 11 08:51:21 amelia sshd[5707]: error: AuthorizedKeysCommand /usr/bin/sss_ssh_authorizedkeys root failed, status 1 Apr 11 08:51:21 amelia sshd[5707]: error: AuthorizedKeysCommand /usr/bin/sss_ssh_authorizedkeys root failed, status 1 Apr 11 08:51:21 amelia sshd[5707]: Accepted publickey for root from 10.0.21.200 port 50798 ssh2: RSA SHA256:kur/vJcNV6ksMFGaMzN9eqhBUMertS7cvRZqU64dMCk Apr 11 08:51:21 amelia sshd[5707]: pam_unix(sshd:session): session opened for user root by (uid=0) Apr 11 08:52:30 amelia sshd[5791]: pam_sss(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=10.0.21.200 user=*smith* Apr 11 08:52:30 amelia sshd[5791]: pam_sss(sshd:auth): received for user *smith*: 4 (System error) Apr 11 08:52:30 amelia sshd[5791]: Failed password for *smith* from 10.0.21.200 port 50830 ssh2 Apr 11 08:55:02 amelia systemd: pam_unix(systemd-user:session): session opened for user pcp by (uid=0) ---------------------------------------- in /var/log/message: Apr 11 08:52:27 amelia audit: CRYPTO_KEY_USER pid=5792 uid=0 auid=4294967295 ses=4294967295 msg='op=destroy kind=server fp=SHA256:3c:91:77:85:c3:d9:70:e2:de:f1:d6:8d:f6:7d:c3:0c:f8:1b:33:70:79:c0:56:55:8c:7e:09:79:ba:c2:8b:a4 direction=? spid=5792 suid=0 exe="/usr/sbin/sshd" hostname=? addr=10.0.21.200 terminal=? res=success' Apr 11 08:52:27 amelia audit: CRYPTO_KEY_USER pid=5792 uid=0 auid=4294967295 ses=4294967295 msg='op=destroy kind=server fp=SHA256:92:c4:7d:59:e2:e5:56:47:d1:7c:e9:2a:f9:d6:45:9e:5d:90:7c:59:2c:28:6f:32:1d:88:8e:25:cc:3c:44:a7 direction=? spid=5792 suid=0 exe="/usr/sbin/sshd" hostname=? addr=10.0.21.200 terminal=? res=success' Apr 11 08:52:27 amelia audit: CRYPTO_KEY_USER pid=5792 uid=0 auid=4294967295 ses=4294967295 msg='op=destroy kind=server fp=SHA256:fb:2b:9b:15:d6:87:b7:d9:f3:05:19:a4:56:ce:13:e4:88:44:03:90:94:4c:e7:2c:28:81:60:b5:f2:e1:2e:be direction=? spid=5792 suid=0 exe="/usr/sbin/sshd" hostname=? addr=10.0.21.200 terminal=? res=success' Apr 11 08:52:27 amelia audit: CRYPTO_SESSION pid=5791 uid=0 auid=4294967295 ses=4294967295 msg='op=start direction=from-server cipher= chacha20-poly1305(a)openssh.com ksize=512 mac=<implicit> pfs= curve25519-sha256(a)libssh.org spid=5792 suid= 74 rport=50830 laddr=10.0.21.210 lport=22 exe="/usr/sbin/sshd" hostname=? addr=10.0.21.200 terminal=? res=success' Apr 11 08:52:27 amelia audit: CRYPTO_SESSION pid=5791 uid=0 auid=4294967295 ses=4294967295 msg='op=start direction=from-client cipher= chacha20-poly1305(a)openssh.com ksize=512 mac=<implicit> pfs= curve25519-sha256(a)libssh.org spid=5792 suid= 74 rport=50830 laddr=10.0.21.210 lport=22 exe="/usr/sbin/sshd" hostname=? addr=10.0.21.200 terminal=? res=success' Apr 11 08:52:27 amelia audit: USER_AUTH pid=5791 uid=0 auid=4294967295 ses=4294967295 msg='op=pubkey acct="*smith*" exe="/usr/sbin/sshd" hostname=? addr=10.0.21.200 terminal=ssh res=failed' Apr 11 08:52:30 amelia [sssd[krb5_child[5795]]]: Error constructing AP-REQ armor: Ticket not yet valid Apr 11 08:52:30 amelia [sssd[krb5_child[5795]]]: Error constructing AP-REQ armor: Ticket not yet valid Apr 11 08:52:30 amelia audit: USER_AUTH pid=5791 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=? acct="*smith*" exe="/usr/sbin/sshd" hostname=10.0.21.200 addr=10.0.21.200 terminal=ssh res=failed' Apr 11 08:52:30 amelia audit: USER_AUTH pid=5791 uid=0 auid=4294967295 ses=4294967295 msg='op=password acct="*smith*" exe="/usr/sbin/sshd" hostname=? addr=10.0.21.200 terminal=ssh res=failed'

2 1

Cockpit 0.101 with Kubernetes Volumes
by Stef Walter 08 Apr '16

08 Apr '16

A summary of the Cockpit weekly release. There’s a new release every week. Here are the highlights from this weeks 0.101 release. Kubernetes Volumes ------------------ You can now set up Kubernetes persistent volume claims through the Cockpit cluster admin interface. These volumes are used to store persistent container data and possibly share them between containers. Each container pod declares the volumes it needs, and when deploying such an application admins provide it with locations to store the data in those volumes. Change: https://github.com/cockpit-project/cockpit/pull/4118 Demo: https://www.youtube.com/watch?v=rlWeO_MsJOA Show SELinux failure messages properly -------------------------------------- As a follow up from last week, several bug fixes landed in the new SELinux troubleshooting support. Change: https://github.com/cockpit-project/cockpit/pull/4155 Get it ------ You can get Cockpit here: http://cockpit-project.org/running.html Cockpit 0.101 is available in Fedora 24: https://bodhi.fedoraproject.org/updates/cockpit-0.101-1.fc24 Or download the tarball here: https://github.com/cockpit-project/cockpit/releases/tag/0.101 Take care, Stef

1 0

Weekly meeting 2015-04-04
by Andreas Nilsson 04 Apr '16

04 Apr '16

=========================================== #cockpit: Cockpit weekly meeting 2016-04-04 =========================================== Meeting started by andreasn at 13:01:47 UTC. The full logs are available at https://meetbot.fedoraproject.org/cockpit/2016-04-04/cockpit_weekly_meeting… . Meeting summary --------------- * agenda (andreasn, 13:01:53) * Storage RAID (andreasn, 13:05:50) * Docker storage setup implementation (andreasn, 13:15:35) * LINK: https://lists.projectatomic.io/mailman/listinfo/atomic-devel (stefw, 13:31:18) * Open Floor (andreasn, 13:32:43) Meeting ended at 13:37:11 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * mvollmer (61) * dperpeet (28) * stefw (28) * andreasn (25) * zodbot (7) * larsu (3) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

cockpit-devel April 2016