Usability

Users should have an option to submit a request for their On-Demand instances to be converted to Reservations. This would be enabled via the Self-Service Reservations feature in the Metal Customer Console.

Currently, instance types must be defined as "on-demand" or "reservation" at build time and built through different workflows. If you try to build a reserved instance and no reservations are available, the build just fails. Would like to see a single workflow where if a server reservation is available, the instance deploys to that reservation. Perhaps something like a tag in the on-demand workflow such as "use_avail_reservation: true"? Where false (default) will act as it currently does and true will check for available reservations before building an on-demand instance and false will just build the on-demand instance without checking for reservations? and/or possibly the reverse scenario for the reservation workflow with a tag like "ondemand_allowed: true" Where again false (default) will act as it currently does and when true, instead of failing when no reservations are available, the workflow will auto-switch over to use an ondemand instance type. Though this 2nd option is understandably "riskier" from a business perspective as a customer might think they're building a reserved instance and get an on-demand one at a higher bill rate instead.

Hi, an idea that came into my mind. Some other places do this as well. If one was to make a tutorial of the service, a how-to on the wiki and/or a blog post, then the creator can receive a reward of some kind.

Lack of management features in Ansible collection ("metal") developed by Equinix. As a consequence, administrators must make extensive use of API calls (Ansible "uri" module) in their playbooks

The cost summary in the GUI when choosing a node and configuring it with OS doesn't currently include the OS licensing fee if chosen.

The only ways to provide iPXE scripts currently are the following: 1 - iPXE script URL The downside to this is that the endpoint hosting the iPXE script must be public. This does not work for users that want to host the iPXE script somewhere private. 2 - Userdata This works great and allows private deployments but the issue is when users want to also pass userdata content such as cloud config or bash scripts. A third option should be available that lets the user provide the iPXE script content in base64 encoding similar to how it is done with the userdata method. This would be something like the following: “ipxe_script” : “base64encodedipxecontentstring” This would allow users to use private scripts and also freely use the userdata option for other automation scripts.

Current reserved server search functionality is unintuitive. Searching by a project name or server type returns unexpected results. We should be able to search by hostname, server type, and/or project name.

MTCS certification for Equinix Metal for Singapore customers since this is a market requirement. https://en.m.wikipedia.org/wiki/SS584

Customers should have a screen in the Customer Console where they can create, view, and manage their existing and historical support tickets. This is currently managed out of our chat service and emails for customers which can be complicated to use and does not provide a historical reference for tickets that have been closed.

Support for a non-human user account to be used for authentication to the Metal API