You can create a vRA 8 blueprint to deploy machines and place them in existing NSX-T security group(s) by putting tags on the machine segment port(s). Update: July 26, 2021 Starting with vRA 8.2, using segment port tags to place machines in NSX-T security groups longer works. Thanks to my colleague, Mukesh Idnani, for this finding! Demo Product Versions vSphere 6.5 U3 vRA 8.0.1 (including vRSLCM and vIDM) NSX-T 2.

You can create a vRA 8 blueprint to deploy machines and place them in existing NSX-T security group(s) using vRA tags. Demo Product Versions vSphere 6.5 U3 vRA 8.0.1 (including vRSLCM and vIDM) NSX-T 2.5.1 vSAN 6.6.1 Prerequisites vRA 8: NSX-T account connected Basic infrastructure configured (Projects, Cloud Zones, Flavor Mappings, Image Mappings) NSX-T: security group(s) configured Process Overview Create a tag on the existing security group(s).

You can create a vRA 8 blueprint to deploy machines and place them in existing NSX-T security group(s) using a network profile. Note that with this method, however, any and all security groups that you select in the network profile will be applied to the machines. If you have multiple machines in a blueprint and want to specify which security group each machine should use, then use vRA tag or segment port tag (refer to series part 4 & 5 for those methods).

vRA 8 blueprint gives random names and numbers to the VMs and on-demand NSX-T networks deployed if you do not specify a naming convention. This blog will cover how you can customize the names of your VMs and on-demand NSX-T networks when they are deployed from a vRA 8 blueprint. Demo Product Versions vSphere 6.5 U3 vRA 8.0.1 (including vRSLCM and vIDM) NSX-T 2.5.1 vSAN 6.6.1 Prerequisites vRA 8:

You can create a vRA 8 blueprint to create an on-demand routed NSX-T network and deploy machines connected to these newly created network. When you tell the blueprint to create an on-demand routed NSX-T network, vRA 8 actually creates a tier-1 gateway that connects to the pre-existing tier-0 gateway. It then creates an on-demand network and attaches it to the tier-1 gateway that it has created. Demo Product Versions vSphere 6.

You can create a vRA 8 blueprint to deploy machines on existing NSX-T networks. Demo Product Versions vSphere 6.5 U3 vRA 8.0.1 (including vRSLCM and vIDM) NSX-T 2.5.1 vSAN 6.6.1 Prerequisites vRA 8: NSX-T account connected Basic infrastructure configured (Projects, Cloud Zones, Flavor Mappings, Image Mappings) NSX-T: logical router (tier-0 or tier-1) configured logical segment(s) attached to a logical router Process Overview Set up the existing networks with IP ranges you want to use for the machines.

With the recent release of vRA 8.0, I have been receiving many questions from customers about how vRA 8 can leverage NSX-T. This blog series will focus on demonstrating how you can create vRA 8 blueprints that utilize NSX-T constructs. Here is a list of blogs that I am planning on creating for this series (as of March 15, 2020): Part 1: vRA 8 Blueprint with Existing NSX-T Networks Part 2: vRA 8 Blueprint with On-demand Routed NSX-T Networks Part 3: vRA 8 Blueprint with Existing Security Groups (network profile) Part 4: vRA 8 Blueprint with Existing Security Groups (vRA tag) Part 5: vRA 8 Blueprint with Existing Security Groups (segment port tag) Part 6: vRA 8 Blueprint with On-demand Security Groups Part 7: vRA 8 Blueprint with Existing NSX-T One-Arm Load Balancer Part 8: vRA 8 Blueprint with On-demand NSX-T One-Arm Load Balancer Part 9: vRA 8 Blueprint with On-demand NAT NSX-T Networks Note: the list of blogs is subject to change.

The first problem I encountered when I decided to start a blog was deciding which hosting platform I should use. There are many great options out there, and I wanted to find a platform that won’t break the bank but is still easy to use and customize. After doing a lot of research and considering various hosting platforms (i.e. WordPress, GoDaddy, Squarespace, Bluehost, AWS, Firebase, etc.), I decided on GitHub Pages and Jekyll for the following reasons: