Merge pull request #70 from anarnold97/update-GiB

MTA-4234: Update GiB to Gi where applicable and Update GiB to GB where applicable

Author: anarnold97

docs/topics/mta-6-installing-web-console-on-openshift.adoc

@@ -24,27 +24,27 @@ To successfully deploy, the {ProductShortName} Operator requires 3 RWO persisten
 |Description
 
 |`hub database`
-|5 GiB
+|`5 Gi`
 |RWO
 |Hub database
 
 |`hub bucket`
-|100 GiB
+|`100 Gi`
 |RWX
 |Hub file storage; required if the `rwx_supported` configuration option is set to `true`
 
 |`keycloak postgresql`
-|1 GiB
+|`1 Gi`
 |RWO
 |Keycloak back end database
 
 |`pathfinder postgresql`
-|1 GiB
+|`1 Gi`
 |RWO
 |Pathfinder back end database
 
 |`cache`
-|100 GiB
+|`100 Gi`
 |RWX
 |Maven m2 cache; required if the `rwx_supported` configuration option is set to `true`
 |====
@@ -55,7 +55,7 @@ You can install the {ProductName} ({ProductShortName}) and the {WebName} on Open
 
 .Prerequisites
 
-* 4 vCPUs, 8 GiB RAM, and 40 GB persistent storage.
+* 4 vCPUs, 8 GB RAM, and 40 GB persistent storage.
 * OpenShift Container Platform 4.12-4.14 installed.
 * You must be logged in as a user with `cluster-admin` permissions.
 
@@ -83,7 +83,7 @@ The most commonly used CR settings are listed in this table:
 |Description
 
 |`cache_data_volume_size`
-|`100 GiB`
+|`100 Gi`
 |Size requested for the cache volume; ignored when `rwx_supported=false`
 
 |`cache_storage_class`
@@ -99,27 +99,27 @@ The most commonly used CR settings are listed in this table:
 |Flag to indicate whether namespace isolation using network policies is enabled
 
 |`hub_database_volume_size`
-|`5 GiB`
+|`5 Gi`
 |Size requested for the Hub database volume
 
 |`hub_bucket_volume_size`
-|`100 GiB`
+|`100 Gi`
 |Size requested for the Hub bucket volume
 
 |`hub_bucket_storage_class`
 |Default storage class
 |Storage class used for the bucket volume
 
 |`keycloak_database_data_volume_size`
-|`1 GiB`
+|`1 Gi`
 |Size requested for the Keycloak database volume
 
 |`pathfinder_database_data_volume_size`
-|`1 GiB`
+|`1 Gi`
 |Size requested for the Pathfinder database volume
 
 |`maven_data_volume_size`
-|`100 GiB`
+|`100 Gi`
 |Size requested for the Maven m2 cache volume; deprecated in {ProductShortName} 6.0.1
 
 |`rwx_storage_class`
@@ -212,34 +212,34 @@ When installed on https://developers.redhat.com/products/openshift-local/overvie
 .OpenShift Local {ProductShortName} memory requirements
 [cols="25%,75%", options="header"]
 |====
-|Memory (GiB)
+|Memory (Gi)
 |Description
 
 
-|`10`
+|`10Gi`
 |{ProductShortName} cannot run the analysis due to insufficient memory
 
-|`11`
+|`11Gi`
 |{ProductShortName} cannot run the analysis due to insufficient memory
 
-|`12`
+|`12Gi`
 |*{ProductShortName} works and the analysis is completed in approximately 3 minutes*
 
-|`15`
+|`15Gi`
 |{ProductShortName} works and the analysis is completed in less than 2 minutes
 
-|`20`
+|`20Gi`
 |{ProductShortName} works quickly and the analysis is completed in less than 1 minute
 |====
 
-The test results indicate that the minimum amount of memory for running {ProductShortName} on OpenShift Local is *12 GiB*.
+The test results indicate that the minimum amount of memory for running {ProductShortName} on OpenShift Local is *12 GB*.
 
 [NOTE]
 ====
 ** The tests were performed by running the {ProductShortName} binary analysis through the {WebName}.
 ** All the analyses used the `tackle-testapp` binary.
 ** All the tests were conducted on an OpenShift Local cluster without the monitoring tools installed.
-** Installing the cluster monitoring tools requires an additional 5 GiB of memory.
+** Installing the cluster monitoring tools requires an additional 5 GB of memory.
 ====
 
 [id="eviction-threshold_{context}"]

docs/topics/mta-7-configuration-web-console-on-ocp-local.adoc

@@ -6,15 +6,15 @@ The following table shows the recommended minimum configurations of {rh-ocp-loca
 
 [width="100%",cols="25%,25%,25%",options="header",]
 |===
-|Memory (GiB)
+|Memory (Gi)
 |CPU
-|Disk sze (GiB)
+|Disk sze (Gi)
 
-|20
+|`20Gi`
 |5
-|110
+|`110Gi`
 
-|20
+|`20Gi`
 |5
-|35, with the {ProductShortName} Operator configurations `cache_data_volume_size` and `hub_bucket_volume_size` set to 5GiB.
+|`35Gi`, with the {ProductShortName} Operator configurations `cache_data_volume_size` and `hub_bucket_volume_size` set to `5Gi`.
 |===

docs/topics/mta-7-installing-web-console-on-ocp-local.adoc

@@ -165,7 +165,7 @@ The `crc start` command starts the {rh-ocp-local} instance and configured contai
 
 |-d, –disk-size
 |uint
-|Total size in GiB of the disk used by the instance
+|Total size in GB of the disk used by the instance
 |31
 
 |-h, –help
@@ -175,7 +175,7 @@ The `crc start` command starts the {rh-ocp-local} instance and configured contai
 
 |-m, –memory
 |int
-|MiB of memory to assign to the instance
+|`Mi` of memory to assign to the instance
 |10752
 
 |-n, –nameserver
@@ -216,9 +216,9 @@ It also offers the following global flags:
 
 |===
 
-The default configuration creates a virtual machine (VM) with 4 virtual CPUs, a disk size of  31 GiB, and 10 GiB of RAM. However, this default configuration is not sufficent to stably run {ProductShortName}.
+The default configuration creates a virtual machine (VM) with 4 virtual CPUs, a disk size of  31 GB, and 10 GB of RAM. However, this default configuration is not sufficent to stably run {ProductShortName}.
 
-To increase the number of virtual CPUs to 6, the disk-size to 200 GiB, and the memory to 20 GiB, run `crc config` as follows:
+To increase the number of virtual CPUs to 6, the disk-size to 200 GB, and the memory to 20 GB, run `crc config` as follows:
 +
 [source,terminal]
 ----
@@ -228,7 +228,7 @@ crc config set cpus 6
 +
 [source,terminal]
 ----
-crc config set disk-size 200 
+crc config set disk-size 200
 ----
 
 +

docs/topics/mta-7-installing-web-console-on-openshift.adoc

@@ -30,22 +30,22 @@ To successfully deploy, the {ProductShortName} Operator requires 2 RWO persisten
 |Description
 
 |`hub database`
-|10 GiB
+|`10Gi`
 |RWO
 |Hub database
 
 |`hub bucket`
-|100 GiB
+|`100Gi`
 |RWX
 |Hub file storage; required if the `rwx_supported` configuration option is set to `true`
 
 |`keycloak postgresql`
-|1 GiB
+|`1Gi`
 |RWO
 |Keycloak back end database
 
 |`cache`
-|100 GiB
+|`100Gi`
 |RWX
 |Maven m2 cache; required if the `rwx_supported` configuration option is set to `true`
 |====
@@ -57,7 +57,7 @@ You can install the {ProductName} ({ProductShortName}) and the {WebName} on Red
 
 .Prerequisites
 
-* 4 vCPUs, 8 GiB RAM, and 40 GiB persistent storage.
+* 4 vCPUs, 8 GB RAM, and 40 GB persistent storage.
 * Any cloud services or self-hosted edition of Red Hat OpenShift on versions 4.13-4.15.
 * You must be logged in as a user with `cluster-admin` permissions.
 
@@ -87,7 +87,7 @@ The most commonly used CR settings are listed in this table:
 |Description
 
 |`cache_data_volume_size`
-|`100 GiB`
+|`100Gi`
 |Size requested for the cache volume; ignored when `rwx_supported=false`
 
 |`cache_storage_class`
@@ -103,27 +103,27 @@ The most commonly used CR settings are listed in this table:
 |Flag to indicate whether namespace isolation using network policies is enabled
 
 |`hub_database_volume_size`
-|`10 GiB`
+|`10Gi`
 |Size requested for the Hub database volume
 
 |`hub_bucket_volume_size`
-|`100 GiB`
+|`100Gi`
 |Size requested for the Hub bucket volume
 
 |`hub_bucket_storage_class`
 |Default storage class
 |Storage class used for the bucket volume
 
 |`keycloak_database_data_volume_size`
-|`1 GiB`
+|`1Gi`
 |Size requested for the Keycloak database volume
 
 |`pathfinder_database_data_volume_size`
-|`1 GiB`
+|`1Gi`
 |Size requested for the Pathfinder database volume
 
 |`maven_data_volume_size`
-|`100 GiB`
+|`100Gi`
 |Size requested for the Maven m2 cache volume; deprecated in {ProductShortName} 6.0.1
 
 |`rwx_storage_class`
@@ -147,15 +147,15 @@ The most commonly used CR settings are listed in this table:
 |Maximum number of CPUs the pod is allowed to use
 
 |`analyzer_container_limits_memory`
-|`4GiB`
+|`4Gi`
 |Maximum amount of memory the pod is allowed to use. You can increase this limit if the pod displays `OOMKilled` errors.
 
 |`analyzer_container_requests_cpu`
 |`1`
 |Minimum number of CPUs the pod needs to run
 
 |`analyzer_container_requests_memory`
-|`4GiB`
+|`4Gi`
 |Minimum amount of memory the pod needs to run
 |====
 
@@ -222,13 +222,13 @@ To prevent out-of-memory events and protect nodes, use the `--eviction-hard` set
 
 .Example of node memory allocation settings
 
-- Node capacity: `32 GiB`
+- Node capacity: `32Gi`
 
-- `--system-reserved` setting: `3 GiB`
+- `--system-reserved` setting: `3Gi`
 
-- `--eviction-hard` setting: `100 MiB`
+- `--eviction-hard` setting: `100Mi`
 
-The amount of memory available for running pods on this node is 28.9 GiB. This amount is calculated by subtracting the `system-reserved` and `eviction-hard` values from the overall capacity of the node. If the memory usage exceeds this amount, the node starts evicting pods.
+The amount of memory available for running pods on this node is 28.9 GB. This amount is calculated by subtracting the `system-reserved` and `eviction-hard` values from the overall capacity of the node. If the memory usage exceeds this amount, the node starts evicting pods.
 
 
 [id="mta-7-red-hat-single-sign-on_{context}"]

docs/topics/mta-requirements-for-java-analyzer.adoc

@@ -6,11 +6,11 @@
 [id="mta-requirements-for-java-analyzer_{context}"]
 = Adding minimum requirements for Java analyzer and discovery
 
-There is a minimum requirement for the Java analyzer, and also the discovery task, which by default is set to 2 GiB.
+There is a minimum requirement for the Java analyzer, and also the discovery task, which by default is set to 2 GB.
 
-While this minimum requirement can be lowered to 1.5 GiB, it is not recommended.
+While this minimum requirement can be lowered to 1.5 GB, it is not recommended.
 
-You can also increase this minimum requirement to more than 2 GiB.
+You can also increase this minimum requirement to more than 2 GB.
 
 [source, yaml]
 ----

docs/topics/mta-rn-upgrade-notes-7-0-0.adoc

@@ -10,9 +10,9 @@ The following are upgrade notes for {ProductFullName}
 
 .Hub database volume size
 
-In version 7.0.0 of {ProductShortName}, the default size of the hub database volume has been increased to 10GiB.
+In version 7.0.0 of {ProductShortName}, the default size of the hub database volume has been increased to 10GB.
 
-If your storage class does not support volume expansion, then an upgrade from 6.2.1 to 7.0.0 will result in a failure due to the operator trying to change the volume size from 5GiB to 10GiB.
+If your storage class does not support volume expansion, then an upgrade from 6.2.1 to 7.0.0 will result in a failure due to the operator trying to change the volume size from 5GB to 10GB.
 
 To avoid this issue, you can directly set the volume size by setting:
 

docs/topics/mta-rn-upgrade-notes-7-0-1.adoc

@@ -25,9 +25,9 @@ Enable the legacy Pathfinder questionnaire to see the completed status of assess
 
 .Hub database volume size
 
-In version 7.0.1 of {ProductShortName}, the default size of the hub database volume has been increased to 10GiB.
+In version 7.0.1 of {ProductShortName}, the default size of the hub database volume has been increased to 10GB.
 
-If your storage class does not support volume expansion, then an upgrade from 6.2.1 to 7.0.1 will result in a failure due to the operator trying to change the volume size from 5GiB to 10GiB.
+If your storage class does not support volume expansion, then an upgrade from 6.2.1 to 7.0.1 will result in a failure due to the operator trying to change the volume size from 5GB to 10GB.
 
 To avoid this issue, you can directly set the volume size by setting:
 

docs/topics/mta-rn-upgrade-notes-7-0-2.adoc

@@ -25,9 +25,9 @@ Enable the legacy Pathfinder questionnaire to see the completed status of assess
 
 .Hub database volume size
 
-In version 7.0.2 of {ProductShortName}, the default size of the hub database volume has been increased to 10GiB.
+In version 7.0.2 of {ProductShortName}, the default size of the hub database volume has been increased to 10GB.
 
-If your storage class does not support volume expansion, then an upgrade from 6.2.1 to 7.0.2 will result in a failure due to the operator trying to change the volume size from 5GiB to 10GiB.
+If your storage class does not support volume expansion, then an upgrade from 6.2.1 to 7.0.2 will result in a failure due to the operator trying to change the volume size from 5GB to 10GB.
 
 To avoid this issue, you can directly set the volume size by setting: