Adding TripleO as one of the projects affected because we will need to fix it in the find_disk() function of the DIB tool.
Right now the DIB tool look at the disk= kernel parameter which is passed by Ironic to find the disk, and it relies on the disk names. I think that DIB should just try to find a suitable disk, and not rely on any names.
Adding TripleO as one of the projects affected because we will need to fix it in the find_disk() function of the DIB tool.
Right now the DIB tool look at the disk= kernel parameter which is passed by Ironic to find the disk, and it relies on the disk names. I think that DIB should just try to find a suitable disk, and not rely on any names.
It's important to note that Ironic will offer a way to pass hints to the deploy ramdisk in order to make it pick the right disk (if required), and that's explainded in more details in the spec merged in Ironic which is here http:// specs.openstack .org/openstack/ ironic- specs/specs/ kilo/root- device- hints.html