| Cloud/Atomic Test Day | |
|---|---|
| |
| Date | 2018-10-01 |
| 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 instalment of Fedora Test Day will focus on Fedora Atomic and Cloud images
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Dustymabe (irc dustymabe), Sinny Kumari (irc ksinny)
- Quality Assurance - Kamil Paral (irc kparal), Geoff Marr (irc coremodule), Sumantro Mukherjee (irc sumantrom)
Prerequisite for Test Day
A fresh system , testcloud to test qcow images locally, or access to a cloud provider like OpenStack or AWS ... a desire to break software?
Fedora Atomic
FAH can be run as a traditional cloud image, or installed to bare metal. Feel free to try out the cloud images locally as a VM. If you have a spare machine you can install FAH to, please test the ISO image (link in table below). Download the image, write it to a USB stick and install like any other Fedora deliverable. If you need help, please ping in IRC.
| Image | Image URL | Checksum URLs |
|---|---|---|
| Fedora AtomicHost qcow2 | x86_64 | |
| Fedora AtomicHost raw | ||
| Fedora AtomicHost Vagrant libvirt | ||
| Fedora AtomicHost Vagrant VirtualBox | ||
| Fedora AtomicHost ISO Installer |
If you have access to an AWS account then please try out an AMI from the following list:
Fedora-AtomicHost-29-20180923.n.0.x86_64 ap-northeast-1 ami-069abac4bd6e7815c hvm standard Fedora-AtomicHost-29-20180923.n.0.x86_64 ap-northeast-2 ami-02f34cb95604a59e0 hvm standard Fedora-AtomicHost-29-20180923.n.0.x86_64 ap-south-1 ami-0288e028bee1bb92a hvm standard Fedora-AtomicHost-29-20180923.n.0.x86_64 ap-southeast-1 ami-06f63ff5c20a9ecf0 hvm standard Fedora-AtomicHost-29-20180923.n.0.x86_64 ap-southeast-2 ami-02074915a91b9d086 hvm standard Fedora-AtomicHost-29-20180923.n.0.x86_64 ca-central-1 ami-0ee342a3faaf5ab44 hvm standard Fedora-AtomicHost-29-20180923.n.0.x86_64 eu-central-1 ami-0719b59d05d72f9d7 hvm standard Fedora-AtomicHost-29-20180923.n.0.x86_64 eu-west-1 ami-075fb2e48614077e3 hvm standard Fedora-AtomicHost-29-20180923.n.0.x86_64 eu-west-2 ami-049c55029b6842821 hvm standard Fedora-AtomicHost-29-20180923.n.0.x86_64 sa-east-1 ami-033a43896642f9ee1 hvm standard Fedora-AtomicHost-29-20180923.n.0.x86_64 us-east-1 ami-0ffeb08175d25a7b2 hvm standard Fedora-AtomicHost-29-20180923.n.0.x86_64 us-west-1 ami-027cbeeb07c50aeec hvm standard Fedora-AtomicHost-29-20180923.n.0.x86_64 us-west-2 ami-0f8389c40b585e464 hvm standard Fedora-AtomicHost-29-20180923.n.0.x86_64 ap-northeast-1 ami-05946cdf40a781cf9 hvm gp2 Fedora-AtomicHost-29-20180923.n.0.x86_64 ap-northeast-2 ami-069020818081822b0 hvm gp2 Fedora-AtomicHost-29-20180923.n.0.x86_64 ap-south-1 ami-02126821b7c6ed70e hvm gp2 Fedora-AtomicHost-29-20180923.n.0.x86_64 ap-southeast-1 ami-06138237f35bdc33d hvm gp2 Fedora-AtomicHost-29-20180923.n.0.x86_64 ap-southeast-2 ami-04b0e9057b29584e1 hvm gp2 Fedora-AtomicHost-29-20180923.n.0.x86_64 ca-central-1 ami-098cbda855581752b hvm gp2 Fedora-AtomicHost-29-20180923.n.0.x86_64 eu-central-1 ami-04fe16981e4e5a711 hvm gp2 Fedora-AtomicHost-29-20180923.n.0.x86_64 eu-west-1 ami-0ab2b1f4ce462ab85 hvm gp2 Fedora-AtomicHost-29-20180923.n.0.x86_64 eu-west-2 ami-042ed9f889a7302cd hvm gp2 Fedora-AtomicHost-29-20180923.n.0.x86_64 sa-east-1 ami-0496e2fa7fbe988e0 hvm gp2 Fedora-AtomicHost-29-20180923.n.0.x86_64 us-east-1 ami-01829fd040b71b94f hvm gp2 Fedora-AtomicHost-29-20180923.n.0.x86_64 us-west-1 ami-0d9f0c00165bf623e hvm gp2 Fedora-AtomicHost-29-20180923.n.0.x86_64 us-west-2 ami-0673605e79a10fe3c hvm gp2
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:
Fedora-Cloud-Base-29-20180923.n.0.x86_64 ap-northeast-1 ami-0b2e3cfb9df8e30ea hvm standard Fedora-Cloud-Base-29-20180923.n.0.x86_64 ap-northeast-2 ami-0ee78768385929685 hvm standard Fedora-Cloud-Base-29-20180923.n.0.x86_64 ap-south-1 ami-07a136826e4f5323d hvm standard Fedora-Cloud-Base-29-20180923.n.0.x86_64 ap-southeast-1 ami-037b0bb3f59b90c20 hvm standard Fedora-Cloud-Base-29-20180923.n.0.x86_64 ap-southeast-2 ami-00412273e1cee8115 hvm standard Fedora-Cloud-Base-29-20180923.n.0.x86_64 ca-central-1 ami-044e310ac31e94552 hvm standard Fedora-Cloud-Base-29-20180923.n.0.x86_64 eu-central-1 ami-02dc50c1a1300ec97 hvm standard Fedora-Cloud-Base-29-20180923.n.0.x86_64 eu-west-1 ami-06b2bf043f28735bc hvm standard Fedora-Cloud-Base-29-20180923.n.0.x86_64 eu-west-2 ami-09443add4299c22f7 hvm standard Fedora-Cloud-Base-29-20180923.n.0.x86_64 sa-east-1 ami-03c431386b7d65d23 hvm standard Fedora-Cloud-Base-29-20180923.n.0.x86_64 us-east-1 ami-0ad4fcc024259b6ce hvm standard Fedora-Cloud-Base-29-20180923.n.0.x86_64 us-west-1 ami-0344b62e1fef5feba hvm standard Fedora-Cloud-Base-29-20180923.n.0.x86_64 us-west-2 ami-0c5e4985cb2a5318d hvm standard Fedora-Cloud-Base-29-20180923.n.0.x86_64 ap-northeast-1 ami-004f2a3dd2234a592 hvm gp2 Fedora-Cloud-Base-29-20180923.n.0.x86_64 ap-northeast-2 ami-0ee25d78fa801ff79 hvm gp2 Fedora-Cloud-Base-29-20180923.n.0.x86_64 ap-south-1 ami-0b95feae82a9686ae hvm gp2 Fedora-Cloud-Base-29-20180923.n.0.x86_64 ap-southeast-1 ami-004ce56719079d085 hvm gp2 Fedora-Cloud-Base-29-20180923.n.0.x86_64 ap-southeast-2 ami-02fda73835af3f01d hvm gp2 Fedora-Cloud-Base-29-20180923.n.0.x86_64 ca-central-1 ami-0ef794da56e9242f0 hvm gp2 Fedora-Cloud-Base-29-20180923.n.0.x86_64 eu-central-1 ami-08d1ac4a806e9d53e hvm gp2 Fedora-Cloud-Base-29-20180923.n.0.x86_64 eu-west-1 ami-0518acff137671371 hvm gp2 Fedora-Cloud-Base-29-20180923.n.0.x86_64 eu-west-2 ami-088153e287f05081c hvm gp2 Fedora-Cloud-Base-29-20180923.n.0.x86_64 sa-east-1 ami-0cd384fdaea2f9159 hvm gp2 Fedora-Cloud-Base-29-20180923.n.0.x86_64 us-east-1 ami-070851333ba7d218a hvm gp2 Fedora-Cloud-Base-29-20180923.n.0.x86_64 us-west-1 ami-093e7c93504ba9a0d hvm gp2 Fedora-Cloud-Base-29-20180923.n.0.x86_64 us-west-2 ami-0a6d5ece6ab22426d hvm gp2
Qcow2 images
The Fedora Cloud Base image and Atomic images 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 -y testcloud
Once it's installed, you can run testcloud like so:
testcloud instance create <name of instance> -u imag.qcow2
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:
Atomic:
- Deploy applications on top of Atomic
- Upgrades and downgrades of existing Atomic Hosts (preferably with applications running)
- Package layering with on top of the base Atomic OSTree
- Install Kubernetes, via ansible or kubeadm
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.