The VeloCloud Gateway runs on a standard hypervisor (KVM or VMware ESXi).
Minimum Server Requirements
To run the hypervisor:
- 10 Intel CPU's at 2.0 Ghz or higher. The CPU must support the AES-NI, SSSE3, SSE4 and RDTSC instruction sets.
- 20+ GB (16 GB is required for VC Gateway VM memory)
- 100 GB magnetic or SSD based, persistent disk volume
- 2 x 1 Gbps (or higher) network interface. The physical NIC card should use the Intel 82599/82599ES chipset (for SR-IOV & DPDK support).
Reference Hardware Specifications:
|NIC card with 82599/82599ES chipset||https://www.hpe.com/h20195/v2/GetPDF.aspx/c04111506.pdf|
Supported Hypervisor Versions
|VMware||ESXi 5.5U3 or later. In order to use SR-IOV, the vCenter and the vSphere Enterprise Plus license are required.|
|KVM||Ubuntu 14.04 LTS and 16.04 LTS|
VCG Virtual Hardware Specification
For VMware, the OVA already specifies the minimum virtual hardware specification. For KVM, an example XML file will be provided. The minimum virtual hardware specifications are:
- 8 vCPUs
- 8 GB of memory
- Minimum of 2 vNICs:
- One vNIC is the public (outside) interface, which must be an untagged interface.
- One vNIC is the private (inside) interface that must be tagged. This is the interface facing the PE router or L3 switch.
- Optional vNIC (if a separate management/OAM interface is required)
- 32 GB of virtual disk
- The firewall needs to allow outbound traffic from the VeloCloud Gateway to TCP/443 (for communication with VeloCloud Orchestrator).
- The firewall needs to allow inbound traffic from the Internet to UDP/2426 (VCMP), UDP/4500, and UDP/500. If NAT is not used, then the firewall needs to also allow IP/50 (ESP).
- If NAT is used, the above ports must be translated to an externally reachable IP address. Both the 1:1 NAT and port translations are supported.
Git Repository with Templates and Samples
The following Git repository contains templates and samples.
git clone https://bitbucket.org/velocloud/deployment.git