Problems in container overview
by Matej Marusak
The ABRT team had an idea - ABRT can catch problems from containers and ABRT displays problems in Cockpit. So why not to show problems that happened in containers directly under container overview?
Here I have a short user story for you (inspired by existing one):
Robert Paulsson is a developer at a small IT company. He's a senior engineer, but got tossed the sysadmin hat at the company. The company have 3 internal servers that runs various services that the R&D unit needs for their day to day basis. He is responsible for these servers and services that are running on them.
Robert logs into the system via Cockpit and goes to the containers page. (version 1. - He immediately sees that something is wrong with running container (there is exclamation mark, see below), so he opens it to learn more.) (version 2. His colleagues brought to his notice, that they are not able to connect to one internal instance of their product. He knows in which container this instance is running, so he opens it to learn more.) He notices 'Problems' tab, opens it and sees that there is some problem. Clicks on it and is redirected into ABRT journal log. After reporting he finds out that the issue is known. He is able to fix this issue.
How it could work:
(navigate to Containers)
Open some container with the dropdown on the left of container name.
You should see container details. Our idea was to add another tab 'Problems' next to details. It should contain list of all problems that occurred in that container.
https://ibb.co/ePxerv (something like this)
Each item should be clickable and redirect into logs.
Maybe it would be nice to display some exclamation mark next to state in the default container view (before dropdown-ing it).
https://ibb.co/fU7qya (something like this)
What do you think of this? Does it sound like a good idea? (The mock-ups are only for better understanding. Definitely I would like to see design from you)
All the best,
5 years, 8 months
IRC meetings - biweekly instead weekly
by Andreas Nilsson
The IRC meetings of late has been fairly short and quiet, and
participation has been low.
One thing is that we don't have enough of an agenda to have much discussion.
Therefore I'm suggesting we make the meetings bi-weekly instead of weekly.
Hence the next IRC meeting will be September 18th.
Interested in hearing more thoughts on why the IRC meetings aren't quite
working out for people.
5 years, 9 months
Getting error when building with webpack
by Bohdan Iakymets
when I trying to build with webpack, and then open page, I getting error in
> Uncaught TypeError: $(...).tooltip is not a function
at HTMLAnchorElement.<anonymous> (domain.js:523)
at Function.each (jquery.js:374)
at jQuery.fn.init.each (jquery.js:139)
at jQuery.fn.init.update_privileged (domain.js:511)
at update_hostname_privileged (system.js:8481)
at PageServer.setup (system.js:8681)
at HTMLDocument.init (system.js:10036)
at fire (jquery.js:3099)
at Object.fireWith [as resolveWith] (jquery.js:3211)
at Function.ready (jquery.js:3417)
But when I build the same sources with Makefile, it working ok.
5 years, 9 months