From Fedora Project Wiki

(Created page with " This is a placeholder. More information will be added shortly.")
 
No edit summary
Line 1: Line 1:
{{Infobox_group
| name = Fedora Test Days
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_22_test_days]]
| caption = Easily deploy and manage your Docker containers
| date = 07 May 2015
| time = all day
| website = [[QA/Fedora_22_test_days]]
| irc = [irc://irc.freenode.net/#atomic #atomic] ([http://webchat.freenode.net/?channels=atomic webirc])
| fedora_mailing_list = cloud
}}


This is a placeholder. More information will be added shortly.
{{admon/note | 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 [http://bugzilla.redhat.com 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 [[QA/Test_Days|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 Host'''
 
== Who's available ==
 
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
* Cloud SIG - [[user:dustymabe|Dusty Mabe]] (dustymabe),
* Quality Assurance - [[User:Roshi|Roshi]] (roshi)
 
 
== 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 [http://github.com/Rorosha/testCloud testCloud] locally
 
* An updated [https://kojipkgs.fedoraproject.org//work/tasks/8904/8118904/Fedora-Cloud-Atomic-20141112-21.x86_64.qcow2 test image], or later nightly live image if one is released before 20 November.
 
== Links for "how to setup" for the Test Day ==
 
* Refer [http://www.projectatomic.io/docs/quickstart/ quickstart guide] for setup Atomic with Virt-manager or KVM
* Don't know how to create cloud init iso? refer [https://www.technovelty.org//linux/running-cloud-images-locally.html running-cloud-images-locally]
 
== AMIs for Test Day ==
 
 
{| class="wikitable"
!Region
!AMI name
|-
|us-east-1     
|ami-XXXXXXXXX
|-
|us-west-1
|ami-XXXXXXXXX
|-
|us-west-2     
|ami-XXXXXXXXX
|-
|eu-west-1     
|ami-XXXXXXXXX
|-
|eu-central-1   
|ami-XXXXXXXXX
|-
|ap-southeast-1 
|ami-XXXXXXXXX
|-
|ap-northeast-1 
|ami-XXXXXXXXX
|-
|ap-southeast-2 
|ami-XXXXXXXXX
|-
|sa-east-1     
|ami-XXXXXXXXX
|}
 
== How to test? ==
 
We need to test several things on the Fedora Atomic release before Fedora 22 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''' ===
 
To test Fedora Atomic, we're going to use a Koji build located here: [https://kojipkgs.fedoraproject.org//work/tasks/8904/8118904/Fedora-Cloud-Atomic-20141112-21.x86_64.qcow2]. You can also use one of the AMIs if you would prefer to do your testing on Amazon Web Services.
 
== Test Cases ==
 
Fedora Cloud Working Group member Dusty Mabe has [https://gist.github.com/dustymabe/bf955b6afa8177ecf6fc 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]]
 
== Test Results ==
 
=== Atomic Tests ===
 
{|
! User
! Hardware
! [http://fedoraproject.org/wiki/User:Roshi/QA/AtomicTests/Atomic_Image_Boots Image Boots]
! [http://fedoraproject.org/wiki/User:Roshi/QA/AtomicTests/Atomic_Upgrade Upgrade Works]
! [http://fedoraproject.org/wiki/User:Roshi/QA/AtomicTests/Atomic_Rollback Rollback Works]
! References
|-
| [[User:larsks|larsks]]
| openstack
| {{result|pass}} 
| {{result|pass}} 
| {{result|pass}} 
| <references/>
|-
| [[User:ssamanta|ssamanta]]
| testvm1
| {{result|pass}} 
|
|
| <references/>
|-
| [[User:Anil|Anil]]
| Virt-Manager
| {{result|pass}}  {{result|pass}} 
| {{result|pass}} 
| {{result|pass}} 
| <references/>
|-
| [[User:amrithajij|amrithajij]]
| KVM
| {{result|warn}}  <ref group="long">All works well except the command - [ sh, -c, 'echo -e "ROOT_SIZE=4G DATA_SIZE=10G" > /etc/sysconfig/docker-storage-setup'] . Thus created the file manually and added ROOT_SIZE=4G DATA_SIZE=10G.</ref>
| {{result|pass}} 
| {{result|pass}} 
| <references/>
|-
| [[User:lnie|lnie]]
| KVM
| {{result|pass}} 
| {{result|pass}} 
|
| <references/>
|-
| [[User:roshi|roshi]]
| KVM
| {{result|pass}} 
| {{result|pass}} 
| {{result|pass}} 
| <references/>
|-
| [[User:sinnykumari|sinnykumari]]
| KVM
| {{result|warn}}  <ref group="long">I tried test mentioned on [[User:Roshi/QA/AtomicTests/Atomic_Image_Boots|roshi page]] . Everything worked well but "runcmd: - [ sh, -c, 'echo -e "ROOT_SIZE=4G DATA_SIZE=10G" > /etc/sysconfig/docker-storage-setup']" didn't run for me. So, added "ROOT_SIZE=4G DATA_SIZE=10G" content in etc/sysconfig/docker-storage-setup file manually.</ref>
|
|
| <references/>
|-
| [[User:sten|sten]]
| openstack RHOSP5 x64
| {{result|pass}} 
| {{result|pass}} 
| {{result|pass}} 
| <references/>
|-
| [[User:jzb|jzb]]
| KVM
| {{result|pass}}  <ref>Yup. Happy result there.</ref>
| {{result|pass}}  <ref>atomic upgrade worked a treat. All happy.</ref>
| {{result|pass}} 
| <references/>
|-
| [[User:jkalliyat|jkalliyat]]
| KVM
| {{result|warn}}  <ref>Executed the 'runcmd' manually to make it work. </ref>
|
|
| <references/>
|-
| [[User:dustymabe|dustymabe]]
| Openstack Juno on F21
| {{result|pass}} 
| {{result|pass}} 
| {{result|pass}} 
| <references/>
|-
| [[User:Prasanth|Prasanth]]
| VM on KVM
| {{result|warn}}  <ref>Executed the 'runcmd' manually to make it work.</ref>
| {{result|pass}} 
|
| <references/>
|-
| [[User:lalatendu|lalatendu]]
| VM on virt-manager
| {{result|pass}}  <ref>runcmd issue</ref>
| {{result|pass}}
| {{result|pass}}
| <references/>
|-
|}
 
=== Docker Tests ===
 
{|
! User
! Hardware
! [http://fedoraproject.org/wiki/User:Roshi/QA/AtomicTests/Atomic_Docker_Storage_Setup docker-storage-setup]
! [http://fedoraproject.org/wiki/User:Roshi/QA/AtomicTests/Atomic_Docker_Lifecycle Docker Lifecycle]
! References
|-
| [[User:larsks|larsks]]
| openstack
| {{result|pass}}  <ref>Appears to have run automatically (and successfully).</ref>
| {{result|pass}}  <ref>Started/interacted with/stopped fedora and ubuntu containers.</ref>
| <references/>
|-
| [[User:amrithajij|amrithajij]]
| KVM
| {{result|warn}}  <ref>Manually expanded the qcow2 image fron host and then ran journalctl -o cat --unit docker-storage-setup.service.</ref>
| {{result|pass}} 
| <references/>
|-
| [[User:roshi|roshi]]
| KVM
| {{result|pass}} 
| {{result|pass}} 
| <references/>
|-
| [[User:sinnykumari|sinnykumari]]
| KVM
| {{result|warn}}  <ref>In test case https://fedoraproject.org/wiki/User:Roshi/QA/AtomicTests/Atomic_Docker_Storage_Setup
 
changes get reflected after rebooting VM</ref>
|
| <references/>
|-
| [[User:sten|sten]]
| openstack RHOSP5 x64
| {{result|pass}} 
| {{result|pass||1164058}}
 
That confused me, but just using "sudo docker foo" works. </ref>
| <references/>
|-
| [[User:jzb|jzb]]
| KVM
| {{result|pass}}  <ref>Works a treat.</ref>
| {{result|pass}}  <ref>All good here.</ref>
| <references/>
|-
| [[User:dustymabe|dustymabe]]
| Openstack Juno on F21
| {{result|pass}} 
| {{result|pass}} 
| <references/>
|-
| [[User:lalatendu|lalatendu]]
| VM on virt-manager
| {{result|pass}}
</ref>
| {{result|pass}}
| <references/>
|-
| [[User:nkhare|nkhare]]
| vm
|
| {{result|pass}} 
| <references/>
|-
|}
 
=== Bugs filled during Test Day (7th May 2015) ===
[https://bugzilla.redhat.com/show_bug.cgi?id=1166073 1166073]
[https://bugzilla.redhat.com/show_bug.cgi?id=1166082 1166082]
 
=== Other Common Bugs ===
[https://bugzilla.redhat.com/show_bug.cgi?id=1164058 1164058]
 
== Long comments ==
<references group="long" />
 
[[Category:Fedora 22 Test Days]]

Revision as of 03:26, 1 May 2015

Fedora Test Days
Echo-testing-48px.png
Easily deploy and manage your Docker containers
Date 07 May 2015
Time all day
Website QA/Fedora_22_test_days
IRC #atomic (webirc)
Mailing list cloud


Note.png
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 instalment of Fedora Test Day will focus on Fedora Atomic Host

Who's available

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


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
  • An updated test image, or later nightly live image if one is released before 20 November.

Links for "how to setup" for the Test Day

AMIs for Test Day

Region AMI name
us-east-1 ami-XXXXXXXXX
us-west-1 ami-XXXXXXXXX
us-west-2 ami-XXXXXXXXX
eu-west-1 ami-XXXXXXXXX
eu-central-1 ami-XXXXXXXXX
ap-southeast-1 ami-XXXXXXXXX
ap-northeast-1 ami-XXXXXXXXX
ap-southeast-2 ami-XXXXXXXXX
sa-east-1 ami-XXXXXXXXX

How to test?

We need to test several things on the Fedora Atomic release before Fedora 22 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

To test Fedora Atomic, we're going to use a Koji build located here: [1]. You can also use one of the AMIs if you would prefer to do your testing on Amazon Web Services.

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

Test Results

Atomic Tests

User Hardware Image Boots Upgrade Works Rollback Works References
larsks openstack
Pass pass
Pass pass
Pass pass
ssamanta testvm1
Pass pass
Anil Virt-Manager
Pass pass
Pass pass
Pass pass
Pass pass
amrithajij KVM
Warning warn
[long 1]
Pass pass
Pass pass
lnie KVM
Pass pass
Pass pass
roshi KVM
Pass pass
Pass pass
Pass pass
sinnykumari KVM
Warning warn
[long 2]
sten openstack RHOSP5 x64
Pass pass
Pass pass
Pass pass
jzb KVM
Pass pass
[1]
Pass pass
[2]
Pass pass
  1. ↑ Yup. Happy result there.
  2. ↑ atomic upgrade worked a treat. All happy.
jkalliyat KVM
Warning warn
[1]
  1. ↑ Executed the 'runcmd' manually to make it work.
dustymabe Openstack Juno on F21
Pass pass
Pass pass
Pass pass
Prasanth VM on KVM
Warning warn
[1]
Pass pass
  1. ↑ Executed the 'runcmd' manually to make it work.
lalatendu VM on virt-manager
Pass pass
[1]
Pass pass
Pass pass
  1. ↑ runcmd issue

Docker Tests

User Hardware docker-storage-setup Docker Lifecycle References
larsks openstack
Pass pass
[1]
Pass pass
[2]
  1. ↑ Appears to have run automatically (and successfully).
  2. ↑ Started/interacted with/stopped fedora and ubuntu containers.
amrithajij KVM
Warning warn
[1]
Pass pass
  1. ↑ Manually expanded the qcow2 image fron host and then ran journalctl -o cat --unit docker-storage-setup.service.
roshi KVM
Pass pass
Pass pass
sinnykumari KVM
Warning warn
[1]
  1. ↑ In test case https://fedoraproject.org/wiki/User:Roshi/QA/AtomicTests/Atomic_Docker_Storage_Setup changes get reflected after rebooting VM
sten openstack RHOSP5 x64
Pass pass
Pass pass [1]

That confused me, but just using "sudo docker foo" works. </ref>

  1. ↑ RHBZ #1164058
jzb KVM
Pass pass
[1]
Pass pass
[2]
  1. ↑ Works a treat.
  2. ↑ All good here.
dustymabe Openstack Juno on F21
Pass pass
Pass pass
lalatendu VM on virt-manager
Pass pass

</ref>

Pass pass
nkhare vm
Pass pass

Bugs filled during Test Day (7th May 2015)

1166073 1166082

Other Common Bugs

1164058

Long comments

  1. ↑ All works well except the command - [ sh, -c, 'echo -e "ROOT_SIZE=4G DATA_SIZE=10G" > /etc/sysconfig/docker-storage-setup'] . Thus created the file manually and added ROOT_SIZE=4G DATA_SIZE=10G.
  2. ↑ I tried test mentioned on roshi page . Everything worked well but "runcmd: - [ sh, -c, 'echo -e "ROOT_SIZE=4G DATA_SIZE=10G" > /etc/sysconfig/docker-storage-setup']" didn't run for me. So, added "ROOT_SIZE=4G DATA_SIZE=10G" content in etc/sysconfig/docker-storage-setup file manually.
Retrieved from "https://fedoraproject.org/w/index.php?title=Test_Day:2015-05-07_Atomic&oldid=411672"