Difference between revisions of "Volumes"
(→Create and Attach a Volume: Organized steps for Creating and Attaching; added subsections for organization) |
(→Create and Attach a Volume: Organized and updated Once You Have Attached The Volume section; made Snapshots section) |
||
Line 17: | Line 17: | ||
# Go to the [https://redcloud.cac.cornell.edu/dashboard/project/volumes/ "<tt>Volumes</tt>" tab] in the [[OpenStack#Using_the_OpenStack_Web_Interface_.28Horizon.29|OpenStack Web Interface]] | # Go to the [https://redcloud.cac.cornell.edu/dashboard/project/volumes/ "<tt>Volumes</tt>" tab] in the [[OpenStack#Using_the_OpenStack_Web_Interface_.28Horizon.29|OpenStack Web Interface]] | ||
− | # On the Actions dropdown menu for the volume you want to attach, select "<tt>Manage Attachments</tt>" | + | # On the <tt>Actions</tt> dropdown menu for the volume you want to attach, select "<tt>Manage Attachments</tt>" |
# Select the instance you wish to attach to and click "<tt>Attach Volume</tt>" | # Select the instance you wish to attach to and click "<tt>Attach Volume</tt>" | ||
#* Note that the device name specified is usually not important and not always adhered to | #* Note that the device name specified is usually not important and not always adhered to | ||
− | === Once | + | === Once You Have Attached The Volume === |
− | :* For Linux: | + | :* For Linux: |
+ | :*# [[Red_Cloud_Linux_Instances#Accessing_Instances|Login to your instance]] | ||
+ | :*# Run <code>lsblk</code> to see which <code>/dev/vdX</code> is the likely candidate (for some character 'X') | ||
+ | :*# Follow the instructions for [[Red_Cloud_Linux_Instances#Initialize_and_Mount_a_Volume|initializing and mounting]] your volume (replace <code>vdb</code> with the <code>vdX</code> discovered in the previous step) | ||
:* For Windows - information coming soon | :* For Windows - information coming soon | ||
+ | == Snapshots == | ||
− | Snapshots of volumes (and of instances, in which case the volume is implicitly the root volume of the instance) | + | Snapshots of volumes (and of [[OpenStack#Instances|instances]], in which case the volume is implicitly the root volume of the instance) create a state save of the existing volume, so you can easily get back to a certain state in the future. This is most useful for OS volumes to create safe checkpoints of working operating system configuration states. It may be less useful for larger data volumes; a more efficient solution might be to use [https://docs.oracle.com/cd/E23824_01/html/821-1448/gbciq.html ZFS snapshots] on [[Red Cloud Linux Instances|Linux instances]]. |
+ | |||
+ | Snapshots can be created from the <tt>Actions</tt> dropdown menu. Note that if you are creating a snapshot of a root volume for an instance, ''it should not be running''. You should first '''stop''' the instance, and then take the snapshot. | ||
== Types of Storage == | == Types of Storage == | ||
Information coming soon. | Information coming soon. |
Revision as of 18:59, 7 February 2019
Create and Attach a Volume
Volume creation is useful or attaching a data volume or a volume with users' home directories to an instance, as it is often good to separate the concerns of an operating system and user data. This makes it relatively easy to switch operating systems and maintain the same data, and to archive the more important parts of the project (the data) if needed.
Create
- Go to the "Volumes" tab in the OpenStack Web Interface
- Click the "Create Volume" button
- Enter a name and size
- Click "Create Volume"
Attach
- Go to the "Volumes" tab in the OpenStack Web Interface
- On the Actions dropdown menu for the volume you want to attach, select "Manage Attachments"
- Select the instance you wish to attach to and click "Attach Volume"
- Note that the device name specified is usually not important and not always adhered to
Once You Have Attached The Volume
- For Linux:
- Login to your instance
- Run
lsblk
to see which/dev/vdX
is the likely candidate (for some character 'X') - Follow the instructions for initializing and mounting your volume (replace
vdb
with thevdX
discovered in the previous step)
- For Windows - information coming soon
- For Linux:
Snapshots
Snapshots of volumes (and of instances, in which case the volume is implicitly the root volume of the instance) create a state save of the existing volume, so you can easily get back to a certain state in the future. This is most useful for OS volumes to create safe checkpoints of working operating system configuration states. It may be less useful for larger data volumes; a more efficient solution might be to use ZFS snapshots on Linux instances.
Snapshots can be created from the Actions dropdown menu. Note that if you are creating a snapshot of a root volume for an instance, it should not be running. You should first stop the instance, and then take the snapshot.
Types of Storage
Information coming soon.