QA:Testcase launch an instance on OpenStack

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(new novarc file uses localhost, so remove warning about addresses changing)
Line 15: Line 15:
 
Verify that the instance has started.
 
Verify that the instance has started.
  
$> euca-describe-instances
 
RESERVATION r-d8wpvydq rbryant default
 
INSTANCE i-00000001 ami-00000003 10.0.0.2 10.0.0.2 pending nova_key (rbryant, f16) 0 m1.small 2011-10-17T20:31:05Z nova aki-00000001 ari-00000002
 
  
It may take a while to transition from the pending to the running state, as reported by euca-describe-instances
+
$>  nova list
 +
+--------------------------------------+----------+--------+------------------+
 +
<nowiki>|                  ID                  |  Name  | Status |    Networks    |</nowiki>
 +
+--------------------------------------+----------+--------+------------------+
 +
<nowiki>| a47a424a-014b-4b81-97e6-b34d31b5589d | Server 1 | ACTIVE | testnet=10.0.0.2 |</nowiki>
 +
+--------------------------------------+----------+--------+------------------+
 +
 
 +
 
 +
It may take a while to transition from the BUILD to the ACTIVE state, as reported by 'nova list'
  
 
  $> sudo virsh list
 
  $> sudo virsh list
Line 30: Line 35:
  
 
Try SSH-ing into the instance:
 
Try SSH-ing into the instance:
$> cd ~/novacreds
+
 
 
  $> ssh -i nova_key.priv -o UserKnownHostsFile=/dev/null root@10.0.0.2
 
  $> ssh -i nova_key.priv -o UserKnownHostsFile=/dev/null root@10.0.0.2
  

Revision as of 15:12, 8 March 2012

Contents

Description

Launch an instance on OpenStack.

Setup

Optionally include information on preparing the test environment

  1. Follow QA:Testcase_download_and_register_guest_images_with_OpenStack

How to test

Launch an instance of one of the images downloaded and registered in the previous test case.

$> . ./novarc
$> euca-run-instances ami-tty --kernel aki-tty --ramdisk ari-tty -k nova_key

Expected Results

Verify that the instance has started.


$>  nova list
+--------------------------------------+----------+--------+------------------+
|                  ID                  |   Name   | Status |     Networks     |
+--------------------------------------+----------+--------+------------------+
| a47a424a-014b-4b81-97e6-b34d31b5589d | Server 1 | ACTIVE | testnet=10.0.0.2 |
+--------------------------------------+----------+--------+------------------+


It may take a while to transition from the BUILD to the ACTIVE state, as reported by 'nova list'

$> sudo virsh list
 Id Name                 State
----------------------------------
 1 instance-00000001    running

Get console output and ensure instance is fully started

$> euca-get-console-output i-00000001

Try SSH-ing into the instance:

$> ssh -i nova_key.priv -o UserKnownHostsFile=/dev/null root@10.0.0.2

Check for new errors in the logs:

$> grep -i error /var/log/nova/*.log

Notes:

  • We use /dev/null for known hosts because the fingerprints associated with these IPs will change when you start over with your testing; updating known hosts gets annoying
  • You've probably got a stale dnsmasq process around if you see:
dnsmasq: failed to create listening socket for 10.0.0.1: Address already in use