Managing our network with an infrastructure as code (IaC) approach means using the same methodologies and processes we would use for the application code. Even better would be to treat the network configurations required to support the application as an integral part of the app itself. But, what does it exactly mean in practice?
When getting started with infrastructure automation, it is common to put together a script that sequentially performs the steps we would have done through the UI or the CLI. There is nothing wrong with that. Still, the more I played with APIs and Automation tools, the more I realized that to really treat my infrastructure …
In this post, I will explore the possibility of leveraging NSX-T Principal Identities in lieu of a proper object-based RBAC functionality not available in the current 2.4 version. This solution may be appealing in some multi-tenant scenarios.
I was planning to write an introductory post about how to get started with Ansible with NSX-T. I then realized that I could not do a better job than what Madhukar Krishnarao did here. I suggest you go through his blog post if you want to get started with Ansible for NSX-T. In this post, I will cover …
I spent the last few blog posts covering the basics of the Policy API introduced in NSX-T 2.4. I will be back to that topic soon with more examples, but for now, I would instead move to a different tool that I have been heavily leveraging when automating NSX-T, Ansible.
The most noticeable change in NSX-T 2.4 is the updated user interfaces. Specifically the option to perform the same configuration trough two very different UIs.
In this post, I will try to provide some insight on how to leverage the NSX-T policy API at its full potential.
In this post, I will review how the new NSX-T policy API interacts with the old management plane API.
In NSX-T version 2.4 VMware introduced a new API to configure and manage our virtual network environment.