VCFA Tenant Portal – Namespace Storage Utilization

Products

• VCF Automation

Issue/Introduction

Namespace Storage utilization on VCFA doesn't match the vCenter values

Environment

VCF Automation 9.0.1

Resolution

This behavior is expected. No changes are required in VCFA

Additional Information

VCFA does not compute the utilization metrics itself, instead, it retrieves and presents the metrics generated in VCFOPs.

When you view namespace‑level storage utilization in VCFA, the figures are derived from a calculation that aggregates all files belonging to the file layout of VMs and PodVMs together.

The algorithm is intentionally focused on data attached to both VMs and PodVMs:

• VM and PodVM configuration files
• All virtual disks attached to a VM or PodVM
• Swap, suspend, log, core and memory files
• Any other files that form part of the file layout of a VM or PodVM

Anything that exists in vCenter but is not directly part of a VM or PodVM’s file layout such as floating persistent volumes, RWX volumes shared via NFS before being mounted into a pod, or external block‑storage objects provisioned through the Volume Service, is not included in this metric.

Why VCFOPs uses its own calculation

The storage metrics that vCenter exposes for namespace utilization have certain limitations that prevent them from providing an accurate picture of real‑time disk usage by VMs and PodVMs. To ensure customers receive reliable data, the VCF Ops team implemented a custom aggregation logic that:

• Captures only actual consumption by VMs, PodVMs, and their attached disks
• Avoids double‑counting storage that may be shared across multiple pods or services
• Provides consistency even when underlying infrastructure changes

What the current metric includes and excludes

 

Included	Excluded
All files that belong to the file layout of VMs or PodVMs (configuration, disks, auxiliary files)	Storage limits set for a namespace or project; floating PVs; RWX volumes shared via NFS; any external storage not attached to a VM or PodVM