The NSX-T Policy API is a powerful concept that was introduced in 2.4 and powers the new Simplified UI. It provides a declarative method of describing, implementing and deleting your entire virtual network and security estate.
In a single API call you deploy a complete logical topology utilising all the features NSX-T provides including T1 Gateways (with NAT/Load Balancer services) for distributed routing, Segments for streched broadcast domains and DFW rules to enforce microsegmentation.
This example performs the following:
- Creates a T1 Gateway and connects it to the existing T0
- Creates three Segments and attaches them to the new T1
- Creates intra-app distributed firewall rules to only allow the necessary communication between tiers
- Creates Gateway Firewall rules to allow external access directly to the web tier
- Creates a Load Balancer for the web tier with TLS-offloading using a valid certificate
And once deployed the topology will look like this:
Currently, on the networking side there is only a T0 Gateway, a single Segment (which is a VLAN-backed transit Segment to the physical network), with no T1s or Load Balancers:
And on the security side there’s no DFW policies :
Once the JSON body (see my example here) is created with the relevant T0, Edge Cluster and Transport Zone IDs inserted, then the REST call can be constructed. Using your favourite REST API client e.g. Curl, Postman, Requests (Python), the request should look like this:
Header: Content-Type: application/json
Auth: Basic (NSX-T Admin User/Password)
Body: The provided JSON
Once you send a successful request you’ll notice you receive a status 200 almost instantly, but don’t be fooled into thinking that your entire topology has now been created!
In reality this is just the policy engine acknowledging your declarative intent. It now works to convert or ‘realise’ that intent in to imperative tasks that are used to create all of the required logical objects.
Once this has all been created you’ll see your network and security components in the GUI:
Now the magic of using this API means that you can also delete your entire topology with the same call, just changing the marked_for_delete to true for each section.
Example code here: https://github.com/certanet/nsx-t-policy-api