You can use network profiles to assign static IP addresses from a predefined range to virtual machines that are provisioned by cloning, by using Linux kickstart or autoYaST, or to cloud machines that are provisioned in OpenStack by using kickstart.
By default, vRealize Automation uses Dynamic Host Configuration Protocol (DHCP) to assign IP addresses to provisioned machines.
You can create network profiles to define a range of static IP addresses that you can assign to machines. You can assign network profiles to specific network paths on a reservation. Machines that are provisioned by cloning or by kickstart or autoYaST and are attached to a network path with an associated network profile are provisioned with an assigned static IP address. For provisioning with a static IP address assignment, you must use a customization specification.
You can assign a network profile to a vSphere machine component in a blueprint by adding an existing, on-demand NAT, or on-demand routed network component to the design canvas and selecting a network profile to which to connect the vSphere machine component. You can also assign network profiles to blueprints by using the custom property VirtualMachine.NetworkN.ProfileName, where N is the network identifier.
You can optionally use the supplied VMware internal IPAM or a registered external IPAM service provider to obtain and configure IP addresses. For information about external IPAM requirements, see Checklist for Preparing External IPAM Provider Support.
When you select an external IPAM endpoint in a network profile, vRealize Automation retrieves IP ranges from the registered external IPAM provider endpoint, such as Infoblox. It then allocates IP values from that endpoint.
If you specify a network profile in a reservation and a blueprint, the blueprint value takes precedence. For example, if you specify a network profile in the blueprint by using the VirtualMAchine.NetworkN.ProfileName custom property and in a reservation that is used by the blueprint, the network profile specified in the blueprint takes precedence. However, if the custom property is not used in the blueprint, and you select a network profile for a machine NIC, vRealize Automation uses the reservation network path for the machine NIC for which the network profile is specified.
When you destroy a machine that has a static IP address, its IP address is made available for other machines to use. Unused addresses might not be available immediately after the machines using them are destroyed because the process to reclaim static IP addresses runs every 30 minutes. If IP addresses are not available in the network profile, you cannot provision machines with static IP assignment on the associated network path.