2011-09-15 02:37:10 +00:00
|
|
|
#!/usr/bin/env bash
|
|
|
|
|
|
|
|
|
|
# **exercise.sh** - using the cloud can be fun
|
|
|
|
|
|
|
|
|
|
# we will use the ``nova`` cli tool provided by the ``python-novaclient``
|
|
|
|
|
# package
|
2011-09-15 05:03:04 +00:00
|
|
|
#
|
2011-09-15 02:37:10 +00:00
|
|
|
|
2011-09-15 05:03:04 +00:00
|
|
|
|
|
|
|
|
# This script exits on an error so that errors don't compound and you see
|
|
|
|
|
# only the first error that occured.
|
|
|
|
|
set -o errexit
|
|
|
|
|
|
|
|
|
|
# Print the commands being run so that we can see the command that triggers
|
|
|
|
|
# an error. It is also useful for following allowing as the install occurs.
|
|
|
|
|
set -o xtrace
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# Settings
|
|
|
|
|
# ========
|
2011-09-15 02:37:10 +00:00
|
|
|
|
|
|
|
|
HOST=${HOST:-localhost}
|
2011-09-15 05:03:04 +00:00
|
|
|
|
|
|
|
|
# Nova original used project_id as the *account* that owned resources (servers,
|
|
|
|
|
# ip address, ...) With the addition of Keystone we have standardized on the
|
|
|
|
|
# term **tenant** as the entity that owns the resources. **novaclient** still
|
|
|
|
|
# uses the old deprecated terms project_id.
|
|
|
|
|
export NOVA_PROJECT_ID=${TENANT:-demo}
|
|
|
|
|
|
|
|
|
|
# In addition to the owning entity (tenant), nova stores the entity performing
|
|
|
|
|
# the action as the **user**.
|
|
|
|
|
export NOVA_USERNAME=${USERNAME:-demo}
|
|
|
|
|
|
|
|
|
|
# With Keystone you pass the keystone password instead of an api key.
|
|
|
|
|
export NOVA_API_KEY=${PASSWORD:-secrete}
|
|
|
|
|
|
|
|
|
|
# With the addition of Keystone, to use an openstack cloud you should
|
|
|
|
|
# authenticate against keystone, which returns a **Token** and **Service
|
|
|
|
|
# Catalog**. The catalog contains the endpoint for all services the user/tenant
|
|
|
|
|
# has access to - including nova, glance, keystone, swift, ... We currently
|
|
|
|
|
# recommend using the 2.0 *auth api*.
|
|
|
|
|
#
|
|
|
|
|
# *NOTE*: Using the 2.0 *auth api* does mean that compute api is 2.0. We will
|
|
|
|
|
# use the 1.1 *compute api*
|
|
|
|
|
export NOVA_URL=${NOVA_URL:-http://$HOST:5000/v2.0/}
|
|
|
|
|
|
|
|
|
|
# Currently novaclient needs you to specify the *compute api* version. This
|
|
|
|
|
# needs to match the config of your catalog returned by Keystone.
|
2011-09-15 02:37:10 +00:00
|
|
|
export NOVA_VERSION=1.1
|
|
|
|
|
|
|
|
|
|
|
2011-09-15 05:44:50 +00:00
|
|
|
# Launching a server
|
|
|
|
|
# ==================
|
2011-09-15 05:03:04 +00:00
|
|
|
|
2011-09-15 05:44:50 +00:00
|
|
|
# List servers for tenant:
|
2011-09-15 02:37:10 +00:00
|
|
|
nova list
|
2011-09-15 05:44:50 +00:00
|
|
|
|
|
|
|
|
# List of flavors:
|
|
|
|
|
nova flavor-list
|
|
|
|
|
|
|
|
|
|
# Images
|
|
|
|
|
# ------
|
|
|
|
|
|
|
|
|
|
# Nova has a **deprecated** way of listing images.
|
|
|
|
|
nova image-list
|
|
|
|
|
|
|
|
|
|
# But we recommend using glance directly
|
|
|
|
|
glance index
|
|
|
|
|
|
|
|
|
|
# show details of the active servers::
|
|
|
|
|
#
|
|
|
|
|
# nova show 1234
|
|
|
|
|
#
|
|
|
|
|
nova list | grep ACTIVE | cut -d \| -f2 | xargs -n1 nova show
|
