About

About Essential Coach

Essential Coach is the technical writing of Noah Farshad — a working consultant publishing the patterns, tools, and lessons learned from real customer engagements with VMware Aria Automation, NSX Federation, BlueCat IPAM, Ansible, and federal STIG compliance.

This isn’t a marketing site. There are no contact forms gated behind ebook downloads. There are no vendor partnerships dictating which technologies get covered. Every story here came from a real customer environment, every line of open-source code on the linked GitHub repositories was written for a real production deployment, and every “lesson learned” section was written because something genuinely went wrong on the way to a working solution.

About Noah

I’ve spent the last decade-plus working in and around VMware infrastructure — first as an operator running production environments, then as a consultant designing and deploying them for enterprise customers. The work that ends up on essential.coach tends to live in the awkward space where vendor documentation runs out: the integration that requires reverse-engineering a reference plugin, the platform feature that doesn’t quite handle the customer’s edge case, the “the docs say this should work” that doesn’t, in production, work.

My current focus areas:

  • VMware Aria Automation (formerly vRealize Automation) — Cloud Assembly blueprints, Service Broker custom forms, ABX action development, Third-Party IPAM integration, vRO 8.x JavaScript actions, event subscription patterns.
  • NSX and NSX Federation — Multi-site network design, Global Manager / Local Manager segment management, network profile cleanup at scale, bare-metal Edge cluster planning.
  • BlueCat IPAM — Production-grade Aria Automation provider development, RESTful integration with BlueCat Address Manager, DNS lifecycle automation, Federation-aware allocation patterns.
  • Ansible automation for Windows and Linux — Idempotent role libraries, vault-managed secrets, post-deploy configuration management, dynamic inventory generators for vSphere and HPE OneView.
  • VMware vSphere STIG compliance — InSpec / CINC Auditor scanning, train-vmware plugin troubleshooting, CKL → CKLB conversion for STIG Viewer 3.x, federal accreditation workflows.
  • VCF lifecycle — VCF 5.x → VCF 9.x upgrade planning, vSAN OSA-to-ESA migration, Aria Suite Lifecycle to MS Fleet Management transition.

If you’re working on a problem in any of those areas, the customer success stories and the linked GitHub repositories are likely to be useful. If you’re working on something adjacent and want to talk through it, the contact link below works.

Why “Essential”?

The name reflects an editorial filter, not a brand promise. Most VMware content lives at one of two extremes: marketing-deck overviews that don’t help the operator, or 800-page reference manuals that don’t help the consultant scoping an engagement. Essential Coach aims for the middle — practical depth, with the friction points and lessons learned actually written down. Not every feature, just what matters. Not every automation, just what works.

How the customer success stories get written

Every story on this site follows the same template, learned the hard way over many engagements:

  • The Challenge — what was actually broken, in concrete terms, with specific numbers where possible.
  • The Journey — what got tried, what failed, what eventually worked, and the discoveries along the way.
  • The Results — quantified outcomes. Time saved, errors eliminated, manual steps replaced.
  • Lessons Learned — what worked, what didn’t, what we’d do differently. The honest parts.
  • Repository — the open-source code, sanitized of customer-identifying detail, with a README that walks through deployment.

Customer names are never published. Specific identifying details (real IPs, real hostnames, real domain names, real VLAN IDs) are sanitized before any code or document goes public. Technical details that aren’t customer-identifying — VCF version, NSX Federation topology, the specific bug discovered in a vendor plugin — stay in, because those are the parts that make the writing useful to the next person facing the same problem.

Open source

Every repository linked from a customer success story is published on GitHub under the GPL-3.0 license. The code is production-tested in the engagement it came from, and it ships with the same README and inline documentation the customer received. Pull requests welcome. Issues even more welcome — the patterns improve every time someone else surfaces an edge case.

Get in touch

The fastest way to reach me is noah@essential.coach. I read every email. Topics I’m always interested in:

  • Customer modernization engagements (vRO → Aria Automation, VCF upgrades, IPAM integrations)
  • NSX Federation design reviews
  • STIG compliance program reviews for VMware environments
  • Ansible role-library architecture for VMware-provisioned VMs
  • Speaking at VMware user group events or technical conferences
  • Bug reports on any of the open-source repositories — please file an issue rather than emailing if it’s reproducible

I generally respond within a few days. If your message is time-sensitive, mention that in the subject line.

What’s coming next

The current customer success story catalog covers two engagements in depth (a six-month modernization with a Fortune 500 federal services integrator and a federal agency STIG compliance program). Future stories I expect to publish, as the engagements they’re drawn from wrap up:

  • Linux post-deploy automation patterns (companion to the existing Windows post-deploy library)
  • VCF 9.1 upgrade planning and execution
  • Bare-metal NSX Edge cluster design (with the NIC compatibility lessons that nearly cost a real customer real money)
  • vSAN performance optimization without buying new hardware
  • Ansible Automation Platform integration patterns at scale

Subscribe to the GitHub profile to see new repositories as they ship. New customer success stories are announced on the Customer Stories page.

Scroll to Top