From Fedora Project Wiki

m (slash was a mistake, removing)
mNo edit summary
Line 9: Line 9:
   elastichosts:
   elastichosts:
     endpoint: api.lon-p.elastichosts.com              # required
     endpoint: api.lon-p.elastichosts.com              # required
     user_uuid: your-user-id                           # required
     username: your-user-id                           # required
     secret_access_key: your-secret-access-key         # required
     password: your-secret-access-key                 # required
     chunk: 128                                        # default: 64 (in MB)
     chunk: 128                                        # default: 64 (in MB)
    start_part: 6                                    # default: 0
     wait: 30                                          # default: 5 (in s)
     wait: 30                                          # default: 5 (in s)
     retry: 2                                          # default: 3
     retry: 2                                          # default: 3
     ssl: true                                        # default: false
     ssl: true                                        # default: false
    drive_uuid: b161fd8b-d56s-4eea-9055-669daaec8aa4
    drive_name: my-bg-drive
</pre>
</pre>


|actions=
|actions=
# Execute <pre>boxgrinder-build boxgrinder-appliances/testing-appliances/jeos-appls/fedora-15-jeos.appl -d elastichosts --trace</pre>   
# Execute <pre>boxgrinder-build boxgrinder-appliances/testing-appliances/jeos-appls/fedora-14-jeos.appl -d elastichosts --trace</pre>   
# Run an instance of the VM through your cloud providers tools, log on via SSH
# Run an instance of the VM through your cloud providers tools, log on via SSH
# 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 06:20, 28 April 2011

Description

Deliver an appliance to an ElasticHost API compatible cloud provider

Setup

Note.png
You need an account with an ElasticHost API compliant cloud provider for these tests!
  1. Launch the JEOS AMI built in the AMI test case: QA:TestCase_boxgrinder_deliver_ami, or any other Fedora 15 AMI.
  2. Put the following BoxGrinder config into a file named: /root/.boxgrinder/config. Insert appropriate values, see: http://boxgrinder.org/tutorials/boxgrinder-build-plugins/#ElasticHosts_Delivery_Plugin, for more information.
plugins:
  elastichosts:
    endpoint: api.lon-p.elastichosts.com              # required
    username: your-user-id                            # required
    password: your-secret-access-key                  # required
    chunk: 128                                        # default: 64 (in MB)
    wait: 30                                          # default: 5 (in s)
    retry: 2                                          # default: 3
    ssl: true                                         # default: false

How to test

  1. Execute 
    boxgrinder-build boxgrinder-appliances/testing-appliances/jeos-appls/fedora-14-jeos.appl -d elastichosts --trace
  2. Run an instance of the VM through your cloud providers tools, log on via SSH
  3. 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 #1 completes without error (indicated on console)
  2. Program completes with exit code 0
  3. The new image has appeared in your cloud provider's management system
  4. Step #2 completes without error
  5. QA:Network_basic_test_case is performed successfully on the new appliance



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