Uppsala Multidisciplinary Center for Advanced Computational Science

Smog user guide

Important: Smog is currently running as a test system. UPPMAX is NOT responsible for any data loss.

Smog cloud is an UPPMAX resource based on OpenStack cloud suite. The deployed system release is OpenStack’s JUNO. This guide provides basic steps to interact with the Smog cloud via web interface (Dashboard). Like other OpenStack based private clouds, Smog offers following services:

  1. Instance management (NOVA)
  2. Volume management (CINDER)
  3. Network access for the instances (NEUTRON)
  4. Object Store (Soon will be available) (SWIFT)
  5. Image management (GLANCE)
  6. Identity management (KEYSTONE)

This document only covers the dashboard (web client), for Comand-Line-Interface (CLI) or APIs please refer the latest OpenStack-User-Guide.

For questions and issue reporting, please send a mail to support@uppmax.uu.se .

In order to gain access to Smog, please apply for a project in the UPPMAX cloud round in SUPR.

Get started with Smog cloud

  • Enter the following URL in your preferred browser:
http://smog.uppmax.uu.se/dashboard
  • Enter your username and password.

  • First page shows the overall resource usage and limit summary.

  • The page has three major sections:
  • Information (top frame).

  • Limit summary (middle frame).

  • Control panel (left frame).

  • The “Instances” menu shows the information of running virtual machines (VMs).

  • Following are the possible actions one can perform on the VMs.

  • “Volume” menu shows the status of the created volumes.

  • Actions on the available volume(s).

  • "Images" are the entire state of the operating system stored on a non-volatile form such as files. “Images” menu shows the available images and their status in the system.

  • Access and Security page.

  • Security Groups tab in Access & Security page.

  • By default VMs are not allowed to respond to any network traffic. In order to make a VM respond to e.g. ping or connect to SSH, one needs to open the appropriate ports.

  • “Networks” menu contains information related to all the networks available in the project. In common settings there are two networks for each project:
    • Local: Each new VM gets a local IP form this network.
    • External: To access the machine from Internet, live IP should be assigned to the VM.

  • Network Topology shows how different VMs, networks and routers are connected for a specific project.

Steps to boot an instance

  • “Create new instance” link is available in “Instances” and “Images” pages. The link will open following dialog box.

Note: Before start a VM make sure that you have a working ssh keypair available in the cloud. For information about how to generate and inject ssh keypair in OpenStack based cloud,

visit: http://docs.openstack.org/user-guide/content/Launching_Instances_using_Dashboard.html

  • Following link will explain each of the available options:
http://docs.openstack.org/user-guide/content/dashboard_launch_instances_from_image.html

  • Security.

  • Networking.
Note: External network should not be selection from the following page. Only select the local or tenant related network(s) for your VM.

  • Once the instance is in “active” state, one can login via VNC console. Click on the instance name to connect your keyboard (sometimes require multiple clicks). For example, to activate displayed console click on the instance name (instance-00000258).

  • The newly build VM is active and one can access it via VNC (SSH is inaccessible at this stage). To connect using SSH requires a VM to be attached to a floating IP. “Attach floating IP” option is available from “Instances” page.

Steps to create a volume

  • “Create new volume” link is available in the “Volumes” page. The link will open following dialog box.

  • Following link will explain each of the available options:
http://docs.openstack.org/user-guide/content/dashboard_manage_volumes.html

Steps to attach volume to a virtual machine

  • Based on LVM, OpenStack consisted private clouds offer dynamic connection to the volume(s). Remember that one volume can only be attached to a single VM whereas one VM can have multiple volumes. Select a volume from the “Volumes” page, click on “Edit attachments”. The link will open the following page:

  • Once the volume is attached to the VM, “Attachments” list will display the volume label (Device), VM (Instance) and available actions.
  • Following steps will make the attached volume accessible:
  • Login to the VM.
  • The volume appear as:
/dev/disk/by-id/virtio-Identifier

Where the "Identifier" is the subset of the volume identifier available in the dashboard.

[root@/]$ ls /dev/disk/by-id/virtio-132456g43-43f54-43
  • Create file system on the volume.
[root@/]$ mkfs.ext4 /dev/disk/by-id/virtio-132456g43-43f54-43
  • Create a new directory and mount the volume.
[root@/]$ mkdir –p /mnt/my-volume
[root@/]$ mount /dev/disk/by-id/virtio-132456g43-43f54-43 /mnt/my-volume
  • You can verify the status by creating a file or running “disk filesystem” command.

[root@/]$ echo “Hello volume” > /mnt/my-volume/Hello
[root@/]$ df –h