cockpit-devel February 2017

cockpit-devel@lists.fedorahosted.org

11 participants
9 discussions

Continuous delivery of release 132 failed and recovery
by Stef Walter 07 Mar '17

07 Mar '17

If you've been following on IRC, you may have noticed that releasing Cockpit 132 failed yesterday. Here's why, and how it's been solved. In general we want the entire release process to be completely automatic, with all failures detected before hand. Earlier this week I made a pull request that passed integration tests, but broke the continuous delivery: https://github.com/cockpit-project/cockpit/pull/5924 The symptom was that certain files we installed in 'make install' when they shouldn't have been installed there. But the root cause was that we were building RPMs differently during integration tests, and later during release: https://fedorapeople.org/groups/cockpit/logs/release-132/log To solve this problem I added patches to the release-132 branch to fix this problem, and then ran the continuous delivery scripts manually from that branch: https://github.com/cockpit-project/cockpit/tree/release-132 ... in the cockpit/infra-release container ... $ git fetch origin $ git checkout release-132 $ RELEASE_SINK= RELEASE_TAG=132 release-runner -v /usr/local/bin/major-cockpit-release What this does is use the 132 git tag to create a tarball, and then any commits after that are included in the SRPM as patches. So how do we prevent this from happening again? 1. Build RPMs during integration more like release: https://github.com/cockpit-project/cockpit/pull/5942 2. Cleanup the code related to 'make install' and 'make install-tests' https://github.com/cockpit-project/cockpit/pull/5941 3. Document how to solve this in the future (this email). 4. I noticed that the release-dsc file does not consider patches the way that release-srpm does. This needs a fix, any takers? https://github.com/cockpit-project/cockpituous/blob/master/release/release-… This wasn't a problem this time around because the patches did not affect debian builds. 5. Figure out how to test upgrading. Martin Pitt caught it this time, but it should have failed before going in: https://github.com/cockpit-project/cockpit/pull/5937 Cheers, Stef

2 1

Supporting ABRT in Cockpit
by Matej Marusak 06 Mar '17

06 Mar '17

Hi Cockpit people, A while ago the ABRT team presented [1] Cockpit module showing problems detected by ABRT and allowing users to report them. It was more less a proof of concept. But we are eager to finish this effort. After speaking with some members of the Cockpit team on DevConf we were advised to start by writing user stories. We did so and today I presented them on the wikipage of cockpit's github [2]. We would love to have a feedback from you. What do you think of this? Is it suitable for Cockpit? We are open-minded to yours ideas. Best regards, Matej ABRT 1: https://lists.fedorahosted.org/archives/list/cockpit-devel@lists.fedorahost… 2: https://github.com/cockpit-project/cockpit/wiki/Feature:-ABRT

7 29

Weekly meeting
by Marius Vollmer 27 Feb '17

27 Feb '17

======================== #cockpit: weekly meeting ======================== Meeting started by mvollmer at 14:03:34 UTC. The full logs are available at https://meetbot.fedoraproject.org/cockpit/2017-02-27/weekly_meeting.2017-02… . Meeting summary --------------- * Agenda (mvollmer, 14:05:12) * Outreachy (mvollmer, 14:08:26) Meeting ended at 14:18:52 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * mvollmer (9) * dperpeet (9) * zodbot (5) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Cockpit 130, 131 and 132
by 'Dominik Perpeet' 24 Feb '17

24 Feb '17

http://cockpit-project.org/blog/cockpit-132.html Cockpit is the modern Linux admin interface. We release regularly. Here are the release notes from version 130, 131 and 132. Kernel dump configuration support added --------------------------------------- Kernel crash dump configuration is now possible in Cockpit: view and toggle the status of the kdump service, with hints how to enable if the kernel boot parameters need to be changed. Cockpit shows the amount of reserved memory and setting a path for dumping the kernel on the local filesystem, with a toggle for compressing the crash dumps. Take a look at the video below for a demo. Demo: https://youtu.be/VXhuqPR2K5c Change: https://github.com/cockpit-project/cockpit/pull/5587 MAC addresses for ethernet adapters and bonds can be modified ------------------------------------------------------------- On the Networking page, MAC addresses for ethernet adapters can now be clicked to edit them, starting with NetworkManager version 1.4. For bonds, the MAC addresses are shown and can be edited starting with NetworkManager version 1.6. Take a look at the video below for a demo. Demo: https://youtu.be/JIHQmFHOrO4 Change: https://github.com/cockpit-project/cockpit/pull/5851 Show session virtual Machines on the machines page -------------------------------------------------- Libvirt differentiates between system virtual machines and session ones, which are tied to the user. In Cockpit all the virtual machines accessible to the logged in user, system and session, are now shown in a combined list. Screenshot: http://cockpit-project.org/blog/images/cockpit-machines-session.png Change: https://github.com/cockpit-project/cockpit/pull/5765 SELinux functionality is now available without setroubleshootd -------------------------------------------------------------- The SELinux page in Cockpit can do more than just troubleshoot. It was therefore renamed to SELinux and the functionality of toggling between enforcing/permissive mode is now also available even if setroubleshoot-server isn't installed. This was cause for unexpected behavior on Atomic Host systems without setroubleshoot-server where it's non-trivial and often undesired to add that package. Screenshot: http://cockpit-project.org/blog/images/cockpit-selinux-disabled.png Change: https://github.com/cockpit-project/cockpit/pull/5868 Optionally disable the dependency on libssh ------------------------------------------- When configuring Cockpit, the option |disable-ssh| disables building |cockpit-ssh| and removes the dependency on |libssh|. This is useful when building on an operating system where |libssh| is not available. Change: https://github.com/cockpit-project/cockpit/pull/5743 Get it ------ You can get Cockpit here: http://cockpit-project.org/running.html Cockpit 132 is available in Fedora 25: https://bodhi.fedoraproject.org/updates/cockpit-132-1.fc25 Or download the tarball here: https://github.com/cockpit-project/cockpit/releases/tag/132 Note: Use the packages to install this version of Cockpit. When installing from the tarball, remove /etc/systemd/system/cockpit.service.d/fatal.conf manually afterwards to prevent Cockpit from exiting in rare cases. Thanks, Dominik

1 0

monitor and manage vpn connection in cockpit
by febry140282＠gmail.com 23 Feb '17

23 Feb '17

Hi All, is there a way that i can monitor and manage vpn connection in my server using cockpit? Best regards, Rabbi

1 0

Cockpit weekly meeting 2017-02-13
by Andreas Nilsson 13 Feb '17

13 Feb '17

=========================================== #cockpit: Weekly Cockpit meeting 2017-02-13 =========================================== Meeting started by andreasn at 14:00:26 UTC. The full logs are available at https://meetbot.fedoraproject.org/cockpit/2017-02-13/weekly_cockpit_meeting… . Meeting summary --------------- * Agenda (andreasn, 14:02:17) * Package Plugins (andreasn, 14:04:58) * translations (andreasn, 14:21:31) * Open Floor (andreasn, 14:57:27) Meeting ended at 15:00:35 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * mvollmer (98) * dperpeet (31) * petervo (27) * pitti (15) * andreasn (13) * zodbot (7) * github (2) * garrett_ (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Discussion: Config format for known machines and ssh keys
by Martin Pitt 10 Feb '17

10 Feb '17

Hello all, We currently have a planned feature to clean up/improve our config format for known (remote) machines: https://trello.com/c/WSEOANNY/268-finalize-machines-json-format This is a bit thin and not easy to understand/rationalize. So I took this plus what I remembered from last week's discussion plus some thoughts what would make sense and wrote a draft for what we want to achieve and how it should look like: https://github.com/cockpit-project/cockpit/wiki/Config-format-for-known-mac… I'd appreciate some feedback about whether this makes sense, and opinions about the per-user → global SSH host key transfer [1]. Thanks! Martin [1] My personal opinion is that we should not second-guess what SSH does and STOP doing it.

3 8

Weekly meeting
by Marius Vollmer 06 Feb '17

06 Feb '17

================= #cockpit: meeting ================= Meeting started by mvollmer at 14:02:37 UTC. The full logs are available at https://meetbot.fedoraproject.org/cockpit/2017-02-06/meeting.2017-02-06-14.… . Meeting summary --------------- * Agenda (mvollmer, 14:05:13) * Setting MAC addresses (mvollmer, 14:09:04) * LINK: https://trello.com/c/Do2N49tA/451-networking-allow-changing-mac-and-set-for… (mvollmer, 14:09:28) * Licenses of packages (mvollmer, 14:14:13) * LINK: https://trello.com/c/6ibl1UJu/460-license-files-in-each-package (stefw, 14:24:51) * LINK: https://fosdem.org/2017/schedule/event/mixed_license/ (stefw, 14:28:12) * Anything else? (mvollmer, 14:32:22) Meeting ended at 14:37:02 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * stefw (33) * mvollmer (30) * pitti (13) * zodbot (9) * garrett (3) * larsu (2) * github (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

invalid_request from openshift origin 1.4.0 oauth server
by tolvecky＠frinx.io 02 Feb '17

02 Feb '17

Hello, I've copied the template from http://cockpit-project.org/guide/latest/feature-kubernetes.html#feature-ope… to openshift, then using GUI set OPENSHIFT_OAUTH_PROVIDER_URL to https://my-master:8443/ server and set COCKPIT_KUBE_URL so that it matches route I've created. When trying to access the cockpit URL, I am redirected to https://my-master:8443/oauth/authorize?client_id=cockpit-oauth-client&respo… The oauth server responds with 400 Bad Request: {"error":"invalid_request","error_description":"The request is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or is otherwise malformed."} I already tried oauth with jenkins template that is integrated in openshift, that seems to be working OK (setting those ENV vars was not needed there). OpenShift Master: v1.4.0+208f053 Kubernetes Master: v1.4.0+776c994

2 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

cockpit-devel February 2017