EDIT: Updated for EHC 4.1.2
Architecting large scale cloud solutions using VMware products have several maximums and limits when it comes to scalability of the different components. People tend to look at only vSphere limits, but the cloud also has several other systems with different kind of limits to consider. In addition to vSphere, we have limits with NSX, vRO, vRA, vROps and the underlying storage. Even some of the management packs for vROps have limitations that can affect large scale clouds. Taking everything into consideration requires quite a lot of tech manual surfing to get all the limitations together. Let’s inspect a maxed out EHC 4.1.2 configuration and see where the limitations are.
This week we ran into an interesting problem during a Federation Enterprise Hybrid Cloud implementation. We had the solution implemented with VMware vRealize Automation 6.2, and everything was running smoothly. The vRA implementation was done as a distributed install, so after configuration we moved to do some vRA component failover testing. We succeeded in failing over the primary component to secondary component on all of the different VMs (vRA appliance, IaaS Web, IaaS Model Manager + IaaS DEM-O, IaaS DEM-Workers and IaaS DEM-Agents), but failback was not successful. After diving into the component logs, we found a distinctive error on almost all of them:
System.Configuration.ConfigurationErrorsException: Error creating the Web Proxy specified in the 'system.net/defaultProxy' configuration section
My blog has been a bit quiet lately, mostly due to my change of job and scenery. I took the opportunity to join EMC Enterprise Hybrid Cloud team as a Senior Solutions Architect to be part of the first deployments and more importantly to participate in the development of the product. 2015 will be a big year for EMC EHC, a lot of things will be happening. Currently, EHC is a product that combines EMC and VMware (aka Federation) products to form a solid hybrid cloud base for our customers. There is still a lot of debate where you should run your application, cloud or private. The answer always depends on the application and the customer. We at EMC strongly believe that the future is hybrid.
EHC is at version 2.5.1, which will bring our customers an infrastructure capable of running IT as a Service. EMC has put a lot of effort and time to take away the burden of developing automation and orchestration processes from the customer. We automate the basic operations task like application backup and application deployment and give the customer time to concentrate on the bigger picture. I know it is a cliché, but cloud is a journey. We have been saying that for years, and it is even more true now that it was back in 2010. With EHC we bring you a platform to start that journey strong. There is no way that you can have a public cloud -like flexibility and automation overnight in a private cloud environment, no matter how much money you throw at it. The technology is relatively easy, it’s the transformation of process, people and business that will be the hard part. We are here to help you with both parts.