Differences

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

--- guide:cloud [2020/08/19 23:20]
lphukungoane [Using OpenStack dashboard]
+++ guide:cloud [2025/10/12 12:31] (current)
sfebruary [CHPC Cloud Resources]
@@ Line 5: / Line 5: @@
     *[[guide:cloud:start|Getting Started]]
     *[[guide:cloud|User Guide]]
+       *[[guide:cloud:advanced|IAC (Advanced)]]
     *[[guide:cloud:practices|Best Practice and Policies]]
     *[[guide:cloud:glossary|Glossary of Terms]]
@@ Line 29: / Line 30: @@
 Openstack volumes are logical block devices that can be attached to a single instance to provide a persistent location for data storage. Unlike a virtual machine's local disk which is destroyed along with the VM, volumes are decoupled from instances so that they may be attached and reattached to different instances. This allows you to create & destroy instances as you see fit while maintaining a persistent store for data.
-. First please open [[https://openstack.chpc.ac.za]] in your browser and login using the credentials provided.
+**1. Create Volume.**
+From the Openstack dashboard, click **Compute > Volumes > Create Volume**, fill out the form by providing a meaningful name, description and size. Once this is done, click **‘Create Volume’**. Your volume will be created and you can move on to the next step, ‘Attach a volume to an instance’.
-{{ :guide:screenshot_2020-06-17_login_-_openstack_dashboard.png?direct&400 |}}
+{{ :guide:screenshot_2020-08-20_volumes_-_openstack_dashboard_1_.png?direct&900 |}}
 ----
-. Launching a virtual machine, You have to accomplish a number of steps.
+**2. Attach a volume to an Instance.**
-a) Provide the initial hostname for the instance, the availability zone where it will be deployed, and the instance count. Increase the Count to create multiple instances with the same settings.:
+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_2_.png?direct&900 |}}
-{{ :guide:screenshot_2020-08-19_instances_-_openstack_dashboard_4_.png?direct&4000 |}}
+//From the Manage Volume Attachments form, select the Instance you wish to attach to and click **‘Attach Volume’**. This will dynamically attach the volume as a new logical block device to your instance. Move on to the next section of identifying the block device from within your Instance.//
+----
-b) Select the instance source, the template used to create an instance. You can use an image, a snapshot of an instance (image snapshot), a volume or a volume snapshot (if enabled). You can also choose to use persistent storage by creating a new volume.
-{{ :guide:screenshot_2020-08-19_instances_-_openstack_dashboard_3_.png?direct&4000 |}}
+**3. Identify A volume within Instance.**
-// For this example. The instance is launched from the image source and  a new volume is created with the instance. The allocated **ubuntu-18 image** is selected from the list of available images and is going to be an Operating System (OS) for the instance/s created. //
+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.//
 ----
+**4. Formatting the Volume.**
+Prerequisite: Install xfsprogs
-c) Decide on the flavor needed when launching the instance, Flavors manage the sizing for the compute, memory and storage capacity of the instance.
+As root: On Ubuntu based systems
-{{ :guide:screenshot_2020-08-19_instances_-_openstack_dashboard_5_.png?direct&4000 |}}
-// For this example. The instance is launched with **m1.tiny flavor** selected from the list of available flavors. The m1.tiny flavor will allocate the instance with 2x vCPU, 5GB of vRAM and 20GB of root disk.
+    apt-get install xfsprogs -y
-In order to carefully manage our compute resources, Only allocate what you are expecting to use, This is the total compute resources allocated to the instance created.//
+**Format using xfs**
+We are using **xfs** in this example because it is widely supported and supports extremely large volume sizes (9 exabytes)
+    mkfs.xfs -f /dev/vdc
 ----
-d) Select the network that your instance will connect to. The network provide the communication channels for instances in the cloud.
+**5. Mounting a Volume.**
-{{ :guide:screenshot_2020-08-19_instances_-_openstack_dashboard_6_.png?direct&4000 |}}
+Create a directory to mount the volume (example ‘data1’), mount the volume and then verify the mount.
-//For this example. The instance is launched with **demo-vxlan** network selected from the list of available networks. The network provide the communication channel for instance/s in the cloud.//
+As root:
+      "mkdir data1
+       mount -t xfs /dev/vdc /data1
+       df -hT /data1"
 ----
+**6. Re-attaching the volume to a different Instance.**
+**a) Unmount the volume.**
-e) Select the security groups to launch the instance in.
+As root, use the command **"umount"** to unmount the directory **data1**
-{{ :guide:screenshot_2020-08-19_instances_-_openstack_dashboard_7_.png?direct&4000 |}}
+    umount /data1
-//For this example. The instance is launched with **Default security group**  selected from the list of available security groups. The security groups are set of restrictive rules defined for the IP space, The selected default security group allows only ssh(22) and HTTPS(443). Openstack allows security groups editing after the instance has started, so additional changes can be made later if the exact requirements are not clearly defined.//
+//NB Remove or comment out the line added in **/etc/fstab** if applicable.//
+**b) Detach a volume.**
+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.
 ----
-f) Select an existing key pair, import a key pair, or generate a new key pair. A key pair allows you to SSH into your newly created instance.
+**7. Re-attach Volume.**
-{{ :guide:file.jpeg?direct&4000 |}}
+Follow the steps at the beginning of this guide to attach the volume to a desired instance. **DO NOT Format the volume from the new instance.** Skip that step and go directly to mounting. The volume is now mounted on a different Instance and the data is preserved.
 ----
-g) Optionally, You can customize your instance after it has launched using the options available here. "Customization Script" is analogous to "User Data" in other systems.
+**8. Extend Volume (Grow)**
-{{ :guide:screenshot_2020-08-19_instances_-_openstack_dashboard_9_.png?direct&4000 |}}
+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]]
 ----
-h) Finally, click the Launch button. It will take a few minutes for the instance to start, depending on how large the base image you chose was, and if it was already cached or not on the physical server where the VM will be scheduled to start.
+===== 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.//
 ----
-i) Associate a floating/public IP address.
+**How to deploy windows on openstack**
-{{ :guide:screenshot_2020-08-19_instances_-_openstack_dashboard_10_.png?direct&4000 |}}
+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.
-//By default, the VM will receive a private IP that is only reachable from inside your virtual network (other VMs connected to the same network).
+Since Microsoft Windows is still a major component in many IT infrastructures, there may be a need to run Windows-based instances on OpenStack.
-Because public IPv4 addresses are limited and there is an inherent security risk when connecting to the Internet, it is recommended to associate a floating/public IP address only to a single VM and use that one as an access server into your cloud environment.//
+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...!

wiki.chpc.ac.za

User Tools

Site Tools

Differences

Page Tools