blob: a1cf025f2bbc81739d43ef7c9b351b6f2be4e0b4 [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 Andrewsb0191512011-09-14 19:37:10 -070055
Jesse Andrews593828d2011-09-14 22:44:50 -070056# Launching a server
57# ==================
Jesse Andrewsb19424f2011-09-14 22:03:04 -070058
Jesse Andrews593828d2011-09-14 22:44:50 -070059# List servers for tenant:
Jesse Andrewsb0191512011-09-14 19:37:10 -070060nova list
Jesse Andrews593828d2011-09-14 22:44:50 -070061
62# List of flavors:
63nova flavor-list
64
65# Images
66# ------
67
68# Nova has a **deprecated** way of listing images.
69nova image-list
70
71# But we recommend using glance directly
72glance index
73
74# show details of the active servers::
75#
76# nova show 1234
77#
78nova list | grep ACTIVE | cut -d \| -f2 | xargs -n1 nova show