December has always been a time where I upgrade the VMware ASEAN lab. The lab has been a critical tool in my roles as an SE. We use it to learn products, see how they fit together, do demo, and do POC.
We’ve been working to upgrade the lab. Folks like Rayne and Iskandar have been great in tidying up all the cables. Now that the physical layer is taken care off, we are now ready to work on the software layer.
When we architect-ed the lab, I wanted to make sure we did not miss anything. I find that thinking in terms of layers help me to ensure nothing is missed. The first diagram shows the components by layer.
Now that I have everything, I need to think in terms of their relationships. I know a lot of things are connected and dependant on vCenter. So I created the diagram below. In this diagram, I also add that there are 2 layers of network, as there are VMs that will be in the virtual network. NSX will be used to separate them from the physical network.
Now, the above is good, but does not show the fact that I need to have Production DC and DR DC. SRM also requires 2 vCenter Servers. So I created the diagram below to show it. I had to simplify some connections, such as SSO and AD, as practically all VMs talk to them. I’m excluding EUC (Horizon, Mirage, Air Watch) as it’s separately managed by our EUC SE.
The next thing is to map them into the physical ESXi and storage that I have. We have limited hardware, so there will be adjustment. For example, EUC and SDDC are sharing vCenter. It is certainly not ideal, but it gives us real experience on what happens when you combine solutions that are best separated.
My plan is to use SRM to protect vRealize Suite. Perhaps not all components due to limited hardware.
The next diagram shows the physical mapping in more details. I’ve listed the datastores this time around. I’m also showing that there is 1 SSO, as it’s more practical this way. I find that being able to manage across vCenter to be useful.
Hope you find it useful. Feel free to replicate it. There is a lot more technical information, as I document most of them in Google Site.