davidlt/fedora-kiwi-descriptions
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
b25a6440f9
fedora-kiwi-descriptions/teams/cloud/vagrant.xml

76 lines
3.1 KiB
XML
Raw Normal View History

Initial import of descriptions
2023-10-14 19:21:23 +00:00
<image>
<profiles>
platforms/vagrant: Define Vagrant images for libvirt and VirtualBox KIWI differentiates between libvirt and VirtualBox based Vagrant images, especially for the box format, so now we split up the Vagrant definition accordingly.
2023-10-14 20:30:57 +00:00
<profile name="VagrantCore" description="Vagrant core packages">
Initial import of descriptions
2023-10-14 19:21:23 +00:00
<requires profile="CloudCore"/>
</profile>
platforms, tmt: Rename and restructure cloud variants We now have more than one cloud system that is essentially a KVM environment that uses cloud-init to boot, so now we declare that "generic" and have the OpenStack and Oracle images reuse those definitions. Also, in preparation for layered cloud image variants, rename them from "Cloud-" to "Cloud-Base-". Vagrant variants are similarly prefixed to make it clear who provides them. Finally, restructure the layout of the tmt plans to match the description structure.
2023-12-21 14:04:37 +00:00
<profile name="Cloud-Base-Vagrant-libvirt" description="Vagrant Base guest image for libvirt">
platforms/vagrant: Define Vagrant images for libvirt and VirtualBox KIWI differentiates between libvirt and VirtualBox based Vagrant images, especially for the box format, so now we split up the Vagrant definition accordingly.
2023-10-14 20:30:57 +00:00
<requires profile="VagrantCore"/>
</profile>
platforms, tmt: Rename and restructure cloud variants We now have more than one cloud system that is essentially a KVM environment that uses cloud-init to boot, so now we declare that "generic" and have the OpenStack and Oracle images reuse those definitions. Also, in preparation for layered cloud image variants, rename them from "Cloud-" to "Cloud-Base-". Vagrant variants are similarly prefixed to make it clear who provides them. Finally, restructure the layout of the tmt plans to match the description structure.
2023-12-21 14:04:37 +00:00
<profile name="Cloud-Base-Vagrant-VirtualBox" description="Vagrant Base guest image for VirtualBox">
platforms/vagrant: Define Vagrant images for libvirt and VirtualBox KIWI differentiates between libvirt and VirtualBox based Vagrant images, especially for the box format, so now we split up the Vagrant definition accordingly.
2023-10-14 20:30:57 +00:00
<requires profile="VagrantCore"/>
</profile>
Initial import of descriptions
2023-10-14 19:21:23 +00:00
</profiles>
teams/cloud: Define compatible architectures for existing profiles 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).
2024-02-24 19:40:59 +00:00
<preferences profiles="Cloud-Base-Vagrant-libvirt" arch="x86_64,aarch64">
teams/cloud: Reformat profile image types for readability This makes it easier to read what all the settings are.
2024-02-23 10:15:15 +00:00
<type image="oem" format="vagrant"
filesystem="btrfs" btrfs_root_is_subvolume="true" btrfs_set_default_volume="false" fsmountoptions="compress=zstd:1"
cloud: Consistent device naming 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>
2024-04-15 15:09:41 +00:00
kernelcmdline="no_timer_check console=tty1 console=ttyS0,115200n8"
teams/cloud: Reformat profile image types for readability This makes it easier to read what all the settings are.
2024-02-23 10:15:15 +00:00
devicepersistency="by-uuid"
bootpartition="true" bootpartsize="1000" bootfilesystem="ext4" efipartsize="100" firmware="uefi"
rootfs_label="fedora"
>
Initial import of descriptions
2023-10-14 19:21:23 +00:00
<bootloader name="grub2" console="serial" timeout="1"/>
<size unit="G">5</size>
platforms/vagrant: Define Vagrant images for libvirt and VirtualBox KIWI differentiates between libvirt and VirtualBox based Vagrant images, especially for the box format, so now we split up the Vagrant definition accordingly.
2023-10-14 20:30:57 +00:00
<vagrantconfig provider="libvirt" virtualsize="5"/>
Initial import of descriptions
2023-10-14 19:21:23 +00:00
<systemdisk>
<volume name="@root=root"/>
<volume name="home" parent="/"/>
<volume name="var" parent="/"/>
</systemdisk>
<oemconfig>
<oem-resize>false</oem-resize>
</oemconfig>
</type>
</preferences>
teams/cloud: Define compatible architectures for existing profiles 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).
2024-02-24 19:40:59 +00:00
<preferences profiles="Cloud-Base-Vagrant-VirtualBox" arch="x86_64">
teams/cloud: Reformat profile image types for readability This makes it easier to read what all the settings are.
2024-02-23 10:15:15 +00:00
<type image="oem" format="vagrant"
filesystem="btrfs" btrfs_root_is_subvolume="true" btrfs_set_default_volume="false" fsmountoptions="compress=zstd:1"
cloud: Consistent device naming 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>
2024-04-15 15:09:41 +00:00
kernelcmdline="no_timer_check console=tty1 console=ttyS0,115200n8"
teams/cloud: Reformat profile image types for readability This makes it easier to read what all the settings are.
2024-02-23 10:15:15 +00:00
devicepersistency="by-uuid"
bootpartition="true" bootpartsize="1000" bootfilesystem="ext4" efipartsize="100" firmware="uefi"
rootfs_label="fedora"
>
platforms/vagrant: Define Vagrant images for libvirt and VirtualBox KIWI differentiates between libvirt and VirtualBox based Vagrant images, especially for the box format, so now we split up the Vagrant definition accordingly.
2023-10-14 20:30:57 +00:00
<bootloader name="grub2" console="serial" timeout="1"/>
<size unit="G">5</size>
<vagrantconfig provider="virtualbox" virtualbox_guest_additions_present="true" virtualsize="5"/>
<systemdisk>
<volume name="@root=root"/>
<volume name="home" parent="/"/>
<volume name="var" parent="/"/>
</systemdisk>
<oemconfig>
<oem-resize>false</oem-resize>
</oemconfig>
</type>
</preferences>
<users profiles="VagrantCore">
Initial import of descriptions
2023-10-14 19:21:23 +00:00
<!-- Standard password for the vagrant user, used by all images -->
<user name="vagrant" groups="vagrant" password="vagrant" home="/home/vagrant" pwdformat="plain" />
<user password="$1$wYJUgpM5$RXMMeASDc035eX.NbYWFl0" home="/root" name="root" groups="root"/>
</users>
platforms/vagrant: Define Vagrant images for libvirt and VirtualBox KIWI differentiates between libvirt and VirtualBox based Vagrant images, especially for the box format, so now we split up the Vagrant definition accordingly.
2023-10-14 20:30:57 +00:00
<packages type="image" patternType="plusRecommended" profiles="VagrantCore">
Initial import of descriptions
2023-10-14 19:21:23 +00:00
<package name="rsync"/>
<package name="fuse-sshfs"/>
<package name="gdisk"/>
<package name="glibc-langpack-en"/>
platforms/vagrant: Define Vagrant images for libvirt and VirtualBox KIWI differentiates between libvirt and VirtualBox based Vagrant images, especially for the box format, so now we split up the Vagrant definition accordingly.
2023-10-14 20:30:57 +00:00
</packages>
platforms, tmt: Rename and restructure cloud variants We now have more than one cloud system that is essentially a KVM environment that uses cloud-init to boot, so now we declare that "generic" and have the OpenStack and Oracle images reuse those definitions. Also, in preparation for layered cloud image variants, rename them from "Cloud-" to "Cloud-Base-". Vagrant variants are similarly prefixed to make it clear who provides them. Finally, restructure the layout of the tmt plans to match the description structure.
2023-12-21 14:04:37 +00:00
<packages type="image" patternType="plusRecommended" profiles="Cloud-Base-Vagrant-libvirt">
Initial import of descriptions
2023-10-14 19:21:23 +00:00
<package name="qemu-guest-agent"/>
</packages>
platforms, tmt: Rename and restructure cloud variants We now have more than one cloud system that is essentially a KVM environment that uses cloud-init to boot, so now we declare that "generic" and have the OpenStack and Oracle images reuse those definitions. Also, in preparation for layered cloud image variants, rename them from "Cloud-" to "Cloud-Base-". Vagrant variants are similarly prefixed to make it clear who provides them. Finally, restructure the layout of the tmt plans to match the description structure.
2023-12-21 14:04:37 +00:00
<packages type="image" patternType="plusRecommended" profiles="Cloud-Base-Vagrant-VirtualBox">
platforms/vagrant: Define Vagrant images for libvirt and VirtualBox KIWI differentiates between libvirt and VirtualBox based Vagrant images, especially for the box format, so now we split up the Vagrant definition accordingly.
2023-10-14 20:30:57 +00:00
<package name="virtualbox-guest-additions"/>
</packages>
<packages type="uninstall" profiles="VagrantCore">
platforms/vagrant: Remove cloud-init This is not used for Vagrant.
2023-10-14 20:08:29 +00:00
<package name="cloud-init"/>
</packages>
Initial import of descriptions
2023-10-14 19:21:23 +00:00
</image>
Reference in New Issue Copy Permalink