I registered the blueprint with short description: https://blueprints.launchpad.net/fuel/+spec/reliable-disk-naming
Let's implement it in 5.0 release and document just https://bugs.launchpad.net/fuel/+bug/1263648 in 4.1 Release Docs. On Fri, Feb 14, 2014 at 1:24 AM, Vladimir Kozhukalov < [email protected]> wrote: > https://bugs.launchpad.net/fuel/+bug/1277151 and > https://bugs.launchpad.net/fuel/+bug/1271549 are actually the same bug. > They are fixed with these two patch sets > https://review.openstack.org/#/c/71885/ and > https://review.openstack.org/#/c/71836/. > > This issue https://bugs.launchpad.net/fuel/+bug/1263648 is completely > another. It is connected with the fact, that PATH_ID variable is not always > unique. Udev just rewrites former by-path links with newer ones. This issue > is not critical at the moment but it can be if we do some kind of disk > reconfiguration in the future. We still need reliable scheme of naming hard > drives throughout the range of various kernels. > > Vladimir Kozhukalov > > > On Thu, Feb 13, 2014 at 3:45 AM, Dmitry Borodaenko < > [email protected]> wrote: > >> On Wed, Feb 12, 2014 at 7:41 AM, Vladimir Kuklin <[email protected]> >> wrote: >> > Vladimir, >> > >> > Please clarify current status for these bugs: >> > >> > https://bugs.launchpad.net/fuel/+bug/1271549 >> > https://bugs.launchpad.net/fuel/+bug/1277151 >> > https://bugs.launchpad.net/fuel/+bug/1263648 >> > >> > >> > >> > AFAIU, https://bugs.launchpad.net/fuel/+bug/1277151 is the main bug and >> > there are change requests >> > >> > https://review.openstack.org/#/c/71836/ and >> > https://review.openstack.org/#/c/71885/ >> > >> > waiting for it. The main problem is that it breaks kvm-based tests as we >> > need to patch devops correspondingly. >> >> The change requests above are designed to fall back to by-path >> specifically to remain compatible with kvm virtio devices. I've done a >> test deployment in a devops-driven kvm based test environment with >> both patches applied and it worked fine. I've approved both patches >> and they are now merged to fuel-web and fuel-library master branches. >> >> > Bug https://bugs.launchpad.net/fuel/+bug/1263648 should be fixed by >> writing >> > patch for nailgun-agent which uses block device id before it falls back >> to >> > by-path or </dev/sda|/dev/sdb> definition. >> > >> > Bug https://bugs.launchpad.net/fuel/+bug/1271549 is duplicate of the >> main >> > bug. >> >> I think it's the other way around: #1263648 is the duplicate, and >> #1271549 is a similar bug that may be fixed by the above two change >> requests. >> >> > Thus, we need to only merge the patches for the main bug, fix devops >> library >> > for our tests and fix nailgun agent for Ubuntu. Then we can write better >> > methods of disks naming for 5.0 release. Please, correct me if I am >> wrong: >> >> With the above fixes merged, I think our disk device identification >> should now be reliable enough, is there a plan for further changes in >> 5.0? >> >> -- >> Dmitry Borodaenko >> > > -- Yours Faithfully, Vladimir Kuklin, Senior Deployment Engineer, Mirantis, Inc. +7 (495) 640-49-04 +7 (926) 702-39-68 Skype kuklinvv 45bk3, Vorontsovskaya Str. Moscow, Russia, www.mirantis.com <http://www.mirantis.ru/> www.mirantis.ru [email protected]
-- Mailing list: https://launchpad.net/~fuel-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~fuel-dev More help : https://help.launchpad.net/ListHelp
