Cockpit 169 (released today) contains a change to take advantage of the
recently added PAM support for /etc/motd.d to display a helpful note to the
admin about how to start or access cockpit.
The required PAM changes have already landed in Fedora 28.
It seems that the PAM configuration of Fedora 28 (at least in our test
images here) doesn't use pam_motd at all, though.
I'd like to start a discussion about what would be appropriate here. We
want at least a message displayed when people log in to an interactive
session with ssh, but it might also be useful to display a message at the
virtual console, before or after login.
Thanks in advance,
I'm Alberto from the Marketing team, I'm asking for help to complete
the Fedora 29 Talking points.
Talking points are key highlights of the new release. There are
different types of talking points for different types of people:
general desktop users/everyone, developers, and sysadmins. They are
meant to provide a short, effective answer to the question "What cool
stuff is in the latest release of Fedora?" They are compelling, not
Alberto Rodriguez Sanchez <bt0dotninja(a)fedoraproject.org>
Cockpit's "Kubernetes" package has provided a web UI for managing
Kubernetes/OpenShift deployments for a long time. In the last year it also got
some initial support for showing KubeVirt VMs that run in OpenShift.
Since Red Hat's acquiring of CoreOS there are now *three* web UIs: OpenShift's
own "OpenShift Console", Tectonic, and Cockpit's "Cluster" dashboard. The first
two are meant to become one at some point  and currently see a lot of
development; i. e. Console/Tectonic/Quay will be *the* web UI for OpenShift
(including KubeVirt) soon. On the other hand, cockpit-kubernetes has been in
maintenance mode for a fair while now - both because of that merging effort,
and also because we haven't had (and still don't have) any development capacity
for it in the Cockpit team. It's also rather hard to maintain, being written in
a very old Angular version.
So long-term cockpit-kubernetes will go away. As a strawman I would propose to
still keep it in Fedora 29 (as it's past beta freeze already), but drop it from
Rawhide. Thus there will still be a supported cockpit-kubernetes package for
~ 1.5 more years.
cockpit-kubernetes also contains some support for KubeVirt. Apparently
community interest has waned on that, and we actually haven't been able to
build a recent kubevirt-enabled OpenShift image in four months --  were the
last attempts at fixing it. Thus we had to kick out kubevirt testing from
the openshift image , and we'll have to kick it off the openshift-prerelease
image as well if we need to rebuild it at some point. Once this happens, there
is no way how we can further support the KubeVirt bits in cockpit-kubernetes,
so I'd actually like to remove this from Fedora 29 already, in its current
Is there any interest from anyone to continue to maintain it? If so, then the
best course of action would be to split it off into a separate
cockpit-kubernetes upstream project, like we recently did with cockpit-ostree ,
and maintain it there (by a different group of people than the Cockpit core
team). Of course we will gladly help you to set this up.
 https://github.com/cockpit-project/cockpit/issues/9479 and https://github.com/cockpit-project/cockpit/pull/9638
Join us on irc.freenode.net in #fedora-meeting-1 for the Fedora 29
Beta Release Readiness meeting. This meeting will be held on Thursday,
2018-09-13 at 19:00 UTC.
We will meet to make sure we are coordinated and ready for the Beta
release of Fedora 29. Please note that this meeting will be held even
if the release is delayed at the Go/No-Go meeting on the same day two
You may receive this message several times in order to open this
meeting to the teams and to raise awareness, so hopefully more team
representatives will come to this meeting. This meeting works best
when we have representatives from all of the teams.
For more information, see
I will ask for readiness from each of the teams listed below. If there
are additional teams that should be explicitly included, let me know.
All teams and contributors are welcome to provide input at the
* Cloud WG
* Fedora Project Leader
* Release Engineering
* Server WG
View the meeting on Fedocal:
Fedora Program Manager