5.3. OpenStack Grizzly

Page Contents

5.3.1. Login

Currently we have OpenStack Grizzly installed on Sierra. To use it you need to first log into sierra and prepare your openstack credentials (Make sure to replace the ‘username’ with your actual FG username):

$ ssh username@sierra.futuregrid.org

5.3.2. Creating the novarc file

Next you need to create your novarc file with our cloudmesh tools:

$ module load cloudmesh
$ cm-manage config sierra-openstack-grizzly

The cm-manage command will create a nova rc file at the default location:

~/.futuregrid/novarc

5.3.3. Activate OpenStack tools

To activate your your OpenStack environment and load the openstack tools you will need to source the novarc file and load the novaclient module:

$ source ~/.futuregrid/novarc
$ module load novaclient

To check if your nova client works we use a simple command to list the flavors:

5.3.4. List flavors

To list the flavors, please execute the following command

$ nova flavor-list

Everything is fine, if you se an output similar to:

+----+-----------+-----------+------+-----------+------+-------+-------------+-----------+-------------+
| ID | Name      | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public | extra_specs |
+----+-----------+-----------+------+-----------+------+-------+-------------+-----------+-------------+
| 1  | m1.tiny   | 512       | 0    | 0         |      | 1     | 1.0         | True      | {}          |
| 2  | m1.small  | 2048      | 20   | 0         |      | 1     | 1.0         | True      | {}          |
| 3  | m1.medium | 4096      | 40   | 0         |      | 2     | 1.0         | True      | {}          |
| 4  | m1.large  | 8192      | 80   | 0         |      | 4     | 1.0         | True      | {}          |
| 5  | m1.xlarge | 16384     | 160  | 0         |      | 8     | 1.0         | True      | {}          |
+----+-----------+-----------+------+-----------+------+-------+-------------+-----------+-------------+

If not your environment may not be set up correctly. Make sure that you follow the steps in this section and the account management section carefully.

5.3.5. List images

After you got the flavor list, you can list the current set of uploaded images with the nova image-list command:

$ nova image-list

You will see an output similar to:

+--------------------------------------+-------------------------+--------+--------+
| ID                                   | Name                    | Status | Server |
+--------------------------------------+-------------------------+--------+--------+
| 18c437e5-d65e-418f-a739-9604cef8ab33 | futuregrid/fedora-18    | ACTIVE |        |
| 1a5fd55e-79b9-4dd5-ae9b-ea10ef3156e9 | futuregrid/ubuntu-12.04 | ACTIVE |        |
+--------------------------------------+-------------------------+--------+--------+

Hint

$USER is your username on sierra machine.

5.3.6. Standard Images

We have provided a number of images that you may want to try out. Image Ids and names of them are listed in the following table. The futuregrid/sl-6 image is Scientific Linux.

Image ID Image Name
53fab752-757e-4b2a-bce6-9f74ba76be26 d5b19d33-8440-4069-815a-de9d8629dae3 d40facd1-7496-42b7-8bc7-70235396d349 18c437e5-d65e-418f-a739-9604cef8ab33 1c46e959-5805-47da-a079-58900787ef25 8f289ebb-d8fb-48f6-8429-430110eacb4a 1a5fd55e-79b9-4dd5-ae9b-ea10ef3156e9 f7459a50-3ef4-40f5-a7d7-955fb3af6432 futuregrid/centos-6 futuregrid/coreos futuregrid/debian-7 futuregrid/fedora-18 futuregrid/fedora-19 futuregrid/sl-6 futuregrid/ubuntu-12.04 futuregrid/ubuntu-13.10

5.3.7. Key management

To start a virtual machine you must first upload a key to the cloud. This can be easily done in the following way:

$ nova keypair-add $USER-key > ~/.ssh/$USER-key
$ chmod 600 ~/.ssh/$USER-key
$ nova keypair-list
+---------------+-------------------------------------------------+
| Name          | Fingerprint                                     |
+---------------+-------------------------------------------------+
| <USER>-key    | ab:a6:63:82:dd:08:d3:bc:c0:21:56:4c:e2:bb:22:ac |
+---------------+-------------------------------------------------+

Where USER is your login name on sierra.

Make sure you are not already having the key with that name in order to avoid overwriting it in the cloud. Thus be extra careful to execute this step twice. Often it is the case that you already have a key in your ~/.ssh directory that you may want to use. For example if you use rsa, your key will be located at ~/.ssh/id_rsa.pub.

5.3.8. Managing security groups

In the next step we need to make sure that the security groups allow us to log into the VMs. To do so we create the following policies as part of our default security policies. Not that whne you are in a group project this may already have been done for you by another group member. We will add ICMP and port 22 on default group:

$ nova secgroup-add-rule default icmp -1 -1 0.0.0.0/0
$ nova secgroup-add-rule default tcp 22 22 0.0.0.0/0
$ nova secgroup-list-rules default

You will see the following output if everything went correctly:

+-------------+-----------+---------+-----------+--------------+
| IP Protocol | From Port | To Port | IP Range  | Source Group |
+-------------+-----------+---------+-----------+--------------+
| icmp        | -1        | -1      | 0.0.0.0/0 |              |
| tcp         | 22        | 22      | 0.0.0.0/0 |              |
+-------------+-----------+---------+-----------+--------------+

5.3.9. Booting an image

To boot an instance you simply can now use the command:

$ nova boot --flavor m1.small \
            --image "futuregrid/ubuntu-12.04" \
            --key_name $USER-key $USER-001

If everything went correctly, you will see an output similar to:

+-----------------------------+--------------------------------------+
| Property                    | Value                                |
+-----------------------------+--------------------------------------+
| status                      | BUILD                                |
| updated                     | 2013-05-15T20:32:03Z                 |
| OS-EXT-STS:task_state       | scheduling                           |
| key_name                    | <USER>-key                           |
| image                       | futuregrid/ubuntu-12.04              |
| hostId                      |                                      |
| OS-EXT-STS:vm_state         | building                             |
| flavor                      | m1.small                             |
| id                          | e15ad5b6-c3f0-4c07-996c-3bbe709a63b7 |
| security_groups             | [{u'name': u'default'}]              |
| user_id                     | 3bd2d773911c4502982e5c2cd81437f7     |
| name                        | vm001                                |
| adminPass                   | KgiKjek99dgk                         |
| tenant_id                   | b7ea98db7b3449b184b58d28e80c7541     |
| created                     | 2013-05-15T20:32:03Z                 |
| OS-DCF:diskConfig           | MANUAL                               |
| metadata                    | {}                                   |
| accessIPv4                  |                                      |
| accessIPv6                  |                                      |
| progress                    | 0                                    |
| OS-EXT-STS:power_state      | 0                                    |
| OS-EXT-AZ:availability_zone | None                                 |
| config_drive                |                                      |
+-----------------------------+--------------------------------------+

5.3.10. List running images

To check if your instance is active you can repeatedly issue the list command and monitor the Status field in the table:

$ nova list

+--------------------------------------+---------------+--------+---------------------+
| ID                                   | Name          | Status | Networks            |
+--------------------------------------+---------------+--------+---------------------+
| e15ad5b6-c3f0-4c07-996c-3bbe709a63b7 | <USER>-001    | ACTIVE | private=10.35.23.18 |
+--------------------------------------+---------------+--------+---------------------+

Once it has changed from for example BUILD to ACTIVE, you can log in. Pleas use the IP address provided under networks. Note that the first address is private and can not be reached from outside sierra:

$ ssh -l ubuntu -i ~/.ssh/$USER-key 10.35.23.18

If you see a warning similar to:

Add correct host key in /home/<USER>/.ssh/known_hosts to get rid of this message.
Offending key in /home/<$USER>/.ssh/known_hosts:3

you need to delete the offending host key from .ssh/known_hosts.

5.3.11. Use block storage

You can create a block storage with the volume-create command. A valume is useful as you can store data in it and associate that particulare volumen to a VM. Hence, if you delete the VM, your volume and the data on t is still there to be reused. To create one 5G volume you can do

$ nova volume-create 5

To list the volumes you can use:

$ nova volume-list
+--------------------------------------+-----------+--------------+------+-------------+-------------+
| ID                                   | Status    | Display Name | Size | Volume Type | Attached to |
+--------------------------------------+-----------+--------------+------+-------------+-------------+
| 6d0d8285-xxxx-xxxx-xxxx-xxxxxxxxxxxx | available | None         |  5   | None        |             |
+--------------------------------------+-----------+--------------+------+-------------+-------------+

To attach the volume to your instance you can use the volume-attach subcommand. Let us assume we like to attache it as “/dev/vdb”, than you can use the command::

$ nova volume-attach $USER-001 6d0d8285-xxxx-xxxx-xxxx-xxxxxxxxxxxx "/dev/vdb"

Hint

Note thate $USER-001 refers to the name of the VM that we have created earlier with the boot command.

Next, let us login to your instance, make filesystem and mount it. Here’s an example, mounting on /mnt:

$ ssh -l ubuntu -i ~/.ssh/$USER-key 10.35.23.18
ubuntu@<USER>-001:~$ sudo su -
root@<USER>-001:~# mkfs.ext4 /dev/vdb
root@<USER>-001:~# mount /dev/vdb /mnt
root@<USER>-001:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/vda1        20G  2.1G   17G  11% /
none            4.0K     0  4.0K   0% /sys/fs/cgroup
udev            998M  8.0K  998M   1% /dev
tmpfs           201M  236K  201M   1% /run
none            5.0M     0  5.0M   0% /run/lock
none           1002M     0 1002M   0% /run/shm
none            100M     0  100M   0% /run/user
/dev/vdb        4.8G   23M  4.2G   1% /mnt

When you want to detach it, unmount /mnt first, go back to sierra’s login node and execute volume-detach:

root@<USER>-001:~# umount /mnt
root@<USER>-001:~# exit
ubuntu@<USER>-001:~$ exit

$ nova volume-detach $USER-001 6d0d8285-xxxx-xxxx-xxxx-xxxxxxxxxxxx

5.3.12. Set up external access to your instance

So far we only used the internal IP address, but you can also assign an external address, so that you can log in from other machines than sierra. Firts, Create an external ip address with:

$ nova floating-ip-create

+-----------------+-------------+----------+------+
| Ip              | Instance Id | Fixed Ip | Pool |
+-----------------+-------------+----------+------+
| 198.202.120.193 | None        | None     | nova |
+-----------------+-------------+----------+------+

Next, put it on your instance with:

$ nova add-floating-ip $USER-001 198.202.120.193
$ nova floating-ip-list

+-----------------+--------------------------------------+-------------+------+
| Ip              | Instance Id                          | Fixed Ip    | Pool |
+-----------------+--------------------------------------+-------------+------+
| 198.202.120.193 | c0bd849a-221a-4e53-bf7b-7097541a9bcc | 10.35.23.20 | nova |
+-----------------+--------------------------------------+-------------+------+

Now you should be able to ping and ssh from external and can use the given ip address.

5.3.13. Make a snapshot of an instance

To allow snapshots, you must use the following convention:

  • use your project number fg### in the prefix of your snapshot name followed by a /
  • If needed you can also add your username as a prefix in addition to the project number.

Let us assume your project is fg101 and you want to save the image with by reminding you it was a my-ubuntu-01 image you want to key. Than you can issue on sierra the following command:

$ nova image-create $USER-001 fg101/$USER/my-ubuntu-01
$ nova image-list
+--------------------------------------+----------------------------+--------+--------------------------------------+
| ID                                   | Name                       | Status | Server                               |
+--------------------------------------+----------------------------+--------+--------------------------------------+
| 18c437e5-d65e-418f-a739-9604cef8ab33 | futuregrid/fedora-18       | ACTIVE |                                      |
| 1a5fd55e-79b9-4dd5-ae9b-ea10ef3156e9 | futuregrid/ubuntu-12.04    | ACTIVE |                                      |
| f43375b4-44d3-4350-a9a8-a73f35589344 | fg101/<USER>/my-ubuntu-01  | ACTIVE | c0bd849a-221a-4e53-bf7b-7097541a9bcc |
+--------------------------------------+----------------------------+--------+--------------------------------------+

If you want to download your customized image, you can do it with this:

$ glance image-download --file "my-ubuntu-01.img" "fg101/$USER/custom-ubuntu-01"

Hint

Please note that images not following this convention will be deleted.

5.3.14. Automate some initial configuration

You may want to install some packages into the iamge, enable root, and add ssh authorized_keys. With the OpenStack cloud-init such steps can be simplified.

Create a file(mycloudinit.txt) containing these lines:

# cloud-config

# Enable root login.
disable_root: false

# Install packages.
packages:
- apt-show-versions
- wget
- build-essential

# Add some more ssh public keys.
ssh_authorized_keys:
- ssh-rsa AAAfkdfeiekf....fES7060rb myuser@s1
- ssh-rsa AAAAAAkgeig78...skdfjeigi myuser@myhost

Now boot your instance with –user-data mycloudinit.txt like this:

$ nova boot --flavor m1.small \
            --image "futuregrid/ubuntu-12.04" \
            --key_name $USER-key \
            --user-data mycloudinit.txt $USER-002

You should be able to login to <USER>-002 as root, and the added packages are installed.

5.3.15. Get the latest version of Ubuntu Cloud Image and upload it to the OpenStack

Todo

In future we will just host these images so we do not duplicate them on the server

Several versions of Ubuntu cloud images are available at http://cloud-images.ubuntu.com/. Choose the version you want and download the file name with ******-cloudimg-amd64-disk1.img. For example, downloading Ubuntu-13.04(Raring Ringtail)is like this:

$ wget http://cloud-images.ubuntu.com/raring/current/raring-server-cloudimg-amd...

You can upload the image with the glance client like this:

$ glance image-create \
       --name fg101/$USER/myimages/ubuntu-13.04 \
       --disk-format qcow2 \
       --container-format bare \
       --file raring-server-cloudimg-amd64-disk1.img

Now your new image is listed on nova image-listand will be available when the status become “ACTIVE”.

5.3.16. Delete your instance

  1. You can delete your instance with:

    $ nova delete $USER-002

    Please do not forget to also delete your 001 vm if you no longer need it

5.3.17. How to change your password

  1. Sometimes, users accidentally send password to a collaborator/support for debugging, and then regret. When you put yourself in the situation by mistake, don’t worry. Just use keystone client and reset your password with:

    $ keystone password-update

    * Remember, you will also need to change it in your novarc. This can be achieved by either editing your novarc file directly, or by editing the file ~/.futuregrid/cloudmesh.yaml and recreating your novarc file.

5.3.17.1. Things to do when you need Euca2ools or EC2 interfaces

Even though the nova client and protocols will provide you with more advanced features, some users still want to access OpenStack with EC2 compatible tools. One such tool are the euca2tools. We explain briefly how you can access them.

  1. Create a directory for putting eucarc, and create pk.pem, cert.pem and cacert.pem:

    cd ~/.futuregrid/
nova x509-create-cert
nova x509-get-root-cert
ls -la

  2. Create EC2_ACCESS_KEY and EC2_SECRET_KEY:

    keystone ec2-credentials-create

  3. Create the file called ~/.futuregrid/eucarc and put your EC2_ACCESS_KEY and EC2_SECRET_KEY that you obtained from the previous command into this file:

    export NOVA_KEY_DIR=$HOME/.futuregrid
export EC2_ACCESS_KEY="Your EC2_ACCESS_KEY"
export EC2_SECRET_KEY="Your EC2_SECRET_KEY"
export EC2_URL="http://s77r.idp.sdsc.futuregrid.org:8773/services/Cloud"
export S3_URL="http://s77r.idp.sdsc.futuregrid.org:3333"
export EC2_PRIVATE_KEY=${NOVA_KEY_DIR}/pk.pem
export EC2_CERT=${NOVA_KEY_DIR}/cert.pem
export NOVA_CERT=${NOVA_KEY_DIR}/cacert.pem
export EUCALYPTUS_CERT=${NOVA_CERT}
alias ec2-bundle-image="ec2-bundle-image --cert ${EC2_CERT} --privatekey ${EC2_PRIVATE_KEY} --user 42 --ec2cert ${NOVA_CERT}"
alias ec2-upload-bundle="ec2-upload-bundle -a ${EC2_ACCESS_KEY} -s ${EC2_SECRET_KEY} --url ${S3_URL} --ec2cert ${NOVA_CERT}"

  4. Confirm if euca2ools works:

    module load euca2ools
source ~/.futuregrid/eucarc
euca-describe-images
euca-describe-instances

Note

Here’s our known issues on using euca2ools or ec2 interface.

  • euca-upload-bundle with Boto 2.25.0 fails with “S3ResponseError: 404 Not Found”.
  • tagging function such as euca-create-tags, euca-describe-tags fail with “InvalidRequest: The request is invalid.”

5.3.18. Horizon GUI

Horizon is a graphical user interface/dashbooard for OpenStack. For starting up VMs and stoping them by hand horizon may be a good mechanism to manage your Virtual machines. We have currently the following horizon deployments available. However, please note that on Alamo an older version of openstack is run.

Horizon endpoints
Image Version Machine Protocol Description
image-horizon Havana India Native OpenStack India offers a Graphical user interface to access OpenStack. For those interested in only managing a few images this may be a good way to start. The link to the GUI is https://openstack-h.india.futuregrid.org/horizon The password can be found by following the method dicussed above.
image-horizon Grizzly Sierra Native OpenStack Sierra offers a Graphical user interface to access OpenStack. For those interested in only managing a few images this may be a good way to start. The link to the GUI is http://openstack-sierra.futuregrid.org/horizon The password can be found by following the method dicussed above.
image-horizon Havana Hotel EC2 Hotel offers a horizon interface to OpenStack, but in contrast to Sierra and India it uses the FG portal name and password. To ensure the security of your portal account, we recommend that you do not store that password in any file on your local or remote hosts. Instead, if you need to use the password, obtain it interactively via the shell builtin command read, with the -s (silent) option. We also recommend that you not store this password in a shell variable, but to ask for it every time it is needed. The link to the GUI is https://openstack.uc.futuregrid.org/dashboard/ The password is the same as the portal password. It only supports EC2.
image-horizon-alamo Folsom Alamo EC2 Alamo offers a horizon interface to OpenStack, but in contrast to Sierra and India it uses the FG portal name and password. To ensure the security of your portal account, we recommend that you do not store that password in any file on your local or remote hosts. Instead, if you need to use the password, obtain it interactively via the shell builtin command read, with the -s (silent) option. We also recommend that you not store this password in a shell variable, but to ask for it every time it is needed. The link to the GUI is https://openstack.futuregrid.tacc.utexas.edu/horizon The password is the same as the portal password. It only supports EC2.

5.3.18.1. Getting rc files via Horizon

On alamo, you can also get your ec2 rc file from the “settings” menu.