Any basic working implementation would be good for start.
Not sure about multiple namespaces - personally I don't think it's needed for first version.
Also, make sure you don't forget there is related bug in linux kernel which gives different device names to namespaces between reboots so /dev/nvme0n1 migth on next reboot be called /dev/nvme1n1
Wish I could add nvme.multipath=0 kernel parameter to maas to use forever but - centos breaks with this parameter.
Any basic working implementation would be good for start.
Not sure about multiple namespaces - personally I don't think it's needed for first version.
Also, make sure you don't forget there is related bug in linux kernel which gives different device names to namespaces between reboots so /dev/nvme0n1 migth on next reboot be called /dev/nvme1n1
Wish I could add nvme.multipath=0 kernel parameter to maas to use forever but - centos breaks with this parameter.
Related references: /github. com/linux- nvme/nvme- cli/issues/ 455 /bugs.launchpad .net/ubuntu- power-systems/ +bug/1778844/ comments/ 35 ubuntu. 5.x6.nabble. com/About- nvme-char- block-naming- mismatch- td5186325. html /bugs.launchpad .net/curtin/ +bug/1830913
https:/
https:/
http://
https:/