Does anyone have any experience running VCD together wtih NSX? What I am looking to find out is if there would be any improvements in the start up time of a vApp in fencing mode using NSX.
Hi,
What sort of improvement are you expecting? When you say start up time of a vapp,what factors are we referring? The complete VAPP start time(Powering on VAPP,individual VM boot time,edge creation time etc)
Since this is a Fence Mode network,edge creation for fenced network is of no difference in NSX&VCNS. As long as the communication between NSX/VCD/Host is good it will get deployed successfully.However you will have choice to switch the replication mode (Multicast mode Replication and can be changed to Unicast or Hybrid mode)
Please do check VMware KB: vCloud Director 5.x and VMware NSX for vSphere 6.x interoperability guidelines .
hello
i haven't migrate yet but planning it too for the coming summer. its much the same to create edge device but underlying i been reading that its different with the multicasting VXLan setup but still reading about that.
should be easier to manage firewall rules also i think
keep me informed too if you find useful information
Thanks for your answers. Today it takes 4min from vapp start until the VMs power on. This is of course acceptable for me personally, but for the users who daily power on multiple vApps it can be frustrating.
I was hoping that this time could be cut in, at least, half with future development.
Hi,
Appreciate your update.One thing i can assure is NSX/VCNS is totally out of scope in this discussion.We need to check the performance matrix for the whole vapps.Few things which i can pin-point
1.No:Vm's residing in the vapps?
2.Type of allocation model Org-VDC is using?
3.Boot time for each VM(Easy to find in logs)?
4.Any underlying Storage latency issue?
5.How about if we remove VCD-VC mapping for those VM's and Power-on directly from VC?
So basically we have to do a performance test and check and confirm the results.Then only we can confirm if we really have a performance issue or is this a expected boot time!