{"id":3054,"date":"2013-03-01T12:42:30","date_gmt":"2013-03-01T17:42:30","guid":{"rendered":"http:\/\/chriscolotti.us\/?p=3054"},"modified":"2014-08-22T14:06:53","modified_gmt":"2014-08-22T18:06:53","slug":"vcloud-director-hybrid-cloud-design-case-study","status":"publish","type":"post","link":"https:\/\/chriscolotti.us\/vmware\/vcloud-director-hybrid-cloud-design-case-study\/","title":{"rendered":"vCloud Director Hybrid Cloud Design Case Study"},"content":{"rendered":"
So all week I have been posting tidbits about the vCloud Director Hybrid cloud<\/a> I have been building. \u00a0So what was my purpose for doing so? \u00a0Well I did it to make a couple of points of course the following is the final outcome formed into a bit of a case study that you can digest for a while. \u00a0The main reason I did this is that I feel we are still\u00a0struggling\u00a0with how to CONSUME the hybrid cloud model. \u00a0 We’ve spent a lot of time architecting the vCloud Director implementations in both the public and private cloud space. \u00a0I decided I wanted to take a look at this from the consumer’s point of view. \u00a0Those people who would be wanting to come to those of you that are vCloud Director providers and help them understand HOW to use these public clouds.<\/p>\n So who are these consumers and users I am speaking about trying to help? \u00a0It can be any one of us but for the purpose of this case study I want to take two specific examples that fit many possible situations out there.<\/p>\n In both cases the need is simple. \u00a0They both need to find new\u00a0infrastructure\u00a0without having to build it themselves. \u00a0In the case of both I am actually focussing on them not building more themselves, but rather leveraging the vCloud Providers out there. \u00a0They could consume in either a public cloud fashion, or a hosted private cloud fashion. \u00a0For purposes of this study let’s assume they have decided to go to public cloud providers. \u00a0I will play the role of the consumer as we continue forward. \u00a0I will also be taking the aspect of the second\u00a0scenario\u00a0above. \u00a0I have a datacenter, that’s met its limits of compute, memory, and storage.<\/p>\n To be clear I am not suggesting where you go, but for my purposes here I happened to already have resources at two vCloud Public providers running vCloud Director 5.1 so I decided I was going to split my\u00a0Infrastructure\u00a0as a service (IaaS) between the two for some level of redundancy. \u00a0Also I personally think that makes you a smart IT person leveraging two different providers. \u00a0For my scenario as we know I have been using:<\/p>\n Obviously\u00a0you can choose whomever you want, but in this case we are focussing on providers that are using vCloud Director 5.1 for it’s flexibility and simplicity to build your new\u00a0organization\u00a0 \u00a0Once I have decided on the providers I am going to use the next steps are fairly simple and frankly are no different than you would do if you were building a physical datacenter, except now we are doing a Software Defined Datacenter, (SDDC).<\/p>\n Like any new datacenter you need to get the basic things configured. \u00a0As I have shown in previous posts, vCloud Director 5.1 provides a lot of power to the organization administrator….YOU. \u00a0The first order of business in my mind is the networking. \u00a0You want to design this separately for each site as you would for a new physical site. \u00a0Most all your traffic will leverage the Edge Gateway as well.<\/p>\n Once you have gotten this figure out in your design of the two remote datacenters you can move forward. \u00a0It goes without saying you don’t want to cross networking subnets between sites or VPN will not work. \u00a0At this point you will also want to establish VPN connectivity between the sites<\/a> and write the basic firewall rules for traffic to pass as you wish. \u00a0This will be important as you begin to stand up your\u00a0infrastructure\u00a0as a service.<\/p>\n Here you can basically download and import the vCloud Connector Nodes into your two Public Clouds. \u00a0However, some providers are now building Multi-Tenant\u00a0Nodes that you can simply leverage based on vCloud Connector 2.0. \u00a0If this is the case you only need to build your vCloud Connector Server hosted<\/a> in one of your clouds, but maybe you want one in both.<\/p>\n Once you have this you can choose to move templates you already have in your current datacenter, or build fresh ones. \u00a0You can upload ISO images and just build new if you want to be sure things are setup fresh. \u00a0Either way you have the option so proceed as you wish. \u00a0So at this point, we have networking, templates, and site 2 site VPN\u00a0connectivity\u00a0established. \u00a0Now we just need to build out the\u00a0Infrastructure\u00a0we need to get started.<\/p>\n Like any new datacenter the first thing we probably need is localized Active Directory. \u00a0Assuming you have Active directory servers in your first datacenter you will want to make sure you setup new Sites and Services with the correct IP\u00a0ranges. \u00a0Now I am now Active Directory expert, I am just trying to at least cover the basics. \u00a0Below you can see in my scenario I have set up the three sites, and also gone ahead and installed at least one Active Directory server in each of the new sites. \u00a0This will become the local\u00a0authentication\u00a0and DNS server for any new Windows\u00a0infrastructure\u00a0in that site.<\/p>\nSetting the Stage For vCloud Director Hybrid Clouds<\/h3>\n
\n
Choosing\u00a0your Providers<\/h3>\n
\n
Build your SDDC – Start with the Networking<\/h3>\n
\n
Build your SDDC – Setup vCloud Connector, Import or Build New Templates<\/h3>\n
Build your SDDC – Active Directory<\/h3>\n