server March 2019

server@lists.fedoraproject.org

7 participants
8 discussions

Proposal: Changes to Fedora Server default partitioning scheme
by Stephen Gallagher 13 Dec '24

13 Dec '24

The following proposal comes out of the discussion at this weeks Server SIG meeting[1] Fedora Server will have: * / (root) will be a minimum of 2 GiB and a maximum of 15 GiB * SWAP will continue to be calculated automatically based on available RAM on the system * All unused space will be assigned to a volume group and available to be assigned to new partitions or extend existing partitions. * Anaconda will continue to handle the appropriate EFI and /boot settings We also discussed during the meeting whether we should have a separate /var partition by default, but the general sense was that we might be better served by developing a mechanism to allow partitions to be split from existing mount points, which would be more flexible going forward. As we did not have quorum in the meeting by the point we got to this proposal, I'm taking it to the list for discussion and votes. For the record, the current behavior of the partitioning scheme is for / to be given up to 50 GiB of space and then any remaining space after that is assigned to a separate /home partition. [1] https://meetbot.fedoraproject.org/fedora-meeting-1/2016-03-15/serversig.201…

4 8

Composer 0.2.0 released
by Jenn Giardino 26 Mar '19

26 Mar '19

Composer generates custom images suitable for deploying systems or uploading to the cloud. It integrates into Cockpit as a frontend for Lorax Composer. Here are the release notes from version 0.2.0: - Include ability to add a user to a blueprint - Fix issue when blueprint contents include a package with more than one arch - Fix issue with loading contents in Export modal on Blueprints page You can get Composer here: https://github.com/weldr/welder-web/tree/0.2.0#cockpit-composer Composer is available in Fedora 30: https://bodhi.fedoraproject.org/updates/cockpit-composer-0.2.0-1.fc30 Or download the tarball here: https://github.com/weldr/welder-web/releases/tag/0.2.0 Regards, Jenn Giardino Jenn Giardino Senior Interaction Designer User Experience Design Team Red Hat, Inc. 1-919-716-5045 jgiardin(a)redhat.com

1 0

Cockpit 190
by Katerina Koukiou 24 Mar '19

24 Mar '19

Cockpit is the modern Linux admin interface. We release regularly. Here are the release notes from version 190: http://cockpit-project.org/blog/cockpit-190.html Summary: - Logs: Filter log entries by service - Machines: Support for Pausing/Resuming VMs - Machines: Make Autostart property of a Virtual Network configurable - Machines: Support for creating VM with option to boot from PXE - Accessibility improvements You can get Cockpit here: http://cockpit-project.org/running.html Cockpit 190 is available in Fedora 29: https://bodhi.fedoraproject.org/updates/cockpit-190-1.fc29 And Fedora 30: https://bodhi.fedoraproject.org/updates/cockpit-190-1.fc30 Or download the tarball here: https://github.com/cockpit-project/cockpit/releases/tag/190 Regards, Katerina Koukiou

1 0

Re: [Test-Announce] Fedora 30 Candidate Beta-1.4 Available Now!
by Adam Williamson 21 Mar '19

21 Mar '19

On Thu, 2019-03-21 at 01:36 +0000, rawhide(a)fedoraproject.org wrote: > According to the schedule [1], Fedora 30 Candidate Beta-1.4 is now > available for testing. Please help us complete all the validation > testing! For more information on release validation testing, see: > https://fedoraproject.org/wiki/QA:Release_validation_test_plan > > Test coverage information for the current release can be seen at: > https://www.happyassassin.net/testcase_stats/30 > > You can see all results, find testing instructions and image download > locations, and enter results on the Summary page: > > https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1.4_Summary > > The individual test result pages are: > > https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1.4_Installation > https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1.4_Base > https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1.4_Server > https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1.4_Cloud > https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1.4_Desktop > https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1.4_Security_Lab > > All Beta priority test cases for each of these test pages [2] must > pass in order to meet the Beta Release Criteria [3]. > > Help is available on #fedora-qa on irc.freenode.net [4], or on the > test list [5]. Hey folks! So, unfortunately we had some trouble getting a candidate build done, but now we have one. The go/no-go meeting is on Thursday at 17:00 UTC - that's in about 11 hours. Obviously time is tight to do the testing, but if folks could help test as much stuff as possible, that'd be great. We do have one outstanding blocker bug, but there's a chance it'll get downgraded at the meeting, so it'd be great if we could complete the testing for all Beta tests on this compose. If there isn't enough time, though, no-one will blame us :) Thanks everyone! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

Fedora 30 Beta Release Readiness meeting
by Ben Cotton 20 Mar '19

20 Mar '19

Dear all, Join us on irc.freenode.net in #fedora-meeting-1 for the Fedora 30 Beta Release Readiness meeting. This meeting will be held on Thursday, 2018-03-21 at 19:00 UTC. We will meet to make sure we are coordinated and ready for the Beta release of Fedora 30. 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 hours earlier. 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 https://fedoraproject.org/wiki/Release_Readiness_Meetings. View the meeting on Fedocal: https://apps.fedoraproject.org/calendar/Fedora%20release/2019/3/21/#m9492 -- Ben Cotton Fedora Program Manager TZ=America/Indiana/Indianapolis

1 1

Cockpit 189
by Sanne Raymaekers 07 Mar '19

07 Mar '19

Cockpit is the modern Linux admin interface. We release regularly. Here are the release notes from version 189: https://cockpit-project.org/blog/cockpit-189.html Summary: - Machines: choose an existing qcow image when creating a new VM - Machines: Show the details and properties of virtual networks - Services: Filter services by name, description, or state You can get Cockpit here: https://cockpit-project.org/running Cockpit 189 is available in Fedora 29: https://bodhi.fedoraproject.org/updates/cockpit-189-1.fc29 And Fedora 30: https://bodhi.fedoraproject.org/updates/cockpit-189-1.fc30 Or download the tarball here: https://github.com/cockpit-project/cockpit/releases/tag/189 Kind regards, Sanne Raymaekers

1 0

Cancelled: Fedora Server Working Group Meeting @ Tuesday, 18 March 2014
by sgallagh＠redhat.com 04 Mar '19

04 Mar '19

1 0

Proposal: Drop most optional packages from Server DVD
by Stephen Gallagher 01 Mar '19

01 Mar '19

For a long time, the Fedora Server Edition has provided a fairly lightweight default installation, but a fairly heavyweight DVD. This is because we opted to include a lot of infrastructure-related content on the disk, such as BIND, FreeIPA, MariaDB and PostgreSQL, among others. The reality these days is that this is probably more or less unnecessary. There's no such thing as a server that is not connected to a network and since we aren't shipping the entirety of the Fedora package collection on this disk, inevitably anyone installing from it is going to need to have access to package mirrors anyway. So I'd like to propose that we get rid of nearly the entirety of the <optionlist> section from comps.xml[1][2] and variants-fedora.xml[3]. The result will be a far smaller install DVD, less space wasted on the mirrors (both for the DVD and the install tree) and very little difference in user experience. Arguments against this have historically been that having it all on one disk is better for network-constrained environments to avoid downloading content multiple times. Realistically, however, I think this is generally going to be solved by local mirroring in most real-world scenarios. [1] https://pagure.io/fedora-comps/blob/master/f/comps-f30.xml.in [2] With the exception of the "server-hardware-support" and "guest-agents" which may be needed for proper installation, depending on the hardware. [3] https://pagure.io/pungi-fedora/blob/master/f/variants-fedora.xml

11 24

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

server March 2019