Cockpit 290 released
by Martin Pitt
Hello all,
Cockpit is the modern Linux admin interface. We release regularly. Here
are the release notes:
https://cockpit-project.org/blog/cockpit-290.html
You can get Cockpit here:
http://cockpit-project.org/running.html
The new releases for cockpit, cockpit-machines, and cockpit-podman are
available in Fedora 37 and 38.
Highlights:
- webserver: Disallow direct URL logins with LoginTo=false
- Machines: Indicate need for shutdown
- Machines: Delete storage file when detaching disk
Take care,
Martin Pitt
1 month, 2 weeks
Call for agenda Items on 2023-04-19 17:00 ==UTC== meeting
by Peter Boy
The upcoming meeting will be held on
===========================================================
Fedora Server IRC meeting Wednesday, April 19 17:00 ==UTC==
irc.libera.chat #fedora-meeting
===========================================================
ATTENTION: Daylight saving time changeover completed
=====================================================
Now, that summertime changeover has completed worldwide, we've shifted our meeting time by one hour earlier again! So our meeting will be at the same local time as during winter (and summer last year).
Please, check your local time using date -d '2023-04-19 17:00UTC'
==== Agenda ====
#link https://pagure.io/fedora-server/report/Meeting
To be able to discuss all topics on the agenda and to prevent us from repeatedly putting off topics that have not been dealt with, we should set time limits for the individual items on the agenda. If we need more time, we should continue on the mailing list.
1. === Follow up actions === 5 mins at max
2. === Fedora Website revamp === 10 mins max
#link Issue #66: https://pagure.io/fedora-server/issue/66
Mailing List:
#link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject....
Latest version:
#link https://fedora.gitlab.io/websites-apps/fedora-websites/fedora-websites-3.0/
We have to look at the final published pages to see if all our wishes and requirements are met.
3. === Each Edition has a story for each release === 20 mins max
#link https://pagure.io/fedora-server/issue/101
Mailing Liste
#link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject....
Original post by Matthew:
#link https://discussion.fedoraproject.org/t/objective-review-each-edition-has-...
Goal here: determine how we would like to proceed
4. === Fedora Server goal(s) for F39 === 30 mins max
#link https://pagure.io/fedora-server/issue/102
Goal: discuss proposals (included in the ticket), add possible options, discuss decision criteria, further detail selected proposals
5. === Open floor ===
For any additions or changes, please reply to this email.
For an overview about current tasks look at:
https://pagure.io/fedora-server/boards/Works%20in%20progress
1 month, 2 weeks
Fedora next: Each Edition has a story for each release
by Peter Boy
I want to point us to Matthews posting today:
https://discussion.fedoraproject.org/t/objective-review-each-edition-has-...
I think, it is a good idea, although at first glance not without some challenge. So I would like to start a discussion about our story for F39.
When I mentally review our past discussions, several options spontaneously come to mind:
1.
Our (famous) Ansible project (Server Edition local desktop management console, control node, Server administration desktop spin).
2.
Server Edition in a virtualized environment (installation support / installation images for multiple VPS hosting environments).
3.
Server Edition on modern Single Board Computer (SBC) (useful scenarios; improved support for particularly suitable models; recommendations)
4.
Backup and restore made easy
5.
Server Edition as identification server (typical usage configuration / setup, typical scenarios)
6.
Server Edition as local or public file server (NFS, Samba, Cockpit support)
7.
Newly polished installation media, maybe additionally an alternative directory tree for better isolation of system and user software, maybe sort of image based media (cf. the OpenSuSE discussion )
8.
Server Edition als central management and installation server (pxe boot server et.al.)
These are just some ideas. Some need a longer time of development and preparation, specifically the latter ones, some are realizable at shorter notice, in particular the former ones. Something like 2. or 3. maybe realistic candidates for F39, a first part of 1., 4., 5. could get candidates for F40, the others may need a longer preparation and development work.
Perhaps we should start by making a list of potential future focus areas and topics that we are interested in working on. So, in a first step everybody of us should specify one or more topics they are interested to work on and/or to contribute to. As an example, from the above list I would be interested on 1., 2., 3., 7.
We would then have to put this in a chronological order and find a project lead and contributors for each at least of the first 2-3 topics.
Well, the floor is open.
--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
pboy(a)fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member
Fedora docs team contributor
Java developer and enthusiast
1 month, 3 weeks
Call for agenda Items on 2023-04-05 17:00 ==UTC== meeting
by Peter Boy
The upcoming meeting will be held on
===========================================================
Fedora Server IRC meeting Wednesday, April 05 17:00 ==UTC==
irc.libera.chat #fedora-meeting
===========================================================
ATTENTION: Daylight saving time changeover completed
=====================================================
Now, that summertime changeover has completed worldwide, we decided to shift our meeting time by one hour earlier again!
So our meeting will be at the same local time as during winter (and summer last year).
Please, check your local time using date -d '2023-04-05 17:00UTC'
==== Agenda ====
#link https://pagure.io/fedora-server/report/Meeting
To be able to discuss all topics on the agenda and to prevent us from repeatedly putting off topics that have not been dealt with, we should set time limits for the individual items on the agenda. If we need more time, we should continue on the mailing list.
1. === Follow up actions === 5 mins at max
2. === F38 Beta testing === 15 mins at max
#link https://pagure.io/fedora-server/issue/99
Maybe, we have a new issue with IPA. See irc discussion Apr 4, 2023 15:42 (UTC) sgallagh / tflink
3. === Shorter Shutdown Timer === 10 mins at max
#link issue #96: https://pagure.io/fedora-server/issue/96
Mailing list discussion:
#link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject....
#link https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o...
#link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject....
#link https://bodhi.fedoraproject.org/updates/FEDORA-2023-814ffcaf1b
4. === Fedora Website revamp – Fedora Server Edition pages === 10 mins max
#link Issue #66: https://pagure.io/fedora-server/issue/66
Mailing List:
#link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject....
We have to check, if all our requirements are met.
5. === Using Ansible to install and configure Wildfly === about 20 mins
#link https://pagure.io/fedora-server/issue/60
Mailing List:
#link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject....
(step through the posts using „newer“ and „older“, I can’t manage to get a link to the complete thread)
#link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject....
We have to discuss how to proceed.
6. === Open floor ===
For any additions or changes, please reply to this email.
For an overview about current tasks look at:
https://pagure.io/fedora-server/boards/Works%20in%20progress
--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
pboy(a)fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member
Fedora docs team contributor
Java developer and enthusiast
2 months