I presented a Cockpit talk at Devconf 2015 in Brno. The goal was to get
people to understand Cockpit and how it's put together.
Here's the video of the talk at Devconf. It just has the screen in it,
but that's pretty useful since most of the talk is demos.
On 07.01.2015 14:02, Mark Constable wrote:
One thing was unresolved was the instructions for how to get it running
on Arch Linux.
Damn I miss using Arch but I have to go with a system supported by
mainstream
hosting providers. Every VPS provider offers Ubuntu/Debian installs but
DO is
the
On 08.01.2015 11:12, Marius Vollmer wrote:
I wrote down some notes about the Big Storage Refresh:
https://github.com/cockpit-project/cockpit/wiki/Storage-refresh
It's quite terse... so be sure to ask lots of question if/when you start
to dig into it.
Of course, it's not expected
Wanted to include a partial response below to the list about extending
Cockpit, in case it helps anyone.
On 08.01.2015 04:39, Mark Constable wrote:
My main interest with cockpit, once I can use it on a current ubuntu
server, will be to provide an ultra simple PHP+BS4 frontend so the
cockpit
Today, we merged a further simplification of how our Cockpit packages
are loaded:
https://github.com/cockpit-project/cockpit/pull/1869
If you're tracking Cockpit from git master, you'll need to do the following:
$ rm ~/.local/share/cockpit/*
$ sudo rm -rf /usr/share/cockpit/*
$ cd
I've added a bit to the Cockpit Coding Guidelines about AMD modules:
https://github.com/cockpit-project/cockpit/wiki/Cockpit-Coding-Guidelines
Some of us were discussing AMD modules [1] with global side-effects.
Normally this would be frowned on, but in real life this comes up all
the time.
We
On 22.06.2015 05:35, Marius Vollmer wrote:
Stef Walter st...@redhat.com writes:
On 18.06.2015 03:17, Marius Vollmer wrote:
Once we have feature negotiation, I think we should not ignore unknown
messages anymore. It is better to know whether or not your peer will
understand a specific
In the next release of Cockpit some branding changes are landing:
* Don't ship logos or trademarked material in cockpit packages.
* Do ship all other branding upstream.
* Use /etc/os-release to determine which branding to use.
The reasoning for this is that cockpit-ws is often run in a
On 24.08.2015 09:03, Stef Walter wrote:
On 24.08.2015 08:54, Marius Vollmer wrote:
Peter pete...@redhat.com writes:
PROS:
- It works and uses a newer OS (Ubuntu 14)
- Allows you to ssh into instances to run / debug tests.
This is very, very nice.
CONS:
Obviously another big con
#cockpit Meeting
Meeting started by stefw at 13:02:41 UTC. The full logs are available at
http://meetbot.fedoraproject.org/cockpit/2015-08-24/cockpit.2015-08-24-13.02.log.html
.
Meeting summary
---
* Agenda (stefw, 13:02:47)
*
Sounds good. I guess we should try and get a cockpit group?
Stef
On 15.10.2015 14:42, Stephen Gallagher wrote:
>
> Should I talk to the COPR folks about converting the sgallagh
> cockpit-preview repo over?
>
>
>
> Forwarded Message
> Subject: Announce: Group projects in
There's a leak in cockpit-0.77 where browser resources spiral out of
control after a while, and cockpit-bridge starts using up crazy amounts
of CPU.
https://github.com/cockpit-project/cockpit/issues/2821
This should be fixed in 0.78. The work-around is to install cockpit-pcp
on your system.
This is a summary of the Cockpit weekly release. This week it was 0.86
SOS Reporting
-
Users can now prepare an SOS Report containing information about the
system and send it to their support representative.
https://youtu.be/-6rfWUoOQbs
This is a summary of the Cockpit weekly release. This week it was 0.87
Fix login on Windows
Cockpit no longer prompts for a strange second login (which had to do
with SSO) on Windows. There are some remaining issues with how Cockpit
works on Internet Explorer, but most have
On 21.12.2015 20:54, Joe Brockmeier wrote:
> On 12/21/2015 01:15 PM, Stef Walter wrote:
>> There will be a Cockpit Hackfest at Devconf in Brno. Admisssion is free.
>>
>> http://devconf.cz/
>>
>> Friday, February 5th, 2016
>> 16:30 - 18:10
>> Brno Univer
This is a summary of the Cockpit weekly release. This week it was 0.88
OSTree upgrades and rollbacks
-
Peter worked to finish the basic OSTree UI has been merged into Cockpit.
This lets the admin perform upgrades and rollbacks on Atomic Host.
Colin, Peter and the
On 18.12.2015 21:51, David Hugh Malcolm wrote:
>> This is a summary of the Cockpit weekly release. This week it was
>> 0.88
>>
>>
>> OSTree upgrades and rollbacks -
>>
>> Peter worked to finish the basic OSTree UI has been merged into
>> Cockpit. This lets the admin
On 21.12.2015 15:56, Douglas Schilling Landgraf wrote:
> As the next ovirt node will be integrated to cockpit, and we will
> install a release rpm into the host to update /etc/os-release,
I've taken a moment to document how branding works:
This is a summary of the Cockpit weekly release. This week it was 0.85
Varying users on dashboard machines
---
Cockpit now supports adding machines to the dashboard with different
user logins for each one. This can be useful in cases where you're
adding cloud
On 02.06.2016 12:33, Jakub Filak wrote:
> On 06/01/2016 04:49 PM, Stef Walter wrote:
>> On 27.05.2016 13:17, Jakub Filak wrote:
>>> The module uses some experimental work and it is definitely not
>>> production
>>> ready. However, we would love to hear any feedb
On 26.05.2016 14:56, Marek Libra wrote:
> Hi,
>
> I was further thinking about splitting the core cockpit and the
> recent 'pkg' plugins to allow independent build for each of them. I
> would expect that plugins will share same set of run/build
> dependencies and I don't think the 'first class'
On 27.05.2016 13:17, Jakub Filak wrote:
> Hello Cockpit crew,
>
> I am working on ABRT and I am the author of the 'org.freedesktop.Problems'
> support idea [1].
>
> I would like to let you that we have developed a Cockpit module [2] showing
> problems detected by ABRT and allowing users to
On 21.06.2016 19:24, Josh Berkus wrote:
> On 06/20/2016 08:44 AM, Stef Walter wrote:
>> On 02.06.2016 17:13, Josh Berkus wrote:
>>> Folks,
>>>
>>> So because of my conference schedule in June, I'm trying to get the demo
>>> atomic cluster f
On 02.06.2016 17:13, Josh Berkus wrote:
> Folks,
>
> So because of my conference schedule in June, I'm trying to get the demo
> atomic cluster for Summit kitted out sooner rather than later.
>
> For that reason, I'd like to know:
>
> 1. What do you want to demo on it? You're welcome to install
On 11.01.2016 11:03, Jan Chaloupka wrote:
> Hi,
>
> cockpit integration tests have proofed to be very useful for discovering
> regression and bugs for kubernetes.
> The current workflow of updating kubernetes is to rebase/rebuilt
> kubernetes, run very basic tests and hope it will work.
> The
This is a summary of the Cockpit weekly release. This week it was 0.91
Testing on RHEL Atomic
--
Marius did some work last week and got each and started testing each and
every pull request on the latest RHEL Atomic. We'd been testing on
Fedora Atomic previously, so this adds
A summary of the Cockpit weekly release. There’s a new release every
week, although it's been a while since the release notes were posted.
Here are the highlights from this weeks 0.107 through 0.111 releases.
SELinux Enforcing Policy
You can now temporarily disable
This is a summary of the Cockpit weekly release. This week it was 0.95
iSCSI initiator support
---
The iSCSI support that Marius worked on with the storaged folks has
finally landed in a Cockpit release. It was waiting on fixes in some
dependencies. Have a look:
Demo:
Looks like the tests produce different output than are expected.
Perhaps some changes are necessary to the normalize() function in
test-list-public-keys.sh file?
___
cockpit-devel mailing list
cockpit-devel@lists.fedorahosted.org
On 21.01.2016 03:39, Joe Brockmeier wrote:
> On 01/20/2016 04:05 PM, Stef Walter wrote:
>> This is a summary of the Cockpit weekly release. This week it was 0.92
>
> The numbering suggests we're nearing a 1.0 release soon? Should we talk
> about how we can promote that and
This is a summary of the Cockpit weekly release. This week it was 0.93
Set CPU performance profile via tuned
-
Cockpit can now talk to tuned and set the CPU performance profile of the
system. Thanks to Ryan Barry for doing the initial prototype, and
Jaroslav
This is a summary of the Cockpit weekly release. This week it was 0.92
SOSReport on Atomic
---
When run on Atomic, Cockpit's sosreport diagnostics will now invoke the
sosreport tool in a privileged container via the 'atomic run' command.
On 09.03.2016 15:45, adri...@noverit.com wrote:
> Hello team,
>
> is there any chance use the cockpit-bridge alone, without cockpit-ws? We
> are interested in integration of cockpit-bridge in our custom ws for a
> management platform project. The idea is to use cockpit-bridge to
> interact with
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
On 23.03.2016 15:34, Martin Polednik wrote:
>>> 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
A summary of the Cockpit weekly release. Over the last two weeks that
was 0.98 and 0.99
Kubernetes Cockpit Pod
--
The Kubernetes cluster admin interface is now deployable as a kubernetes
pod. Peter did a lot of work to make this happen. It's a good example of
taking just one
On 23.03.2016 12:00, Stephen Gallagher wrote:
> On 03/23/2016 05:06 AM, Marek Libra wrote:
>> Hi,
>>
>> I would like to hear your opinion on adding Virtual Machine status and
>> management capability to the Cockpit.
>>
>
> I've been pitching this for about a year now:
>
I hope it's okay if I post my response to the cockpit mailing list.
On 06.03.2016 11:01, Jean-Paul Geerets wrote:
> recently i fount the application "cockpit".
> it looks great and i wanna give it a try on my vps.
> it is a openvz with centos7 on it.
>
> install was very easy, not a problem.
>
On 08.03.2016 06:36, Josh Berkus wrote:
> Folks,
>
> Is there a version of the Cockpit container which has the beta
> kubernetes support available? I'm headed to Kubecon and would love to
> show it off.
Indeed there is. It's on the Docker hub at: cockpit/kubernetes:wip
This is a summary of the Cockpit weekly release ... yup we missed a
couple weeks. This week it was 0.96
Cockpit now limits authentication requests
--
Cockpit now keeps itself from spawning too many processes to handle
authentication requests. The
On 27.02.2016 12:21, tdi...@gmail.com wrote:
> Hi Stef, thank you for your answer, which I missed it and saw it just
> now...
>
> is cockpit "pluggable" in any way, meaning that I can creare a plugin
> that just alter/enhance existing modules?
>
> for example, some features now available should
On 08.03.2016 15:58, Harish Anand wrote:
> Hello,
>
> I am interested in the development of Cockpit support for systemd timers
> as part of GSoC 2016. I am an undergraduate student pursuing Computer
> Science and Engineering in India. I would like propose an idea on
> modifying the timer support
A summary of the Cockpit weekly release. There’s a new release every
week. Here are the highlights from this weeks 0.100 release. Even though
0.100 may seem to be a magical number … it’s really just the number
after 0.99
SELinux Troubleshooting
---
Cockpit can now help you
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
A summary of the Cockpit weekly release. There’s a new release every
week. Here are the highlights from this weeks 0.106 release.
Stable Cockpit Styles
-
One of the annoying things about CSS is that when you bring in
stylesheets from multiple projects, they can conflict. You
On 29.04.2016 16:56, Eduardo Hernacki wrote:
> 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 ifCockpit could provide a method to
I'm working to make the Cockpit javascript and CSS in the base package
stable and allow out of tree building of components and plugins.
One of the changes is adding a namespace to each of our own CSS classes
in the base package. This is similar to what Patternfly does. The idea
is to avoid
A summary of the Cockpit weekly release. There’s a new release every
week, although it's been a month since the release notes were posted.
Here are the highlights from this weeks 0.114 through 0.117 releases.
Configure volumes and environment for a Docker container
A summary of the Cockpit weekly release. There's a new release every
week. Here are the highlights from the 0.112 and 0.113 releases.
Display time information for systemd timer jobs
---
Harish Anand a Google Summer of Code student working on Cockpit,
On 07.07.2016 18:55, Josh Berkus wrote:
> On 07/07/2016 09:50 AM, Stef Walter wrote:
>> A summary of the Cockpit weekly release. There's a new release every
>> week. Here are the highlights from the 0.112 and 0.113 releases.
>
> Mind if I put this up as a blog post?
>
S
Thanks for summarizing this well.
It's worth noting that Peter Volpe is moving the libssh code that
consumes SSH keys ... and I believe he has working code for using
/etc/ssh/known_hosts.
On 07.02.2017 15:17, Martin Pitt wrote:
> Hello all,
>
> We currently have a planned feature to clean
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
On 18.01.2017 07:46, Muhammed Roshan wrote:
> 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.
How are you installing Cockpit in the cluster? Are you following
instructions? In addition do you know which
On 18.08.2016 22:12, Josh Berkus wrote:
> On 08/18/2016 02:24 AM, Stef Walter wrote:
>> Yesterday several of us (roughly the top contributors [1] to Cockpit)
>> discussed removing the '0.x' from the Cockpit version number.
>>
>> The plan is from here on out to ju
On 19.08.2016 12:53, Stephen Gallagher wrote:
> On 08/19/2016 04:20 AM, Stef Walter wrote:
>> But if you have reasons not to do that, I'd love to hear them.
>>
>
>
> Well, one of the fundamental problems with going to a whole-integer release
> number is that it ba
On 22.08.2016 18:25, Josh Berkus wrote:
> Stef,
>
>> Cockpit is continuously developed, integrated, and delivered. We're able
>> to do that with aggressive upstream testing and feedback. On busy days
>> 10,000 of instances are started to test Cockpit changes.
>>
>> Out of the 50 or so releases in
On 06.09.2016 17:15, Josh Berkus wrote:
> On 08/22/2016 08:11 AM, Stef Walter wrote:
>> So all that said, I think this is *still* something we want to do: have
>> monotonously increasing version numbers.
>
> OK.
>
> There's one other technical issue: how to handle bugf
http://cockpit-project.org/blog/cockpit-118.html
Cockpit is the modern Linux admin interface There's usually a release
every week, but this time around we were delinquent and it's been
nearly a month.
You'll notice that we've dropped the 0.x from the beginning of the
version numbers. This
Cockpit should display the command used to resolve the situation
(similar to what the ssh command does).
Which version of Cockpit are you using? I think there were a few
versions that didn't have that message displayed. 0.103 fixed the
problem if I remember correctly.
The command looks like
Yesterday several of us (roughly the top contributors [1] to Cockpit)
discussed removing the '0.x' from the Cockpit version number.
The plan is from here on out to just go with integer versions, starting
with version '118' following version '0.117'.
Cockpit releases weekly. Some versions of
On 16.11.2016 09:17, Fuji San wrote:
> Hi,
>
> I use version 117 of cockpit distributed packages from Fedora
> repositories on the server as well as on the clients. Reloading
> cockpit with systemd doesn't help. I've tried that before asking on
> this mailing list.
Could you install
On 16.11.2016 16:40, Matej Habrnal wrote:
> Hello,
>
> I'd like to inform you there is a new feature in ABRT.
> Now, it's is possible to report problems into systemd journal.
> If some problem occurs, abrt sends a catalog message into systemd
> journal with some details about the problem (e.g.
On 18.11.2016 08:02, Jakub Filak wrote:
> Stef,
>
> this is part of our effort to better integrate with Cockpit. On this May, I
> posted a video here and the video is showing how users can report crashes
> via ABRT Cockpit module [1].
>
> You asked me if there is a relevant journal entry, but
On 28.10.2016 15:21, Lucas Castro wrote:
>
>
> On 28-10-2016 06:58, Stef Walter wrote:
>> On 28.10.2016 05:36, Lucas Castro wrote:
>>> Cockpit depends of babel, and babel-cli has been moved to babel-cli package.
>> Does 'npm install' fail for you? It still works h
Nice work! I did some review on the pull request. For me the fundamental
things that need to happen before merging this initial implementation are:
* UX (review by a designer)
* Monitoring for changes
* Unit tests
* Integration tests
Seems like IOMMU Grouups, Topology, USB, and SCSI could be
On 05.01.2017 09:59, Martin Pitt wrote:
> Hello Marius,
>
> thanks for sharing your setup!
>
> Marius Vollmer [2017-01-05 10:44 +0200]:
>> - I run the integration tests on my bare metal laptop. They have few
>>dependencies and do all their destructive work inside their own VMs,
>>so
On 04.01.2017 16:45, Martin Pitt wrote:
> 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
>
On 10.01.2017 08:09, Ramesh Nachimuthu wrote:
> 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.
>
>
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
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
On 28.06.2017 16:02, Tom McKay wrote:
> The project I was working on, foreman[1], has started using react.js and
> redux for portions of the UI. I have done any work in this area before
> but noticed that cockpit has a good number of jsx files.
Many sections of Cockpit use react. And the
On 25.06.2017 07:46, Stef Walter wrote:
> On 22.06.2017 18:18, Josh Berkus wrote:
>> On 06/21/2017 11:51 PM, Stef Walter wrote:
>>> Many of the Cockpit folks are having a Hackfest in Karlsruhe, Germany
>>> from the 26th of June until the 30th. You might have already hear
Had fun talking with the guys at FLOSS Weekly about Cockpit, usability
and automation. Here's the interview:
https://twit.tv/shows/floss-weekly/episodes/440
Cheers,
Stef
___
cockpit-devel mailing list -- cockpit-devel@lists.fedorahosted.org
To
On 22.06.2017 18:18, Josh Berkus wrote:
> On 06/21/2017 11:51 PM, Stef Walter wrote:
>> Many of the Cockpit folks are having a Hackfest in Karlsruhe, Germany
>> from the 26th of June until the 30th. You might have already heard about
>> this from other postings
On 18.05.2017 21:03, Josh Berkus wrote:
> Cockpit folks:
>
> Both openshift-ansible and most Kubernetes installers cause port 9090 to
> be blocked or routed to the orchestration system. For that matter, I
> expect that a default firewalld also blocks it.
>
> Is there some way we can unblock the
On 07.06.2017 11:02, Daniel P. Berrange wrote:
> On Wed, Jun 07, 2017 at 10:47:25AM +0200, Stef Walter wrote:
>> On 07.06.2017 07:49, Martin Pitt wrote:
>>> Hello Richard,
>>>
>>> Richard W.M. Jones [2017-05-31 18:00 +0100]:
>>>> I agree with
On 07.06.2017 07:49, Martin Pitt wrote:
> Hello Richard,
>
> Richard W.M. Jones [2017-05-31 18:00 +0100]:
>> I agree with others that as things stand you will need a REST or DBus
>> or similar API added to libvirt.
>>
>> However have you considered using gobject-introspection to generate
>> new
On 07.06.2017 10:55, Martin Pitt wrote:
> Stef Walter [2017-06-07 10:47 +0200]:
>> On 07.06.2017 07:49, Martin Pitt wrote:
>>> C/GI interfaces also don't map well to D-Bus, i. e. it's not practical to
>>> autogenerate a D-Bus interface for a given GI API. This still wo
On 06.06.2017 12:13, Daniel P. Berrange wrote:
> On Tue, Jun 06, 2017 at 06:07:21PM +0200, Stef Walter wrote:
>> On 06.06.2017 17:17, Daniel P. Berrange wrote:
>>> On Tue, Jun 06, 2017 at 05:11:55PM +0200, Peter Krempa wrote:
>>>> On Tue, Jun 06, 2017 at 07:45:10 -070
On 21.09.2017 01:55, Peter wrote:
> I started putting together a plan on how we might be able to implement
> machine isolation in cockpit building off the somewhat stalled sandbox
> work that Stef started.
>
> https://github.com/cockpit-project/cockpit/wiki/Machine-isolation
>
> I'd appreciate
On 17.10.2017 11:24, Radka Janekova wrote:
>> Sorry to hear that happened. Cockpit depends on Network manager to
> provide it's network functionality. Network manager is pretty standard
> part of many linux distros. Having the cockpit-networking package depend
> on it is not a mistake, it needs to
I like the idea. Andreas, don't we already have designs for containers
that have gone "bad" (such as need security updates, failed scans) ...
This seems like related info. Where a container exited due to crashing
and has further info to aid investigation.
Cheers,
Stef
On 06.09.2017 17:15,
On 12.09.2017 13:17, Stef Walter wrote:
> I like the idea. Andreas, don't we already have designs for containers
> that have gone "bad" (such as need security updates, failed scans) ...
>
> This seems like related info. Where a container exited due to crashing
> an
On 22.11.2017 06:31, Andreas Nilsson wrote:
> On 2017-10-19 11:44, Marek Libra wrote:
>> Hi,
>>
>> I would like to renew the effort on Host Devices for Cockpit [1].
>>
>> To move forward, let's implement it step by step while opening brand
>> new PR picking just a subset of the already implemented
Andreas, does this use the listing view, so that once additional
features (perhaps even per device) can be added when expanding or
navigating to the view of a device?
Stef
On 14.12.2017 03:05, Marek Libra wrote:
> Andreas, thanks for that!
>
> So far it makes sense for me.
> Tthe covered
p the URL as in the
> manifest?
This is a bug in Cockpit. I've filed a pull request to fix it. If all
goes well, this fix should be included in Cockpit version 170, which is
due next week.
https://github.com/cockpit-project/cockpit/pull/9348
Cheers,
Stef
--
Stef Walter
Platform Engine
On 18.06.2018 16:09, Mark Reynolds wrote:
> Hello,
>
> So I need to loop over a bunch of cockpit.spawns, but after each one is
> done I need to print a success message
>
> for (var attr in mods){
> var cmd = [DSCONF, '-j', 'ldapi://%2fvar%2frun%2f' + server_id +
> '.socket','config',
fferent kinds of credentials could be passed.
Also, do you feeling for what kind of credentials you'd choose to pass
Foreman/Satellite?
Stef
--
Stef Walter
Platform Engineering
Red Hat
signature.asc
Description: OpenPGP digital signature
//getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/cockpit-devel@lists.fedorahosted.org/message/XM2H7IOW3YAYAMUQTHCV2DKOVSM2HHMV/
>
--
Stef Walter
Platform Eng
On 11.01.2018 15:03, Marius Vollmer wrote:
> Stef Walter <st...@redhat.com> writes:
>
>> On 11.01.2018 13:17, Marius Vollmer wrote:
>>> Hi,
>>>
>>> the Fleet Commander should now show up as a Cockpit application on
>>> Fedora 27 (and ma
On 12.01.2018 09:14, Marius Vollmer wrote:
> Stef Walter <st...@redhat.com> writes:
>
>> On 11.01.2018 15:03, Marius Vollmer wrote:
>>> Stef Walter <st...@redhat.com> writes:
>>>
>>>> On 11.01.2018 13:17, Marius Vollmer wrote:
>&g
try it out and give advice.
Stef
On 02.02.2018 18:58, Iván Chavero wrote:
> El jue, 01-02-2018 a las 06:30 +0100, Stef Walter escribió:
>> Maybe something like this, or its related code would be a place to
>> start
>> investigating?
>>
>&g
Maybe something like this, or its related code would be a place to start
investigating?
pkg/kubernetes/scripts/main.js:
KubeDiscoverSettingsProvider.KubeDiscoverSettingsFactory =
"cockpitKubeDiscoverSettings";
Cheers,
Stef
On 01.02.2018 04:12, Iván Chavero wrote:
> Hello,
>
> I'm writing a
On 03.02.2018 02:37, John Pearson wrote:
> I manage a fleet of linux devices and I need a way to send telemtry
> data(CPU, memory, drives, etc.) from devices to a centralized server
> and also send commands(linux service restarts for example) from server
> to devices to execute on the device. I
On 07.02.2018 08:43, Martin Pitt wrote:
> Hello Stef,
>
> Stef Walter [2018-02-06 14:30 +0100]:
>> I'd like to remove the following outdated repos from the
>> https://github.com/cockpit-project/
>>
>> * jsx-transform (fork no longer used)
>> * less.js (fo
I'd like to remove the following outdated repos from the
https://github.com/cockpit-project/
* jsx-transform (fork no longer used)
* less.js (fork no longer used)
* pam_selfpolkit (never used)
* registry-image-widgets (moved to https://github.com/openshift )
* system-api-roles (moved to
On 07.03.2018 16:05, Mark Reynolds wrote:
> Hello,
>
> So I am running into two issues with file watching on cockpit-151-2
>
> [1] The first one appears to be a permissions issue. So I am trying to
> watch a file that the Cockpit user does have immediate permissions to,
> but the Cockpit user
No worries. Did you see the same behavior when accessing your flask
service with curl? If not, you may have run into a bug in the HTTP
client code of Cockpit, and I'd be interested in reproducing.
Stef
On 08/11/2018 05:42, Paul Cuzner wrote:
>
> This now looks like an app library problem. My
On 08/10/2018 22:24, Paul Cuzner wrote:> Hi,
>
> I can see in the docs that there is http based support for cockpit to
> interact with HTTP endpoint, which works fine.
>
> Could anyone clarify the approach when the endpoint that the plugin
> needs to interact with is https instead of http (I'm
do not have anything appropriate
to put under "authority" in order to make them validate.
Stef
> On Tue, Oct 9, 2018 at 7:38 PM Stef Walter wrote:
>>
>> On 08/10/2018 22:24, Paul Cuzner wrote:> Hi,
>>>
>>> I can see in the docs that there is http
1 - 100 of 115 matches
Mail list logo
