From Fedora Project Wiki

Line 106: Line 106:
Once it's installed, you will have to create a small yaml file with name <pre>cloudinit-user-data.yaml</pre>
Once it's installed, you will have to create a small yaml file with name '''cloudinit-user-data.yaml'''
password: 'r00t'
password: 'r00t'
chpasswd: { expire: false }
chpasswd: { expire: false }
Once that is done, you can set up the instance using the following

Revision as of 18:52, 16 April 2021

Cloud Test Day

Date 2021-04-16 to 2021-04-19
Time all day

Website QA/Test Days
IRC #fedora-test-day (webirc)
Mailing list test

Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?

Today's installment of Fedora Test Day will focus on Fedora 34 Cloud images

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

Prerequisite for Test Day

Fedora Cloud Base

This section is for the Fedora Cloud Base images, which can be used to run a yum/dnf based fedora in the cloud or as a VM. There are also Vagrant boxes available.

Image Image URL Checksum URLs
Fedora Cloud qcow2

x86_64 ppc64le aarch64

x86_64 ppc64le aarch64

Fedora Cloud raw

x86_64 ppc64le aarch64

x86_64 ppc64le aarch64

Fedora Cloud Vagrant libvirt



Fedora Cloud Vagrant VirtualBox



If you have access to an AWS account then please try out an AMI from the following list:

Fedora-Cloud-Base-34-20210415.n.0.aarch64     ap-northeast-1       ami-0b24da31a2dcd3a94 hvm           gp2            
Fedora-Cloud-Base-34-20210415.n.0.aarch64     ap-northeast-2       ami-0bedaf0df665d5a44 hvm           gp2            
Fedora-Cloud-Base-34-20210415.n.0.aarch64     ap-south-1           ami-099d123da082621a0 hvm           gp2            
Fedora-Cloud-Base-34-20210415.n.0.aarch64     ap-southeast-1       ami-0651f0e11f4127a61 hvm           gp2            
Fedora-Cloud-Base-34-20210415.n.0.aarch64     ap-southeast-2       ami-0bb65d3b976623354 hvm           gp2            
Fedora-Cloud-Base-34-20210415.n.0.aarch64     ca-central-1         ami-0767dc10ce57476af hvm           gp2            
Fedora-Cloud-Base-34-20210415.n.0.aarch64     eu-central-1         ami-09a0ee57cb0c91ea4 hvm           gp2            
Fedora-Cloud-Base-34-20210415.n.0.aarch64     eu-west-1            ami-0fd79453e977958a7 hvm           gp2            
Fedora-Cloud-Base-34-20210415.n.0.aarch64     eu-west-2            ami-0d36c48662d320ec4 hvm           gp2            
Fedora-Cloud-Base-34-20210415.n.0.aarch64     sa-east-1            ami-04bf4423d20d241e7 hvm           gp2            
Fedora-Cloud-Base-34-20210415.n.0.aarch64     us-east-1            ami-0e34271bcd53f411f hvm           gp2            
Fedora-Cloud-Base-34-20210415.n.0.aarch64     us-east-2            ami-09be128e27e370675 hvm           gp2            
Fedora-Cloud-Base-34-20210415.n.0.aarch64     us-west-1            ami-066f7fd70190afa38 hvm           gp2            
Fedora-Cloud-Base-34-20210415.n.0.aarch64     us-west-2            ami-0a8893b934b00a65e hvm           gp2            

Fedora-Cloud-Base-34-20210415.n.0.x86_64      ap-northeast-1       ami-09cda636489eba7c4 hvm           gp2            
Fedora-Cloud-Base-34-20210415.n.0.x86_64      ap-northeast-2       ami-01902e2d4a2cde31b hvm           gp2            
Fedora-Cloud-Base-34-20210415.n.0.x86_64      ap-south-1           ami-09401f83dff3d2bba hvm           gp2            
Fedora-Cloud-Base-34-20210415.n.0.x86_64      ap-southeast-1       ami-0946bff62f882ea9e hvm           gp2            
Fedora-Cloud-Base-34-20210415.n.0.x86_64      ap-southeast-2       ami-06e0db38c8f42c5a2 hvm           gp2            
Fedora-Cloud-Base-34-20210415.n.0.x86_64      ca-central-1         ami-086f26b8c788ee7a0 hvm           gp2            
Fedora-Cloud-Base-34-20210415.n.0.x86_64      eu-central-1         ami-09b2d82880885a4d0 hvm           gp2            
Fedora-Cloud-Base-34-20210415.n.0.x86_64      eu-west-1            ami-086c20bedaa9e35f5 hvm           gp2            
Fedora-Cloud-Base-34-20210415.n.0.x86_64      eu-west-2            ami-0550015b642e7c89b hvm           gp2            
Fedora-Cloud-Base-34-20210415.n.0.x86_64      sa-east-1            ami-0f5dd6655dba5f0bd hvm           gp2            
Fedora-Cloud-Base-34-20210415.n.0.x86_64      us-east-1            ami-07a4dfef4b75d822b hvm           gp2            
Fedora-Cloud-Base-34-20210415.n.0.x86_64      us-east-2            ami-0cb9cd97ad38c338f hvm           gp2            
Fedora-Cloud-Base-34-20210415.n.0.x86_64      us-west-1            ami-0dd83807d0e613f79 hvm           gp2            
Fedora-Cloud-Base-34-20210415.n.0.x86_64      us-west-2            ami-0441f099256701a6d hvm           gp2

A fresh system, testcloud to test qcow images locally, or access to a cloud provider like OpenStack or AWS, and a desire to break software.

Qcow2 images

The Fedora Cloud Base image are also delivered as qcow2 images. You can use testcloud to locally boot and test either of these images. You can run testcloud from a git checkout, or use dnf to install it:

sudo dnf install virt-install

Once it's installed, you will have to create a small yaml file with name cloudinit-user-data.yaml

password: 'r00t'
chpasswd: { expire: false }

Once that is done, you can set up the instance using the following

virt-install --name <name_of_cloud> \ --memory 2000 --noreboot \ --os-variant detect=on,name=fedora-unknown \ --cloud-init user-data="/path/to/cloudinit-user-data.yaml" \ --disk=size=10,backing_store="/path/to/Fedora-Cloud-Base-xxx.qcow2"

You can also boot qcow2 images using virtualization clients like virt-manager or VirtualBox with instruction provided here

How to test?

This testday is more general, so attempt to do anything and everything with these images :) Specifically though, we'd like to take a look at the following scenarios:


  • Test different cloud-init configs
  • Deploy and run some applications in the cloud

EC2 If you have access to Amazon EC2, you can use one of the AMIs listed above for testing.

Run the tests

Visit the result page and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the Enter result button for the test.

This testday is also meant to be exploratory, so the list on the testday app is not at all comprehensive!

Reporting bugs

If you find anything that seems wrong or off, please report a bug on Bugzilla. The affected component should be clear from whatever error message you happen to find, but if you aren't sure, ask in IRC. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.

Test Results

Test results will be uploaded here once the test day is over