The next type of Network Policy we want to talk about is called Routed Network Policy. If you have worked with vRealize Automation 7 before, you might notice that Routed Network Policies correspond to Routed Networks in vRA 7. Hence you use a routed network policy when there is...
We have given a short introduction into vRealize Automation 8 networks in the last two blog posts. In short, the Network show the following information: The networks and networking objects that can be used for provisioning. Those networks are discovered from the underlying Cloud Accounts and can encompass vSphere...
As discussed in the last blog post, vRealize Automation allows to manage networks and their configuration settings in an intuitive and comfortable manner. Administrators have an overview over all networks imported from the underlying Cloud Accounts and are able to centrally manage stuff like CIDR Ranges, DNS settings, Gateways...
In order to use the capabilities of NSX-V in vRealize Automation, it is necessary to setup a NSX-V account. This can be done as follows: Navigate to Infrastructure > Cloud Accounts On the Account Types page, click NSX-V Choose NSX-V Provide the following information and click on Validate:...
When provisioning virtual machines to a cloud provider, users usually cannot exactly specify how much memory or CPUs should be used by a virtual machine. Instead cloud providers come with predefined flavors. vRealize Automation 8 also allows to define flavors. That is quite simple, hence this blog post is...
After having described how to install vRealize Automation, we have already shown how to add Cloud Accounts and Zones in vRealize Automation 8. As a recap, Cloud Accounts serve as endpoints for to importing existing resources into vRA (for example compute, network or storage resources). With Cloud Zones you...
Recent Comments