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

153 lines
6.4 KiB
XML
Raw Normal View History

Initial import of descriptions
2023-10-14 19:21:23 +00:00
<image>
<profiles>
<profile name="CloudCore" description="Cloud spin core packages">
<requires profile="BootCore"/>
</profile>
platforms/cloud: add Cloud-Base-UEFI-UKI profile This is a variation of Cloud-Base-Generic which boots using UKIs. This also adds uki-editbootconfig.sh script which makes the image bootable via "UEFI firmware -> shim.efi -> UKI.efi". Some background information: https://fedoraproject.org/wiki/Changes/Unified_Kernel_Support_Phase_2 Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
2023-11-30 14:21:36 +00:00
<profile name="CloudCoreUKI" description="Cloud spin core packages for UKI">
<requires profile="BootCoreUKI"/>
</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-Azure" description="Azure Base Guest Image">
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-AmazonEC2" description="Amazon EC2 HVM Base Guest Image">
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-GCE" description="GCE Base Guest Image">
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-Generic" description="Generic Base Guest Image">
Initial import of descriptions
2023-10-14 19:21:23 +00:00
<requires profile="CloudCore"/>
</profile>
platforms/cloud: add Cloud-Base-UEFI-UKI profile This is a variation of Cloud-Base-Generic which boots using UKIs. This also adds uki-editbootconfig.sh script which makes the image bootable via "UEFI firmware -> shim.efi -> UKI.efi". Some background information: https://fedoraproject.org/wiki/Changes/Unified_Kernel_Support_Phase_2 Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
2023-11-30 14:21:36 +00:00
<profile name="Cloud-Base-UEFI-UKI" description="UEFI Base Guest Image using UKIs">
<requires profile="CloudCoreUKI"/>
</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-OpenStack" description="OpenStack Base Guest Image">
<requires profile="Cloud-Base-Generic"/>
</profile>
<profile name="Cloud-Base-Oracle" description="Oracle Cloud Base Guest Image">
<requires profile="Cloud-Base-Generic"/>
platforms/cloud: Add Oracle Cloud image Oracle Cloud images are KVM cloud images, just like the OpenStack images. Reuse the OpenStack image definition for Oracle Cloud.
2023-10-14 20:50:29 +00:00
</profile>
Initial import of descriptions
2023-10-14 19:21:23 +00:00
</profiles>
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
<preferences profiles="Cloud-Base-Azure">
azure: ensure early boot messages are directed to the serial console In the event that there's an issue with early boot, setting earlyprintk=ttyS0 ensures that the messages are routed to the serial console so it can be debugged. This particular option is documented as required in the Azure VM certification FAQ[0]. [0] https://learn.microsoft.com/en-us/partner-center/marketplace/azure-vm-certification-faq#linux-test-cases
2024-02-22 21:11:15 +00:00
<type image="oem" filesystem="btrfs" kernelcmdline="no_timer_check net.ifnames=0 console=tty1 console=ttyS0,115200n8 earlyprintk=ttyS0" devicepersistency="by-uuid" formatoptions="force_size" format="vhd-fixed" bootpartition="true" bootpartsize="1000" bootfilesystem="ext4" efipartsize="100" firmware="uefi" fsmountoptions="compress=zstd:1" btrfs_root_is_subvolume="true" btrfs_set_default_volume="false" rootfs_label="fedora">
Initial import of descriptions
2023-10-14 19:21:23 +00:00
<bootloader name="grub2" console="serial" timeout="0"/>
<systemdisk>
<volume name="@root=root"/>
<volume name="home" parent="/"/>
<volume name="var" parent="/"/>
</systemdisk>
<size unit="G">5</size>
<oemconfig>
<oem-resize>false</oem-resize>
</oemconfig>
</type>
</preferences>
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
<preferences profiles="Cloud-Base-AmazonEC2">
Initial import of descriptions
2023-10-14 19:21:23 +00:00
<type image="oem" filesystem="btrfs" kernelcmdline="no_timer_check net.ifnames=0 console=tty1 console=ttyS0,115200n8" devicepersistency="by-uuid" bootpartition="true" bootpartsize="1000" bootfilesystem="ext4" efipartsize="100" firmware="uefi" fsmountoptions="compress=zstd:1" btrfs_root_is_subvolume="true" btrfs_set_default_volume="false" rootfs_label="fedora">
<bootloader name="grub2" timeout="0"/>
<size unit="G">5</size>
<systemdisk>
<volume name="@root=root"/>
<volume name="home" parent="/"/>
<volume name="var" parent="/"/>
</systemdisk>
<oemconfig>
<oem-resize>false</oem-resize>
</oemconfig>
</type>
</preferences>
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
<preferences profiles="Cloud-Base-GCE">
Initial import of descriptions
2023-10-14 19:21:23 +00:00
<type image="oem" filesystem="btrfs" kernelcmdline="no_timer_check net.ifnames=0 console=ttyS0,38400n8d" devicepersistency="by-uuid" bootpartition="true" bootpartsize="1000" bootfilesystem="ext4" efipartsize="100" format="gce" firmware="uefi" fsmountoptions="compress=zstd:1" btrfs_root_is_subvolume="true" btrfs_set_default_volume="false" rootfs_label="fedora">
<bootloader name="grub2" timeout="0"/>
<size unit="G">5</size>
<systemdisk>
<volume name="@root=root"/>
<volume name="home" parent="/"/>
<volume name="var" parent="/"/>
</systemdisk>
<oemconfig>
<oem-resize>false</oem-resize>
</oemconfig>
</type>
</preferences>
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
<preferences profiles="Cloud-Base-Generic">
Initial import of descriptions
2023-10-14 19:21:23 +00:00
<type image="oem" filesystem="btrfs" kernelcmdline="no_timer_check net.ifnames=0 console=tty1 console=ttyS0,115200n8" devicepersistency="by-uuid" bootpartition="true" bootpartsize="1000" bootfilesystem="ext4" efipartsize="100" firmware="uefi" format="qcow2" fsmountoptions="compress=zstd:1" btrfs_root_is_subvolume="true" btrfs_set_default_volume="false" rootfs_label="fedora">
<bootloader name="grub2" timeout="0"/>
<size unit="G">5</size>
<systemdisk>
<volume name="@root=root"/>
<volume name="home" parent="/"/>
<volume name="var" parent="/"/>
</systemdisk>
<oemconfig>
<oem-resize>false</oem-resize>
</oemconfig>
</type>
</preferences>
platforms/cloud: add Cloud-Base-UEFI-UKI profile This is a variation of Cloud-Base-Generic which boots using UKIs. This also adds uki-editbootconfig.sh script which makes the image bootable via "UEFI firmware -> shim.efi -> UKI.efi". Some background information: https://fedoraproject.org/wiki/Changes/Unified_Kernel_Support_Phase_2 Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
2023-11-30 14:21:36 +00:00
<preferences profiles="Cloud-Base-UEFI-UKI">
<type image="oem" format="qcow2"
firmware="uefi" efipartsize="1000"
bootpartition="false"
filesystem="btrfs" btrfs_root_is_subvolume="true" btrfs_set_default_volume="true"
devicepersistency="by-uuid"
rootfs_label="fedora"
initrd_system="none"
editbootconfig="uki-editbootconfig.sh"
>
<bootloader name="custom"/>
<size unit="G">5</size>
<systemdisk>
<volume name="@root=root"/>
<volume name="home" parent="/"/>
<volume name="var" parent="/"/>
</systemdisk>
<oemconfig>
<oem-resize>false</oem-resize>
</oemconfig>
</type>
</preferences>
Initial import of descriptions
2023-10-14 19:21:23 +00:00
<packages type="image" patternType="plusRecommended" profiles="CloudCore">
<namedCollection name="cloud-server-environment"/>
<ignore name="dracut-config-rescue"/>
<ignore name="firewalld"/>
<ignore name="kernel"/>
<ignore name="*-firmware"/>
<ignore name="geolite2-city"/>
<ignore name="geolite2-country"/>
<ignore name="plymouth"/>
<package name="python3-dnf-plugin-tracer"/>
<package name="glibc-langpack-en"/>
</packages>
platforms/cloud: add Cloud-Base-UEFI-UKI profile This is a variation of Cloud-Base-Generic which boots using UKIs. This also adds uki-editbootconfig.sh script which makes the image bootable via "UEFI firmware -> shim.efi -> UKI.efi". Some background information: https://fedoraproject.org/wiki/Changes/Unified_Kernel_Support_Phase_2 Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
2023-11-30 14:21:36 +00:00
<packages type="image" patternType="plusRecommended" profiles="CloudCoreUKI">
<namedCollection name="cloud-server-environment"/>
<ignore name="dracut-config-rescue"/>
<ignore name="firewalld"/>
<ignore name="kernel"/>
<ignore name="[a-oq-z]*-firmware"/>
<ignore name="geolite2-city"/>
<ignore name="geolite2-country"/>
<ignore name="plymouth"/>
<package name="python3-dnf-plugin-tracer"/>
<package name="glibc-langpack-en"/>
</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-Azure">
Initial import of descriptions
2023-10-14 19:21:23 +00:00
<package name="WALinuxAgent"/>
azure: support accelerated networking feature Azure provides an optional "Accelerated Networking" feature. Enabling this feature when creating a VM enables SR-IOV and provides the guest with a virtual function. Supporting this requires two changes. Firstly, the kernel-modules package is required as it contains the Mellanox drivers required for the VF provided to the guest. Secondly, the interface needs to be ignored by NetworkManager or it'll try and fail to bring up the device and the VM will be unreachable except by serial console. If this is observed, it's likely new hardware has been deployed and additional drivers need to be added to the NetworkManager config. See https://learn.microsoft.com/en-us/azure/virtual-network/accelerated-networking-overview for details.
2024-02-22 21:16:31 +00:00
<package name="kernel-modules"/>
azure: install the hyperv-daemons package This pulls in a number of services to integrate a guest running under Hyper-V. These services are all automatically activated via udev rules.
2024-02-22 21:36:49 +00:00
<package name="hyperv-daemons"/>
Initial import of descriptions
2023-10-14 19:21:23 +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-GCE">
Initial import of descriptions
2023-10-14 19:21:23 +00:00
<package name="google-compute-engine-guest-configs"/>
<package name="google-compute-engine-oslogin"/>
<package name="google-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-Generic">
Initial import of descriptions
2023-10-14 19:21:23 +00:00
<package name="qemu-guest-agent"/>
</packages>
platforms/cloud: add Cloud-Base-UEFI-UKI profile This is a variation of Cloud-Base-Generic which boots using UKIs. This also adds uki-editbootconfig.sh script which makes the image bootable via "UEFI firmware -> shim.efi -> UKI.efi". Some background information: https://fedoraproject.org/wiki/Changes/Unified_Kernel_Support_Phase_2 Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
2023-11-30 14:21:36 +00:00
<packages type="image" patternType="plusRecommended" profiles="Cloud-Base-UEFI-UKI">
<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="uninstall" profiles="Cloud-Base-GCE">
Initial import of descriptions
2023-10-14 19:21:23 +00:00
<package name="cloud-init"/>
</packages>
</image>
Reference in New Issue Copy Permalink