QA:Testcase launch an instance on OpenStack

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
Line 13: Line 13:
 
  --libvirt_type=qemu
 
  --libvirt_type=qemu
 
After adding this item, you will need to restart the OpenStack services.
 
After adding this item, you will need to restart the OpenStack services.
  $> for svc in api objectstore compute network volume scheduler; do sudo service openstack-nova-$svc stop; done
+
  $> sudo service openstack-nova-compute restart
  $> for svc in api objectstore compute network volume scheduler; do sudo service openstack-nova-$svc start; done
+
  $> sudo service openstack-nova-compute status
$> for svc in api objectstore compute network volume scheduler; do sudo service openstack-nova-$svc status; done
+
  
 
|actions=
 
|actions=

Revision as of 21:11, 17 October 2011

Contents

Description

Launch an instance on OpenStack.

Setup

Optionally include information on preparing the test environment

  1. Follow QA:Testcase_download_and_register_tty_images_with_OpenStack
  2. Make sure the nbd kernel module is loaded so that injecting SSH key files into the filesystem on the qcow2 image works:
$> sudo modprobe nbd

OpenStack in a Virtual Machine

If you are not testing OpenStack in a virtual machine, you may skip this section of the setup.

If you are testing OpenStack in a virtual machine, everything will have worked up to this point. However, launching an instance will fail unless you set an additional configuration option. Edit /etc/nova/nova.conf and add the following text to a new line in the configuration file:

--libvirt_type=qemu

After adding this item, you will need to restart the OpenStack services.

$> sudo service openstack-nova-compute restart
$> sudo service openstack-nova-compute status 

How to test

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

$> cd ~/novacreds
$> euca-run-instances ami-tty --kernel aki-tty --ramdisk ari-tty -k nova_key

Expected Results

Verify that the instance has started.

$> euca-describe-instances 
RESERVATION	r-d8wpvydq	rbryant	default
INSTANCE	i-00000003	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
$> sudo virsh list
 Id Name                 State
----------------------------------
 1 instance-00000003    running

Try SSHing into the instance:

$> cd ~/novacreds
$> ssh -i nova_key.priv root@10.0.0.2

Get conosle output:

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

Finally, terminate the instance:

$> euca-terminate-instances i-00000003