server

server@lists.fedoraproject.org

2 participants
1492 discussions

[Fedocal] Reminder meeting : Fedora Server WG
by pboy＠fedoraproject.org 29 Apr '24

29 Apr '24

Dear all, You are kindly invited to the meeting: Fedora Server WG on 2024-05-01 from 17:00:00 to 18:00:00 UTC The meeting will be about: Standing meeting of the Fedora Server Edition Working Group More information available at: [https://pagure.io/fedora-server/report/Meeting](https://pagure.io/fedora-se… We meet at [Matrix Fedora meeting room](https://chat.fedoraproject.org/#/room/#meeting:fedoraproject.org) Source: https://calendar.fedoraproject.org//meeting/10709/

1 0

Updated some Doku
by Peter Boy 29 Apr '24

29 Apr '24

Folks, Just updated: * our Docs landing page * pur Installation overview * our local interactive Installation guide * our Virtualization overview * our Virtualization installation guide („Add Virtualization“). I added some minor information to the installation guide and to the Add Virtualization guide. It’s all minor, so I already published everything to our main docs. While making updated screenshots I noticed a problem with Anaconda. Until F37 you could use <shift>+<print> in any screen and Anaconda made a screenshot in /root/anaconda-screenshots/ (/tmp/anaconda-screenshots). With F40 I couldn’t make a screenshot anymore. Does get someone this issue, too? Without that feature it’s a mess to produce documentation. Best Peter -- 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 and board member Java developer and enthusiast

2 1

Re: Review Installation Media
by Peter Boy 29 Apr '24

29 Apr '24

Hi Folks, Here is my attempt at an updated brief summary of the current status as a first impetus for our discussion at the upcoming meeting on May 1. 1. Our initial information that Kiwi can also be used for the generation of iso files is currently not applicable in this form. We will create the iso files in unchanged form for at least a few more releases. If we don't want to spend another number of releases with the current outdated iso files (and that seems very bad to me), then we should start tackling the issues now, starting with the oldest one. !proposed: So I suggest starting now with the oldest issue (#32, https://pagure.io/fedora-server/issue/32) and doing another video meeting soon. 2. We don't have to decide at the moment which tool we will use to create our images in the future. We would be busy with the iso files for the time being. Instead, we could discuss with RelEng what tools are available and which is best. And in what timeframe the changeover needs to take place. Kiwi may not be optimal for us as we would have to maintain another set of configuration files instead of using Kickstart files throughout. Therefore, our situation differs from Cloud, which does not need to create iso files for Cloud VMs. But there may be no other solution that is better for us. And in the end, it also comes down to choosing a solution that can be managed with the resources available to Fedora (i.e. releng). !proposed: So I propose to postpone the decision about image generation for now. -- 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 and board member Java developer and enthusiast

1 0

Revisiting Server installation media naming convention
by Peter Boy 28 Apr '24

28 Apr '24

See: https://pagure.io/fedora-server/issue/126 We want to pursue this topic for F41, so we should start now. There is a new initiative from GLB in the Fedora Server Matrix Channel. > • Server WG: The websites and apps team is thinking about adding/promoting links to the "Everything" network installer on fp.o. I'm wondering if we should consider renaming "network installer" to "online installer" because I've seen people confused about what is meant by "network". I've encountered people who think it is for PXE booting. I guess, to be consistent, such a rename would also translate the "Server network installer" to the "Server online installer". Otherwise, I don't think any other groups would be affected. > • 22:36 > Would the Server WG be OK with such a rename? Or do you have other ideas? (Leaving it be as it is is also fine. I'm just trying to help with a point of confusion.) 🙂 So, an idea is to use something like: Fedora-Server-40-offline-x.y.-<arch>.iso long name: Fedora Server Edition release 40 local fully offline installation Fedora-Server-40-online-x.y.-<arch>.iso long name: Fedora Server Edition release 40 local online installation We had a releng ticket once ago: https://pagure.io/releng/issue/11089 It’s resolved regarding the Checksum file naming for F40 (didn’t test it yet). So we should aim to modify the name and get rid of DVD and unify the naming structure: Fedora-Server-<rel>-<method>-<x.y>-arch.<filetyp> 40 offline x64_86 iso online arch qcow2 kvm raw.xz Image checksum -- 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 and board member Java developer and enthusiast

3 5

Review Installation Media
by Peter Boy 18 Apr '24

18 Apr '24

Hi folks, Here is my attempt at a brief summary as a starting point for our further discussion. At our first video meeting, we arrived at an approach to create all installation media with one tool if possible. Kiwi is obviously the tool of choice at the moment. I think there are several steps to be taken now: 1. We should try Kiwi, preferably with our VM image. There is already a template from the Cloud WG. Here's what came to mind: (a) Apparently Kiwi does not use kickstart files. How does this work with Anaconda? b) What happens to our PXE network installation? c) Do we have a "playing field" on Koji where we can experiment, or should we install our own Kiwi instance, e.g. on the server where I had developed our VM with ImageFactory (and where we can all have access, as with the Wildfly server)? 2. We should contact the other editions, and especially RelEng, to coordinate the course of action. RelEng is currently busy with F40. We can only start with it after its release. 3. Another consideration is time. Currently, F41 is built in Rawhide as before, so it will certainly be released that way. The question is whether we want to continue publishing our iso files unchanged (and with errors). One possibility would be to at least remove the difference between DVD and netboot. We have to look at their build steps anyway, whether with the current tools or with Kiwi. The logic should be the same. This leads to at least 3 alternatives for the next steps we take. 1. we wait until F40 is published and then contact RelEng about the options for the best way forward. 2. we meet for another video meeting, e.g. next week, and spend some time trying out Kiwi and looking at it in detail. 3. we wait with Kiwi for the discussion with RelEng and the other editions and try in a next meeting specifically to determine the differences between DVD and netbook and to test how big a modified DVD file would become (this would be our issue #32 [1], 2 years old. Can anyone think of any other ways? We should decide what we want to do next and when. One option would be another video session on Wednesday, April 24. Best Peter [1] https://pagure.io/fedora-server/issue/32 -- 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 and board member Java developer and enthusiast

3 2

Testing rc 1.12
by Peter Boy 18 Apr '24

18 Apr '24

I did some testing with rc 1.12 LVM devices file issue ====================== https://bugzilla.redhat.com/show_bug.cgi?id=2247872 * Both Server image files (Fedora-Server-KVM-40-1.12.x86_64.qcow2 & Fedora-Server-40-1.12.aarch64.raw.xz) still contain a devices file in /etc/lvm/devices/system.devices, which specifies device /dev/vda3, obviously from the build host. * If you leave this unchanged, the devices file in the KVM image will be left as /dev/vda3, which is correct for a libvirt KVM, and for the ARM SBC device correctly changed to mmcblk1p3 * If you manually delete the devices file in each of the images, then after the first boot the /etc/lvm/devices subdirectory in both images remains empty. So I think, the issue is resolved, but we need more information to add to server documentation. Various issues with kernel boot and initial grub screen ======================================================= There were various issues with keyboard navigation, keyboard not reacting on the select (enter) key, etc, which are all resolved with 1.13 Error messages while booting ============================ There were a lot of error messages durch boot, which had no negative effect, which, as far as can be seen, had no negative effect. Most of them are gone new ones have appeared There is: ACPI Error: Aborting method \_SB.PC00.RHUB.HS01._PLD due to previous error … ACPI BIOS Eror (bug): Could not resolve symbol [\_SB.UBTC.R’UCC ] … Usbhlld 3-4:1.3: couldn’t an input interrupt endpoint overlayfs: failed to resolve … Some of them may depend on my test hardware (a quite recent Intel board and some older ones). In any case I see no opportunity to fix these. Anaconda ======== With custom partitioning, Anaconda mixes up the order of the partitions again. This was solved for some releases, but occurs again now. I don't see any chance of a solution for this at the moment either. We may try to get it fixed for Rawhide. -- 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 and board member Java developer and enthusiast

2 4

[Fedocal] Reminder meeting : Fedora Server WG
by pboy＠fedoraproject.org 15 Apr '24

15 Apr '24

Dear all, You are kindly invited to the meeting: Fedora Server WG on 2024-04-17 from 17:00:00 to 18:00:00 UTC The meeting will be about: Standing meeting of the Fedora Server Edition Working Group More information available at: [https://pagure.io/fedora-server/report/Meeting](https://pagure.io/fedora-se… We meet at [Matrix Fedora meeting room](https://chat.fedoraproject.org/#/room/#meeting:fedoraproject.org) Source: https://calendar.fedoraproject.org//meeting/10709/

1 0

2024-04-15 @ 16:00 UTC - Fedora 40 Blocker Review Meeting
by Adam Williamson 14 Apr '24

14 Apr '24

# F40 Blocker Review meeting # Date: 2024-04-15 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for another blocker review meeting. We have 1 proposed blocker (kinda...) and 4 proposed freeze exceptions for Final. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+40+Blocker… The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F40 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

Re: Our video meeting today at 17:00 UTC
by John W. Himpel 11 Apr '24

11 Apr '24

Jason, Someone may have better notes, but one source would be: https://chat.fedoraproject.org/#/room/#server:fedoraproject.org It was strongly suggested that we migrate away the current build module and move to kiwi. Again, strongly suggested we chose an existing output image and work on generating a exact (as possible) image under kiwi. Then using the same process, generate the remaining output images. Only after we are completely converted to kiwi, then begin to make whatever modifications we deem necessary. I believe Tomas has agreed to assist us in this process as he has the requisite access credentials. I'm sure if any of the above is not correct, someone will please send a correction. John On Thu, 2024-04-11 at 08:03 -0500, J Beard wrote: > > I hate that I missed the session yesterday. I couldn't break free > from work. Any chance it was recorded? If not no worries. Any one > have notes? > > Thanks, > Jason > > > > > On 4/10/24 08:15, Peter Boy wrote: > > > > > Folks, > > > > After our video test session yesterday, the Matrix video functionality in the "Fedora Server" room is no longer functional. The Infra team is working on it as time allows in this hot phase of the new release. > > > > As a way out, Tomáš has opened up a Jitsi option and we have tested it. The new link is: > > > > > > NEW LINK! > > ===> https://meet.jit.si/fedorainfrastandup <=== > > > > > > Simply open the link in your browser, Firefox or Chrome, and off you go. If it worked yesterday with the Matrix Jitsi instance, it works the same way with a Jitsi instance in the open Jitsi project infrastructure. > > > > > > However, to be on the safe side in case a problem does occur, we open the session 15 minutes beforehand. > > > > > > And I keep an eye on the "Fedora Server" matrix room in parallel, so that we always have a means of communication if there are difficulties at the beginning. > > > > > > > > > > -- > > 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 and board member > > Java developer and enthusiast > > > > > > > > -- > > _______________________________________________ > > server mailing list -- server(a)lists.fedoraproject.org > > To unsubscribe send an email to server-leave(a)lists.fedoraproject.org > > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue > > > > -- > _______________________________________________ > server mailing list -- server(a)lists.fedoraproject.org > To unsubscribe send an email to server-leave(a)lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: > https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue

2 1

Our video meeting today at 17:00 UTC
by Peter Boy 11 Apr '24

11 Apr '24

Folks, After our video test session yesterday, the Matrix video functionality in the "Fedora Server" room is no longer functional. The Infra team is working on it as time allows in this hot phase of the new release. As a way out, Tomáš has opened up a Jitsi option and we have tested it. The new link is: NEW LINK! ===> https://meet.jit.si/fedorainfrastandup <=== Simply open the link in your browser, Firefox or Chrome, and off you go. If it worked yesterday with the Matrix Jitsi instance, it works the same way with a Jitsi instance in the open Jitsi project infrastructure. However, to be on the safe side in case a problem does occur, we open the session 15 minutes beforehand. And I keep an eye on the "Fedora Server" matrix room in parallel, so that we always have a means of communication if there are difficulties at the beginning. -- 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 and board member Java developer and enthusiast

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

server