January 2017 - cockpit-devel - Fedora mailing-lists

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

Weekly meeting
by Marius Vollmer 23 Jan '17

23 Jan '17

================= #cockpit: Meeting ================= Meeting started by mvollmer at 14:02:23 UTC. The full logs are available at https://meetbot.fedoraproject.org/cockpit/2017-01-23/meeting.2017-01-23-14.… . Meeting summary --------------- * Agenda (mvollmer, 14:03:43) * the GitHub BUG label (mvollmer, 14:08:25) * LINK: https://github.com/cockpit-project/cockpit/labels/enhancement (pitti, 14:13:23) * Network integration tests (mvollmer, 14:16:08) * Other business (mvollmer, 14:30:03) Meeting ended at 14:32:58 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * mvollmer (38) * dperpeet (32) * pitti (9) * zodbot (5) * larsu (2) * stefw (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Cockpit 128 and 129
by 'Dominik Perpeet' 20 Jan '17

20 Jan '17

http://cockpit-project.org/blog/cockpit-129.html Cockpit is the modern Linux admin interface. We release regularly. Here are the release notes from version 128 and 129 Manage remotes and rebasing in OSTree ------------------------------------- When working with OSTrees on operating systems like Atomic Host [1] there will often be multiple branches to choose from. For example there may be a beta version of the operating system. Thanks to Peter’s work, Cockpit can now switch between branches and view and activate OSTrees from those branches. Also, Cockpit supports managing multiple remotes and viewing their branches. Remotes are a way of describing where OSTree should pull updates from. Take a look at the video below for a demo. Demo: https://youtu.be/dF8M3xq9FcI Change: https://github.com/cockpit-project/cockpit/pull/5599 [1] http://www.projectatomic.io/docs/os-updates/ The subpackage cockpit-dashboard has been split out --------------------------------------------------- The new |cockpit-dashboard| subpackage contains the dashboard itself and the |cockpit-ssh| process. Eventually this paves the way for more flexibility regarding authentication processes, but for now |cockpit-ws| unconditionally depends on |cockpit-dashboard|, and also requires the identical versions. Nothing changes for those who install the |cockpit| package. But this allows more flexibility when using Cockpit for specific use cases. Change: https://github.com/cockpit-project/cockpit/pull/5338 Issues upgrading Cockpit on Debian and Fedora have been fixed ------------------------------------------------------------- Our packaging changes in recent versions broke upgrading Cockpit on Debian and Fedora. This is fixed now and updates should work properly once again. On Atomic, sosreport works again -------------------------------- A bug that prevented the diagnostic tool sosreport from working on Atomic systems was fixed. Generating and accessing these diagnostic reports can be very helpful when diagnosing or reporting an issue on the system. 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 129 is available in Fedora 25: https://bodhi.fedoraproject.org/updates/cockpit-129-1.fc25 Or download the tarball here: https://github.com/cockpit-project/cockpit/releases/tag/129 Thanks, Dominik

1 0

Re: Issue with configuring cockpit in openshift cluster
by Peter 18 Jan '17

18 Jan '17

Looks like the websocket is failing. What browser are you using? Have you tried a multiple browsers? Is there anything in the browser console (usually f12 opens). On 01/18/2017 08:47 PM, Muhammed Roshan wrote: > Hi, > > Please find attached the console view and the log messages. > > Regards, > Muhammed Roshan > > On Wed, Jan 18, 2017 at 10:37 PM, Peter <petervo(a)redhat.com > <mailto:petervo@redhat.com>> wrote: > > On 01/17/2017 11:49 PM, Muhammed Roshan wrote: > > Hi, > > I followed this documentation. > > http://cockpit-project.org/guide/latest/feature-kubernetes.html#feature-ope… > <http://cockpit-project.org/guide/latest/feature-kubernetes.html#feature-ope…> > > Is there anything else I need to configure? > > > No that should be it. What is happening in the browser when you try > to connect? Any errors in the console? > > You can also try adding > > { > "name": "G_MESSAGES_DEBUG", > "value": "all" > }, > > To the "env" array in the template, that will output more info about > what it is trying to do. > > _______________________________________________ > cockpit-devel mailing list -- cockpit-devel(a)lists.fedorahosted.org > <mailto:cockpit-devel@lists.fedorahosted.org> > To unsubscribe send an email to > cockpit-devel-leave(a)lists.fedorahosted.org > <mailto:cockpit-devel-leave@lists.fedorahosted.org> > >

1 0

Issue with configuring cockpit in openshift cluster
by Muhammed Roshan 18 Jan '17

18 Jan '17

Hi, I am new to cockpit. I am trying to install cockpit in openshift cluster. But I am seeing the following errors from the logs. ========== INFO: cockpit-ws: logged in user: roshan MESSAGE: cockpit-protocol: couldn't read from connection: Error receiving data: Connection reset by peer INFO: cockpit-ws: roshan: timed out MESSAGE: cockpit-protocol: couldn't read from connection: Error receiving data: Connection reset by peer MESSAGE: cockpit-protocol: couldn't read from connection: Error receiving data: Connection reset by peer MESSAGE: cockpit-protocol: couldn't read from connection: Error receiving data: Connection reset by peer MESSAGE: cockpit-protocol: couldn't read from connection: Error receiving data: Connection reset by peer MESSAGE: cockpit-protocol: couldn't read from connection: Error receiving data: Connection reset by peer MESSAGE: cockpit-protocol: couldn't read from connection: Error receiving data: Connection reset by peer ========= How to fix this issue.? Any help will be much appreciated. Regards, Muhammed Roshan

3 3

Cockpit in openshift not working
by Muhammed Roshan 18 Jan '17

18 Jan '17

I am trying to configure cockpit in my openshift cluster. I am getting the following error in the logs ======================= INFO: cockpit-ws: logged in user: roshan MESSAGE: cockpit-protocol: couldn't read from connection: Error receiving data: Connection reset by peer MESSAGE: cockpit-protocol: couldn't read from connection: Error receiving data: Connection reset by peer MESSAGE: cockpit-protocol: couldn't read from connection: Error receiving data: Connection reset by peer MESSAGE: cockpit-protocol: couldn't read from connection: Error receiving data: Connection reset by peer MESSAGE: ======================== How to fix this issue. Regards, Muhammed Roshan

1 0

Cockpit Hackfest during DevConfCz
by Andreas Nilsson 17 Jan '17

17 Jan '17

We're planning to do a Cockpit Hackfest during DevConfCz What: We're going to work together to build admin interfaces using Cockpit. Cockpit is a real Linux session in a browser. It's as easy to get started: Building an interface is as easy writing a shell script. But we'll dive deeper and help work out thorny issues with javascript toolkits, Linux APIs and more. When: January 27th, 15:00-18:00 Where: Faculty of Information Technology (VUT FIT) Božetěchova 2 - Brno, Czech Republic https://goo.gl/maps/25jDyjhw7wN2 How: If you have a system with Cockpit already built from source, that's great. If not, we'll help you get set up. In the meantime, take a look at https://github.com/cockpit-project/cockpit/blob/master/HACKING.md More about DevConfCz https://devconf.cz/ Google plus event: https://plus.google.com/events/c00f8kf14biompcv3li3rkpqpt0 - Andreas

1 0

Weekly meeting 2017-01-16
by Andreas Nilsson 16 Jan '17

16 Jan '17

=========================================== #cockpit: Cockpit Weekly Meeting 2016-01-16 =========================================== Meeting started by andreasn at 14:02:24 UTC. The full logs are available at https://meetbot.fedoraproject.org/cockpit/2017-01-16/cockpit_weekly_meeting… . Meeting summary --------------- * Agenda (andreasn, 14:05:25) * Agenda (andreasn, 14:10:39) * Translations (andreasn, 14:11:22) * NFS Role (andreasn, 14:20:57) * LINK: https://github.com/cockpit-project/cockpit/wiki/Feature:-NFS-Server (andreasn, 14:21:11) * Firewall Support (andreasn, 14:29:53) * Open Floor (andreasn, 14:36:39) Meeting ended at 14:40:21 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * andreasn (43) * dperpeet (40) * stefw (11) * bhakti (8) * mvollmer (7) * zodbot (7) * larsu (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Terminal on Cockpit - Increase size?
by luis＠bitamins.net 16 Jan '17

16 Jan '17

Is it possible to increase the size of the terminal window tool on cockpit. It seems that it is limited to a 640x480 iframe. I would like to use the whole frame to run the terminal. Is this possible? I've looked at the documentation and couldn't find a way to change the size of the terminal display. Best regards, Peter

2 1

Few requirements for gluster deployment in cockpit-ovirt plugin.
by Ramesh Nachimuthu 10 Jan '17

10 Jan '17

Hi, We are working with oVirt team to integrate Gluster deployment in cockpit-ovirt plugin. We are using an ansible based tool called gdeploy to do the actual deployment. We have few requirements in cockpit to support this flow in UI. 1. Listing all available storage devices in the system. We would like to show a list of available free storage devices in the system so that user can pick any of them for gluster deployment. I know cockpit already shows this in the storage section. But we need it in the gluster deployment wizard. Is there an API which we can use to show a similar list in our wizard?. 2. Setting up password less SSH to communicate with other nodes. Ansible needs password less SSH to access other nodes. Is there way to setup this through cockpit?. 3. Task Runner Is there a way to create long running tasks and track them through cockpit UI?. To me more specific, in our case, whole gluster deployment take long time like more than hour when we have to install more package. So instead of keeping the user waiting and watching the wizard, we would like to close the wizard and create a task and show it some where in the UI(Top right corner?). When user wants to see the status, he can click and open the task and see the status. We can also show a notification when it completes. oVirt feature page: http://www.ovirt.org/develop/release-management/features/gluster/gdeploy-co… Regards, Ramesh

3 3

Cockpit on Debian Jessie
by Stef Walter 10 Jan '17

10 Jan '17

The repository that contains the weekly builds for Debian now supports Debian Jessie. You can see instructions here: http://cockpit-project.org/running.html Or use the following repository in your sources.list: deb http://repo-cockpitproject.rhcloud.com/debian/ jessie main Unfortunately at the same time Debian Unstable has had dependency problems and the last few releases of Cockpit did not build properly there. Hopefully that will resolve itself soon. Cheers, Stef

2 1

Cockpit 126 and 127
by Stef Walter 10 Jan '17

10 Jan '17

http://cockpit-project.org/blog/cockpit-127.html Cockpit is the modern Linux admin interface. We release regularly. Here are the release notes from version 126 and 127 Show security scan information about container images ----------------------------------------------------- Lars did work to show security scan information about container images. The displayed scans happen via the atomic scan [1] tools and the data comes from the OpenSCAP [2] system. Take a look at the video below. Demo: https://www.youtube.com/watch?v=zANUkEmfaAk Change: https://github.com/cockpit-project/cockpit/pull/4952 https://github.com/cockpit-project/cockpit/pull/5259 https://github.com/cockpit-project/cockpit/pull/5686 [1] https://developers.redhat.com/blog/2016/05/02/introducing-atomic-scan-conta… [2] https://www.open-scap.org/ Choose whether password is cached and reused on the login screen ---------------------------------------------------------------- The typical workflow for peforming privileged tasks on a Linux system is to log in as a non-root user and then use sudo or Polkit to escalate privileges. Stef did work to make Cockpit's privilege escalation reflect this properly. Cockpit now has an option on the login screen to "Reuse my password for privileged tasks". Checking this option automatically performs reuses the login password as necessary to escalate privileges. If you leave this box unchecked then Cockpit will behave exactly as a normal user login without special privileges. In the future we'll have a way to enable this option once logged in, and retype your password inside of the logged in session. Demo: https://www.youtube.com/watch?v=TW6UsPbNkV4 Change: https://github.com/cockpit-project/cockpit/pull/5522 The remotectl command can now combine certificate and key files --------------------------------------------------------------- Peter did work to make it easier to use TLS certificate and key files with Cockpit for port 9090. Normally the server certificate(s) and key need to be combined into a single file and placed into the /etc/cockpit/ws-certs.d directory. The remotectl command that comes with Cockpit can now be used to build such a combined file. Due to this, when Cockpit is deployed as an Openshift Pod it can use certificates provided by Openshift. Docs: man remotectl Change: https://github.com/cockpit-project/cockpit/pull/5525 Cockpit respects /etc/shells ---------------------------- Martin fixed Cockpit so it only allows the user to log in if the user has a valid shell listed in /etc/shells. In addition bugs on Ubuntu and Debian have been fixed where users were created without valid shells. Change: https://github.com/cockpit-project/cockpit/pull/5665 Allow renaming of active devices in networking interface -------------------------------------------------------- You can now rename network devices like bonds or bridges while they're active. The change will apply immediately and without any interruption in service. Change: https://github.com/cockpit-project/cockpit/pull/5570 Rename cockpit-shell to cockpit-system -------------------------------------- The cockpit-shell subpackage has been renamed to cockpit-system to better reflect its focus: configuring and troubleshooting the local system. Change: https://github.com/cockpit-project/cockpit/pull/5600 Kerberos authentication now work even if gss-proxy is in use ------------------------------------------------------------ Sometimes Kerberos (or GSSAPI) single-sign-on authentication requires multiple round trips to the server. Cockpit now supports this properly, and the end result is that SSO works even when fancy things like GSS-Proxy [3] are in use. Change: https://github.com/cockpit-project/cockpit/pull/5495 [3] https://fedorahosted.org/gss-proxy/ Get it ------ You can get Cockpit here: http://cockpit-project.org/running.html Cockpit 127 is available in Fedora 25: https://bodhi.fedoraproject.org/updates/cockpit-127-1.fc25 Or download the tarball here: https://github.com/cockpit-project/cockpit/releases/tag/127 Take care, Stef

1 0

Weekly meeting
by Marius Vollmer 09 Jan '17

09 Jan '17

================= #cockpit: meeting ================= Meeting started by mvollmer at 14:03:11 UTC. The full logs are available at https://meetbot.fedoraproject.org/cockpit/2017-01-09/meeting.2017-01-09-14.… . Meeting summary --------------- * Agenda (mvollmer, 14:03:27) * virt-build vs virt-install (mvollmer, 14:07:55) * firewall (mvollmer, 14:21:31) * LINK: https://github.com/cockpit-project/cockpit/wiki/Feature:-Firewall (andreasn, 14:21:53) * NFS Server config (mvollmer, 14:36:53) * LINK: https://raw.githubusercontent.com/cockpit-project/cockpit-design/master/rol… (andreasn, 14:58:30) * Any other business (mvollmer, 15:07:06) Meeting ended at 15:10:10 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * mvollmer (88) * dperpeet (60) * famicom (46) * sgallagh (38) * andreasn (27) * bhakti (13) * zodbot (6) * pitti (3) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Script to create a cockpit devel VM
by Martin Pitt 05 Jan '17

05 Jan '17

Hello all, first, a quick intro of myself: I'm Martin Pitt (nicknamed "pitti" on IRC and IRL) and joined Red Hat's Cockpit team yesterday. Until then I've been a Debian developer for about 14 years and an Ubuntu developer for about 12½. I've touched a lot of things over the years, but most recently I've mostly been involved in plumbing (systemd, networking, udisks and the like) and Ubuntu's CI. While learning about cockpit and how to test it I put together a small script [1] that creates a Fedora 25 based Cockpit development VM out of thin air (using mkosi). This contains a running cockpit (as it comes with F25) as well as all build and test dependencies. This helped me personally to figure out some issues with setting up the tests (like [2]), gives me a tool to get a reproducible dev environment without cluttering my host system with lots of build/test depends, and I can use QEMU's snapshots to reset to a clean state. Stef mentioned that this might also be useful for improving our isolation in GitHub's integration tests. How does it look like? You call it with the output VM path and cockpit's git checkout directory as arguments, it will do some grinding and eventually give you some info how to use it: | $ ~/cockpit-dev-vm.sh /srv/vm/cockpit.img ~/upstream/cockpit | [...] | Run the VM (possibly with appending "-snapshot"): | | qemu-system-x86_64 -enable-kvm -cpu host -nographic -m 6144 -bios /usr/share/edk2/ovmf/OVMF_CODE.fd \ | -virtfs local,id=src,path=.,security_model=none,mount_tag=src,readonly \ | -net nic,model=virtio -net user,hostfwd=tcp::22000-:22,hostfwd=tcp::9099-:9090 /srv/vm/cockpit.img | | Cockpit: https://localhost:9099 | SSH: ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o CheckHostIP=no -p 22000 test@localhost | (password "test") | | Read-only view of . is at /src After booting the VM and ssh'ing in, you can copy the read-only view of outside cockpit tree to writable place: | cp -a /src cockpit | cd cockpit ... and run some integration test: | $ sudo test/vm-prep | $ test/verify/testsuite-prepare | # the following is a bug [2], PR is pending | $ npm install phantomjs-prebuilt | | $ test/verify/check-login The binding of the outside checkout dir is useful so that the VM doesn't have to re-download the large test VMs, and you don't need to spend so much VM disk space on them. I'm not too happy about the read-only /src yet, I'll see if it's feasible to automatically set up an overlayfs for ~test/cockpit instead. Note that the VM gets 6 GiB of RAM, as some of its inner VMs are quite large. So you need sufficient RAM on your host. Also note that this requires booting with "kvm-intel.nested=1" option on the kernel command line -- while /etc/modprobe.d/kvm-intel.conf apparently intends to supply that option, it doesn't work at least in F25. Maybe this is useful for someone/something else, please let me know if you have ideas for improvements. Thanks, Martin [1] http://www.piware.de/tools/cockpit-dev-vm [2] https://github.com/cockpit-project/cockpit/issues/5676 -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)

4 6

Feature:Firewall Wireframes Feedback
by Bhakti Bhikne 04 Jan '17

04 Jan '17

Hello everyone! I am Bhakti Bhikne and I am an Outreachy intern working on the firewall support of Cockpit. I've been working on this for sometime now and have created a few wireframes [1] for the same .I would really appreciate if I could get some feedback on the wireframes. 1.https://github.com/cockpit-project/cockpit/wiki/Feature:-Firewall#wirefra… Thank You for your time and feedback! Regards, Bhakti

1 0

Weekly meeting
by Marius Vollmer 02 Jan '17

02 Jan '17

================= #cockpit: meeting ================= Meeting started by mvollmer at 14:02:49 UTC. The full logs are available at https://meetbot.fedoraproject.org/cockpit/2017-01-02/meeting.2017-01-02-14.… . Meeting summary --------------- * Agenda (mvollmer, 14:06:05) * NFS Server (mvollmer, 14:08:05) * VLAN testing (mvollmer, 14:13:55) * AOB (mvollmer, 14:19:34) Meeting ended at 14:20:21 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * mvollmer (40) * stefw (10) * zodbot (5) * github (2) 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 January 2017