wiki.chpc.ac.za

User Tools

Site Tools

You are here: start » guide » cloud
Trace:
guide:cloud

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
guide:cloud [2020/08/20 00:35]
lphukungoane [Introduction - Volumes] 		guide:cloud [2025/10/12 12:31] (current)
sfebruary [CHPC Cloud Resources]
Line 5: Line 5:
     *[[guide:cloud:start|Getting Started]]     *[[guide:cloud:start|Getting Started]]
     *[[guide:cloud|User Guide]]     *[[guide:cloud|User Guide]]
 +       *[[guide:cloud:advanced|IAC (Advanced)]]
     *[[guide:cloud:practices|Best Practice and Policies]]     *[[guide:cloud:practices|Best Practice and Policies]]
     *[[guide:cloud:glossary|Glossary of Terms]]     *[[guide:cloud:glossary|Glossary of Terms]]
Line 50: Line 51:
 **3. Identify A volume within Instance.** **3. Identify A volume within Instance.**
  
-SSH into your instance, su to root and run ‘lsblk’+SSH into your instance, su to root and run **‘lsblk’**
  
 //**‘vda’** is the first disk of your Instance and contains one partition **‘vda1’** which contains the operating system. Any volumes attached to your Instance will be named **‘vdb, vdc, vdd’ & etc**. Identify the new disk by checking the size and comparing that to the size you created in the Openstack dashboard. Now that you have identified the logical block device from within the Instance you can move on to Formatting.// //**‘vda’** is the first disk of your Instance and contains one partition **‘vda1’** which contains the operating system. Any volumes attached to your Instance will be named **‘vdb, vdc, vdd’ & etc**. Identify the new disk by checking the size and comparing that to the size you created in the Openstack dashboard. Now that you have identified the logical block device from within the Instance you can move on to Formatting.//
Line 68: Line 69:
 We are using **xfs** in this example because it is widely supported and supports extremely large volume sizes (9 exabytes) We are using **xfs** in this example because it is widely supported and supports extremely large volume sizes (9 exabytes)
  
-    mkfs.xfs -f /dev/vdb +    mkfs.xfs -f /dev/vdc 
-     +
-      +
 ---- ----
  
 **5. Mounting a Volume.** **5. Mounting a Volume.**
  
-Create a directory to mount the volume (example ‘db1’), mount the volume and then verify the mount.+Create a directory to mount the volume (example ‘data1’), mount the volume and then verify the mount.
  
 As root: As root:
  
       "mkdir data1       "mkdir data1
-       mount -t xfs /dev/vdb /data1+       mount -t xfs /dev/vdc /data1
        df -hT /data1"        df -hT /data1"
  
Line 88: Line 88:
 **a) Unmount the volume.** **a) Unmount the volume.**
  
-As root, Within your VM instance, use the command **"umount"** to unmount the directory **data1**+As root, use the command **"umount"** to unmount the directory **data1**
  
     umount /data1     umount /data1
Line 97: Line 97:
  
 From the Openstack dashboard, click **Compute > Volumes** and then on the Actions drop down for the volume you want to attach to an Instance, click **‘Manage Attachments’**. From the Openstack dashboard, click **Compute > Volumes** and then on the Actions drop down for the volume you want to attach to an Instance, click **‘Manage Attachments’**.
 +
 +{{ :guide:screenshot_2020-08-20_volumes_-_openstack_dashboard_3_.png?direct&900 |}}
  
 From the Manage Volume Attachments form, Click **‘Detach Volume’** for the instance you wish to detach the volume from. From the Manage Volume Attachments form, Click **‘Detach Volume’** for the instance you wish to detach the volume from.
Line 107: Line 109:
 **8. Extend Volume (Grow)** **8. Extend Volume (Grow)**
  
 +Volumes can also be extended in size. In order to Extend the volume it must be unmounted and detached from an Instance.
 +
 +     Note: Volumes cannot have their size reduced.
 +     
 +{{ :guide:screenshot_2020-08-20_volumes_-_openstack_dashboard_4_.png?direct&900 |}}
 +     
 +Enter the new size of the volume and click **Extend Volume**.
 +
 +Re-attach the volume to your Instance, and remount the volume from within the instance. You will need to grow the xfs filesystem before it will make the new space available.
 +
 +As root:
 +
 +     xfs_growfs /dev/vdc -d
 +     
 +For more details, visit the openstack official pages:[[https://docs.openstack.org/mitaka/user-guide/dashboard_manage_volumes.html|Manage Volumes]]
 +----
 +===== Upload and manage images =====
 +
 +A virtual machine image, referred to in this document simply as an image, is a single file that contains a virtual disk that has a bootable operating system installed on it. Images are used to create virtual machine instances within the cloud. For information about creating image files, see the [[https://docs.openstack.org/image-guide/ | OpenStack Virtual Machine Image Guide.]]
 +
 +**1. Upload an image**
 +
 +Follow this procedure to upload an image to a project:
 +
 +   a) Log in to the dashboard.
 +   b) Select the appropriate project from the drop down menu at the top left.
 +   c) On the Project tab, open the Compute tab and click Images category.
 +   d) Click Create Image.
 +   
 +Then Create An Image dialog box appears
 +
 +{{ :guide:screenshot_2020-08-20_images_-_openstack_dashboard.png?direct&900 |}}
 +
 +
 +//Select **"Create Image"**, After you have filled all the required information.//
 +
 +----
 +**How to deploy windows on openstack**
 +
 +Windows Image for OpenStack: For most Linux distributions, it is possible to download a generic QCOW2 file for the purposes of running instances in a cloud environment. However, Microsoft does not provide such instances for any Cloud platform other than Azure.
 +
 +Since Microsoft Windows is still a major component in many IT infrastructures, there may be a need to run Windows-based instances on OpenStack.
 +
 +To upload Windows image, We suggest that you follow this tutorial for [[https://superuser.openstack.org/articles/how-to-deploy-windows-on-openstack/|Preparing windows images]] before uploading to the openstack environment.
 +
 +       Note: CHPC does not provide licenses, Appropriate licenses for any software run on the service by
 +       users must be sought and applied by the users, including any licenses that may be required to run
 +       instance operating systems.
 +
 +----
 +
 +
 +===== Access and security for instances =====
 +    work in progess...!
/app/dokuwiki/data/attic/guide/cloud.1597876536.txt.gz · Last modified: 2021/12/09 16:42 (external edit)

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 3.0 Unported
CC Attribution-Noncommercial-Share Alike 3.0 Unported Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki