From Fedora Project Wiki

(change <code> to <pre> for a sample that the user should execute)
No edit summary
Line 2: Line 2:
|description=Deliver an appliance to a locally mounted drive.
|description=Deliver an appliance to a locally mounted drive.
|setup=
|setup=
* Clone the BoxGrinder test appliances into a convenient location using command <code>git clone https://github.com/msavy/boxgrinder-appliances.git</code>
# [[Test_Day:2011-04-28_Cloud_SIG_BoxGrinder_Build#Prepare your environment|Prepare your environment]]
* Create a directory to deliver file, for instance <code>mkdir ~/delivered_appliances</code>
# Put the following BoxGrinder config into a file named: <code>/root/.boxgrinder/config</code>.
* Put the following BoxGrinder config into a file named: <code>~/.boxgrinder/config</code>. Please replace '''YOUR_USERNAME''' above with the appropriate username in the snippet.
<pre>
<pre>
plugins:
plugins:
   local:
   local:
     path: /home/YOUR_USERNAME/delivered_appliances
     path: /tmp/boxgrinder-appliances
     package: true
     package: true
     overwrite: false
     overwrite: false
</pre>
</pre>


{{admon/note|You cannot use environment variables such as $HOME or ~/ for the local delivery plugin's ''path'' parameter|At present a literal path must be used for ''local path'' param, as BoxGrinder Build does not handle environment variables correctly for this specific field. This will be fixed in an upcoming version.}}
{{admon/warning|BoxGrinder Build config file location|The default location for this file is <code>/root/.boxgrinder/config</code>. You can put this file in different location by specifying <code>BG_CONFIG_FILE</code> environment variable.}}


{{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.}}
|actions=
|actions=
# Navigate to directory <code>boxgrinder-appliances/testing-appliances/jeos-appls/</code>
# Execute: <pre>boxgrinder-build testing-appliances/jeos-appls/fedora-15-jeos.appl -d local</pre>   
# Execute <pre>boxgrinder-build fedora-15-jeos.appl -d local</pre>   
|results=
|results=
The following must be true to consider this a successful test run.
The following must be true to consider this a successful test run.
# Step #2 completes without error (indicated on console)
# Step #1 completes without error (indicated on console)
# Program completes with exit code 0
# Program completes with exit code 0
# Determine whether a tar.gz file has appeared in the expected local directory
# Determine whether a tar.gz file has appeared in the expected local directory
}}
}}

Revision as of 09:05, 23 April 2011

Description

Deliver an appliance to a locally mounted drive.

Setup

  1. Prepare your environment
  2. Put the following BoxGrinder config into a file named: /root/.boxgrinder/config.
plugins:
  local:
    path: /tmp/boxgrinder-appliances
    package: true
    overwrite: false
Warning.png
BoxGrinder Build config file location
The default location for this file is /root/.boxgrinder/config. You can put this file in different location by specifying BG_CONFIG_FILE environment variable.

How to test

  1. Execute: 
    boxgrinder-build testing-appliances/jeos-appls/fedora-15-jeos.appl -d local

Expected Results

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

  1. Step #1 completes without error (indicated on console)
  2. Program completes with exit code 0
  3. Determine whether a tar.gz file has appeared in the expected local directory



Retrieved from "https://fedoraproject.org/w/index.php?title=QA:TestCase_boxgrinder_deliver_local&oldid=233314"