The Rodeo Portal for New Users

The purpose of this lab is to explore using the Rodeo Portal to perform end-user tasks.

Login to the Rodeo Portal

Point your web browser at and login using your TACC User Portal credentials.

Import or Create SSH Key

  1. Navigate to the "Access & Security" menu, then the "Key Pairs" tab.
  2. If you already have an SSH key generated, click on "Import Key Pair".

    1. Type a name in "Key Pair Name"
    2. Paste your public key in the "Public Key" box.
    3. Click "Import Key Pair".

    Import Key Pair

  3. If you don't have an SSH Keypair, Click on "+ Create Key Pair"

    1. Type a name and then click on "Create Key Pair".
    2. A key will be created and your browser should download the private key pair.


      Download Key Pair


    3. You will need the location of this .pem file to login to your Openstack instances.

    4. Run the following command on your laptop/desktop to change permissions on the file.


    ubuntu@myinstance:~$ chmod 600 RodeoLaunchKey.pem


Launch an Instance (basic workflow)

  1. Navigate to "Instances" in the navigation pane. Click the "+ Launch Instance" button.
  2. Fill in the following fields:

    1. Instance Name: Your Instance Name
    2. Flavor: m1.tiny
    3. Instance Boot Source: Boot from image
    4. Image Name: TACC CentOS 6.5


    Launch Instance - Details


  3. The "Access & Security" tab should already have your Key Pair selected.


    Launch Instance - Access


  4. Click the "Networking" button.

  5. Click the "+" next to the private network created for your project to add it to "Selected Networks". Do NOT use the Public-Network yet. That will be added to the instance later.


    Launch Instance - Networking


  6. Click the blue "Launch" button.

  7. You should be back at the Instances list with your new instance in a "Spawning" state.


    State - Spawning


  8. Click on the "More" button and then "Associate Floating IP"


    Actions - Associate Floating IP


  9. Choose an IP from the "IP Address" list, or if none are available, click the "+".


    Manage Floating IP


  10. Choose "Public-Network" from the Pool and then "Allocate IP".


    Allocation Floating IP


  11. Click Associate.

  12. Your instance should now have a Powe State of "Running" and 2 IP addresses assigned; 1 public and 1 private.


    State - Running


  13. Login to the instance as the rodeo user. Replace the floating-IP variable appropriately.

ubuntu@myinstance:~$ ssh -i RodeoKeyPair.pem rodeo@floating-IP
The authenticity of host ' (' can't be established.
RSA key fingerprint is e5:c7:7a:dc:5a:87:4f:ea:e0:ee:5e:15:93:70:26:db.
`Are you sure you want to continue connecting (yes/no)? yes

Warning: Permanently added '' (RSA) to the list of known hosts.
Welcome to Ubuntu 12.04.2 LTS (GNU/Linux 3.2.0-38-virtual x86_64)
* Documentation:
System information as of Sun Apr  7 21:04:35 UTC 2013
System load:  0.01              Processes:           59
Usage of /:   15.4% of 4.91GB   Users logged in:     0
Memory usage: 8%                IP address for eth0:
Swap usage:   0%

Attach a Volume to Your Instance

  1. Navigate to the Volumes menu and click "+ Create Volume".
  2. Fill in the "Volume Name" and "Size (GB)". Click "Create Volume"


    Create Volume


  3. Your volume should be created. To attach it to an instance, click "More" and "Edit Attachments".




  4. Choose an instance from the "Attach To Instance" dropdown and then click "Attach Volume".


    Manage Volume Attachments


  5. Return to the command window of your SSH session.

  6. Run the following commands to prepare your volume for use in the instance.

    1. List volumes present in your instance:

      ubuntu@myinstance:~$ sudo fdisk -l
      Disk /dev/vde: 5368 345, 5368709120 bytes
      255 heads, 63 sectors/track, 652 cylinders, total 10485760 sectors
      Units = sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes
      Disk identifier: 0x00000000
       Device Boot Start End Blocks Id System
       /dev/vdal 16065 10474379 5229157+ 63 Linux
      Disk /dev/vdb: 10.7 GB, 10737418240 bytes
      16 heads, 63 sectors/track, 20805 cylinders, total 20971520 sectors
      Units = sectors of 1 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes
      Disk identifier: Ox00000000
      Disk /dev/vdb doesn't contain a valid partition table


    2. Create a file system:

      ubuntu@myinstance:~$ sudo mkfs -t ext4 /dev/vdb
      mkfs -t ext4 /dev/vdb mke2fe 1.42 (29-Nov-2011)
      Filesystem label=
      OS type: Linux
      Block size=4096 (log=2)
      Fragment size=4096 (log=2)
      Stride=0 blocks, Stripe width=0 blocks
      655360 inodes, 2621440 blocks
      131072 blocks (5.00%) reserved for the super user
      First data 11001=0 Maximum filesystem blocks=2684354560
      80 block groups 32768 blocks per group, 32768 fragments per group
      8192 inodes per group
      Superblock backups stored on blocks:
           32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632
      Allocating group tables: done
      Writing inode tables: done
      Creating journal (32768 blocks): done
      Writing superblocks and filesystem accounting information: done


    3. Create a mount point:

      ubuntu@myinstance:~$ sudo mkdir /myvol


    4. Mount the file system:

      ubuntu@myinstance:~$ sudo mount /dev/vdb /myvol


    5. Verify the file system is mounted:

      ubuntu@myinstance:~$ sudo df -h
      Filesystem        Size   Used   Avail  Use%   Mounted on
      /dev/vdal         5.0G   775M    4.0G   17%   /
      udev              242M   8.0K    242M    1%   /dev
      tmpfs              99M   216K     99M    1%   /run
      none              5.0M      0    5.0M    0%   /run/lock
      none              246M      0    246M    0%   /run/shm
      /dev/vdh          9.9G   151M    9.2G    2%   /myvol




Last update: September 11, 2014 8:30am