Difference between revisions of "Volumes"

From CAC Documentation wiki
Jump to navigation Jump to search
m
(→‎Create and Attach a Volume: Organized steps for Creating and Attaching; added subsections for organization)
Line 7: Line 7:
 
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.
 
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 a volume
+
=== Create ===
# Go to Volumes/Volumes in the Horizon Web GUI
 
# Click "Create Volume"
 
# On the Actions dropdwon menu, click "Manage Attachments"
 
# Select the instance you wish to attach to and click "Attach Volume"; note the device name specifies is usually not important and not always adhered to.
 
::- For Linux: Once you have attached the volume, login to your instance and run <code>lsblk</code> to see which <code>/dev/vdX</code> is the likely candidate (for some character 'X'). You can then edit <code>/etc/fstab</code> to have this mounted; see standard Linux documentation for this and how to use the <code>mount</code> command.
 
::- TODO: notes for Windows?
 
  
 +
# 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]]
 +
# Click the "<tt>Create Volume</tt>" button
 +
# Enter a name and size
 +
# Click "<tt>Create Volume</tt>"
  
Snapshots of volumes (and of instances, in which case the volume is implicitly the root volume of the instance) can be created from the Actions dropwdown menu. This creates a state save of the existing volume. 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 Linux operating systems.  
+
=== Attach ===
 +
 
 +
# 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>"
 +
# 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
 +
 
 +
=== Once you have attached the volume ===
 +
 
 +
:* For Linux: Once you have attached the volume, login to your instance and run <code>lsblk</code> to see which <code>/dev/vdX</code> is the likely candidate (for some character 'X'). You can then edit <code>/etc/fstab</code> to have this mounted; see standard Linux documentation for this and how to use the <code>mount</code> command.
 +
:* For Windows - information coming soon
 +
 
 +
 
 +
Snapshots of volumes (and of instances, in which case the volume is implicitly the root volume of the instance) can be created from the Actions dropwdown menu. This creates a state save of the existing volume. 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 Linux operating systems.
  
 
== Types of Storage ==
 
== Types of Storage ==
 
Information coming soon.
 
Information coming soon.

Revision as of 18:42, 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

  1. Go to the "Volumes" tab in the OpenStack Web Interface
  2. Click the "Create Volume" button
  3. Enter a name and size
  4. Click "Create Volume"

Attach

  1. Go to the "Volumes" tab in the OpenStack Web Interface
  2. On the Actions dropdown menu for the volume you want to attach, select "Manage Attachments"
  3. 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: Once you have attached the volume, login to your instance and run lsblk to see which /dev/vdX is the likely candidate (for some character 'X'). You can then edit /etc/fstab to have this mounted; see standard Linux documentation for this and how to use the mount command.
  • For Windows - information coming soon


Snapshots of volumes (and of instances, in which case the volume is implicitly the root volume of the instance) can be created from the Actions dropwdown menu. This creates a state save of the existing volume. 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 operating systems.

Types of Storage

Information coming soon.