cc: anaconda-devel@
From today's Fedora QA minutes https://meetbot.fedoraproject.org/fedora-meeting/2022-01-24/fedora-qa.2022-0...
16:20:54 <pboy> I'll test that again, but I'm sure, if you use everything DVD you get the wrong preconfiguration. We had a thread about that on server list.
I'm not finding this thread. But Adamw surely knows the history of Everything ISO better than I do. My fuzzy memory is that it's sort of a side effect of how images are made and it's kept around as a catch all. It's the only way to do a netinstall for any of the desktops. The default package set is for a minimal install, a.k.a. Fedora Custom. The idea is to make it straightforward to get a minimum bootable system and then use dnf to build it up from there.
Just for context, "Everything ISO" e.g. https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20220124.n...
This image defines "automatic" partitioning as btrfs. It's intrinsic to the image itself what the partitioning defaults to. It's not a function of the package set, i.e. choosing the Server package set doesn't get you Server's default partitioning. It's a little confusing, but it's working as designed, insofar as it has one.
I cc'd Anaconda folks, because I'm not sure exactly where the "autopart" kickstart command gets defined these days. And also whether it's worth the effort to make autopart variable based on what edition or spin is selected in the Everything netinstaller? I'm not sure that it is.
Am 24.01.2022 um 18:42 schrieb Chris Murphy lists@colorremedies.com:
cc: anaconda-devel@
From today's Fedora QA minutes https://meetbot.fedoraproject.org/fedora-meeting/2022-01-24/fedora-qa.2022-0...
16:20:54 <pboy> I'll test that again, but I'm sure, if you use everything DVD you get the wrong preconfiguration. We had a thread about that on server list.
I'm not finding this thread. But Adamw surely knows the history of Everything ISO better than I do. My fuzzy memory is that it's sort of a side effect of how images are made and it's kept around as a catch all. It's the only way to do a netinstall for any of the desktops. The default package set is for a minimal install, a.k.a. Fedora Custom. The idea is to make it straightforward to get a minimum bootable system and then use dnf to build it up from there.
Just for context, "Everything ISO" e.g. https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20220124.n...
This image defines "automatic" partitioning as btrfs. It's intrinsic to the image itself what the partitioning defaults to. It's not a function of the package set, i.e. choosing the Server package set doesn't get you Server's default partitioning. It's a little confusing, but it's working as designed, insofar as it has one.
I cc'd Anaconda folks, because I'm not sure exactly where the "autopart" kickstart command gets defined these days. And also whether it's worth the effort to make autopart variable based on what edition or spin is selected in the Everything netinstaller? I'm not sure that it is.
Chris,
if I remember correctly, wasn’t it you who informed me (about a year ago in the context of F32/33) that booting from everything DVD and select „Fedora Server“ does not result in an identical installation as booting from Server DVD and selecting „Fedora Server“? (when I wondered about the installation on a rented remote hardware where only „Everything“ was available).
Anyway, no case to worry at the current status, I think. I will test this more closely. At the moment I am still completing and refining my dedicated server test environment.
Besides the question about the boot medium and group selection, the January 18 build has still the issue with /etc/resolv.conf being a file instead of a link (and thus breaking split DNS). The bug is marked as resolved (in December/January according to Adam), maybe the build was made just before that became effective. We have to keep this in mind.
Best Peter
On Mon, Jan 24, 2022 at 1:46 PM Peter Boy pboy@uni-bremen.de wrote:
Am 24.01.2022 um 18:42 schrieb Chris Murphy lists@colorremedies.com:
cc: anaconda-devel@
From today's Fedora QA minutes https://meetbot.fedoraproject.org/fedora-meeting/2022-01-24/fedora-qa.2022-0...
16:20:54 <pboy> I'll test that again, but I'm sure, if you use everything DVD you get the wrong preconfiguration. We had a thread about that on server list.
I'm not finding this thread. But Adamw surely knows the history of Everything ISO better than I do. My fuzzy memory is that it's sort of a side effect of how images are made and it's kept around as a catch all. It's the only way to do a netinstall for any of the desktops. The default package set is for a minimal install, a.k.a. Fedora Custom. The idea is to make it straightforward to get a minimum bootable system and then use dnf to build it up from there.
Just for context, "Everything ISO" e.g. https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20220124.n...
This image defines "automatic" partitioning as btrfs. It's intrinsic to the image itself what the partitioning defaults to. It's not a function of the package set, i.e. choosing the Server package set doesn't get you Server's default partitioning. It's a little confusing, but it's working as designed, insofar as it has one.
I cc'd Anaconda folks, because I'm not sure exactly where the "autopart" kickstart command gets defined these days. And also whether it's worth the effort to make autopart variable based on what edition or spin is selected in the Everything netinstaller? I'm not sure that it is.
Chris,
if I remember correctly, wasn’t it you who informed me (about a year ago in the context of F32/33) that booting from everything DVD and select „Fedora Server“ does not result in an identical installation as booting from Server DVD and selecting „Fedora Server“? (when I wondered about the installation on a rented remote hardware where only „Everything“ was available).
That's a different case. That's referring to the package collection. The Everything ISO has the base Fedora "profile" that most variants use (which uses Btrfs). But it also doesn't select Fedora Server by default and is explicitly designed "for experts", The Fedora Server netinstall ISO uses the Fedora Server "profile" and will use the Fedora Server settings by default, including using LVM+XFS.
Think of the Everything ISO as something that an Arch convert would use, while the Fedora Server netinstall ISO would be something that a sysadmin doing server deployments from a central repo mirror would use.
Am 24.01.2022 um 20:20 schrieb Neal Gompa ngompa13@gmail.com:
On Mon, Jan 24, 2022 at 1:46 PM Peter Boy pboy@uni-bremen.de wrote:
Am 24.01.2022 um 18:42 schrieb Chris Murphy lists@colorremedies.com:
cc: anaconda-devel@
From today's Fedora QA minutes https://meetbot.fedoraproject.org/fedora-meeting/2022-01-24/fedora-qa.2022-0...
16:20:54 <pboy> I'll test that again, but I'm sure, if you use everything DVD you get the wrong preconfiguration. We had a thread about that on server list.
I'm not finding this thread. But Adamw surely knows the history of Everything ISO better than I do. My fuzzy memory is that it's sort of a side effect of how images are made and it's kept around as a catch all. It's the only way to do a netinstall for any of the desktops. The default package set is for a minimal install, a.k.a. Fedora Custom. The idea is to make it straightforward to get a minimum bootable system and then use dnf to build it up from there.
Just for context, "Everything ISO" e.g. https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20220124.n...
This image defines "automatic" partitioning as btrfs. It's intrinsic to the image itself what the partitioning defaults to. It's not a function of the package set, i.e. choosing the Server package set doesn't get you Server's default partitioning. It's a little confusing, but it's working as designed, insofar as it has one.
I cc'd Anaconda folks, because I'm not sure exactly where the "autopart" kickstart command gets defined these days. And also whether it's worth the effort to make autopart variable based on what edition or spin is selected in the Everything netinstaller? I'm not sure that it is.
Chris,
if I remember correctly, wasn’t it you who informed me (about a year ago in the context of F32/33) that booting from everything DVD and select „Fedora Server“ does not result in an identical installation as booting from Server DVD and selecting „Fedora Server“? (when I wondered about the installation on a rented remote hardware where only „Everything“ was available).
That's a different case. That's referring to the package collection. The Everything ISO has the base Fedora "profile" that most variants use (which uses Btrfs). But it also doesn't select Fedora Server by default and is explicitly designed "for experts", The Fedora Server netinstall ISO uses the Fedora Server "profile" and will use the Fedora Server settings by default, including using LVM+XFS.
Think of the Everything ISO as something that an Arch convert would use, while the Fedora Server netinstall ISO would be something that a sysadmin doing server deployments from a central repo mirror would use.
Thanks for the clarification. I read it as: If I boot the Server netboot DVD I get the Server profile, regardless of the source from which the individual packages are downloaded. And the „Installation Source“ is just for download all the needed rpms. So it must have been something messed up in my test environment. It is not yet in a state where I would like it to be.
Thanks Peter
On Mon, 2022-01-24 at 23:01 +0100, Peter Boy wrote:
Thanks for the clarification. I read it as: If I boot the Server netboot DVD I get the Server profile, regardless of the source from which the individual packages are downloaded. And the „Installation Source“ is just for download all the needed rpms. So it must have been something messed up in my test environment. It is not yet in a state where I would like it to be.
Yes, this is how it *should* be. For things like the default filesystem, they're decided by what 'flavor' the installer is. If you use the Server netinst, you should get Server defaults, whatever package set you install. If you use the Everything netinst, you will get universal defaults, whatever package set you install.
The Server netinst should default to using the Everything repo as its package source, but it should default to the Server package set and Server defaults for filesystem and so on. If it does not do that, that's a bug that should be investigated. From what I can see in the openQA results, though, it does seem to do this.
Am 25.01.2022 um 02:02 schrieb Adam Williamson adamwill@fedoraproject.org:
On Mon, 2022-01-24 at 23:01 +0100, Peter Boy wrote:
Thanks for the clarification. I read it as: If I boot the Server netboot DVD I get the Server profile, regardless of the source from which the individual packages are downloaded. And the „Installation Source“ is just for download all the needed rpms. So it must have been something messed up in my test environment. It is not yet in a state where I would like it to be.
... The Server netinst should default to using the Everything repo as its package source, but it should default to the Server package set and Server defaults for filesystem and so on. If it does not do that, that's a bug that should be investigated. From what I can see in the openQA results, though, it does seem to do this.
Thanks, I will test this tomorrow in a cleaned up test environment.
Peter
Am 25.01.2022 um 02:02 schrieb Adam Williamson adamwill@fedoraproject.org:
The Server netinst should default to using the Everything repo as its package source, but it should default to the Server package set and Server defaults for filesystem and so on. If it does not do that, that's a bug that should be investigated. From what I can see in the openQA results, though, it does seem to do this.
I tested it again and it works indeed as expected.
Best Peter
server@lists.fedoraproject.org
-
Adam Williamson -
Chris Murphy -
Neal Gompa -
Peter Boy