Organizations must consider numerous hardware and software requirements before deploying VMware vCloud Connector. The requirements for vCC 2.7.2 include a variety of component and configuration prerequisites, such as processors, memory and network controllers.
Admins install vCloud Connector (vCC) as a plug-in under the vSphere client, so any host system capable of running vSphere and using Internet Explorer can also support vCC. Administrators looking for specific hardware can locate systems using VMware's list of ESXi-supported servers in the VMware Compatibility Guide.
Software and hardware requirements
VCC also carries several software requirements depending on how an organization deploys it. When vCC is deployed on vSphere, organizations require vSphere 4.0 update 3 or later. If an organization wants to use the vCC's "stretch deploy" capability on vSphere, it must use vSphere 5.1 or later. If vCC is deployed on vCloud Director, organizations require vCloud Director 5.1 or later. To use the stretch deploy capability on vCloud Director, organizations require vShield Manager 5.1.2 or later.
Remember that vCC requires several ports to be available. For example, SSL communication between vCC components requires port 443 -- although port 80 enables non-SSL communication between nodes. Port 8190 must be open on destination vCC components for user-defined type data transfers, such as when transferring data between a private cloud and public cloud. Admins must use port 5480 for administrative web consoles on vCC components. Security admins should review the port requirements and ensure that the necessary ports are available.
Always be certain to review the complete documentation for the latest available version of vCC to ensure that a data center meets all current hardware and software requirements.
VMware vCC availability and pricing
VCC 2.6 is available free of charge, and admins can download a vCC 2.7.2 server and node virtual appliances directly from VMware.
Version 2.7.2 is a security update intended to harden the kernel and address a stack-based buffer overflow vulnerability. Version 2.7.2 updates 2.7.1 with no change in functionality. Admins can easily update by deploying new open virtualization format templates and then changing the vCC Server and vCC Node registrations with the vSphere client -- essentially pointing vSphere to the newer virtual appliances.
Virtual appliances come in .zip format; they're large files at almost 1.5 GB for the vCC Server file and nearly 900 MB for the vCC Node file. Plan appropriately for download time and storage. VCC users can also access release notes, documentation and knowledge base articles through the download page.
Dig Deeper on VMware cloud
Related Q&A from Stephen J. Bigelow
Fog computing vs. edge computing -- while many IT professionals use the terms synonymously, others make subtle but important distinctions between ... Continue Reading
Learn how load balancing in the cloud differs from a traditional network traffic distribution, and explore services available from AWS, Google and ... Continue Reading
Access management is critical to securing the cloud. Understand the differences between AWS IAM roles and users to properly restrict access to AWS ... Continue Reading