LACP for crossconnects
Support the ability for customers to create LACP bonds for cross connect ports into Metal. Currently cross connects require unique vlans per port which can in many cases require customers to run routing protocols for high availability (eg BGP). Enabling LACP would allow customers to run high-performance physical firewalls and storage in Colo in front of metal instances in HA.
Support for true Multicast
Enable IGMP snooping so that we can do true Multicast between servers on Layer2 VLANs.
Ability to have an Internet gateway and enable private IP space or VLANs to access the Internet through a default route.
Preconfigured dedicated ports in each IBX
Currently, the process can take more than 2 weeks after placing an order for dedicated ports and requires a lot of coordination with multiple teams. The same process repeats every time a new customer orders the port. By having preconfigured dedicated ports which are already patched, customer can right away order and start using the service.
Allow private 10.x.x.x networking traffic between Projects
It would be great to have the option of allowing server instances in different projects to communicate over the private 10.x.x.x network.
Allow Z-Side to Z-Side Fabric Connectivity
Currently, only an A-side can initiate connections to a Z-side on Fabric. Which means that if a Metal customer wants to connect to another Z-side, they either need to get a dedicated port or use a Network Edge device to act as an A-Side.
Customers would like to have the ability to request a server with SR-IOV enabled, either as a option to toggle on reboot or for a new installation.
Private Cloud Layer 2 Networking for VCF
To meet the needs of VMware VCF and VMware 7 automation, a solution to deliver the same VLAN on unbonded individual links is required. VMWare handles the HA for the network after the deploy is complete. We have worked with VMware engineering and there is no practical way to deploy VCF without this feature. https://docs.vmware.com/en/VMware-Cloud-Foundation/4.1/vcf-41-ovdeploy-guide.pdf