Include the User-Agent in the Timeline
When reviewing the list of events, the user, action, and time are listed. I would also like to know how the event was triggered (User Agent). This can tell me, for example, if the action was performed by one of my users in the Portal (via a browser) or if a third-party integration was used, such as Terraform, Rancher, or ClusterAPI. Managed provisioners, such as Rancher or ClusterAPI, or CI/CD triggered provisioners, like Metal CLI and Terraform, can go unnoticed. When automation is running smoothly and a manual change or deletion was made via the portal, I'd also like to understand that and see it reflected in the portal. The User-Agent will tell me this. Reporting the UserAgent (or some aggregate of that) would help in identifying how my resources are being acted upon.
Expose minor revisions of hardware plan via Metadata
An Equinix Metal "c3.medium.x86" can come in a couple of different form factors depending on luck at time of provision. Internally these different form factors are identified by a minor revision number, that is currently NOT exposed to the outside of the platform. Some of those revisions can introduce consequential changes to a customers ability to consume the service. Different drive types that will get named differently by the host OS, different NICs with different layouts etc. Without providing customers a way of keying of this information, it can present a significant challenge to customers trying to build auto-mateable / repeateable deployment patterns on Metal. We should expose the minor rev of the instance in Metadata, including the unathenticated metadata service. This would provide customers with a place to pivot instead of having to screen scrape the world and rebuild in it on-demand every time they want to in stall an OS.
Meraki vMX on Network Edge
Enable customers to order Cisco Meraki vMX on Network Edge Marketplace
Custom BIOS Management
Customers would like to have additional visibility and management capabilities of BIOS-enabled features, e.g SR-IOV, SGX, etc. Ideally a customer should be able to manage their BIOS settings through the API, Customer Console, or metadata service.
In Portal Storage Appliance Quoting and Reservation Workflow
There should be a specific in portal workflow created that allows me to select, quote, reserve, or initiate a sales led conversation for the consumption of a storage appliance from any integrated, available vendors. Indicating specifics related to availability of any pre-stocked hardware for rapid delivery would be a great value added feature to this mechanism.
A10 on Network Edge Marketplace
Enable customers to order A10 devices on Network Edge Marketplace
Juniper 128T SDWAN on Network Edge
Enable customers to order Juniper 128T SDWAN on Network Edge Marketplace
Support Key Switching in Metal SOS for ESXI
Refering VMware KB, when accesing to ESXi you can switch between DCUI/Console using [ALT+F1] key. https://kb.vmware.com/s/article/2148363?lang=en_us But in out-of-band console metal access to ESXi, it seems the keys don't work and only DCUI can be used. Of course SSH connection can be used instead under normal conditions, but I assume their are possible situations in which SSH connection cannot be established, such as switch failure on the upper level of the Metal server, or incorrect NW settings put into the ESXi. In those cases out-of-band console operations are needed to check status and operate virtual machines, or recover Network. Therefore it will be good if there is a way to execute console operations out-of-band in ESXi.