| Cloud Test Day | |
|---|---|
| |
| Date | 2021-10-11 to 2021-10-12 |
| Time | all day |
| Website | QA/Test Days |
| IRC | #fedora-test-day (webirc) |
| Mailing list | test |
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 35 Cloud images
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Dustymabe (irc dustymabe), davedunc (irc davedunc), mhayden (irc mhayden), otubo (irc otubo)
- Quality Assurance - Kamil Paral (irc kparal), Geoff Marr (irc coremodule), Sumantro Mukherjee (irc sumantrom)
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 | ||
| Fedora Cloud raw | ||
| 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:
This section will be populated a day before the test day happens
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 can launch a VM directly with:
echo mypasswd > passwordfile virt-install --import --name cloudtest \ --memory 2000 --network bridge=virbr0 \ --os-variant detect=on,name=fedora-unknown \ --cloud-init root-password-file=./passwordfile \ --disk=size=10,backing_store="/path/to/Fedora-Cloud-Base-xxx.qcow2"
Note that you can only log in with a password on the console of the machine. Not via SSH. If you'd like to ssh you can use:
virt-install --import --name cloudtest \ --memory 2000 --network bridge=virbr0 \ --os-variant detect=on,name=fedora-unknown \ --cloud-init ssh-key=/home/user/.ssh/id_rsa.pub \ --disk=size=10,backing_store="/path/to/Fedora-Cloud-Base-xxx.qcow2"
If you'd like to use your own cloud-init yaml file to test with you can do that too. Here's is a very short example. First create a file with name cloudinit-user-data.yaml:
#cloud-config
password: 'mypasswd'
chpasswd: { expire: false }
Then run:
virt-install --import --name cloudtest \ --memory 2000 --network bridge=virbr0 \ --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:
Cloud:
- 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.