First of all, I appreciate all of your help. Thanks! I'm a bit of a gumbie on the networking stuff, and new to the vmware world as well.
2. Isolated Org Network
You basically "make up" a network. This will not have external access ... if you attach a VM to this network, it can communicate with any other VM on this exact network.
I understand the isolated network concept pretty well. How is the IP allocation handled? I guess you can probably assign them yourselves, or install a dhcp service?
3. Routed Org Network
it's like #2, but with a vShield Gateway that would be created. This vShield edge would perform the functions of your "default gateway". Think of this as a large private network, or a massive N:1 NAT.
If you just want to give a bunch of people internet access, you can put VMs on here and make a Firewall rule to allow all outbound traffic and put it through a single IP (which would come from your external network).
RE: 1 - this is a value inside the network you are defining. let's say we want our gateway to be 10.150.10.1 on a /23 ... when you create the network the gateway will have an internal IP of 10-.150.10.1
So, I can define the subnet address and the gateway specific IP however I like. I guess one of the reserved private subnet spaces are typical?
RE: 2 - this is just a range to assign out to VMs put onto the network. say 10.150.10.100 - 10.150.254. These will become IPs which vCloud will delegate to a VM's NIC card as they are created.
So the vCloud will handle IP config for me? If I choose not to specify a range, can the vCloud just use all of the ones from the subnet?