fedora-linux-surface-pro-12in/kiwi-descriptions.git/teams/cloud/vagrant.xml, branch rawhideUnnamed repository; edit this file 'description' to name the repository.https://sayag.it/fedora-linux-surface-pro-12in/kiwi-descriptions.git/atom/teams/cloud/vagrant.xml?h=rawhide2025-12-09T18:50:44Zteams/cloud: Drop /boot partition and use a Btrfs subvolume for /boot2025-12-09T18:50:44ZNeal Gompangompa@fedoraproject.org2025-10-10T20:02:12Zurn:sha1:edebd133afa3443df356b41c5c4e587eb9ef5c59
This lets us free up the space allocated for the partition and gives
us dynamically allocated space for boot data like we have with the
rest of the operating system.
We do not do this for s390x because zipl does not support it.
Reference: https://fedoraproject.org/wiki/Changes/BtrfsBootForCloud
Raise the size of the boot partition to 2G for Fedora images2025-10-06T14:18:44ZNeal Gompangompa@fedoraproject.org2025-10-06T14:18:44Zurn:sha1:6c3b674a92536bbaa02d0473294472b5360d5bfd
With the increase in content in initramfs, a long-overdue raise
of the default size for /boot is warranted.
Reference: https://fedoraproject.org/wiki/Changes/2GbootPartition
grub2: Enable `bls` for all non-live images2025-04-29T20:36:27ZJanne Grunaujanne-fdr@jannau.net2025-04-27T20:19:29Zurn:sha1:66b87054e8155204fcaae4196f88592a07ee9457
This became necessary with 10.0.13 / after merging
https://github.com/OSInside/kiwi/pull/2535 but doesn't seem to
noticeable effects besides miisin "GRUB_ENABLE_BLSCFG=true" in
/etc/default/grub.
Adjust configs for SwitchToDnf5 Change2024-05-09T06:10:06ZAdam Williamsonawilliam@redhat.com2024-04-25T21:19:35Zurn:sha1:678ee6243cb73f0f668d123ac904643d2c02b39d
dnf5 (in obsoleting-dnf mode) provides /usr/bin/yum and obsoletes
yum, so we should drop the 'dnf-yum' entries (which installed
yum). dnf5 also appears to provide and obsolete microdnf, so we
should replace microdnf with dnf5 in the minimal image, I guess.
dnf5-plugins seems the logical replacement for dnf-plugins-core
(which is not removed yet, but is specific to dnf4).
Signed-off-by: Adam Williamson <awilliam@redhat.com>
cloud: Consistent device naming2024-04-15T15:09:41ZMajor Haydenmajor@redhat.com2024-04-15T15:09:41Zurn:sha1:72083f7ba069497df8ae3ec41424854d6964b646
Use consistent network device names for network devices instead of
forcing the old "ethX" names from pre-2017. This ensures that
specialized network devices, such as SR-IOV devices, are easy to
recognize and configure inside a Fedora instance on a public cloud or
OpenStack cloud.
FESCo ticket: https://pagure.io/fesco/issue/3190
Change proposal: https://fedoraproject.org/wiki/Changes/EnableConsistentDeviceNamingCloud
Signed-off-by: Major Hayden <major@redhat.com>
teams/cloud: Define compatible architectures for existing profiles2024-02-24T19:57:26ZNeal Gompangompa@fedoraproject.org2024-02-24T19:40:59Zurn:sha1:3ac0ae9240ca8ba0bbbe6bbdcd38a47dfd3fddc7
Most of the Fedora Cloud-owned profiles are limited to a subset of
architectures, generally x86_64 and aarch64 (with the exception of
the VirtualBox Vagrant image, which is x86_64 only).
teams/cloud: Reformat profile image types for readability2024-02-23T10:15:15ZNeal Gompangompa@fedoraproject.org2024-02-23T10:15:15Zurn:sha1:7235c1e6f40b2bf262bb1bc88933abd08f534330
This makes it easier to read what all the settings are.
Reorganize configuration around Fedora teams2024-02-23T00:15:21ZNeal Gompangompa@fedoraproject.org2024-02-23T00:15:21Zurn:sha1:749771647624e6be1f574fbf31b60aa0f90d0bbc
This realigns the configuration into separate files/folders that
would be modified by specific teams (e.g. WGs and SIGs).