diff --git a/docs/get-started/allocation/adding-a-new-allocation.md b/docs/get-started/allocation/adding-a-new-allocation.md index 1362af7e..cf388623 100644 --- a/docs/get-started/allocation/adding-a-new-allocation.md +++ b/docs/get-started/allocation/adding-a-new-allocation.md @@ -7,6 +7,10 @@ where all existing users for the project will be listed on the bottom of the req form. PIs can select desired user(s) to make the requested resource allocations available on their NERC's OpenStack or OpenShift projects. +Here, you can view the Resource Type, information about your Allocated Project, +status, End Date of the allocation, and actions button or any pending actions as +shown below: + ![Adding a new Resource Allocation](images/adding_new_resource_allocations.png) ## Adding a new Resource Allocation to your OpenStack project @@ -20,9 +24,9 @@ available on their NERC's OpenStack or OpenShift projects. **Storage quotas**, where the cost is determined by [your requested and approved allocation values](allocation-details.md#pi-and-manager-allocation-view-of-openstack-resource-allocation) to reserve storage from the total NESE storage pool. For **NERC (OpenStack)** - Resource Allocations, storage quotas are specified by the "OpenStack Volume - GB Quota" and "OpenStack Swift Quota in Gigabytes" allocation attributes. If - you have common questions or need more information, refer to our + Resource Allocations, the **Storage quotas** are specified by the "OpenStack + Volume Quota (GiB)" and "OpenStack Swift Quota (GiB)" allocation attributes. + If you have common questions or need more information, refer to our [Billing FAQs](../../get-started/cost-billing/billing-faqs.md) for comprehensive answers. Keep in mind that you can easily scale and expand your current resource allocations within your project by following [this documentation](allocation-change-request.md#request-change-resource-allocation-attributes-for-openstack-project) @@ -41,7 +45,7 @@ available on their NERC's OpenStack or OpenShift projects. [your requested and approved allocation values](allocation-details.md#pi-and-manager-allocation-view-of-openshift-resource-allocation) to reserve storage from the total NESE storage pool. For **NERC-OCP (OpenShift)** Resource Allocations, storage quotas are specified by the "OpenShift Request - on Storage Quota (GB)" and "OpenShift Limit on Ephemeral Storage Quota (GB)" + on Storage Quota (GiB)" and "OpenShift Limit on Ephemeral Storage Quota (GiB)" allocation attributes. If you have common questions or need more information, refer to our [Billing FAQs](../../get-started/cost-billing/billing-faqs.md) for comprehensive answers. Keep in mind that you can easily scale and expand diff --git a/docs/get-started/allocation/allocation-change-request.md b/docs/get-started/allocation/allocation-change-request.md index a75325e5..fa3f9818 100644 --- a/docs/get-started/allocation/allocation-change-request.md +++ b/docs/get-started/allocation/allocation-change-request.md @@ -14,10 +14,12 @@ This will bring up the detailed Quota attributes for that project as shown below !!! warning "Important: Requested/Approved Allocated OpenStack Storage Quota & Cost" For **NERC (OpenStack)** resource types, the **Storage quotas** are controlled - by the values of the "OpenStack Swift Quota in Gigabytes" and "OpenStack Volume - GB Quota" quota attributes. The **Storage cost** is determined by [your requested + by the values of the "OpenStack Volume Quota (GiB)" and "OpenStack Swift Quota + (GiB)" quota attributes. The **Storage cost** is determined by [your requested and approved allocation values](allocation-details.md#pi-and-manager-allocation-view-of-openstack-resource-allocation) - for these quota attributes. + for these quota attributes. If you have common questions or need more information, + refer to our [Billing FAQs](../../get-started/cost-billing/billing-faqs.md) + for comprehensive answers. PI or project managers can provide a new value for the individual quota attributes, and give justification for the requested changes so that the NERC admin can review @@ -50,8 +52,8 @@ This will show more details about the change request as shown below: !!! warning "Important: Requested/Approved Allocated OpenShift Storage Quota & Cost" For **NERC-OCP (OpenShift)** resource types, the **Storage quotas** are controlled - by the values of the "OpenShift Request on Storage Quota (GB)" and "OpenShift - Limit on Ephemeral Storage Quota (GB)" quota attributes. The **Storage cost** + by the values of the "OpenShift Request on Storage Quota (GiB)" and "OpenShift + Limit on Ephemeral Storage Quota (GiB)" quota attributes. The **Storage cost** is determined by [your requested and approved allocation values](allocation-details.md#pi-and-manager-allocation-view-of-openshift-resource-allocation) for these quota attributes. diff --git a/docs/get-started/allocation/images/adding_new_resource_allocations.png b/docs/get-started/allocation/images/adding_new_resource_allocations.png index 04a78822..34e7cf86 100644 Binary files a/docs/get-started/allocation/images/adding_new_resource_allocations.png and b/docs/get-started/allocation/images/adding_new_resource_allocations.png differ diff --git a/docs/get-started/allocation/images/coldfront-allocation-renewal-requested.png b/docs/get-started/allocation/images/coldfront-allocation-renewal-requested.png index ccf88bda..e9d757ed 100644 Binary files a/docs/get-started/allocation/images/coldfront-allocation-renewal-requested.png and b/docs/get-started/allocation/images/coldfront-allocation-renewal-requested.png differ diff --git a/docs/get-started/allocation/images/coldfront-openshift-allocation-attributes.png b/docs/get-started/allocation/images/coldfront-openshift-allocation-attributes.png index affc98d2..f73a7fcf 100644 Binary files a/docs/get-started/allocation/images/coldfront-openshift-allocation-attributes.png and b/docs/get-started/allocation/images/coldfront-openshift-allocation-attributes.png differ diff --git a/docs/get-started/allocation/images/coldfront-openshift-allocation-general-user-view.png b/docs/get-started/allocation/images/coldfront-openshift-allocation-general-user-view.png index b9c09464..74c9f678 100644 Binary files a/docs/get-started/allocation/images/coldfront-openshift-allocation-general-user-view.png and b/docs/get-started/allocation/images/coldfront-openshift-allocation-general-user-view.png differ diff --git a/docs/get-started/allocation/images/coldfront-openshift-allocation-pi-manager-view.png b/docs/get-started/allocation/images/coldfront-openshift-allocation-pi-manager-view.png index 03ac0bb8..2b3e5f50 100644 Binary files a/docs/get-started/allocation/images/coldfront-openshift-allocation-pi-manager-view.png and b/docs/get-started/allocation/images/coldfront-openshift-allocation-pi-manager-view.png differ diff --git a/docs/get-started/allocation/images/coldfront-openshift-change-requested-details.png b/docs/get-started/allocation/images/coldfront-openshift-change-requested-details.png index 085d8b07..b9ce9f67 100644 Binary files a/docs/get-started/allocation/images/coldfront-openshift-change-requested-details.png and b/docs/get-started/allocation/images/coldfront-openshift-change-requested-details.png differ diff --git a/docs/get-started/allocation/images/coldfront-openstack-allocation-attributes.png b/docs/get-started/allocation/images/coldfront-openstack-allocation-attributes.png index c6446a12..8e237fd1 100644 Binary files a/docs/get-started/allocation/images/coldfront-openstack-allocation-attributes.png and b/docs/get-started/allocation/images/coldfront-openstack-allocation-attributes.png differ diff --git a/docs/get-started/allocation/images/coldfront-openstack-allocation-general-user-view.png b/docs/get-started/allocation/images/coldfront-openstack-allocation-general-user-view.png index 87346473..1e252430 100644 Binary files a/docs/get-started/allocation/images/coldfront-openstack-allocation-general-user-view.png and b/docs/get-started/allocation/images/coldfront-openstack-allocation-general-user-view.png differ diff --git a/docs/get-started/allocation/images/coldfront-openstack-allocation-pi-manager-view.png b/docs/get-started/allocation/images/coldfront-openstack-allocation-pi-manager-view.png index 3e68bd7e..de1bdf59 100644 Binary files a/docs/get-started/allocation/images/coldfront-openstack-allocation-pi-manager-view.png and b/docs/get-started/allocation/images/coldfront-openstack-allocation-pi-manager-view.png differ diff --git a/docs/get-started/allocation/images/coldfront-renewed-allocation.png b/docs/get-started/allocation/images/coldfront-renewed-allocation.png index 43c61fda..5143b977 100644 Binary files a/docs/get-started/allocation/images/coldfront-renewed-allocation.png and b/docs/get-started/allocation/images/coldfront-renewed-allocation.png differ diff --git a/docs/get-started/allocation/images/coldfront-request-a-new-openshift-allocation.png b/docs/get-started/allocation/images/coldfront-request-a-new-openshift-allocation.png index 766ec7b1..9df1fdc4 100644 Binary files a/docs/get-started/allocation/images/coldfront-request-a-new-openshift-allocation.png and b/docs/get-started/allocation/images/coldfront-request-a-new-openshift-allocation.png differ diff --git a/docs/get-started/allocation/images/coldfront-request-a-new-openstack-allocation.png b/docs/get-started/allocation/images/coldfront-request-a-new-openstack-allocation.png index 217fd0ba..cdf3ec6a 100644 Binary files a/docs/get-started/allocation/images/coldfront-request-a-new-openstack-allocation.png and b/docs/get-started/allocation/images/coldfront-request-a-new-openstack-allocation.png differ diff --git a/docs/get-started/allocation/images/coldfront-request-new-openshift-allocation-with-users.png b/docs/get-started/allocation/images/coldfront-request-new-openshift-allocation-with-users.png index 16e64e31..62060e56 100644 Binary files a/docs/get-started/allocation/images/coldfront-request-new-openshift-allocation-with-users.png and b/docs/get-started/allocation/images/coldfront-request-new-openshift-allocation-with-users.png differ diff --git a/docs/get-started/allocation/images/coldfront-request-new-openshift-allocation.png b/docs/get-started/allocation/images/coldfront-request-new-openshift-allocation.png index 9bfdcce3..b50228b3 100644 Binary files a/docs/get-started/allocation/images/coldfront-request-new-openshift-allocation.png and b/docs/get-started/allocation/images/coldfront-request-new-openshift-allocation.png differ diff --git a/docs/get-started/allocation/images/coldfront-request-new-openstack-allocation-with-users.png b/docs/get-started/allocation/images/coldfront-request-new-openstack-allocation-with-users.png index e9cd0458..d715d132 100644 Binary files a/docs/get-started/allocation/images/coldfront-request-new-openstack-allocation-with-users.png and b/docs/get-started/allocation/images/coldfront-request-new-openstack-allocation-with-users.png differ diff --git a/docs/get-started/allocation/images/coldfront-request-new-openstack-allocation.png b/docs/get-started/allocation/images/coldfront-request-new-openstack-allocation.png index 1f4fff72..051328c6 100644 Binary files a/docs/get-started/allocation/images/coldfront-request-new-openstack-allocation.png and b/docs/get-started/allocation/images/coldfront-request-new-openstack-allocation.png differ diff --git a/docs/get-started/allocation/images/renew_expiring_allocation.png b/docs/get-started/allocation/images/renew_expiring_allocation.png index f3648285..216599d4 100644 Binary files a/docs/get-started/allocation/images/renew_expiring_allocation.png and b/docs/get-started/allocation/images/renew_expiring_allocation.png differ diff --git a/docs/get-started/allocation/requesting-an-allocation.md b/docs/get-started/allocation/requesting-an-allocation.md index fc810c6e..cb4b8b93 100644 --- a/docs/get-started/allocation/requesting-an-allocation.md +++ b/docs/get-started/allocation/requesting-an-allocation.md @@ -34,9 +34,9 @@ to be included in this allocation before clicking the "Submit" button. **Storage quotas**, where the cost is determined by [your requested and approved allocation values](allocation-details.md#pi-and-manager-allocation-view-of-openstack-resource-allocation) to reserve storage from the total NESE storage pool. For **NERC (OpenStack)** - Resource Allocations, storage quotas are specified by the "OpenStack Volume - GB Quota" and "OpenStack Swift Quota in Gigabytes" allocation attributes. If - you have common questions or need more information, refer to our + Resource Allocations, the **Storage quotas** are specified by the "OpenStack + Volume Quota (GiB)" and "OpenStack Swift Quota (GiB)" allocation attributes. + If you have common questions or need more information, refer to our [Billing FAQs](../../get-started/cost-billing/billing-faqs.md) for comprehensive answers. Keep in mind that you can easily scale and expand your current resource allocations within your project by following [this documentation](allocation-change-request.md#request-change-resource-allocation-attributes-for-openstack-project) @@ -56,10 +56,10 @@ integer value that corresponds to multiple OpenStack resource quotas. For exampl | `Instances` | 1 | | `vCPUs` | 1 | | `GPU` | 0 | -| `RAM(MB)` | 4096 | +| `RAM(MiB)` | 4096 | | `Volumes` | 2 | -| `Volume Storage(GB)` | 20 | -| `Object Storage(GB)` | 1 | +| `Volume Storage(GiB)` | 20 | +| `Object Storage(GiB)` | 1 | !!! info "Information" By default, **2 OpenStack Floating IPs**, **10 Volume Snapshots** and **10 Security @@ -96,10 +96,10 @@ integer value that corresponds to multiple OpenShift resource quotas. For exampl | :-------------------: | :-----------------------------------: | | `vCPUs` | 1 | | `GPU` | 0 | -| `RAM(MB)` | 4096 | -| `Persistent Volume Claims (PVC)` | 2 | -| `Storage(GB)` | 20 | -| `Ephemeral Storage(GB)` | 5 | +| `RAM(MiB)` | 4096 | +| `Persistent Volume Claims (PVC)` | 2 | +| `Storage(GiB)` | 20 | +| `Ephemeral Storage(GiB)` | 5 | !!! warning "Important: Requested/Approved Allocated OpenShift Storage Quota & Cost" Ensure you choose **NERC-OCP (OpenShift)** in the Resource option (**Always Remember:** @@ -110,7 +110,7 @@ integer value that corresponds to multiple OpenShift resource quotas. For exampl [your requested and approved allocation values](allocation-details.md#pi-and-manager-allocation-view-of-openshift-resource-allocation) to reserve storage from the total NESE storage pool. For **NERC-OCP (OpenShift)** Resource Allocations, storage quotas are specified by the "OpenShift Request - on Storage Quota (GB)" and "OpenShift Limit on Ephemeral Storage Quota (GB)" + on Storage Quota (GiB)" and "OpenShift Limit on Ephemeral Storage Quota (GiB)" allocation attributes. If you have common questions or need more information, refer to our [Billing FAQs](../../get-started/cost-billing/billing-faqs.md) for comprehensive answers. Keep in mind that you can easily scale and expand diff --git a/docs/get-started/cost-billing/how-pricing-works.md b/docs/get-started/cost-billing/how-pricing-works.md index e1598c50..f4a416d3 100644 --- a/docs/get-started/cost-billing/how-pricing-works.md +++ b/docs/get-started/cost-billing/how-pricing-works.md @@ -12,11 +12,11 @@ Hat OpenStack and Platform-as-a-Service (PaaS) – Red Hat OpenShift. The except is the **Storage quotas** in NERC Storage Tiers, where the cost is determined by [your requested and approved allocation values](../allocation/allocation-details.md#pi-and-manager-view) to reserve storage from the total NESE storage pool. For **NERC (OpenStack)** -Resource Allocations, storage quotas are specified by the "OpenStack Volume GB -Quota" and "OpenStack Swift Quota in Gigabytes" allocation attributes. Whereas for +Resource Allocations, storage quotas are specified by the "OpenStack Volume Quota +(GiB)" and "OpenStack Swift Quota (GiB)" allocation attributes. Whereas for **NERC-OCP (OpenShift)** Resource Allocations, storage quotas are specified by the -"OpenShift Request on Storage Quota (GB)" and "OpenShift Limit on Ephemeral Storage -Quota (GB)" allocation attributes. If you have common questions or need more +"OpenShift Request on Storage Quota (GiB)" and "OpenShift Limit on Ephemeral Storage +Quota (GiB)" allocation attributes. If you have common questions or need more information, refer to our [Billing FAQs](billing-faqs.md) for comprehensive answers. NERC offers a flexible cost model where an institution (with a per-project breakdown) is billed solely for the duration of the specific services required. Access is based @@ -29,7 +29,7 @@ and billing model. ### Service Units (SUs) -| Name | vGPU | vCPU | RAM (GB) | Current Price | +| Name | vGPU | vCPU | RAM (GiB) | Current Price | | - | - | - | - | - | | CPU | 0 | 1 | 4 | $0.013 | | A100 GPU | 1 | 24 | 74 | $1.803 | @@ -50,7 +50,7 @@ of the base SU for the maximum resource they reserve. - A Project or VM with: - `1 A100 GPU, 24 vCPUs, 95MB RAM, 199.2hrs` + `1 A100 GPU, 24 vCPUs, 95MiB RAM, 199.2hrs` - Will be charged: @@ -62,11 +62,11 @@ of the base SU for the maximum resource they reserve. - A Project or VM with: - `3 vCPU, 20 GB RAM, 720hrs (24hr x 30days)` + `3 vCPU, 20 GiB RAM, 720hrs (24hr x 30days)` - Will be charged: - `5 CPU SUs due to the extra RAM (20GB vs. 12GB(3 x 4GB)) x 720hrs x $0.013` + `5 CPU SUs due to the extra RAM (20GiB vs. 12GiB(3 x 4GiB)) x 720hrs x $0.013` `$46.80` @@ -86,11 +86,11 @@ of the base SU for the maximum resource they reserve. - Project with 3 Pods with: - i. `1 vCPU, 3 GB RAM, 720hrs (24hr*30days)` + i. `1 vCPU, 3 GiB RAM, 720hrs (24hr*30days)` - ii. `0.1 vCPU, 8 GB RAM, 720hrs (24hr*30days)` + ii. `0.1 vCPU, 8 GiB RAM, 720hrs (24hr*30days)` - iii. `2 vCPU, 4 GB RAM, 720hrs (24hr*30days)` + iii. `2 vCPU, 4 GiB RAM, 720hrs (24hr*30days)` - Project Will be charged: @@ -98,9 +98,9 @@ of the base SU for the maximum resource they reserve. `1 CPU SUs due to first pod * 720hrs * $0.013` - `2 CPU SUs due to extra RAM (8GB vs 0.4GB(0.1*4GB)) * 720hrs * $0.013` + `2 CPU SUs due to extra RAM (8GiB vs 0.4GiB(0.1*4GiB)) * 720hrs * $0.013` - `2 CPU SUs due to more CPU (2vCPU vs 1vCPU(4GB/4)) * 720hrs * $0.013` + `2 CPU SUs due to more CPU (2vCPU vs 1vCPU(4GiB/4)) * 720hrs * $0.013` `))` @@ -120,9 +120,8 @@ GPU pods, as GPU pods cannot currently share resources with CPU pods. ### Storage -Storage is charged separately at a rate of $0.009 TB/hr or $9.00E-12 KB/hr at a -granularity of KB/hr. For ease of reporting, storage SUs are shown in GB but calculated -in KB. OpenStack volumes remain provisioned until they are deleted. VM’s reserve +Storage is charged separately at a rate of **$0.009 TiB/hr** or **$9.00E-6 GiB/hr**. +OpenStack volumes remain provisioned until they are deleted. VM's reserve volumes, and you can also create extra volumes yourself. In OpenShift pods, storage is only provisioned while it is active, and in persistent volumes, storage remains provisioned until it is deleted. @@ -133,10 +132,10 @@ provisioned until it is deleted. Once approved, these **Storage quotas** will need to be reserved from the total NESE storage pool for both **NERC (OpenStack)** and **NERC-OCP (OpenShift)** resources. For **NERC (OpenStack)** Resource Allocations, storage quotas are - specified by the "OpenStack Volume GB Quota" and "OpenStack Swift Quota in - Gigabytes" allocation attributes. Whereas for **NERC-OCP (OpenShift)** Resource + specified by the "OpenStack Volume Quota (GiB)" and "OOpenStack Swift Quota + (GiB)" allocation attributes. Whereas for **NERC-OCP (OpenShift)** Resource Allocations, storage quotas are specified by the "OpenShift Request on Storage - Quota (GB)" and "OpenShift Limit on Ephemeral Storage Quota (GB)" allocation + Quota (GiB)" and "OpenShift Limit on Ephemeral Storage Quota (GiB)" allocation attributes. Even if you have deleted all volumes, snapshots, and object storage buckets and @@ -155,11 +154,11 @@ provisioned until it is deleted. - Volume or VM with: - `500GB for 699.2hrs` + `500GiB for 699.2hrs` - Will be charged: - `.5 Storage TB SU (.5 TB x 700hrs) x $0.009 TB/hr` + `.5 Storage TiB SU (.5 TiB x 700hrs) x $0.009 TiB/hr` `$3.15` @@ -167,11 +166,11 @@ provisioned until it is deleted. - Volume or VM with: - `10TB for 720hrs (24hr x 30days)` + `10TiB for 720hrs (24hr x 30days)` - Will be charged: - `10 Storage TB SU (10TB x 720 hrs) x $0.009 TB/hr` + `10 Storage TiB SU (10TiB x 720 hrs) x $0.009 TiB/hr` `$64.80` diff --git a/docs/openshift/decommission/decommission-openshift-resources.md b/docs/openshift/decommission/decommission-openshift-resources.md index eb1a8996..52636c6a 100644 --- a/docs/openshift/decommission/decommission-openshift-resources.md +++ b/docs/openshift/decommission/decommission-openshift-resources.md @@ -209,7 +209,7 @@ Each allocation, whether requested or approved, will be billed based on the is determined by [your requested and approved allocation values](../../get-started/allocation/allocation-details.md#pi-and-manager-allocation-view-of-openshift-resource-allocation) to reserve storage from the total NESE storage pool. For **NERC-OCP (OpenShift)** Resource Allocations, storage quotas are specified by the "OpenShift Request -on Storage Quota (GB)" and "OpenShift Limit on Ephemeral Storage Quota (GB)" +on Storage Quota (GiB)" and "OpenShift Limit on Ephemeral Storage Quota (GiB)" allocation attributes. Even if you have deleted all Persistent Volume Claims (PVC) in your OpenShift project. @@ -218,8 +218,8 @@ resource allocations to zero (0) otherwise you will still be incurring a charge for the approved storage as explained in [Billing FAQs](../../get-started/cost-billing/billing-faqs.md). To achieve this, you must submit a final change request to reduce the -**Storage Quotas** for "OpenShift Request on Storage Quota (GB)" and "OpenShift -Limit on Ephemeral Storage Quota (GB)" to zero (0) for your **NERC-OCP (OpenShift)** +**Storage Quotas** for "OpenShift Request on Storage Quota (GiB)" and "OpenShift +Limit on Ephemeral Storage Quota (GiB)" to zero (0) for your **NERC-OCP (OpenShift)** resource type. You can review and manage these resource allocations by visiting the [resource allocations](https://coldfront.mss.mghpcc.org/allocation/). Here, you can filter the allocation of your interest and then proceed to request a diff --git a/docs/openshift/decommission/images/change_request_zero.png b/docs/openshift/decommission/images/change_request_zero.png index 19edd6d8..25cfef21 100644 Binary files a/docs/openshift/decommission/images/change_request_zero.png and b/docs/openshift/decommission/images/change_request_zero.png differ diff --git a/docs/openstack/backup/backup-with-snapshots.md b/docs/openstack/backup/backup-with-snapshots.md index f39b6b63..6f3a1416 100644 --- a/docs/openstack/backup/backup-with-snapshots.md +++ b/docs/openstack/backup/backup-with-snapshots.md @@ -258,21 +258,21 @@ below: Please remember that any volumes and snapshots stored will consume your **Storage quotas**, which represent the storage space allocated to your project. For **NERC (OpenStack)** Resource Allocations, storage quotas are specified - by the "OpenStack Volume GB Quota" and "OpenStack Swift Quota in Gigabytes" + by the "OpenStack Volume Quota (GiB)" and "OpenStack Swift Quota (GiB)" allocation attributes. You can delete any volumes and snapshots that are no longer needed to free up space. However, even if you delete volumes and snapshots, you will still be billed based on [your approved and reserved storage allocation](../../get-started/allocation/allocation-details.md#general-user-view-of-openstack-resource-allocation), which reserves storage from the total NESE storage pool. If you request additional storage by specifying a changed quota value for - the "OpenStack Volume GB Quota" and "OpenStack Swift Quota in Gigabytes" + the "OpenStack Volume Quota (GiB)" and "OpenStack Swift Quota (GiB)" allocation attributes through [NERC's ColdFront interface](https://coldfront.mss.mghpcc.org/), invoicing for the extra storage will take place upon fulfillment or approval of your request, as explained in our [Billing FAQs](../../get-started/cost-billing/billing-faqs.md). Conversely, if you request a reduction in the **Storage quotas**, specified - by the "OpenStack Volume GB Quota" and "OpenStack Swift Quota in Gigabytes", + by the "OpenStack Volume Quota (GiB)" and "OpenStack Swift Quota (GiB)", through a [change request using ColdFront](../../get-started/allocation/allocation-change-request.md#request-change-resource-allocation-attributes-for-openstack-project), your invoicing will be adjusted accordingly when the request is submitted. diff --git a/docs/openstack/create-and-connect-to-the-VM/create-a-Windows-VM.md b/docs/openstack/create-and-connect-to-the-VM/create-a-Windows-VM.md index c0dfa1fd..d74defc1 100644 --- a/docs/openstack/create-and-connect-to-the-VM/create-a-Windows-VM.md +++ b/docs/openstack/create-and-connect-to-the-VM/create-a-Windows-VM.md @@ -17,7 +17,7 @@ from an external volume: the normal process using `boot from image` as [described here](launch-a-VM.md). - To ensure smooth upgrade and maintenance of the system, select at least - 100GB for the size of the volume. + 100 GiB for the size of the volume. - Make sure your project has sufficient [storage quotas](../../get-started/allocation/allocation-details.md#general-user-view). @@ -36,7 +36,7 @@ Create a **Volume** using that *Windows Image*: ![MS-Winodws-2022 Image to Volume Create](images/stack_image_to_volume.png) -To ensure smooth upgrade and maintenance of the system, select at least 100GB +To ensure smooth upgrade and maintenance of the system, select at least 100 GiB for the size of the volume as shown below: ![Create Volume](images/create_volume.png) @@ -68,7 +68,7 @@ Identify the image for the initial volume contents from `openstack image list`. In the example above, this is image id `a9b48e65-0cf9-413a-8215-81439cd63966` for `MS-Windows-2022`. -Creating a disk from this image with a size of **100GB** named "my-volume" +Creating a disk from this image with a size of **100 GiB** named "my-volume" as follows. openstack volume create --image a9b48e65-0cf9-413a-8215-81439cd63966 --size 100 --description "Using MS Windows Image" my-volume diff --git a/docs/openstack/create-and-connect-to-the-VM/flavors.md b/docs/openstack/create-and-connect-to-the-VM/flavors.md index fa8f001c..94e93f7c 100644 --- 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 | @@ -71,7 +71,7 @@ that produce unprecedented performance boosts for technical computing workloads. should specify the number of GPUs they intend to use by setting the "OpenStack GPU Quota" attribute. We recommend ensuring that this count accurately reflects the current GPU usage. Additionally, they need to adjust the quota values for - "OpenStack Compute RAM Quota" and "OpenStack Compute vCPU Quota" to sufficiently + "OpenStack Compute RAM Quota (MiB)" and "OpenStack Compute vCPU Quota" to sufficiently accommodate the GPU flavor they wish to use when launching a VM in their OpenStack Project. @@ -219,7 +219,7 @@ hr of wall time. !!! question "NERC IaaS Storage Tiers Cost" Storage both **OpenStack Swift (object storage)** and **Cinder (block storage/ volumes)** are charged separately at a rate of - $0.009 TB/hr or $9.00E-12 KB/hr at a granularity of KB/hr. More about cost + **$0.009 TiB/hr** or **$9.00E-6 GiB/hr**. More about cost can be [found here](../../get-started/cost-billing/how-pricing-works.md) and some of the common billing related FAQs are [listed here](../../get-started/cost-billing/billing-faqs.md). @@ -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 index 1f078842..f1f1088f 100644 --- a/docs/openstack/create-and-connect-to-the-VM/images.md +++ b/docs/openstack/create-and-connect-to-the-VM/images.md @@ -28,6 +28,7 @@ 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? @@ -35,7 +36,7 @@ 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 new file mode 100644 index 00000000..89e8fa3e Binary files /dev/null and b/docs/openstack/create-and-connect-to-the-VM/images/resize_instance_confirm.png differ 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 new file mode 100644 index 00000000..e27ee7bf Binary files /dev/null and b/docs/openstack/create-and-connect-to-the-VM/images/resize_instance_dialog.png differ 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 new file mode 100644 index 00000000..392f1e03 Binary files /dev/null and b/docs/openstack/create-and-connect-to-the-VM/images/resize_instance_flavor.png differ 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 index f2a811c3..814439f8 100644 --- 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 index 3f395cb3..de403a71 100644 --- 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 centos@199.94.60.219:~/myfile.zip:~/ + scp -i ~/.ssh/your_pem_key_file.pem ./myfile.zip centos@199.94.60.219:~/myfile.zip !!! info "Important Note" While it’s probably best to compress all the files you intend to transfer into diff --git a/docs/openstack/decommission/decommission-openstack-resources.md b/docs/openstack/decommission/decommission-openstack-resources.md index 9d734747..abbecb3d 100644 --- a/docs/openstack/decommission/decommission-openstack-resources.md +++ b/docs/openstack/decommission/decommission-openstack-resources.md @@ -124,8 +124,8 @@ Each allocation, whether requested or approved, will be billed based on the **pay-as-you-go** model. The exception is for **Storage quotas**, where the cost is determined by [your requested and approved allocation values](../../get-started/allocation/allocation-details.md#pi-and-manager-allocation-view-of-openstack-resource-allocation) to reserve storage from the total NESE storage pool. For **NERC (OpenStack)** -Resource Allocations, storage quotas are specified by the "OpenStack Volume GB -Quota" and "OpenStack Swift Quota in Gigabytes" allocation attributes. +Resource Allocations, storage quotas are specified by the "OpenStack Volume Quota +(GiB)" and "OpenStack Swift Quota (GiB)" allocation attributes. Even if you have deleted all volumes, snapshots, and object storage buckets and objects in your OpenStack project. It is very essential to adjust the approved @@ -134,8 +134,8 @@ still be incurring a charge for the approved storage as explained in [Billing FAQs](../../get-started/cost-billing/billing-faqs.md). To achieve this, you must submit a final change request to reduce the -**Storage Quotas** for "OpenStack Volume GB Quota" and "OpenStack Swift Quota in -Gigabytes" to zero (0) for your **NERC (OpenStack)** resource type. You can review +**Storage Quotas** for the "OpenStack Volume Quota (GiB)" and "OpenStack Swift Quota +(GiB)" to zero (0) for your **NERC (OpenStack)** resource type. You can review and manage these resource allocations by visiting the [resource allocations](https://coldfront.mss.mghpcc.org/allocation/). Here, you can filter the allocation of your interest and then proceed to request a @@ -156,7 +156,7 @@ approved quota values are accurately displayed as [explained here](#review-your- Please confirm and verify that the `gigabytes` resource value that specifies total space in [external volumes](../persistent-storage/volumes.md#volumes) is set to -a limit of zero (0) in correspondence with the approved "OpenStack Volume GB Quota" +a limit of zero (0) in correspondence with the approved "OpenStack Volume Quota (GiB)" of your allocation when running `openstack quota show` openstack client command as shown below: @@ -175,7 +175,7 @@ To check the overall space used, you can use the following command Also, please confirm and verify that the `Quota-Bytes` property value is set to a limit of zero (0) in correspondence with the approved "OpenStack Swift Quota -in Gigabytes" of your allocation and also check the overall space used in `Bytes` +(GiB)" of your allocation and also check the overall space used in `Bytes` is one (1) along with no Containers and Objects, when running `openstack object store account show` openstack client command as shown below: diff --git a/docs/openstack/decommission/images/change_request_zero_storage.png b/docs/openstack/decommission/images/change_request_zero_storage.png index b63e541a..0089929f 100644 Binary files a/docs/openstack/decommission/images/change_request_zero_storage.png and b/docs/openstack/decommission/images/change_request_zero_storage.png differ diff --git a/docs/openstack/openstack-cli/openstack-CLI.md b/docs/openstack/openstack-cli/openstack-CLI.md index e47769cf..0458be5e 100644 --- a/docs/openstack/openstack-cli/openstack-CLI.md +++ b/docs/openstack/openstack-cli/openstack-CLI.md @@ -91,6 +91,16 @@ For more information on configuring the OpenStackClient please see the ### OpenStack Hello World +Generally, the OpenStack terminal client offers the following methods: + +- **list**: Lists information about objects currently in the cloud. + +- **show**: Displays information about a single object currently in the cloud. + +- **create**: Creates a new object in the cloud. + +- **set**: Edits an existing object in the cloud. + To test that you have everything configured, try out some commands. The following command lists all the images available to your project: diff --git a/docs/openstack/persistent-storage/create-an-empty-volume.md b/docs/openstack/persistent-storage/create-an-empty-volume.md index 533ab57e..ac11282f 100644 --- a/docs/openstack/persistent-storage/create-an-empty-volume.md +++ b/docs/openstack/persistent-storage/create-an-empty-volume.md @@ -51,7 +51,8 @@ To create a volume using the CLI, do this: ### Using the openstack client This allows an arbitrary sized disk to be attached to your virtual machine, like -plugging in a USB stick. The steps below create a disk of 20GB with name "my-volume". +plugging in a USB stick. The steps below create a disk of 20 gibibytes (GiB) with +name "my-volume". openstack volume create --size 20 my-volume diff --git a/docs/openstack/persistent-storage/extending-volume.md b/docs/openstack/persistent-storage/extending-volume.md index ca4b3930..b84308ea 100644 --- a/docs/openstack/persistent-storage/extending-volume.md +++ b/docs/openstack/persistent-storage/extending-volume.md @@ -18,7 +18,7 @@ Navigate to *Project -> Volumes -> Volumes*. ![Extending Volume](images/extending_volumes.png) -Specify, the new extened size in GB: +Specify, the new extened size in GiB: ![Volume New Extended Size](images/volume_new_extended_size.png) @@ -34,16 +34,16 @@ To run the OpenStack CLI commands, you need to have: ### Using the openstack client The following openstack client command syntax can be used to extend any existing -volume from its previous size to a new size of : +volume from its previous size to a new size of : - openstack volume set --size + openstack volume set --size For example: openstack volume set --size 100 my-volume -where "my-volume" is the existing volume with a size of **80 GB** and is going to -be extended to a new size of **100 GB**." +where "my-volume" is the existing volume with a size of **80 GiB** and is going +to be extended to a new size of **100 GiB**." !!! tip "Pro Tip" If your volume name `` includes spaces, you need to enclose diff --git a/docs/openstack/persistent-storage/format-and-mount-the-volume.md b/docs/openstack/persistent-storage/format-and-mount-the-volume.md index 2df80076..dcc1651e 100644 --- a/docs/openstack/persistent-storage/format-and-mount-the-volume.md +++ b/docs/openstack/persistent-storage/format-and-mount-the-volume.md @@ -75,7 +75,7 @@ mount it to another instance, the second instance will have access to the data. Here, we create an empty volume following the steps outlined in [this documentation](create-an-empty-volume.md). -Please make sure you are creating volume of the size 100 GB: +Please make sure you are creating volume of the size 100 GiB: ![Create Volume for Windows VM](images/create_volume_win.png) diff --git a/docs/openstack/persistent-storage/volumes.md b/docs/openstack/persistent-storage/volumes.md index 7acf1d76..06945f6c 100644 --- a/docs/openstack/persistent-storage/volumes.md +++ b/docs/openstack/persistent-storage/volumes.md @@ -72,31 +72,33 @@ You can opt for a **"volume snapshot"** if you only need to capture the volume's data. However, if your VM involves extended running processes and vital in-memory data, preserving the precise VM state is essential. In such cases, we recommend regularly taking a snapshot of the entire instance, known as an -**"instance snapshot"**, provided you have sufficient **Storage quotas**, -specifically the "OpenStack Volume Quota", "OpenStack Volume GB Quota", and -"OpenStack Swift Quota in Gigabytes" allocated for [your resource allocation](../../get-started/allocation/allocation-details.md#general-user-view-of-openstack-resource-allocation). -Utilizing snapshots for backups is of utmost importance, particularly when -safeguarding or recovering critical states and data from your instance. +**"instance snapshot"**, provided you have sufficient Volume **Storage quotas**, +specifically the "OpenStack Volume Quota (GiB)" allocated for [your resource allocation](../../get-started/allocation/allocation-details.md#general-user-view-of-openstack-resource-allocation). +Please ensure that your allocation includes sufficient quota for the "OpenStack +Number of Volumes Quota" to allow for the creation of additional volumes based on +your quota attributes. Utilizing snapshots for backups is of utmost importance, +particularly when safeguarding or recovering critical states and data from your +instance. !!! danger "Very Important: Requested/Approved Allocated Storage Quota and Cost" When you [delete virtual machines](../decommission/decommission-openstack-resources.md#delete-all-vms) backed by persistent volumes, the disk data is retained, continuing to consume approved storage resources for which you will still be billed. It's important to note that the **Storage quotas** for **NERC (OpenStack)** Resource Allocations, - are specified by the "OpenStack Volume GB Quota" and "OpenStack Swift Quota - in Gigabytes" allocation attributes. Storage cost is determined by + are specified by the "OpenStack Volume Quota (GiB)" and "OpenStack Swift Quota + (GiB)" allocation attributes. Storage cost is determined by [your requested and approved allocation values](../../get-started/allocation/allocation-details.md#pi-and-manager-allocation-view-of-openstack-resource-allocation) to reserve storage from the total NESE storage pool. If you request additional storage by specifying a changed quota value for - the "OpenStack Volume GB Quota" and "OpenStack Swift Quota in Gigabytes" + the "OpenStack Volume Quota (GiB)" and "OpenStack Swift Quota (GiB)" allocation attributes through [NERC's ColdFront interface](https://coldfront.mss.mghpcc.org/), invoicing for the extra storage will take place upon fulfillment or approval of your request, as explained in our [Billing FAQs](../../get-started/cost-billing/billing-faqs.md). Conversely, if you request a reduction in the **Storage quotas** by specifying - a reduced quota value for the "OpenStack Volume GB Quota" and "OpenStack Swift + a reduced quota value for the "OpenStack Volume Quota (GiB)" and "OpenStack Swift Quota in Gigabytes" allocation attributes through a [change request using ColdFront](../../get-started/allocation/allocation-change-request.md#request-change-resource-allocation-attributes-for-openstack-project), your invoicing will be adjusted accordingly when the request is submitted.