Hi, Just to clarify things on this diagram I have multiple questions : In the "pink" area, I see the "User or Dev WKS" is this a VM that you want to duplicate in your "vApp" setup or is it ...
See more...
Hi, Just to clarify things on this diagram I have multiple questions : In the "pink" area, I see the "User or Dev WKS" is this a VM that you want to duplicate in your "vApp" setup or is it something external (like a real physical laptop) ? I'm asking because I see it in the "pink" area which is the Internal Virtual network "zone" in your diagram. So are we having 3/4 VMs within your vApp (WKS, monowall, App, DB) ? Another point bothering me in the diagram is the "native Lab manager router" having 2 nics on the same subnet (172.30.0.x/24), is this a copy/paste error ? There are multiples ways of building a Dev vApp for your needs, and the simplest one that comes to mind is a vApp with a vApp Network, having (if you don't need different subnets for the "monowall" and the wks/app tier, 3 VMs configured statically, (WKS, App, DB), and then fenced to an Org Network. (using NAT or IP Translation, depending your needs externally) That way once you add it to the catalog, and specify "make identical copy", you will be able to deploy multiple vApp with the exact same configuration for your developers, and they will just need to know the "external public IP" of their VMs (in case you are using IP translation) or the vShield Edge public IP (in the case you used NAT Port forwarding rules for Oracle / App for example). Hope this helps,