updated some files

nerc-project · May 31, 2024 · 5569630 · 5569630
1 parent df1ddf6
commit 5569630
Show file tree

Hide file tree

Showing 7 changed files with 50 additions and 8 deletions.
diff --git a/docs/openstack/create-and-connect-to-the-VM/flavors.md b/docs/openstack/create-and-connect-to-the-VM/flavors.md
@@ -12,8 +12,8 @@ The important fields are
 
 | Field      | Description                                      |
 |------------|--------------------------------------------------|
-| RAM        | Memory size in MB                                |
-| Disk       | Size of disk in GB                               |
+| RAM        | Memory size in MiB                                |
+| Disk       | Size of disk in GiB                               |
 | Ephemeral  | Size of a second disk. 0 means no second disk is defined and mounted. |
 | VCPUs      | Number of virtual cores                          |
 
@@ -234,8 +234,49 @@ Our team will review your request and reach out to you to discuss further.
 
 ## How to Change Flavor of an instance
 
-!!! warning "Important Note"
-    This is only possible using the openstack client at this time!
+### Using Horizon dashboard
+
+Once you're logged in to NERC's Horizon dashboard, you can navigate to
+*Project -> Compute -> Instances*.
+
+You can select the instance you wish to extend or change the flavor. Here, you
+will see several options available under the Actions menu located on the right-hand
+side of your instance, as shown here:
+
+![Resize VM's Instance](images/resize_instance_flavor.png)
+
+Click "Resize Instance".
+
+In the Resize Instance dialog box, select the new flavor of your choice under the
+"New Flavor" dropdown options. In this example, we are changing the current flavor
+"**cpu-su.1**" to the new flavor "**cpu-su.2**" for our VM, as shown below:
+
+![Resize Instance Dialog](images/resize_instance_dialog.png)
+
+Once reviwing the new flavor details and verified all details, press "Resize" button.
+
+!!! warning "Very Important Information"
+    You will only be able to choose flavors that are within your current available
+    resource quotas, i.e., vCPUs and RAM.
+
+You will see the status of the resize in the following page.
+
+When it says "Confirm or Revert Resize/Migrate", login to the instance and verify
+that it worked as intended (meaning the instance is working as before but with
+the new flavor).
+
+If you are happy with the result, press "Confirm Resize/Rigrate" in drop-down to
+the far right (it should be pre-selected) as shown below:
+
+![Confirm Resize/Migrate](images/resize_instance_confirm.png)
+
+This will finalise the process and make it permanent.
+
+If you are unhappy (for some reason the process failed), you are able to instead
+press "Revert resize/Migrate" (available in the drop-down). This will revert the
+process.
+
+### Using the CLI
 
 **Prerequisites**:
 

diff --git a/docs/openstack/create-and-connect-to-the-VM/images.md b/docs/openstack/create-and-connect-to-the-VM/images.md
@@ -28,14 +28,15 @@ an instance:
 | ubuntu-18.04-x86_64                   |
 | ubuntu-20.04-x86_64                   |
 | ubuntu-22.04-x86_64                   |
+| MS-Windows-2022                       |
 
 ## How to create and upload own custom images?
 
 Beside the above mentioned system provided images users can customize and upload
 their own images to the NERC, as documented in [this documentation](../advanced-openstack-topics/setting-up-your-own-images/how-to-build-windows-image.md).
 
 Please refer to [this guide](https://docs.openstack.org/image-guide/obtain-images.html)
-to understand more on how can you get other virtual machine images to the NERC's
-OpenStack platform.
+to learn more about how to obtain other publicly available virtual machine images
+for the NERC OpenStack platform within your project space.
 
 ---
diff --git a/docs/openstack/create-and-connect-to-the-VM/images/resize_instance_confirm.png b/docs/openstack/create-and-connect-to-the-VM/images/resize_instance_confirm.png
diff --git a/docs/openstack/create-and-connect-to-the-VM/images/resize_instance_dialog.png b/docs/openstack/create-and-connect-to-the-VM/images/resize_instance_dialog.png
diff --git a/docs/openstack/create-and-connect-to-the-VM/images/resize_instance_flavor.png b/docs/openstack/create-and-connect-to-the-VM/images/resize_instance_flavor.png
diff --git a/docs/openstack/create-and-connect-to-the-VM/launch-a-VM.md b/docs/openstack/create-and-connect-to-the-VM/launch-a-VM.md
@@ -94,7 +94,7 @@ you may choose any available images.
     If you don't specify custom value for the "**Volume Size (GB)**", that will
     be set to the root disk size of your selected Flavor. For more about the
     default root disk size you can refer to [this documentation](flavors.md).
-    We can override this value by entering our own custom value (in GB) and that
+    We can override this value by entering our own custom value (in GiB) and that
     is available as a Volume that is attach to the instance to enable persistent
     storage.
 

diff --git a/docs/openstack/data-transfer/data-transfer-from-to-vm.md b/docs/openstack/data-transfer/data-transfer-from-to-vm.md
@@ -131,7 +131,7 @@ for `my home directory`)
 
 For e.g.
 
-    scp -i ~/.ssh/your_pem_key_file.pem ./myfile.zip [email protected]:~/myfile.zip:~/
+    scp -i ~/.ssh/your_pem_key_file.pem ./myfile.zip [email protected]:~/myfile.zip
 
 !!! info "Important Note"
     While it’s probably best to compress all the files you intend to transfer into