Allow Provisioning of Specific Metal Server Plan Versions
under review
Damian Sieczkowski
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.
R
Ravinder Braich
M
Miles Thomas
under review
Pedro Amoedo
+1, I'm currently suffering this problem with "c3.medium.x86" in DA metro, I have some static configuration that relies on hardcoded interfaces names (ens3f0,ens3f1), however there are some v1 instances still running there that have a different chassis that present different interface names (enp1s0f0,enp1s0f1).