Merge pull request #203 from nerc-project/GiB_MiB_memory_rename

WIP: updated TiB, GiB and MiB

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

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.
 

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

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,21 +86,21 @@ 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:
 
     `RoundUP(Sum(`
 
     `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,23 +154,23 @@ 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`
 
 **Storage Example 2:**
 
 - 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`
 

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

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.
 

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