sig_cloud/diskimage-builder
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
3071457355
diskimage-builder/diskimage_builder/elements/bootloader/pkg-map

38 lines
1.2 KiB
Plaintext
Raw Normal View History

Fill out bootloader pkg-map Our bootloader install fails on non-gentoo builds due to missing pkg-map for grub-pc. This map should really live in the bootloader element, so move it there and fill it out. Change-Id: Ib11b9df84b593ab25232729a570c812f1b4b8774
2016-01-14 02:01:14 +00:00
{
"family": {
"gentoo": {
"dkms_package": "",
"extlinux": "syslinux",
Choose appropriate bootloader for block-device In the prior change we added block-device-[mbr|gpt|efi] elements to create appropriate disk-layouts. This adds an environment flag to each so the bootloader can install the right thing. The EFI install path is updated to work with this (this part a copy of I572937945adbb5adaa5cb09200752e323c2c9531) We do some basic sanity checking in the block-device elements; e.g. mbr is not suitable for aarch64, and efi is not suitable for power. This updates the bootloader to install EFI where appropriate Co-Authored-By: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org> Change-Id: Ib80acbfd9a12efd976c3fa15a5d1081eb0799305
2018-01-31 23:32:51 +00:00
"grub-pc": "grub",
update gentoo to allow building arm64 images Adds: 1. grub-efi package mappings 2. efi-64 support 3. default (openrc) arm64 profile 4. systemd arm64 profile Cleans up the keywords and use flags in 02-gentoo-02-flags. Most stuff was stablized. Also cleaned up some formatting for the if statements. Enables less trusted overlays (up to the end user to verify). in 10-gentoo-image I cleaned up some bash lint things as well. using && instead of -a and avoiding $? Change-Id: I3dffe1aab4bbdc4946a9bf2269bf0cde49529a4e
2020-08-13 03:23:29 +00:00
"grub-efi": "grub",
"grub-efi-amd64": "grub",
"grub-efi-arm64": "grub",
"grub-efi-aarch64": "grub"
Fill out bootloader pkg-map Our bootloader install fails on non-gentoo builds due to missing pkg-map for grub-pc. This map should really live in the bootloader element, so move it there and fill it out. Change-Id: Ib11b9df84b593ab25232729a570c812f1b4b8774
2016-01-14 02:01:14 +00:00
},
"suse": {
Fix OpenSUSE support The dhcp-all-interfaces and simple-init elements did not have the ISC DHCP Client package mapped for OpenSUSE, which caused DIB to fail with "'isc-dhcp-client' not found in package names. Trying capabilities." Similarly, the bootloader element did not have the grub-pc package properly mapped for OpenSuse, which caused DIB to fail with "Package 'grub-pc' not found.". This patch adds the package mappings for these elements so that the opensuse element can be created and booted successfully. Change-Id: Ife478158fec3a95de73a9206b38dcc6511d56cc8
2016-05-04 05:23:51 +00:00
"dkms_package": "",
drop deprecated map-services/packages from zypper element Change-Id: Ie3065dcc6aefccba93c02085e9977681d1b0535c
2017-04-07 16:22:51 +00:00
"extlinux": "syslinux",
Choose appropriate bootloader for block-device In the prior change we added block-device-[mbr|gpt|efi] elements to create appropriate disk-layouts. This adds an environment flag to each so the bootloader can install the right thing. The EFI install path is updated to work with this (this part a copy of I572937945adbb5adaa5cb09200752e323c2c9531) We do some basic sanity checking in the block-device elements; e.g. mbr is not suitable for aarch64, and efi is not suitable for power. This updates the bootloader to install EFI where appropriate Co-Authored-By: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org> Change-Id: Ib80acbfd9a12efd976c3fa15a5d1081eb0799305
2018-01-31 23:32:51 +00:00
"grub-pc": "grub2",
"grub-efi": "grub2"
Add pkg-map for redhat The bootloader element lacks the mapping for grub-pc and extlinux This adds it. Change-Id: Ic7b82903f02faaab143d2bd682876bf4853fd90d Closes-Bug: 1534387
2016-01-15 20:06:16 +00:00
},
"redhat": {
"extlinux": "syslinux-extlinux",
Support for Cloud Images on ppc64le for rhel7 and centos7 In order to support {CentOS,RHEL}7 for building cloud images we need to handle the differences in grub packaging from Ubuntu. We also need to populate the defualt location for cloud images for CentOS builds. Change-Id: Ie0d82ff21a42b08c4cb94b7a5635f80bfabf684e
2017-04-12 05:26:27 +00:00
"grub-pc": "grub2-tools grub2",
Support secure-boot bootloader where possible As of grub2 >= 2.02-95 on redhat family distros, calling grub2-install on an EFI partition will fail with: "this utility cannot be used for EFI platforms because it does not support UEFI Secure Boot." This version of grub is now in centos8-stream and non-eus repos of RHEL-8. It is not currently possible to build whole-disk UEFI images on these distros, and when this package is promoted this will also affect centos8 and RHEL-8 eus. The grub maintainers made this change because the grub2-install generated /boot/efi/EFI/BOOT/BOOTX64.EFI will never be capable of booting with Secure Boot. This change defines a $EFI_BOOT_DIR for every distro element. When directory /boot/efi/$EFI_BOOT_DIR exists a grub.cfg file in will be generated there. This change also installs the shim package on redhat family distros, which installs a copy of the shim bootloader to /boot/efi/EFI/BOOT/BOOTX64.EFI. Using centos as an example, this allows UEFI to boot the shim /boot/efi/EFI/BOOT/BOOTX64.EFI which then chains to /boot/efi/EFI/centos/grubx64.efi. If /boot/efi/$EFI_BOOT_DIR doesn't exist (such as for Ubuntu, /boot/efi/EFI/ubuntu) the current behaviour of running grub-install to generate /boot/efi/EFI/BOOT/BOOTX64.EFI will continue. For distros such as Ubutnu where packaging does not populate /boot/efi/EFI/ubuntu with .efi files, secure boot can be added in the future by copying .efi files to /boot/efi/EFI/ubuntu and copying the shim file to /boot/efi/EFI/BOOT/BOOTX64.EFI. Change-Id: I90925218ff2aa4c4daffcf86e686b6d98d6b0f21
2021-03-05 03:35:21 +00:00
"grub-efi-amd64": "grub2-tools grub2 grub2-pc grub2-efi-x64 grub2-efi-x64-modules efibootmgr shim-x64",
"grub-efi-arm64": "grub2-tools grub2-efi-aa64 grub2-efi-aa64-modules efibootmgr shim-aa64",
"grub-efi-aarch64": "grub2-tools grub2-efi-aa64 grub2-efi-aa64-modules efibootmgr shim-aa64",
Add efibootmgr utility for UEFI boot menu management As of grub2 >= 2.02-95 calling grub2-install on an EFI partition will fail with: "this utility cannot be used for EFI platforms because it does not support UEFI Secure Boot." In the case of ironic deployments, ironic-python-agent will call efibootmgr to set the local boot for subsequent boots. This change adds efibootmgr to the image as well so any other UEFI menu changes can be made manually. Change-Id: I765ded15da07d6227d1e337960e54ad0e0d6ca39
2021-03-04 21:00:49 +00:00
"grub-efi": "grub2-tools grub2-efi efibootmgr",
Support secure-boot bootloader where possible As of grub2 >= 2.02-95 on redhat family distros, calling grub2-install on an EFI partition will fail with: "this utility cannot be used for EFI platforms because it does not support UEFI Secure Boot." This version of grub is now in centos8-stream and non-eus repos of RHEL-8. It is not currently possible to build whole-disk UEFI images on these distros, and when this package is promoted this will also affect centos8 and RHEL-8 eus. The grub maintainers made this change because the grub2-install generated /boot/efi/EFI/BOOT/BOOTX64.EFI will never be capable of booting with Secure Boot. This change defines a $EFI_BOOT_DIR for every distro element. When directory /boot/efi/$EFI_BOOT_DIR exists a grub.cfg file in will be generated there. This change also installs the shim package on redhat family distros, which installs a copy of the shim bootloader to /boot/efi/EFI/BOOT/BOOTX64.EFI. Using centos as an example, this allows UEFI to boot the shim /boot/efi/EFI/BOOT/BOOTX64.EFI which then chains to /boot/efi/EFI/centos/grubx64.efi. If /boot/efi/$EFI_BOOT_DIR doesn't exist (such as for Ubuntu, /boot/efi/EFI/ubuntu) the current behaviour of running grub-install to generate /boot/efi/EFI/BOOT/BOOTX64.EFI will continue. For distros such as Ubutnu where packaging does not populate /boot/efi/EFI/ubuntu with .efi files, secure boot can be added in the future by copying .efi files to /boot/efi/EFI/ubuntu and copying the shim file to /boot/efi/EFI/BOOT/BOOTX64.EFI. Change-Id: I90925218ff2aa4c4daffcf86e686b6d98d6b0f21
2021-03-05 03:35:21 +00:00
"grub-efi-x86_64": "grub2-tools grub2 grub2-efi-x64 grub2-efi-x64-modules efibootmgr shim-x64",
Support for Cloud Images on ppc64le for rhel7 and centos7 In order to support {CentOS,RHEL}7 for building cloud images we need to handle the differences in grub packaging from Ubuntu. We also need to populate the defualt location for cloud images for CentOS builds. Change-Id: Ie0d82ff21a42b08c4cb94b7a5635f80bfabf684e
2017-04-12 05:26:27 +00:00
"grub-ppc64": "grub2-tools grub2"
Fill out bootloader pkg-map Our bootloader install fails on non-gentoo builds due to missing pkg-map for grub-pc. This map should really live in the bootloader element, so move it there and fill it out. Change-Id: Ib11b9df84b593ab25232729a570c812f1b4b8774
2016-01-14 02:01:14 +00:00
}
},
"default": {
"dkms_package": "dkms",
"extlinux": "extlinux",
Support for Cloud Images on ppc64le for rhel7 and centos7 In order to support {CentOS,RHEL}7 for building cloud images we need to handle the differences in grub packaging from Ubuntu. We also need to populate the defualt location for cloud images for CentOS builds. Change-Id: Ie0d82ff21a42b08c4cb94b7a5635f80bfabf684e
2017-04-12 05:26:27 +00:00
"grub-pc": "grub-pc",
Add efibootmgr utility for UEFI boot menu management As of grub2 >= 2.02-95 calling grub2-install on an EFI partition will fail with: "this utility cannot be used for EFI platforms because it does not support UEFI Secure Boot." In the case of ironic deployments, ironic-python-agent will call efibootmgr to set the local boot for subsequent boots. This change adds efibootmgr to the image as well so any other UEFI menu changes can be made manually. Change-Id: I765ded15da07d6227d1e337960e54ad0e0d6ca39
2021-03-04 21:00:49 +00:00
"grub-efi-amd64": "grub-efi grub-pc-bin efibootmgr",
Support secure-boot bootloader where possible As of grub2 >= 2.02-95 on redhat family distros, calling grub2-install on an EFI partition will fail with: "this utility cannot be used for EFI platforms because it does not support UEFI Secure Boot." This version of grub is now in centos8-stream and non-eus repos of RHEL-8. It is not currently possible to build whole-disk UEFI images on these distros, and when this package is promoted this will also affect centos8 and RHEL-8 eus. The grub maintainers made this change because the grub2-install generated /boot/efi/EFI/BOOT/BOOTX64.EFI will never be capable of booting with Secure Boot. This change defines a $EFI_BOOT_DIR for every distro element. When directory /boot/efi/$EFI_BOOT_DIR exists a grub.cfg file in will be generated there. This change also installs the shim package on redhat family distros, which installs a copy of the shim bootloader to /boot/efi/EFI/BOOT/BOOTX64.EFI. Using centos as an example, this allows UEFI to boot the shim /boot/efi/EFI/BOOT/BOOTX64.EFI which then chains to /boot/efi/EFI/centos/grubx64.efi. If /boot/efi/$EFI_BOOT_DIR doesn't exist (such as for Ubuntu, /boot/efi/EFI/ubuntu) the current behaviour of running grub-install to generate /boot/efi/EFI/BOOT/BOOTX64.EFI will continue. For distros such as Ubutnu where packaging does not populate /boot/efi/EFI/ubuntu with .efi files, secure boot can be added in the future by copying .efi files to /boot/efi/EFI/ubuntu and copying the shim file to /boot/efi/EFI/BOOT/BOOTX64.EFI. Change-Id: I90925218ff2aa4c4daffcf86e686b6d98d6b0f21
2021-03-05 03:35:21 +00:00
"grub-efi-arm64": "grub-efi-arm64 grub-efi-arm64-bin efibootmgr",
Support for Cloud Images on ppc64le for rhel7 and centos7 In order to support {CentOS,RHEL}7 for building cloud images we need to handle the differences in grub packaging from Ubuntu. We also need to populate the defualt location for cloud images for CentOS builds. Change-Id: Ie0d82ff21a42b08c4cb94b7a5635f80bfabf684e
2017-04-12 05:26:27 +00:00
"grub-ppc64": "grub-ieee1275"
Fill out bootloader pkg-map Our bootloader install fails on non-gentoo builds due to missing pkg-map for grub-pc. This map should really live in the bootloader element, so move it there and fill it out. Change-Id: Ib11b9df84b593ab25232729a570c812f1b4b8774
2016-01-14 02:01:14 +00:00
}
}
Reference in New Issue Copy Permalink