...

Before the tools are installed, you will want an environment that can use Python, as all of the OpenStack command-line tools are written in that language. This can be your local desktop or it could be a virtual machine in the Rapid Access Cloud. The instructions outlined below will assume a Ubuntu 14.04 instance in the Rapid Access Cloud, a virtual machine running on your desktop or a native Ubuntu desktop.

From an Ubuntu 14.04 command-line:

1. Install Python package management (pip) and required packages: 

   Code Block
   $ sudo apt-get install pythonpython3-pip pythonpython3-dev

   
   

2. Install Openstack command-line tools using pip: 

   Code Block
   $ sudo pippip3 install python-openstackclient

   
   

Installing command-line tools (

...

macOS)

1. Ensure you have the Developer Tools (Xcode) with the Command Line Tools for OS X.

2. Open the Terminal application.

3. Install pip (a package management system for software packages written in python): macOS:

   Code Block
   $ sudo xcode-select --install $ sudo pip3 easy_install --upgrade pip

   
   

4. Open the Terminal application.

5. Install the openstack command line tool: 

   Code Block
   $ pippip3 install --user python-openstackclient

   Note: We recommend installing this as a user to avoid running into issues with system updates.

6. Add the following to .bashrczshrc: 

   Code Block
   export PATH=/Users/<username>/Library/Python/23.78/bin:$PATH export PYTHONPATH=/Users/<username>/Library/Python/23.78/lib/python/site-packages

   
   

Openrc file

The ‘rc’ "rc" in rc file stands for any or all of the following:

...

1. Log-in to the Rapid Access Cloud dashboard at https://cloud.cybera.ca.

2. In the left-hand panel under “Compute”, click “Access & Security”.

3. Click the “API Access” tab at the top then click the “Download Openstack RC file v3” on the right.

4. The file downloaded will be named after your account name, e.g. <email>@<domain>-openrc.sh. This can be renamed to openrc if you like, or you can copy it and modify it so you can have one for the Calgary region and one for the Edmonton region. The rc file downloaded will be keyed for the region you are signed into in the dashboard.

...

#!/bin/bash
export OS_AUTH_URL=https://yegyyc.cloud.cybera.ca:5000/v3
export OS_PROJECT_NAME="<account_username>"
export OS_USERNAME="<account_username>"
export OS_USER_DOMAIN_NAME="Default"
export OS_REGION_NAME="Calgary"
export OS_INTERFACE=public
export OS_IDENTITY_API_VERSION=3
echo "Please enter your OpenStack Password for project $OS_PROJECT_NAME as user $OS_USERNAME: "
read -sr OS_PASSWORD_INPUT
export OS_PASSWORD=$OS_PASSWORD_INPUT

...

• Delete a volume. This is a destructive action and all data associated with the volume is lost: 

  Code Block
  $ openstack volume delete <volume_name>

...

Images

While it is true that instances in the Rapid Access Cloud are intended to be ephemeral, it is still possible to capture the state of an instance at any moment and save it as an image that can in turn be provisioned in a similar fashion to deploying a new instance using openstack server create as outlined above. This permits the ability to back-up an instance for safe keeping or create a base image with required applications already installed if you want to rapidly deploy many instances with a similar role. Volume snapshots are point-in-time stateful ‘freeze’ of a volume, meaning the volume itself cannot be attached after a snapshot is taken. (see volumes above for creating new volumes from snapshots)

Before snapshotting your instance, make sure it is in a shut-off state.

• Create an image Create an image of an existing instance: 

  Code Block
  $ openstack server image create --name <image_name> <instance_name>

   

• Download an image to a local computer: 

  Code Block
  $ openstack image save --file <file_name> <image_name>

  Snapshot an existing volume, unattached to an instance: 

  Code Block
  $ openstack snapshot create --name <snapshot_name> <volume_name>

  Snapshot an existing volume, attached to an instance: 

  Code Block
  $ openstack snapshot create --name <snapshot_name> --force <volume_name>

  Note
  Note about volume snapshots: Notice the use of the --force switch when taking a snapshot of an attached volume; the snapshot will work and not fail, however if there are open files being actively written to the validity of the data being cloned cannot be guaranteed.