Note: Please go to to access the current RightScale documentation set. Also, feel free to Chat with us!
Home > Reference Info > Dashboard Help Text > Volumes



Volumes can be created from the New Volume form, which can be reached in a number of different ways: from the Cloud menu's New action button, from the Volumes Index page or from a Volume Snapshot page.

When creating a new Volume you need to specify the following items:

  • Name - A short name that lets you recognize the Volume.
  • Description - Describe the purpose of the Volume and any other useful information. This is for documentation purposes only and does not affect behavior of the Volume. Best practices does suggest you fill it out though!
  • Datacenter / Zone - The Datacenter / Zone that you would like to place your Volume into. You can only attach a Volume to an Instance that is in the same Datacenter / Zone. Before creating a new Volume you may need to specify the Datacenter / Zone of the Instance that you want to attach the new Volume to. This is because once a Volume is created, it cannot be moved into a different Datacenter / Zone.
  • Snapshot - A Volume Snapshot that you would like to build a Volume from. You are not required to provide a snapshot if you wish to create an empty volume. Simply select the "none" option in order to create a blank Volume.
  • Size in GB - The size of the volume in gigabytes. If you are creating the Volume based on an existing snapshot, a minimum size will be displayed. Size restrictions vary depending on the Cloud infrastructure you are using. Depending on the cloud there may be implied rules on volume size when creating a new volume. As a general rule some clouds allow you to make it any size larger than the size of the Volume Snapshot, while other clouds restrict the Volume to the exact size of the Volume Snapshot.
Clouds > Cloud > Volumes > New


Volumes provide persistent, high-performance, and high-availability block-level storage which you can attach to a running Instance in the Cloud (in the same zone only). Volumes can be formatted and mounted as a file system. You can attach a Volume to a Server at run-time or schedule it to be attached at boot-time. Multiple volumes can be mounted to the same Instance, but a Volume can only be attached to one Instance at a time. You can take Volume Snapshots at a particular point in time and then create multiple Volumes from a snapshot and place them into any zone however. You can also view the lineage of a Volume or Volume Snapshot to see when it was created, as well as any parent/child relationships it has.

Clouds > Cloud > Volumes

- -

Volumes Lineage tab

The Lineage tab shows a chronological lineage of all created Volumes within the account. Select an individual Volume to view a more detailed lineage report including the following information: Object (volume), Parent, Action (attach/detach/snapshot), Child and Time.

Clouds > Cloud > Volumes > Index > Lineage tab


A Volume provides a highly reliable, efficient and persistent storage solution that can be mounted to a cloud instance (in the same datacenter / zone).

Action Buttons

  • Attach now - Attach this volume to an operational Server. You will also have the option to configure the volume to be attached at boot time the next time the Server is launched.
  • Attach on boot time - Attach this volume to the Server instance (at boot time) the next time the Server is launched.
  • Detach - Unmount and detach the volume from a running Server instance. The volume will not be deleted after being detached.
  • Snapshot - When you attach a snapshot to a Server instance, a volume of that snapshot will be created and attached to the instance.
  • Delete - Delete the volume. You cannot delete a volume that is currently attached to a running Server instance. You must first detach it before you can delete it.
Clouds > Cloud > Volumes > Show

Volumes Lineage tab

The Lineage tab of an individual Volume shows the descendant Volumes and Snapshots of the Volume, their ancestral relationships to each other, and the attachments and detachments of the displayed Volumes.


  • Object - The Object is either a Volume, or Volume Snapshot.
  • Parent - A hyperlink to additional information about the Object (Volume or Volume Snapshot).
  • Action - The action that resulted in the lineage. Examples: attached to, detached from, cloned from (volume) or cloned from (snapshot).
  • Child - A hyperlink to additional information about the instance. For example, that a Volume was attached to, detached from, etc.
  • Time - Time stamp that the action occurred.
Clouds > Cloud > Volumes > Show > Lineage tab

Snapshots tab

The Snapshots tab shows the following field information for the selected snapshot: * Default Fields*

  • Name - Name of the snapshot.
  • Resource UID - The cloud's unique identification number of the Volume. It is generated by and persistent in the cloud, and passed through to the Dashboard for display.
  • Owner - Owner name associated with the account that owns the snapshot in the cloud (or nothing if there is no snapshot).
  • Volume - Volume name from which the Volume Snapshot was created.
  • Status - Status of the snapshot, where legal values are "pending", "failed" or "available". You can only use a snapshot to create a Volume if its status is completed and marked "available".
  • Tag(s) - Private metadata tags that have been added to the snapshot.
  • Started at - The timestamp of when the snapshot started to be created (not when it was completed).
  • Actions - Legal action (icons) are displayed. Actions that can be performed against the snapshot.

Other Fields

  • Size - Size of the snapshot in gigabytes. (Example: 10G)
  • Visibility - Visibility of the snapshot. This will be either "private" or "public". Where private means only the account itself has visibility to the Volume, and public is everybody has visibility.


  • Delete - Delete the selected snapshot. You can use the Delete action icon iteratively, or select multiple snapshots via the checkbox and then use the "delete selected" action button. (Note there are also "select all" and "clear all" links to help with multiple selections.)
Clouds > Cloud > Volumes > Show > Snapshots tab

Volumes Info tab

The Info tab displays the following field information for the volume:

  • Description - User-defined description of the Volume.
  • Resource UID - The cloud's unique identification number of the Volume. It is generated by and persistent in the cloud, and passed through to the Dashboard for display.
  • Datacenter / Zone - The Datacenter or Zone the Volume is in. Select the link to see more specific Datacenter / zone information.
  • Status - Status of the Volume. Legal values are: pending, available, in-use, terminating, failed.
  • Size - Size of the volume in gigabytes. (e.g. 10 GB)
  • Attachment status - Volume attachment status. If attached to a running instance, the status should be "Attached to InstanceID" (ID of the Instance). Otherwise, the status is "not attached".
  • Server - If the volume is attached to a Server than a link to that Server is provided.
  • Device - If the Volume is attached, the system identifier of the block device as it is manifested on the running Server is displayed (if known/reported). If the cloud does not report the Device, an unknown but unique value is assigned and displayed. For example: unknown_1538:1236
  • Attached at - Date/timestamp when the Volume was attached.
  • Started at - Date/timestamp of when the Volume was created. (More specifically, when the creation started, not completed.)
  • Created from - Snapshot the volume was created from, or "-" if it was not created from a snapshot.
  • Created by - RightScale User that started the Volume. Example:
  • Tag(s) - Private metadata tags that you've added to the Volume. Select the Edit Tags action link to manage Volume tags.
Clouds > Cloud > Volumes > Show > Info tab

Recurring Attachments tab

Recurring Attachments specify which Volumes should be attached to a Server the next time that it is launched. All of the Servers to which a Volume is scheduled to be attached at boot time are displayed in the "Recurring Attachments" tab of the Volume itself.


  • Runnable - The Server or Server Array to which a Volume attachment is attached or scheduled to be attached.
  • Runnable Type - Either "Server" or "Server Array", depending on what is Runnable.
  • Device - If a Volume is attached to an instance, the system identifier of the block device as it is manifested on the running Server is displayed. (If known and reported. For example, "/dev/sdj" ) If the Device of the Volume is not known it is labeled as such along with a unique/random number. Example: unknown_1438:1235.
  • Size - Size of the Volume in gigabytes. (For example, 10 GB.)


  • Delete - Delete the recurring Volume attachment between the Server/Server Array/instance and the Volume. You will be prompted prior to removal. (For example: "OK to delete Recurring Volume Attachment between MyServer and MyVolume?")
Clouds > Cloud > Volumes > Show > Recurring Attachments tab
You must to post a comment.
Last modified
08:19, 8 Jul 2013


This page has no custom tags.


This page has no classifications.



© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.