Hi,
I am working on creating a ova deployment package for one of the products and am stuck is catering to different deployment scenarios though one single ovf/ova, which can lead to either an single machine creation or multiple machine creation based on scenario chosen at the time of deployment.
The scenario is described below:
- The product server has three different flavors in terms of installation and configuration:
- Primary Server (The main Server)
- Secondary Server (Add-on to Primary Server. Installation components are same and only at the time configuration it is marked to work as secondary)
- WebConnector Server (A different server installation. The functionality is dependent on Primary server though)
- The disk creation is done with deltadisk partitioning and following three vmdk are contained within the DiskSection of ovf:
- parent-disk.vmdk (Contains Windows 2008 R2 and will work as base/parent for next two vmdks)
- disk1.vmdk (Server (primary/secondary) installation delta)
- disk2.vmdk (Webconnector installation delta)
- To support these scenario in OVA, I’ve created following four different entries in the DeploymentOptionSection of the ovf:
- Deploy Primary Server (Requires a single machine to be created during deployment (parent-disk.vmdk + disk1.vmdk) and corresponding configuration properties to be collected)
- Deploy Secondary Server (Requires a single machine to be created during deployment (parent-disk.vmdk + disk1.vmdk) and corresponding configuration properties to be collected)
- Deploy WebConnector (Requires a single machine to be created during deployment (parent-disk.vmdk + disk2.vmdk) and corresponding configuration properties to be collected)
- Deploy Primary Server and WebConnector (It is a combination of Deployment Scenario 1 & 2 and requires TWO machines to be created during deployment and corresponding configuration properties for both machines to be collected individually)
- Different deployment scenarios will ask for different input properties and that is controlled by ovf:configuration within Property section of ovf. This seems working fine as it shows different inputs to be collected based on deployment scenario. But is there any way to propagate only relevant properties to a given machine? Right now it propagates all (same) properties to all the machines created through ova deployment.
- When I use ovf:configuration within VirtualSystem section of ovf, it seems to be NOT working. I choose any deployment scenario, it always creates TWO machines.
Is there any other way to do this?
Your help and guidance is needed. I am using vSphere 5.1 with vCenter.
Let me know if any clearification is required to understand my query.
I am attaching the ovf file for reference.