Ecosystem Support

Hypervisor Support

  • Amazon Web Services (AWS)
  • Google Cloud Platform
  • Nutanix (Linux Server Cloud)
  • OpenStack environments: KVM
  • VMware vSphere 5.5, 6.0, 6.5

Bare Metal (Linux Server Cloud)

Bare-Metal Operating Systems

  • Bare metal hosts running OEL7.0, 7.1, 7.2, 7.3, 7.4, RHEL7.0, 7.1, 7.2, 7.3, CentOS 7.0, 7.1, 7.2, 7.3, Ubuntu 14.04, 16.04
  • Bare metal hosts running these kernels:

Supported Linux kernels

Bare-Metal NICs

  • For non-DPDK mode, Avi supports any server NIC.
  • For DPDK mode (recommended), Avi Networks has qualified:
    • Intel NICs
      • 82599, X520, X540, X550, X552, X710, and XL710 — all 17.1.x releases

Orchestrator Support

  • Kubernetes 1.3+
  • Marathon 0.13.x, 0.14.x, 0.15.0, 0.15.1, 0.15.2, and 0.15.3
  • Mesos 0.23.0, 0.23.1, 0.24.0, 0.24.1, 0.25.0, 0.26.0, 0.27.0, and 0.27.1
  • Mesosphere DC/OS 1.6, 1.7, 1.8, 1.9, 1.10
  • OpenShift v3
  • OpenStack Version Support:
    • Havana, Icehouse, Juno, Kilo, Liberty, Mitaka, Newton, Ocata, Pike
      Note: Avi Vantage does not support Neutron DVR mode.
    • LBaaS v1 and v2. Avi LBaaS driver (required only for OpenStack-managed LBaaS mode) must match the Avi Controller version, not less than 16.3
    • Keystone v2 and v3 (Avi Vantage 16.3 or higher required for Keystone v3)
    • Support for Keystone v3 in Avi Heat resources.
    • Avi SSL extension for OpenStack Horizon required only for OpenStack-managed LBaaS mode, adds tabs to Horizon for accessing Avi Controller (16.3 or higher)
    • Neutron extension for allowed-address-pair
      • Community Distribution: Supported from Havana onwards
      • VSP Version 3.1 or higher
      • Contrail: Version 3.0.2 or higher
      • OpenContrail
  • VMware vCenter 5.5, 6.0, 6.5, vRO and vRA

SDN Solutions

  • Cisco APIC Version 1.03(f) and later
  • Juniper Contrail v3.0.2 and later (only for OpenStack)
  • Nuage v3.1 and later (only for OpenStack)
  • VMware NSX 6.2.4+

IPAM /DNS

  • Avi DNS
  • AWS Route 53
  • Infoblox

Avi Vantage may be deployed in various environments with write (recommended), read, or no access integration with the virtualization orchestrator. The primary difference among these modes is the level of automation performed by Avi Vantage and the cloud orchestrator compared to the level of manual configuration required of administrators. There are no differences in hardware or system requirements among these modes. Servers being load balanced by Avi Vantage may exist within the same virtualization environment or be bare-metal, non-virtualized servers.

Avi supports the ability to manage multiple cloud environments from a single Controller cluster.