cockpit-devel May 2020

cockpit-devel@lists.fedorahosted.org

13 participants
8 discussions

Suggestion for changing cockpit default session timeout
by Gal Zaidman 06 Jul '20

06 Jul '20

Hi Cockpit developers, I saw that on cockpit-209 Session timeouts were added with the default to 15 minutes of inactivity (https://cockpit-project.org/blog/cockpit-209.html ). I think that this change is problematic because: 1. The timeout is very short and it can cause unexpected behavior to users and cockpit packages. 2. The timeout can only be configured in the /etc/cockpit.conf file, so it is hard for packages to configure it to fit to their behavior. For example, we created a package for installing ovirt with cockpit UI, that installation can take a lot of time, it has different phases and logging out in the middle can cause problems. We prefer to avoid editing /etc/cockpit.conf because we don't want to run over user configuration (what to do when there is already cockpit.conf present?) I want to suggest: 1. Raising the timeout to 2 hours of inactivity, this seems reasonable. 2. Provide a more flexible way of configuring the timeout, with an option to the manifest.json package file and/or with a cockpit API call. Thanks

7 8

Cockpit 220
by Matej Marusak 28 May '20

28 May '20

Cockpit is the modern Linux admin interface. We release regularly. Here are the release notes from version 220: https://cockpit-project.org/blog/cockpit-220.html <https://cockpit-project.org/blog/cockpit-219.html> Summary: - New navigation with integrated switching of hosts - Logs: Inline help for filtering - Storage: Improve side panel on details page You can get Cockpit here: http://cockpit-project.org/running.html Cockpit 220 is available in Fedora 31: https://bodhi.fedoraproject.org/updates/FEDORA-2020-be42373991 And Fedora 32: https://bodhi.fedoraproject.org/updates/FEDORA-2020-c21a90d666 Or download the tarball here: https://github.com/cockpit-project/cockpit/releases/tag/220 <https://github.com/cockpit-project/cockpit/releases/tag/219> All the best, MM -- Matej Marušák Software Engineer Red Hat <https://www.redhat.com> <https://red.ht/sig>

1 0

Tests failing from cockpit bots repo in check_journal_messages()
by Justin Stephenson 22 May '20

22 May '20

Hi, I am validating some tests in cockpit-session-recording downstream in dist-git, but they are failing when tests are being executed from the cockpit bots repository: http://pastebin.test.redhat.com/867945 A full test run can be found here: https://jenkins.osci.redhat.com/job/rhel-8-pr-pipeline/4656/artifact/packag… I tried setting the environment variable below before running the tests but it still fails with the same errors: # export TEST_ALLOW_JOURNAL_MESSAGES=".*Permission denied.*" It could be the way we are running the tests is outdated: http://pkgs.devel.redhat.com/cgit/rpms/cockpit-session-recording/tree/?h=rh… Is there a known fix for this, or can I avoid running these tests completely when I am attempting to run our tests only. Thanks a lot. -Justin

2 2

Cockpit on smaller sysems (OpenWRT, QNAP, and other embedded Linux systems)
by Bernd Wechner 14 May '20

14 May '20

I see cockpit is available on all the major Linux distros. And I love having the overview in a cokjpit of all my systems. That set does include an OpenWRT router and a QNAP NAS, both of which are smaller stripped down embedded Linux systems if you will which use the opkg package manager: https://en.wikipedia.org/wiki/Opkg These systems have web interfaces already (OPenWRT typically under lighttpd and QNAP use Apache) but methinks cockpit is independent of these running it's own web service (cockpit-ws). Like the Pi these are typically ARM based machines and it's even plausible that the Pi build runs on them, but they don't typically have developement tools on them by default for building (compiling and linking) software locally. Anyhow, I thought I'd ask if anyone has considered this, as it would rock to see the gateway router on the list of servers overseen and the NAS.

2 2

Installing the latest version
by Bernd Wechner 14 May '20

14 May '20

I just installed an Ubuntu 20.04 server. Then cockipt. And it looked way different to what I have elsewhere. So I checked versions. And sure enough on Ubuntu 20.04 we ghave: Version: 215-1 and on our other systems: Version: 164-1 Now it's not unusual for the repos to have different versions like this but it's usually due to lag in getting updates into repos. For which reason many packages maintain a PPA (Personal Package Archive) which a project can push latest version too without waiting on downstream approvals. As I'd love to see all my system looking similar and have the latest all round, is there a way to install the latest version that I'm not seeing documented, that does not rely on the Ubuntu repos to absorb them?

3 3

Unable to connect to cockpit
by Parth Dhanjal 14 May '20

14 May '20

Hey! I have a remote machine on which I have installed RHVH4.4 I'm unable to access the cockpit-plugin. journalctl -u cockpit returns this error cockpit-tls: gnutls_handshake failed: A TLS fatal alert has been received. Screenshot while trying to reach cockpit through the browser attached. Is anyone else facing this issue as well? And does anyone has a solution/workaround to this?

6 7

Cockpit 219
by Katerina Koukiou 14 May '20

14 May '20

Cockpit is the modern Linux admin interface. We release regularly. Here are the release notes from version 219: https://cockpit-project.org/blog/cockpit-219.html Summary: - Logs: Improved filtering - Gain or drop administrative access in a running Cockpit session You can get Cockpit here: http://cockpit-project.org/running.html Cockpit 215 is available in Fedora 31: https://bodhi.fedoraproject.org/updates/FEDORA-2020-9196806743 And Fedora 32: https://bodhi.fedoraproject.org/updates/FEDORA-2020-8bffc7d9dd Or download the tarball here: https://github.com/cockpit-project/cockpit/releases/tag/219 Kind regards, Katerina

1 0

Kubernetes exec protocol
by Marc Boorshtein 08 May '20

08 May '20

All, I'm adding websockets support to kubectl for exec and port forwarding. I have some simple POCs working but am trying to now integrate it into client-go & kubectl and have some questions on how their different protocols are differentiated. Looking at https://github.com/kubernetes-ui/container-terminal/blob/master/container-t… i see how you're integrating with the terminal resize but I don't see how yuo're telling the api server which of the four protocols to use. If anyone here has worked on this code and can point me in the right direction I'd really appreciate it. Thanks Marc Boorshtein

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

cockpit-devel May 2020