Line 150: | Line 150: | ||
=== Atomic Docker Tests === | === Atomic Docker Tests === | ||
For the Atomic Tests, download the latest image from | For the Atomic Tests, download the latest image from and execute tests | ||
{| | {| |
Revision as of 03:11, 22 September 2015
Fedora Test Days | |
---|---|
Easily deploy and manage your Docker containers | |
Date | 22 Sep 2015 |
Time | all day |
Website | QA/Fedora_23_test_days |
IRC | #atomic (webirc) |
Mailing list | cloud |
What to test?
Today's installment of Fedora Test Day will focus on Fedora Atomic
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Cloud SIG - Dusty Mabe (dustymabe),
- Quality Assurance - Roshi (roshi)
- Cloud / Infra - Adam Miller (maxamillion)
Prerequisite for Test Day
You'll need to either have an AWS account or a system that's capable of running one of the Atomic images for KVM/OpenStack.
- OpenStack installation [outside the scope of test day to set up!]
- Virt-Manager or KVM setup to run the qcow2 image.
- Run testcloud locally
We need to add links to images here.
Links for "how to setup" for the Test Day
- Refer quickstart guide for setup Atomic with Virt-manager or KVM
- Don't know how to create cloud init iso? refer running-cloud-images-locally
AMIs for Test Day
Update this table with correct AMIs NOTE: We are not going to be testing AMIs on this test day
Region | AMI name |
---|---|
us-east-1 | ami-xxxxxxxx |
us-west-1 | ami-xxxxxxxx |
us-west-2 | ami-xxxxxxxx |
eu-west-1 | ami-xxxxxxxx |
eu-central-1 | ami-xxxxxxxx |
ap-southeast-1 | ami-xxxxxxxx |
ap-northeast-1 | ami-xxxxxxxx |
ap-southeast-2 | ami-xxxxxxxx |
sa-east-1 | ami-xxxxxxxx |
How to test?
We need to test several things on the Fedora Atomic release before Fedora 23 Final.
- Test with a variety of Docker images. We do want to test the Fedora images in particular, but also we need to test a wide variety of images to see if there are any hidden bugs or problems we might not have noticed yet.
- Test Cockpit to make sure that managing Docker images and connecting multiple hosts works.
- Try out Kubernetes and make sure those packages are working.
- Test out the rpm-ostree/atomic update/rollback commands and other functions.
- Try out docker-storage-config.
- What is the image/package set missing? What is unnecessary?
Grab the Image
Update the image links here
To test Fedora Atomic, we're going to use a beta image located here: [1].
Test Cases
Fedora Cloud Working Group member Dusty Mabe has quite a few tests on this Gist. For other examples, see Category:Test_Cases.
For better worded test steps please refer to Mike's pages: User:Roshi/QA/AtomicTests
Additionally, many of the tests that are written for Cloud Base also apply to atomic. The tests are located here. If you don't know if the test applies to Atomic or not then feel free to ask in #fedora-cloud on freenode.
Test Results
If you are unsure about exactly how to file a bug report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the appropriate table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one. For each test case, use the result template to enter your result, as shown in the example result line.
Atomic Basic Cloud Tests
User | Hardware | Startup | System Logging | Services Start | SELinux | Service Manipulation | References |
---|---|---|---|---|---|---|---|
Example User | Example Hardware |
Atomic Host Tests DO NOT EXECUTE THESE TESTS - NO UPDATE TREES ARE AVAILABLE
For the Atomic Tests, download the latest image from and execute tests
User | Hardware | Image Boots | Upgrade Works | Rollback Works | References |
---|---|---|---|---|---|
Example | Example Hardware |
Atomic Docker Tests
For the Atomic Tests, download the latest image from and execute tests
User | Hardware | docker-storage-setup | Docker Lifecycle | Docker Image Test | References |
---|---|---|---|---|---|
Example Username | Example hardware |