This idea was imported from Canny. Originally created by: Sal Carrasco. The current owner is: Sal Carrasco.
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.
This comment was imported from Canny. Originally created by: Sal Carrasco with 0 likes.
We've received a variety of requests to allow customers to manage different BIOS settings. The goal is to create a feature that allows customers to manage as many of their BIOS settings as possible through the API, Customer Console, or metadata service. Stay tuned.
This comment was imported from Canny. Originally created by: Jacob Smith with 0 likes.
Ed Warnicke: Sorry for the long delay - n3.xlarge is now enabled with SR-IOV by default. Small step for mankind!
This comment was imported from Canny. Originally created by: Jacob Smith with 0 likes.
We've enabled SR-IOV by default on all n3.xlarge servers, and adjusted this feature request to improve how users can programmatically understand which servers in our fleet support this (and other similar) feature. https://feedback.equinixmetal.com/changelog/sr-iov-enabled-by-default-on-n3xlarge-servers
This comment was imported from Canny. Originally created by: Matti Paksula with 0 likes.
related https://github.com/ayeks/SGX-hardware/issues/91
This comment was imported from Canny. Originally created by: Neil Vexler with 0 likes.
Bumping an old post. Are there any updates on this?
This comment was imported from Canny. Originally created by: Haridev Cheviry with 1 likes.
Equinix team, When can we expect this feature ?
This comment was imported from Canny. Originally created by: Pedro Amoedo with 0 likes.
For example, having an option to enable TPM modules during provisioning would be great in order to automate disk encryption, it's present but disabled by default on the PowerEdge servers. Best Regards.
This comment was imported from Canny. Originally created by: Taylor Carpenter with 2 likes.
There are some examples and use cases in CNCF's CNF Testbed and the Network Service Mesh (NSM) project that we would like to use in the Equinox Metal (EM) provided CNCF community. Having a way to programmatically select nodes with SR-IOV enabled will make it easier for development+testing as well as letting other folks try those examples in EM w/o using reserved instances. Reference: - https://github.com/networkservicemesh/deployments-k8s/tree/main/examples/use-cases/SriovKernel2Noop - https://github.com/networkservicemesh/deployments-k8s/tree/main/examples/use-cases/SriovKernel2Noop - https://github.com/cncf/cnf-testbed/tree/master/examples/use_case/sriov-device-on-k8s-on-packet - https://github.com/networkservicemesh/sdk-sriov
This comment was imported from Canny. Originally created by: Ed Warnicke with 5 likes.
I second this request. It would be incredibly useful to simply have SRIOV available without having to jump through hoops with reserve instances. This is doubly true when wanting to provide 'kick the tire' instructions to potential adopters...
This comment was imported from Canny. Originally created by: Sean Larimore with 0 likes.
I would also like to request that the NIC information is available via API
This comment was imported from Canny. Originally created by: Paul Teich with 0 likes.
Working on enabling this in 2q2021, first step is "collect firmware & bios features on deprov" bet
This comment was imported from Canny. Originally created by: Holger Winkelmann with 0 likes.
Adam Rothschild: In our experience it should not hurt a long you not slice the NIC it is just as normal. But I have not seen 100s of cases yet ;-)
This comment was imported from Canny. Originally created by: Holger Winkelmann with 1 likes.
yeah, and this should be somehow knwon to the meta data so thats i.e. k8s deployments like sr-iov operator can interact with that
This comment was imported from Canny. Originally created by: Rain Leander with 0 likes.
Where are we on this one?
This comment was imported from Canny. Originally created by: Adam Rothschild with 1 likes.
is there any downside to just enabling this on all supporting cards (as opposed to a toggle)? might be our easiest option...