I have successfully added a worker role to a virtual network by adding the following into the service config:
<NetworkConfiguration>
<VirtualNetworkSite name="VirtualNetwork" />
<AddressAssignments>
<InstanceAddress roleName="RoleName">
<Subnets>
<Subnet name="Front" />
</Subnets>
</InstanceAddress>
</AddressAssignments>
</NetworkConfiguration>
The dashboard for the role shows a single public address and IP, which would be the address of the NLB, but not the internal IP (the address on the virtual network). The 'resources' section of the virtual network shows the IP addresses of
the two instances of the role that are running, not the load balancer. Using one or other IP address works well across the VPN gateway that has been set up (which is cool!).
So, in this scenario:
1. Is there an internal IP (virtual network IP) of the existing load balancer? Do I need to add extra configuration to the above to enable it?
2. Assuming that there is an internal IP for the NLB, how can I set the lease of the NLB to be infinite? As you can with VMs, so that I can add a VPN DNS entry.
Without a private IP on the load balancer, worker roles on Virtual Networks are unusable. Apart from having an IP address per instance, it will change every time the role is recycled (including role upgrades).
Finally, it seems that the support of roles in Virtual Networking is not well supported or documented. What are the plans for this support come GA of virtual networking?
Simon