Editing Test Day:2011-04-28 Cloud SIG BoxGrinder Build

{{Infobox_group
| name = Cloud SIG BoxGrinder Build Fedora Test Day
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_15_test_days]]
| caption = BoxGrinder Build
| date = 2011-04-28
| time = all day
| website = [http://boxgrinder.org BoxGrinder]
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])
| fedora_mailing_list = cloud
}}

{{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 '''BoxGrinder Build'''

== New to BoxGrinder? ==

<!-- Change this back to #boxgrinder once the test day is over -->
Don't worry. Please read this [https://github.com/boxgrinder/boxgrinder-build/blob/master/README.md README] or scan our [http://boxgrinder.org/ BoxGrinder homepage]. If something is still unclear, don't hesitate to [irc://irc.freenode.net/#fedora-test-day ask us on IRC].

== Who's available ==

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
* Development - [[User:Goldmann|Marek Goldmann]] (mgoldmann), [[User:Msavy|Marc Savy]] (msavy)

== Prerequisite for Test Day == 

* Free time
* An updated [http://fedoraproject.org/get-prerelease Fedora 15 pre-release]
* Your hardware profile uploaded to [http://www.smolts.org Smolt] according to [http://smolts.org/smolt-wiki/Main_Page#Usage these instructions]
* At least 15GB of free space available on a storage device (or more, depending on your later definition choices)
* Internet connectivity for the test machines (or an active local YUM repository mirror)
* Standard Fedora repositories must be available
* Some virtualization software such as KVM, VirtualBox OSE or VMware Player for local tests
* For the cloud-based tests you should have access to the corresponding cloud provider (e.g. Amazon AWS, CloudFront).

Several GB of space may be required transiently during the build process, in addition to storage of appliances produced and caching.  Any mountable storage with Read/Write access should be suitable (e.g. HDD, USB flash drive, eSATA disk).

{{admon/note|Those with very slow Internet connections, or small bandwidth allowances|Be aware that you may transfer several GB of files in the course of testing.}}

{{admon/tip|You may not be able to perform every Test Case, but please do those that you can|Some of the Test Cases require the availability of cloud services such as Amazon's AWS that you may not have access to. However, please complete those you can, many of the important cases still possible!}}

== How to test? ==

=== Test Day Virtual Image ===

{{admon/warning|User your system where possible|Although we have [[Test Day:2011-04-28 Cloud SIG BoxGrinder Build Meta Appliance|Test Day Meta-Appliance]] but it seems that it has some [[Test Day:2011-04-28 Cloud SIG BoxGrinder Build Known Issues|known issues]] preventing you from executing the test cases. You can always [[Test Day:2011-04-28 Cloud SIG BoxGrinder Build Meta Appliance|download stable meta appliance]] based on Fedora 14.}}

Optionally, a pre-prepared BoxGrinder Virtual Images are available in multiple formats for your architecture.
 
* Download the [[Test Day:2011-04-28 Cloud SIG BoxGrinder Build Meta Appliance|Test Day Meta-Appliance]] in your preferred format, and run in your favorite virtualization software.

=== Update your machine to Fedora 15 ===

If you are already running or want to try the pre-release of Fedora 15, [http://fedoraproject.org/get-prerelease install Fedora 15 Beta] and then update to the latest packages.

== Prepare your environment ==

If you're testing with the BoxGrinder [[Test Day:2011-04-28 Cloud SIG BoxGrinder Build Meta Appliance|Test Day Meta-Appliance]], then everything is already prepared for you.  Otherwise, it is a matter of a few simple steps to prepare your environment.

* Install '''rubygem-boxgrinder-build''', '''git''' and '''createrepo''' via your favoured package manager.  For instance, in YUM:

<pre>
yum install --enablerepo=updates-testing git rubygem-boxgrinder-build createrepo
git clone https://github.com/msavy/boxgrinder-appliances.git
cd boxgrinder-appliances
</pre>

== Test Cases ==

{{admon/note|Known issues|
We have a list of [[Test Day:2011-04-28 Cloud SIG BoxGrinder Build Known Issues|known issues]] that have shown up while releasing version 0.9.1. }}
{{admon/tip|Ignore any GNOME mount errors|GNOME attempts to mount the [http://boxgrinder.org/faq/#How_can_I_prevent_mounting_partitions_in_my_GNOME_Desktop_while_building_appliances loop devices BoxGrinder creates], and fails. This is not a problem, just a minor annoyance.}}

=== Local Test Cases ===
These test cases require no access to cloud providers to perform.

[[QA:TestCase_boxgrinder_jeos_build]]

[[QA:TestCase_boxgrinder_modular_test_appliances_build]]

[[QA:TestCase_boxgrinder_platform_vmware]]

[[QA:TestCase_boxgrinder_platform_virtualbox]]

[[QA:TestCase_boxgrinder_deliver_local]]

[[QA:TestCase_boxgrinder_deliver_sftp]]

[[QA:TestCase_boxgrinder_xarch_pipeline]]

=== Cloud Test Cases ===
An account with a cloud provider is needed to enact the following test-cases

[[QA:TestCase_boxgrinder_platform_ec2]] No AWS account needed

[[QA:TestCase_boxgrinder_deliver_s3]] Amazon AWS

[[QA:TestCase_boxgrinder_deliver_ami]] Amazon AWS

[[QA:TestCase_boxgrinder_deliver_ebs]] Amazon AWS

[[QA:TestCase_boxgrinder_deliver_cloudfront]] Amazon AWS CloudFront

[[QA:TestCase_boxgrinder_deliver_elastichosts]] ElasticHosts API [http://boxgrinder.org/tutorials/boxgrinder-build-plugins/#ElasticHosts_Delivery_Plugin compatible hosts]

== Test Results ==

If you have problems with any of the tests, report a bug to [https://issues.jboss.org/secure/CreateIssue.jspa?pid=12310920&issuetype=1 JIRA] or [https://bugzilla.redhat.com/enter_bug.cgi?component=rubygem-boxgrinder-build&product=Fedora Bugzilla], although '''we prefer JIRA'''. After submitting a ticket, attach the relevant data from log file <code>log/boxgrinder.log</code>.

{{admon/note|Use 'testday' label|Please mark the issues with <code>testday</code> label in JIRA. This makes it easier to categorize submitted bug reports.}}

=== Need help? ===

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. Once you have completed the tests, add your results to the Results 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, and the second should be a link to the Smolt profile of the system you tested. For each test case, use the [[Template:result|result template]] to enter your result, as shown in the example result line.

{|
! User
! Smolt Profile
! [[QA:TestCase_boxgrinder_jeos_build|JEOS]]
! [[QA:TestCase_boxgrinder_modular_test_appliances_build|Modular]]
! [[QA:TestCase_boxgrinder_platform_vmware|vmware]]
! [[QA:TestCase_boxgrinder_platform_virtualbox|virtualbox]]
! [[QA:TestCase_boxgrinder_deliver_local|local]]
! [[QA:TestCase_boxgrinder_deliver_sftp|sftp]]
! [[QA:TestCase_boxgrinder_xarch_pipeline|xarch]]
! [[QA:TestCase_boxgrinder_platform_ec2|ec2]]
! [[QA:TestCase_boxgrinder_deliver_s3|s3]]
! [[QA:TestCase_boxgrinder_deliver_ami|ami]]
! [[QA:TestCase_boxgrinder_deliver_ebs|ebs]]
! [[QA:TestCase_boxgrinder_deliver_cloudfront|cloudfront]]
! [[QA:TestCase_boxgrinder_deliver_elastichosts|elastichosts]]
! References
|-
| [[User:SampleUser|Sample User]]
| [http://www.smolts.org/client/show/pub_84465125-1350-4f83-87b9-5f16f7430eb8 HW]
| {{result|pass}} 
| {{result|pass}}
| {{result|warn}} <ref>Test pass, but also encountered Bug #[https://issues.jboss.org/browse/BGBUILD-12345 12345]</ref>
| {{result|fail}} <ref>Bug #[https://issues.jboss.org/browse/BGBUILD-56789 56789]</ref>
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|none}}
| {{result|none}}
| {{result|fail}} <ref>Example, this time a BugZilla ticket {{bz|1234567}}</ref>
| <references/>
|-
| [[User:gospo|gospo]]
| Meta-appliance <ref>Fully updated f15 and boxgrinder-build update to 0.9.1</ref>
| {{result|pass}}
| 
| 
| 
| 
| 
| {{result|pass}}
| {{result|pass}} <ref>With boxgrinder-build 0.9.0 and 0.9.1</ref>
| {{result|pass}} <ref>S3 coherency leaves a bit to be desired, but it you wait the image shows up</ref>
| {{result|pass}}
| <ref>Was running meta-appliance locally so I could not upload to EBS</ref>
| {{result|fail}}
| 
| <references/>
|-
| [[User:verdurin|verdurin]]
| [http://smolts.org/client/show/?uuid=pub_564bee59-c975-4e8b-93ea-01d8e2c7c8f4 HW]<ref>Fedora 14</ref>
| {{result|pass}}
| {{result|fail}}<ref>Found bug https://issues.jboss.org/browse/BGBUILD-210</ref><ref>fixed by commenting line 13 of boxgrinder-appliances/testing-appliances/modular-appls/_test_base.appl</ref>
| {{result|none}}
| {{result|none}}
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}<ref>Generated KVM-type image as I don't have VirtualBox</ref>
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| <references/>
|-
| [[User:Tflink | Tim Flink]]
| [http://www.smolts.org/client/show/pub_75513d90-c6e6-4765-9c59-ec9c09387bd4 HW]
| {{result|pass}}
| {{result|pass}}
| {{result|none}}
| {{result|none}}
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| <references/>
|-
| [[User:ktofte | ktofte]]
| [http://www.smolts.org/client/show/?uuid=pub_d36eca34-03ed-4c7d-92ab-cefe0f906c1d HW]
| {{result|pass}} 
| {{result|none}}
| {{result|none}}
| {{result|warn}} <ref>Yum couldn't find the repositories, but the networking worked fine otherwise. I've had similar trouble with Yum before anyway.</ref>
| {{result|pass}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| <references/>
|-
| [[User:bertux | Bertrand Juglas]]
| [http://www.smolts.org/client/show/pub_7a0b63e7-f7af-44fd-ada4-13e1f6e209d8 HW]
| {{result|pass}}
| {{result|fail}}<ref>[https://issues.jboss.org/browse/BGBUILD-210?focusedCommentId=12598898&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12598898 Bug comment]</ref><ref>fixed by commenting line 13 of boxgrinder-appliances/testing-appliances/modular-appls/_test_base.appl</ref>
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| <references/>
|}

[[Category:Fedora 15 Test Days]]
@@ Line 61: / Line 61: @@
 If you're testing with the BoxGrinder [[Test Day:2011-04-28 Cloud SIG BoxGrinder Build Meta Appliance|Test Day Meta-Appliance]], then everything is already prepared for you.  Otherwise, it is a matter of a few simple steps to prepare your environment.
-=== Install BoxGrinder Build ===
+* Install '''rubygem-boxgrinder-build''', '''git''' and '''createrepo''' via your favoured package manager.  For instance, in YUM:
-==== For Fedora 15 ====
-<pre>
-wget http://kojipkgs.fedoraproject.org/packages/rubygem-boxgrinder-core/0.3.1/1.fc15/noarch/rubygem-boxgrinder-core-0.3.1-1.fc15.noarch.rpm
-wget http://kojipkgs.fedoraproject.org/packages/rubygem-boxgrinder-build/0.9.1/1.fc15/noarch/rubygem-boxgrinder-build-0.9.1-1.fc15.noarch.rpm
-yum localinstall ./rubygem-boxgrinder-*
-</pre>
-==== For Fedora 13/14 ====
-<pre>
-yum install --enablerepo=updates-testing rubygem-boxgrinder-core rubygem-boxgrinder-build
-</pre>
-=== Install other tools ===
-<pre>
-yum install git createrepo
-</pre>
-=== Grab test appliances ===
 <pre>
+yum install --enablerepo=updates-testing git rubygem-boxgrinder-build createrepo
 git clone https://github.com/msavy/boxgrinder-appliances.git
 cd boxgrinder-appliances