Lab feature for subsidized testing, exploration and learning
Users want to access Equinix Metal for trials, learning, demos, testing, and general exploration but without the high cost of "big iron" production gear. Smaller bite-sized config Subsidized if possible Reduced SLA and other considerations (e.g. bandwidth limitations) Technical support and content focused on users, not companies Basically a really cool homelab, but sitting at Equinix and paired with all the cool platform features, automation, and advanced networking features.
Provide a feature that gives users the ability to view and manage server component and firmware versions through both the API and Metal Console. Specifically, users will be able to view the current firmware version of each server component through the API and the Customer Portal, giving them greater visibility and control over their systems. In addition, users should be able to update the firmware version of each server component through the API and the Metal Console, simplifying the process of managing and maintaining system firmware. This will allow users to quickly and easily update their firmware versions to the latest available release, ensuring that their systems are secure and up-to-date.
Instance State in Metadata API
It would be useful if the Metadata API for an instance could return the running state for that instance as part of it's response. As in if I am a Metal instance, I want to be able to get "state": "powered_on" or "state": "provisioning" from my Metadata API. This would let automation pivot based on the platform state of the box, as in "If I am still in provisioning state in the Metal platform, wait until state is powered_on before performing proceeding. Exposing it through metadata dramatically simplifies the act of getting the answer needed as opposed to querying it via the public API
Pre-stock and or preprovision storage appliance options
To provide faster time to value, prestock or pre-enroll storage appliances in metal metros
Provide more Metro location options when provisioning instances
Allow the ability to pass several Metro locations in order of importance or "any" when provisioning an instance with "metro". This would work similar to "facilities" where you can pass an array of facilities and the API will choose the location in order of importance/capacity levels. Users can also pass "any" for more general tasks that aren't latency sensitive.
Meraki vMX on Network Edge
Enable customers to order Cisco Meraki vMX on Network Edge Marketplace
Support for SAP HCL for Standard Metal Instances
Support validation and listing on the SAP HCL for select Metal instance models: https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN/#/solutions?filters=iaas This would enable workloads including SAP HANA and NetWeaver.
Allow Provisioning of Specific Metal Server Plan Versions
Often times, a Metal server has multiple versions that aren't publicly exposed. These cane be minor alterations between plan versions and in some cases, e.g. the c3.small, may be on an entirely different platform from server to server. This causes unexpected, and sometimes breaking behavior, for someone deploying servers on-demand. We should add capability to the Metal API that allows specifying a particular plan version during device provision.