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.
Ability to have an Internet gateway and enable private IP space or VLANs to access the Internet through a default route.
Global IPv6 Anycast Support
The existing Global IPv4 Anycast feature should be replicated for IPv6. Equinix advertises a block on customers' behalf at most/all sites and carves out individual (or blocks of) addresses from within that advertisement on demand for each customer. The assigned IPv6 /56 block to each org/project/site can be used to replicate the IPv4 Public IP feature (using local BGP), however there is no dedicated Equinix provided IPv6 block for Global Anycast. A customer could bring their own IPv6 space, however since the Global IPv4 feature exists now this seems like an easy evolution to IPv6. Probably goes without saying, but Global IPv6 shouldn't cost $0.15/hr/address though.
Use Your IPs as Equinix Metal Elastic IPs
Instead of running and configuring BIRD to announce your block on Equinix Metal... users supply their ASN and IP blocks so they can be managed as an Elastic IP Address Pool. Users control where they want to attach their IPs through the portal and API, just like Equinix Metal Elastic IPs!
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.
Native VLAN support for Layer 2 Bonded networking mode
Currently it's not possible to set a VLAN as a native VLAN if you have multiple VLANs attached to a Layer 2 Bonded instance. It would be great to support native VLANs for the Layer 2 Bonded networking mode as there are certain use cases that can benefit from untagged VLAN traffic in the host.
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
Support for 802.1ad/QnQ
The ability to support double tagged or stacked tags to match Equinix Fabric network design. Some service provider use cases require the ability to operate with inner and outer tags.
Restrict Org from Public Internet Access
Certain security policy burdened customers may have a policy of restricting the use of any infrastructure service with public facing internet connectivity. More than just the optional toggle in the instance provisioning flow, these customers want to guarantee that no instance launched under a given org could ever have had ingress or egress access to the public internet, so that no "regular" permissioned user can provision an instance or service with any access to a publically routable network. * This could be accomplished by enforcing a "Do not provision with public IPs" toggle for an entire org * Could also be enforced by creating a setting for "Default VLANs" for a "Layer-2" only/by default deployment flow (does not currently exist). This would enable a customer to provision an instance into a customer managed network for the lifecycle of that instance.