blob: fb95fdf856db08059776f708b2b9d55e65f0908b [file] [log] [blame]
Jesse Andrewsb0191512011-09-14 19:37:10 -07001#!/usr/bin/env bash
2
3# **exercise.sh** - using the cloud can be fun
4
5# we will use the ``nova`` cli tool provided by the ``python-novaclient``
6# package
Jesse Andrewsb19424f2011-09-14 22:03:04 -07007#
Jesse Andrewsb0191512011-09-14 19:37:10 -07008
Jesse Andrewsb19424f2011-09-14 22:03:04 -07009
10# This script exits on an error so that errors don't compound and you see
11# only the first error that occured.
12set -o errexit
13
14# Print the commands being run so that we can see the command that triggers
15# an error. It is also useful for following allowing as the install occurs.
16set -o xtrace
17
18
19# Settings
20# ========
Jesse Andrewsb0191512011-09-14 19:37:10 -070021
22HOST=${HOST:-localhost}
Jesse Andrewsb0191512011-09-14 19:37:10 -070023
Jesse Andrewsb19424f2011-09-14 22:03:04 -070024# Nova original used project_id as the *account* that owned resources (servers,
25# ip address, ...) With the addition of Keystone we have standardized on the
26# term **tenant** as the entity that owns the resources. **novaclient** still
Anthony Young0edde7d2011-10-06 07:10:24 -070027# uses the old deprecated terms project_id. Note that this field should now be
28# set to tenant_name, not tenant_id.
29export NOVA_PROJECT_ID=${TENANT:-demo}
Jesse Andrewsb19424f2011-09-14 22:03:04 -070030
31# In addition to the owning entity (tenant), nova stores the entity performing
32# the action as the **user**.
33export NOVA_USERNAME=${USERNAME:-demo}
34
35# With Keystone you pass the keystone password instead of an api key.
36export NOVA_API_KEY=${PASSWORD:-secrete}
37
38# With the addition of Keystone, to use an openstack cloud you should
39# authenticate against keystone, which returns a **Token** and **Service
40# Catalog**. The catalog contains the endpoint for all services the user/tenant
41# has access to - including nova, glance, keystone, swift, ... We currently
42# recommend using the 2.0 *auth api*.
43#
44# *NOTE*: Using the 2.0 *auth api* does mean that compute api is 2.0. We will
45# use the 1.1 *compute api*
46export NOVA_URL=${NOVA_URL:-http://$HOST:5000/v2.0/}
47
48# Currently novaclient needs you to specify the *compute api* version. This
49# needs to match the config of your catalog returned by Keystone.
Jesse Andrewsb0191512011-09-14 19:37:10 -070050export NOVA_VERSION=1.1
51
Anthony Young43876902011-09-27 00:29:28 -070052# FIXME - why does this need to be specified?
53export NOVA_REGION_NAME=RegionOne
54
Jesse Andrewsb9c77d62011-10-15 18:37:25 -070055# set log level to DEBUG (helps debug issues)
56export NOVACLIENT_DEBUG=1
Jesse Andrewsb0191512011-09-14 19:37:10 -070057
Anthony Young94c889a2011-10-11 18:07:48 +000058# Get a token for clients that don't support service catalog
59# ==========================================================
Jesse Andrewsb9c77d62011-10-15 18:37:25 -070060
61# manually create a token by querying keystone (sending JSON data). Keystone
62# returns a token and catalog of endpoints. We use python to parse the token
63# and save it.
64
65TOKEN=`curl -s -d "{\"auth\":{\"passwordCredentials\": {\"username\": \"$NOVA_USERNAME\", \"password\": \"$NOVA_API_KEY\"}}}" -H "Content-type: application/json" http://$HOST:5000/v2.0/tokens | python -c "import sys; import json; tok = json.loads(sys.stdin.read()); print tok['access']['token']['id'];"`
Anthony Young94c889a2011-10-11 18:07:48 +000066
Jesse Andrews593828d2011-09-14 22:44:50 -070067# Launching a server
68# ==================
Jesse Andrewsb19424f2011-09-14 22:03:04 -070069
Jesse Andrews593828d2011-09-14 22:44:50 -070070# List servers for tenant:
Jesse Andrewsb0191512011-09-14 19:37:10 -070071nova list
Jesse Andrews593828d2011-09-14 22:44:50 -070072
Jesse Andrews593828d2011-09-14 22:44:50 -070073# Images
74# ------
75
76# Nova has a **deprecated** way of listing images.
77nova image-list
78
79# But we recommend using glance directly
Jesse Andrews4e8847c2011-10-15 19:29:55 -070080glance -A $TOKEN index
Jesse Andrews593828d2011-09-14 22:44:50 -070081
Jesse Andrewsd888e1c2011-10-15 20:01:12 -070082# Let's grab the id of the first AMI image to launch
83IMAGE=`glance -A $TOKEN index | egrep ami | cut -d" " -f1`
84
Anthony Young20a2cae2011-10-17 16:02:24 -070085# Security Groups
86# ---------------
87SECGROUP=test_secgroup
88
89# List of secgroups:
90nova secgroup-list
91
92# Create a secgroup
93nova secgroup-create $SECGROUP "test_secgroup description"
Jesse Andrewsd888e1c2011-10-15 20:01:12 -070094
95# Flavors
96# -------
97
98# List of flavors:
99nova flavor-list
100
101# and grab the first flavor in the list to launch
102FLAVOR=`nova flavor-list | head -n 4 | tail -n 1 | cut -d"|" -f2`
103
Anthony Young20a2cae2011-10-17 16:02:24 -0700104NAME="myserver"
Jesse Andrewsd888e1c2011-10-15 20:01:12 -0700105
Anthony Young20a2cae2011-10-17 16:02:24 -0700106nova boot --flavor $FLAVOR --image $IMAGE $NAME --security_groups=$SECGROUP
Jesse Andrewsd888e1c2011-10-15 20:01:12 -0700107
108# let's give it 10 seconds to launch
109sleep 10
110
111# check that the status is active
112nova show $NAME | grep status | grep -q ACTIVE
113
114# get the IP of the server
115IP=`nova show $NAME | grep "private network" | cut -d"|" -f3`
116
117# ping it once (timeout of a second)
Jesse Andrewsda892682011-10-15 20:14:07 -0700118ping -c1 -w1 $IP || true
119
120# sometimes the first ping fails (10 seconds isn't enough time for the VM's
121# network to respond?), so let's wait 5 seconds and really test ping
122sleep 5
123
124ping -c1 -w1 $IP
Anthony Young20a2cae2011-10-17 16:02:24 -0700125# allow icmp traffic
126nova secgroup-add-rule $SECGROUP icmp -1 -1 0.0.0.0/0
127
128# List rules for a secgroup
129nova secgroup-list-rules $SECGROUP
130
131# allocate a floating ip
132nova floating-ip-create
133
134# store floating address
135FIP=`nova floating-ip-list | grep None | head -1 | cut -d '|' -f2 | sed 's/ //g'`
136
137# add floating ip to our server
138nova add-floating-ip $NAME $FIP
139
140# sleep for a smidge
141sleep 1
142
143# ping our fip
144ping -c1 -w1 $FIP
145
146# dis-allow icmp traffic
147nova secgroup-delete-rule $SECGROUP icmp -1 -1 0.0.0.0/0
148
149# sleep for a smidge
150sleep 1
151
152# ping our fip
153if ( ping -c1 -w1 $FIP); then
154 print "Security group failure - ping should not be allowed!"
155 exit 1
156fi
157
158# de-allocate the floating ip
159nova floating-ip-delete $FIP
Jesse Andrewsd888e1c2011-10-15 20:01:12 -0700160
161# shutdown the server
162nova delete $NAME
163
Anthony Young20a2cae2011-10-17 16:02:24 -0700164# Delete a secgroup
165nova secgroup-delete $SECGROUP
166
Jesse Andrewsd888e1c2011-10-15 20:01:12 -0700167# FIXME: validate shutdown within 5 seconds
168# (nova show $NAME returns 1 or status != ACTIVE)?