From Fedora Project Wiki

m (improve layout slightly to make it simpler to read (hopefully))
m (standardise a bit of descriptive text and info)
Line 11: Line 11:


{{admon/tip|Choose the right $HOME|Please note the location of $HOME (~/) will vary depending upon the manner in which you elevated to root privileges. Ensure you place the configuration file in the correct location for your preferred method.}}
{{admon/tip|Choose the right $HOME|Please note the location of $HOME (~/) will vary depending upon the manner in which you elevated to root privileges. Ensure you place the configuration file in the correct location for your preferred method.}}
{{admon/tip|If you are doing this test case using a virtual machine|You should transfer any images produced by BoxGrinder Build for testing onto your ''real'' host rather than attempting to execute a VM inside of another VM. }}


|actions=
|actions=
# Navigate to directory <code>boxgrinder-appliances/testing-appliances/jeos-appls/</code>
# Navigate to directory <code>boxgrinder-appliances/testing-appliances/jeos-appls/</code>
# Execute <code>boxgrinder-build fedora-rawhide-jeos.appl -p vmware</code>
# Execute <code>boxgrinder-build fedora-rawhide-jeos.appl -p vmware</code>
# Run the produced vmdk/vmx files in your favourite virtualization application. Replace '''$basearch''' in the paths with your architecture, for example:'''<code>uname -i</code>''': <code>build/appliances/$basearch/fedora/rawhide/Rawhide-jeos/vmware-plugin/fedora-rawhide.vmdk</code> and <code>build/appliances/$basearch/fedora/rawhide/Rawhide-jeos/vmware-plugin/fedora-rawhide.vmx</code>   
# Run the produced vmdk/vmx files in your favourite virtualization application. Replace '''$basearch''' in the paths with your architecture, for instance via:'''<code>uname -i</code>''': <code>build/appliances/$basearch/fedora/rawhide/Rawhide-jeos/vmware-plugin/fedora-rawhide.vmdk</code> and <code>build/appliances/$basearch/fedora/rawhide/Rawhide-jeos/vmware-plugin/fedora-rawhide.vmx</code>   
# Log in with user: <code>root</code> password: <code>boxgrinder</code>   
# Log in with user: <code>root</code> password: <code>boxgrinder</code>   
# Run the following Test Case in the VM: [[QA:Network_basic_test_case]]
# Run the following Test Case in the VM: [[QA:Network_basic_test_case]]

Revision as of 12:33, 22 April 2011

Description

We are converting the JEOS build to the vmware platform format.

Setup

Clone the BoxGrinder test appliances into a convenient location using command git clone https://github.com/msavy/boxgrinder-appliances.git

Put the following BoxGrinder config into a file named: ~/.boxgrinder/config

plugins:
  vmware:
    type: enterprise
    thin_disk: true
Idea.png
Choose the right $HOME
Please note the location of $HOME (~/) will vary depending upon the manner in which you elevated to root privileges. Ensure you place the configuration file in the correct location for your preferred method.
Idea.png
If you are doing this test case using a virtual machine
You should transfer any images produced by BoxGrinder Build for testing onto your real host rather than attempting to execute a VM inside of another VM.

How to test

  1. Navigate to directory boxgrinder-appliances/testing-appliances/jeos-appls/
  2. Execute boxgrinder-build fedora-rawhide-jeos.appl -p vmware
  3. Run the produced vmdk/vmx files in your favourite virtualization application. Replace $basearch in the paths with your architecture, for instance via:uname -i: build/appliances/$basearch/fedora/rawhide/Rawhide-jeos/vmware-plugin/fedora-rawhide.vmdk and build/appliances/$basearch/fedora/rawhide/Rawhide-jeos/vmware-plugin/fedora-rawhide.vmx
  4. Log in with user: root password: boxgrinder
  5. Run the following Test Case in the VM: QA:Network_basic_test_case

Expected Results

The following must be true to consider this a successful test run.

  1. Step #2 completes without error (indicated on console)
  2. Program completes with exit code 0
  3. Successfully boot and log into the vmware appliance without error
  4. QA:Network_basic_test_case is performed successfully on the new appliance