Home

FIELD NOTES ON VIRTUALIZATION, STORAGE AND INFRASTRUCTURE

Written from production, not from datasheets.

Three hundred and fourteen posts on vSphere internals, storage latency, automation and the failure modes that only show up at three in the morning. If a walkthrough here says something works, it is because it was run, broken, and run again.

tapas@vmwareblogs:~$ site --summary

  author     Tapas Kumar Mahanta, Solutions Architect
  focus      vSphere internals, storage, automation, infrastructure
  posts      314
  subjects   6
  linkedin   /in/tapas-kumar-mahanta
  method     reproduce it, break it, then write it down
  promise    every command in every post has been run

tapas@vmwareblogs:~$ _

What you will find here

Six subject areas, built up over nine years of support escalations, lab builds and customer engagements.

vSphere and ESXi

Hypervisor internals, vCenter services, cluster behaviour, and the errors whose text points you at the wrong layer.

172 posts

Storage

vSAN, Tintri arrays, NFS and VMFS behaviour, snapshot chains, and tracing where the milliseconds actually go.

74 posts

Automation

PowerCLI and Python that replace repeated clicking, with the scripts written out in full rather than summarised.

97 posts

Compute and networking

Cisco UCS fabric, service profiles, and the network faults that arrive disguised as storage faults.

28 posts

Containers and cloud

Kubernetes, container runtimes and AWS, mostly at the point where they meet on premises infrastructure.

8 posts

Operations

Monitoring pipelines, backup platforms and Hyper-V, the systems that live alongside a vSphere estate.

11 posts


Latest posts


Three worth starting with


About me

I am Tapas Kumar Mahanta, a Solutions Architect working on storage and virtualization infrastructure, based in Bangalore. Most of what appears on this site starts as a customer escalation, a lab build or a proof of concept that did not behave the way the documentation said it would.

The day job covers vSphere and ESXi at scale, Tintri and vSAN storage, Cisco UCS, Kubernetes and CSI driver development, and OpenStack and OpenShift integration work. The writing here is the residue of that: the specific thing that was wrong, how it was found, and what to do about it.

Nothing here is vendor approved and none of it is official guidance. It is what worked, written down while it was still fresh. Corrections and disagreements are welcome, and more useful to me than agreement.

Get in touch