As you create or edit your vRealize Automation cloud template designs, use the most appropriate network resources for your objectives. Learn about the NSX and cloud-agnostic network options that are available in the cloud template.
Select one of the available network resource types based on machine and related conditions in your vRealize Automation cloud template.
Cloud agnostic network resource
Cloud.Networkresource type. The default resource displays as:
Cloud_Network_1: type: Cloud.Network properties: networkType: existing
Use a cloud agnostic network when you want to specify networking characteristics for a target machine type that is not, or might not, be connected to an NSX network.
- Cloud agnostic machine
- Google Cloud Platform (GCP)
- Amazon Web Services (AWS)
- Microsoft Azure
- VMware Cloud on AWS (VMC)
vSphere network resource
Cloud.vSphere.Networkresource type. The default resource displays as:
Cloud_vSphere_Network_1: type: Cloud.vSphere.Network properties: networkType: existing
Use a vSphere network when you want to specify networking characteristics for a vSphere machine type (
The vSphere network resource is only available for a
Cloud.vSphere.Machine machine type.
For more information about network types, see Netwerkinstellingen gebruiken in netwerkprofielen en cloudsjablonen in vRealize Automation.
NSX network resource
Cloud.NSX.Networkresource type. The default resource displays as:
Cloud_NSX_Network_1: type: Cloud.NSX.Network properties: networkType: existing
Use an NSX network when you want to attach a network resource to one or more machines that have been associated to an NSX-V or NSX-T cloud account. The NSX network resource allows you to specify NSX networking characteristics for a vSphere machine resource that is associated to an NSX-V or NSX-T cloud account.
Cloud.NSX.Networkresource is available for these network type (
- routed - Routed networks are only available for NSX-V and NSX-T.
Each on-demand NSX-T network creates a new Tier-1 logical router. Each on-demand NSX-V network creates a new Edge.
To support NAT rules and NAT port forwarding, you can add a
Cloud.NSX.Gateway cloud template resource to allow DNAT rules to be specified for the gateway/router that is connected to an outbound NSX-V or NSX-T network. The gateway must be attached to a single outbound network and can be connected to multiple machines or load balancers that are connected to the same outbound network. DNAT rules specified within the gateway reference these machines or load balancers as their target. NAT rules cannot be specified for clustered machines, however as a Day 2 operation they can be specified for individual machines within the cluster.
For related information, see Network, security, and load balancer examples in vRealize Automation cloud templates.
External IPAM integration options
For information about properties that are available for use with your Infoblox IPAM integrations in cloud template designs and deployments, see Infoblox-specifieke eigenschappen en uitbreidbaarheidskenmerken voor IPAM-integraties in vRealize Automation gebruiken.
Available day 2 operations
For a list of common day 2 operations that are available for cloud template and deployment resources, see Welke acties kan ik op vRealize Automation Cloud Assembly-implementaties uitvoeren.
For an example of how to move from one network to another, see Een geïmplementeerde machine naar een ander netwerk verplaatsen.
For information about defining network resources, see Netwerkresources in vRealize Automation.
For information about defining network profiles, see Meer informatie over netwerkprofielen in vRealize Automation.
For examples of cloud template designs that illustrate sample network resources and settings, see Network, security, and load balancer examples in vRealize Automation cloud templates.