vrealize automation without NSX

[klabiak]

Guys, does it make sense to install "vrealize automation" without NSX?

I just considering scenario to install automation without any network virtualization (just based on distributed switches).

How then network should be managed from vrealize automation? Do I have to permanently stick network to blueprint?

Thanks for any tips.

[bayupw]

Yes, you basically connect VMs to existing network (PortGroup) and cannot use the On-Demand network/security objects without NSX

Depends on your use case but in my opinion it is quite common to start automating VM provisioning without NSX and do network/security automation or integration with NSX at later stage

Check HOL-1821-02-CMP - vRealize Automation 7 - Advanced Topics on labs.hol.vmware.com if you want to see how this work

[daphnissov]

Yes, it makes total sense to still use it without NSX, but you do not have to pin networks to blueprints. There are other ways to consume existing networks in vRA that are more flexible. It all comes down to your requirements.

[klabiak]

Thank you for information. I am very happy to see that there are vra experts.

For sure I will go through HOL.

My requirements will be to give the users possibility to choose between networks (in my case portgroup) during os_system deployment wizard. The network choose should be limited to users/business group. What I mean, one users group should see some limited networks list and the other users should see other networks list.

How can I made such configuration. Is something changed in version 7+?

Few years ago I implemented vra version 6 and it was impossible (or extremely hard to implement) to limit network in deployment wizard based on logged user. So I decided to stick network inside blueprint which in consequences forced me to create many blueprints. That's why my question appear - if there is any sens to implement vRA without NSX.

I know in version 7+ blueprint designer changed a lot.

[daphnissov]

What you want to do at this point is very standard and has been well addressed in a number of different ways including blogs and even orchestrator actions. There's no need to use NSX after describing your use case and you can safely move to vRA 7 and not worry.