aboutsummaryrefslogtreecommitdiff
path: root/teams/cloud/cloud.xml
AgeCommit message (Collapse)Author
2024-09-25Azure: include azure-vm-utils package in the imageGravatar Jeremy Cline
This package is intended to be the place for Azure utilities along with the various udev rules that currently live in the WALinuxAgent package. At the moment it just contains the `azure-nvme-id` binary and udev rules for providing symlinks in /dev/disk/azure/ for local, data, and OS disks.
2024-06-03cloud: updates for s390xGravatar Dan Horák
updates for "virtual image" usable under KVM - don't use 4k block size - don't use CDL partitioning - don't use DASD related kernel parameters
2024-06-03cloud: don't use 4k block size on ppc64leGravatar Dan Horák
2024-05-22Disable systemd-firstboot on Cloud images via cmdline (#2282195)Gravatar Adam Williamson
systemd 256 added a new feature which wants to create users on boot if none exist yet: https://github.com/systemd/systemd/commit/3ccadbce3358ba1db7ce5fa3f8dd17c627ffd93b We don't want that, cloud-init handles this situation. So let's disable it. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-05-10AmazonEC2: Add more helpful packagesGravatar Major Hayden
The amazon-ec2-utils package includes udev rules that make it easier to identify block storage devices and sets some configuration for other storage devices. Users can run awscli2 to manage their AWS cloud resources. The ec2-instance-connect package allows one click console access to a Fedora instance from the AWS console (website). Signed-off-by: Major Hayden <major@redhat.com>
2024-05-03Add btrfs-progs to Cloud imagesGravatar Adam Williamson
It was previously being pulled in via weak dependencies of fwupd, but we removed fwupd in #47 and now it's not there any more. It is needed for the first boot resize by cloud-init to work, since we use a btrfs filesystem. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-05-01cloud: exclude fwupd from cloud imagesGravatar Yanko Kaneti
2024-04-15cloud: Consistent device namingGravatar Major Hayden
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-03teams/cloud/cloud: add console="serial" to grub2Gravatar František Zatloukal
Fixes booting the Generic image on systems without any video device. ref. https://github.com/teemtee/tmt/issues/2771
2024-03-20cloud: set Google root size to 10 GB and EC2 back to 5 GBGravatar Adam Williamson
It's the *Google* image that's required to have a 10 GB root for performance reasons, not the EC2 image, as the comment says, but the change was inadvertently applied to the EC2 image not the Google one. This means our Google image is slow and our EC2 images are failing to be published as AMIs. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-03-11Add s390x variant for Cloud-Base-GenericGravatar Neal Gompa
This allows building cloud images for Z systems.
2024-03-06teams/cloud/cloud: Bump the Google Cloud image to 10GGravatar Neal Gompa
Anything lower than that causes performance problems.
2024-03-04Install fedora-release-* at bootstrap phase for various imagesGravatar Neal Gompa
This ensures that the correct variant packages are installed.
2024-02-24Add ppc64le variant for Cloud-Base-GenericGravatar Neal Gompa
This allows building cloud images for POWER systems.
2024-02-24teams/cloud: Define compatible architectures for existing profilesGravatar Neal Gompa
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-23teams/cloud: Reformat profile image types for readabilityGravatar Neal Gompa
This makes it easier to read what all the settings are.
2024-02-23azure: install the hyperv-daemons packageGravatar Jeremy Cline
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-23azure: support accelerated networking featureGravatar Jeremy Cline
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-23azure: ensure early boot messages are directed to the serial consoleGravatar Jeremy Cline
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-22Reorganize configuration around Fedora teamsGravatar Neal Gompa
This realigns the configuration into separate files/folders that would be modified by specific teams (e.g. WGs and SIGs).