QA:Testcase launch an instance on OpenStack

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(remove from cloud SIG category)
m
 
(7 intermediate revisions by 4 users not shown)
Line 8: Line 8:
  
 
Launch an instance of one of the images downloaded and registered in the previous test case.
 
Launch an instance of one of the images downloaded and registered in the previous test case.
  $> . ./novarc
+
  $> . ./keystonerc
  $> euca-run-instances ami-tty --kernel aki-tty --ramdisk ari-tty -k nova_key
+
  $> <nowiki>nova boot --image $(nova image-list | grep ami-tty | awk '{print $2}') --flavor 1 --key_name nova_key testvm</nowiki>
  
 
|results=
 
|results=
Line 16: Line 16:
  
  
  $> nova list
+
  $> nova list
 
  +--------------------------------------+----------+--------+------------------+
 
  +--------------------------------------+----------+--------+------------------+
 
  <nowiki>|                  ID                  |  Name  | Status |    Networks    |</nowiki>
 
  <nowiki>|                  ID                  |  Name  | Status |    Networks    |</nowiki>
Line 24: Line 24:
  
  
It may take a while to transition from the BUILD to the ACTIVE state, as reported by 'nova list'
+
It may take a while to transition from the BUILD to the ACTIVE state, as reported by 'nova list'.
 +
 
 +
If the instance goes into the ERROR state, then check the nova-compute logs for errors:
 +
 
 +
$> grep ERROR /var/log/nova/compute.log
 +
 
 +
What might help is to restart the nova scheduler with 'sudo systemctl restart openstack-nova-scheduler.service' and try again in case the scheduler reports an error in the logs.
 +
 
 +
Confirm the VM running with virsh:
  
 
  $> sudo virsh list
 
  $> sudo virsh list
Line 32: Line 40:
  
 
Get console output and ensure instance is fully started
 
Get console output and ensure instance is fully started
  $> euca-get-console-output i-00000001
+
  $> nova console-log --length 100 <instanceid>
  
 
Try SSH-ing into the instance:
 
Try SSH-ing into the instance:

Latest revision as of 18:32, 25 October 2012

Contents

Description

Launch an instance on OpenStack.

Setup

Optionally include information on preparing the test environment

  1. Follow QA:Testcase_register_images_with_OpenStack

How to test

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

$> . ./keystonerc
$> nova boot --image $(nova image-list | grep ami-tty | awk '{print $2}') --flavor 1 --key_name nova_key testvm

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'.

If the instance goes into the ERROR state, then check the nova-compute logs for errors:

$> grep ERROR /var/log/nova/compute.log

What might help is to restart the nova scheduler with 'sudo systemctl restart openstack-nova-scheduler.service' and try again in case the scheduler reports an error in the logs.

Confirm the VM running with virsh:

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

Get console output and ensure instance is fully started

$> nova console-log --length 100 <instanceid>

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