tenant

f5devcentral · Aug 2, 2024 · 7b0a2fe · 7b0a2fe
1 parent 1c57a78
commit 7b0a2fe
Show file tree

Hide file tree

Showing 4 changed files with 1 addition and 1 deletion.
diff --git a/docs/images/initial_setup_of_rseries_network_layer/image1.png b/docs/images/initial_setup_of_rseries_network_layer/image1.png
diff --git a/docs/images/initial_setup_of_rseries_network_layer/storage-utilization.png b/docs/images/initial_setup_of_rseries_network_layer/storage-utilization.png
diff --git a/docs/images/rseries_deploying_a_tenant/dashboard.png b/docs/images/rseries_deploying_a_tenant/dashboard.png
diff --git a/docs/initial_setup_of_rseries_network_layer.rst b/docs/initial_setup_of_rseries_network_layer.rst
@@ -20,7 +20,7 @@ More granular **Memory Utilization** is displayed showing how much memory is ded
   :align: center
   :scale: 70% 
 
-There is also more granularity showing **Storage Utilization**. In the below example, you can see that F5OS has utilized 60% of the 109.7GB of disk it has dedicated. You can also see that there is 448.6GB available for BIG-IP Tenant virtual disks, and that currently only 5% is used. This is the space shared by all BIG-IP Tenants virtual disks. It is important to remember that TMOS based BIG-IP virtual disks utilize thin provisioning, so the TMOS tenant may think it has more storage but in reality it is using much less capacity on the physical disk. You can see this by the **BIG-IP Tenant** utilizations. In the output below, there are two BIG-IP tenants (fix-ll & test-tenant). One has been allocated 80GB of disk while the other has been allocated 82GB of disk, however the actual size on disk is much lower (~5-7GB each).
+There is also more granularity showing **Storage Utilization**. In the below example, you can see that F5OS has utilized 60% of the 109.7GB of disk it has dedicated. You can also see that there is 448.6GB available for **F5OS Tenant Disks** (BIG-IP Tenant) virtual disks, and that currently only 5% is used. This is the space shared by all BIG-IP Tenants virtual disks. It is important to remember that TMOS based BIG-IP virtual disks utilize thin provisioning, so the TMOS tenant may think it has more storage but in reality it is using much less capacity on the physical disk. You can see this by the **BIG-IP Tenant** utilizations. In the output below, there are two BIG-IP tenants (fix-ll & test-tenant). One has been allocated 80GB of disk while the other has been allocated 82GB of disk, however the actual size on disk is much lower (~5-7GB each). Lastly, there is a single BIG-IP Next tenant that has 25GB allocated to it, but is currently utilizing 7% of that space.
 
 .. NOTE:: Storage utilization and allocation may be different on various rSeries platforms.