7.2.4 vCloud Networks and vFabric Application Director
When provisioning a vApp, vFabric Application Director does not create any vApp internal networks. Application Director connects provisioned vApps directly to a vCloud organization virtual datacenter network. This removes the ability to provision fenced vApps with vFabric Application Director. Properties can be dynamically updated at deployment time, so service scripts can be written to modify relevant configuration parameters for software being installed or configured.
As an example, a property can be created to acquire the IP address of a new virtual machine at deployment time. This IP address property can be used by a service script to properly configure an application based on the new IP address of the newly provisioned virtual machine. This property can be exposed across multiple services and across multiple virtual machines deployed by vFabric Application Director through dependency mapping in the blueprint.
vFabric Application Director
deployed vApps that are directly connected to an organization virtual datacenter
network must allow for the agent service in each virtual machine to contact the vFabric Application Director
server.vFabric Application Director
will not connect a vApp to an isolated organization virtual datacenter
network as that would remove the ability for the agent to contact the vFabric Application Director
server. vFabric Application Director
only connects
vApps to an organization virtual datacenter
network that is “direct” or “routed” to an external network.