)]}'
{"specs/approved/classic-drivers-future.rst":[{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"825210b28dc9d30c2cfc519adbef20822da7776b","unresolved":false,"context_lines":[{"line_number":103,"context_line":""},{"line_number":104,"context_line":"  .. note::"},{"line_number":105,"context_line":"    We decided to not provide any automatic migration on the API level in the"},{"line_number":106,"context_line":"    node create and update API."},{"line_number":107,"context_line":""},{"line_number":108,"context_line":"**Rocky**"},{"line_number":109,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"df87a7cf_76527515","line":106,"updated":"2017-12-19 15:29:43.000000000","message":"it would be good to provide the reason. (Based on TheJulia asking \u0027why\u0027 wrt certain parts of the BIOS spec :-))","commit_id":"66d8ef9bef48a20e079f881c3cdcc71405dfd06b"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"29a503b2fa18d94ff93adc8daefa58961e7f694b","unresolved":false,"context_lines":[{"line_number":103,"context_line":""},{"line_number":104,"context_line":"  .. note::"},{"line_number":105,"context_line":"    We decided to not provide any automatic migration on the API level in the"},{"line_number":106,"context_line":"    node create and update API."},{"line_number":107,"context_line":""},{"line_number":108,"context_line":"**Rocky**"},{"line_number":109,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"9f91af0f_8cba7d6b","line":106,"in_reply_to":"df87a7cf_76527515","updated":"2018-01-09 13:24:23.000000000","message":"Done","commit_id":"66d8ef9bef48a20e079f881c3cdcc71405dfd06b"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"825210b28dc9d30c2cfc519adbef20822da7776b","unresolved":false,"context_lines":[{"line_number":144,"context_line":"        \"\"\""},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"  .. note::"},{"line_number":147,"context_line":"    *network* and *vendor* interfaces are excluded, because they are already"},{"line_number":148,"context_line":"    dynamic even for classic drivers."},{"line_number":149,"context_line":""},{"line_number":150,"context_line":"  For example, for the ``agent_ipmitool`` driver:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"df87a7cf_965ff90d","line":147,"updated":"2017-12-19 15:29:43.000000000","message":"do you mean s/vendor/storage/ ? If so, I suggest adding this to L143 so people reading the code will know why :)","commit_id":"66d8ef9bef48a20e079f881c3cdcc71405dfd06b"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"29a503b2fa18d94ff93adc8daefa58961e7f694b","unresolved":false,"context_lines":[{"line_number":144,"context_line":"        \"\"\""},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"  .. note::"},{"line_number":147,"context_line":"    *network* and *vendor* interfaces are excluded, because they are already"},{"line_number":148,"context_line":"    dynamic even for classic drivers."},{"line_number":149,"context_line":""},{"line_number":150,"context_line":"  For example, for the ``agent_ipmitool`` driver:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9f91af0f_ec7d49b2","line":147,"in_reply_to":"df87a7cf_965ff90d","updated":"2018-01-09 13:24:23.000000000","message":"Done","commit_id":"66d8ef9bef48a20e079f881c3cdcc71405dfd06b"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"825210b28dc9d30c2cfc519adbef20822da7776b","unresolved":false,"context_lines":[{"line_number":171,"context_line":"* Update the ``online_data_migration`` command with a new migration:"},{"line_number":172,"context_line":""},{"line_number":173,"context_line":"  #. Load classes for all classic drivers in the ``ironic.drivers`` entrypoint"},{"line_number":174,"context_line":"     (but do not instantiated them)."},{"line_number":175,"context_line":""},{"line_number":176,"context_line":"  #. For each node using a classic driver:"},{"line_number":177,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"df87a7cf_b68a3d61","line":174,"updated":"2017-12-19 15:29:43.000000000","message":"nit s/instantiated/instantiate/","commit_id":"66d8ef9bef48a20e079f881c3cdcc71405dfd06b"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"29a503b2fa18d94ff93adc8daefa58961e7f694b","unresolved":false,"context_lines":[{"line_number":171,"context_line":"* Update the ``online_data_migration`` command with a new migration:"},{"line_number":172,"context_line":""},{"line_number":173,"context_line":"  #. Load classes for all classic drivers in the ``ironic.drivers`` entrypoint"},{"line_number":174,"context_line":"     (but do not instantiated them)."},{"line_number":175,"context_line":""},{"line_number":176,"context_line":"  #. For each node using a classic driver:"},{"line_number":177,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"9f91af0f_cc52c53b","line":174,"in_reply_to":"df87a7cf_b68a3d61","updated":"2018-01-09 13:24:23.000000000","message":"Done","commit_id":"66d8ef9bef48a20e079f881c3cdcc71405dfd06b"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"825210b28dc9d30c2cfc519adbef20822da7776b","unresolved":false,"context_lines":[{"line_number":186,"context_line":"            re-run this command after fixing the warnings to update the"},{"line_number":187,"context_line":"            skipped nodes."},{"line_number":188,"context_line":""},{"line_number":189,"context_line":"     #. Update the node record in the database."},{"line_number":190,"context_line":""},{"line_number":191,"context_line":"Alternatives"},{"line_number":192,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"df87a7cf_d6034141","line":189,"updated":"2017-12-19 15:29:43.000000000","message":"ironic-dbsync upgrade\" will prevent an upgrade to the next release, if any objects do not have the latest version [1]. So to leverage this mechanism, we\u0027ll need to add a new node version. This migration (and when saving a node) will:\n- for nodes using hw types, cause the node version to be incremented\n- for nodes using classic drivers, cause the classic driver to be converted to hw type etc and the node saved in the new version. Note that this will happen \u0027under the hood\u0027 if the node gets saved eg, via a \u0027OS BM node set\u0027 command or even when creating a node with a classic driver.\n\nIF we don\u0027t want the above behavior, we can add some other kind of check in ironic-dbsync.\n\n[1] https://github.com/openstack/ironic/blob/351677d3b83f83a5d203642c750133a58e695570/ironic/cmd/dbsync.py#L97","commit_id":"66d8ef9bef48a20e079f881c3cdcc71405dfd06b"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"29a503b2fa18d94ff93adc8daefa58961e7f694b","unresolved":false,"context_lines":[{"line_number":186,"context_line":"            re-run this command after fixing the warnings to update the"},{"line_number":187,"context_line":"            skipped nodes."},{"line_number":188,"context_line":""},{"line_number":189,"context_line":"     #. Update the node record in the database."},{"line_number":190,"context_line":""},{"line_number":191,"context_line":"Alternatives"},{"line_number":192,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9f91af0f_17175647","line":189,"in_reply_to":"df87a7cf_d6034141","updated":"2018-01-09 13:24:23.000000000","message":"This sounds interesting, but I\u0027d avoid it, because then we\u0027ll have to error out on saving nodes, if matching hardware types are not found.. I\u0027d better introduce a dbsync check.","commit_id":"66d8ef9bef48a20e079f881c3cdcc71405dfd06b"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"fdb147c17291282b6b8c625cf34caa6765f6005f","unresolved":false,"context_lines":[{"line_number":105,"context_line":"    We decided to not provide any automatic migration on the API level in the"},{"line_number":106,"context_line":"    node create and update API. Doing so would require us to maintain mapping"},{"line_number":107,"context_line":"    between classic drivers and corresponding hardware types/interfaces"},{"line_number":108,"context_line":"    foreever. It also may be confusing for operators, if, for example, the"},{"line_number":109,"context_line":"    result of the node creation request differs from the outcome."},{"line_number":110,"context_line":""},{"line_number":111,"context_line":"**Rocky**"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9f91af0f_da1eeeb9","line":108,"updated":"2018-01-09 17:00:03.000000000","message":"nit s/foreever/forever/","commit_id":"d7532ca02855f707afc556ea6bb1478627e4bec5"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"fdb147c17291282b6b8c625cf34caa6765f6005f","unresolved":false,"context_lines":[{"line_number":192,"context_line":"  nodes are using classic drivers. As the list of classic drivers will not be"},{"line_number":193,"context_line":"  available at that time (they will be removed from the tree), maintain the"},{"line_number":194,"context_line":"  list of classic driver names that used to be in tree and check nodes against"},{"line_number":195,"context_line":"  this list. Remove this check in the release after Rocky."},{"line_number":196,"context_line":""},{"line_number":197,"context_line":"Alternatives"},{"line_number":198,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9f91af0f_da2b4e92","line":195,"updated":"2018-01-09 17:00:03.000000000","message":"The alternative is to check that the driver value is one of the hardware types. Which might be faster since there are fewer of them :)","commit_id":"d7532ca02855f707afc556ea6bb1478627e4bec5"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"80dcb2575cc513362616a466486023f0e8d09738","unresolved":false,"context_lines":[{"line_number":192,"context_line":"  nodes are using classic drivers. As the list of classic drivers will not be"},{"line_number":193,"context_line":"  available at that time (they will be removed from the tree), maintain the"},{"line_number":194,"context_line":"  list of classic driver names that used to be in tree and check nodes against"},{"line_number":195,"context_line":"  this list. Remove this check in the release after Rocky."},{"line_number":196,"context_line":""},{"line_number":197,"context_line":"Alternatives"},{"line_number":198,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7f96bb07_e723d0bd","line":195,"in_reply_to":"7f96bb07_07c83c53","updated":"2018-01-10 17:51:51.000000000","message":"I did a quick search and didn\u0027t find anything definitive. my recollection from Queens PTG, was that the fast-forward was a release-by-release thing, where you\u0027d have to run, per release, dbsync upgrade, dbsync online_data_migrations.\n\nIf that assumption is wrong, we\u0027ll have to change the roling upgrades process, cuz the online_data_migrations are removed after that particular release.","commit_id":"d7532ca02855f707afc556ea6bb1478627e4bec5"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"f509d5ac438cc5b91fc34d71e62951900b63bc22","unresolved":false,"context_lines":[{"line_number":192,"context_line":"  nodes are using classic drivers. As the list of classic drivers will not be"},{"line_number":193,"context_line":"  available at that time (they will be removed from the tree), maintain the"},{"line_number":194,"context_line":"  list of classic driver names that used to be in tree and check nodes against"},{"line_number":195,"context_line":"  this list. Remove this check in the release after Rocky."},{"line_number":196,"context_line":""},{"line_number":197,"context_line":"Alternatives"},{"line_number":198,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7f96bb07_c755741f","line":195,"in_reply_to":"7f96bb07_07c83c53","updated":"2018-01-10 17:51:30.000000000","message":"Yeah, but even for fast-forward you must do all migrations. Even if people skip Rocky, they\u0027ll still run its dbsync and especially online_data_migrations.","commit_id":"d7532ca02855f707afc556ea6bb1478627e4bec5"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"d72ba424245e9f9aef6dcf7a8c61a003bd9ca80d","unresolved":false,"context_lines":[{"line_number":192,"context_line":"  nodes are using classic drivers. As the list of classic drivers will not be"},{"line_number":193,"context_line":"  available at that time (they will be removed from the tree), maintain the"},{"line_number":194,"context_line":"  list of classic driver names that used to be in tree and check nodes against"},{"line_number":195,"context_line":"  this list. Remove this check in the release after Rocky."},{"line_number":196,"context_line":""},{"line_number":197,"context_line":"Alternatives"},{"line_number":198,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7f96bb07_07c83c53","line":195,"in_reply_to":"7f96bb07_47f724f7","updated":"2018-01-10 17:37:28.000000000","message":"My interpretation of fast forward is having a juno install, and jumping to mitaka without stopping on kilo or spending the time to install kilo and get it running.","commit_id":"d7532ca02855f707afc556ea6bb1478627e4bec5"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"51fa139a8870e5beefe9c684a0b2b40cd08f1393","unresolved":false,"context_lines":[{"line_number":192,"context_line":"  nodes are using classic drivers. As the list of classic drivers will not be"},{"line_number":193,"context_line":"  available at that time (they will be removed from the tree), maintain the"},{"line_number":194,"context_line":"  list of classic driver names that used to be in tree and check nodes against"},{"line_number":195,"context_line":"  this list. Remove this check in the release after Rocky."},{"line_number":196,"context_line":""},{"line_number":197,"context_line":"Alternatives"},{"line_number":198,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7f96bb07_729a20c6","line":195,"in_reply_to":"7f96bb07_e723d0bd","updated":"2018-01-10 17:57:45.000000000","message":"Thinking a bit more about this. Given the assumption we/i\u0027ve made about how for each release, dbsync upgrade \u0026 online_data_migrations have to successfully complete, the check that is mentioned here conforms to that model.\n\nWe can revisit this if this model/assumption has to change. For now though, I think we should be consistent so as not to confuse (at least) me!","commit_id":"d7532ca02855f707afc556ea6bb1478627e4bec5"},{"author":{"_account_id":6637,"name":"Sam Betts","email":"sam@code-smash.net","username":"sambetts"},"change_message_id":"fd8465d3a329cfc5848b648ca6c81699c7f08bbc","unresolved":false,"context_lines":[{"line_number":192,"context_line":"  nodes are using classic drivers. As the list of classic drivers will not be"},{"line_number":193,"context_line":"  available at that time (they will be removed from the tree), maintain the"},{"line_number":194,"context_line":"  list of classic driver names that used to be in tree and check nodes against"},{"line_number":195,"context_line":"  this list. Remove this check in the release after Rocky."},{"line_number":196,"context_line":""},{"line_number":197,"context_line":"Alternatives"},{"line_number":198,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9f91af0f_5c2ac7da","line":195,"in_reply_to":"9f91af0f_1cc43f3f","updated":"2018-01-10 12:34:12.000000000","message":"It doesn\u0027t need to have them enabled, it can load the list like we load the list of classic drivers on line 173, and I think we\u0027re relying on the node running dbsync having all the drivers/hardware types installed for the check on L180 right? \n\nI also have concern that the check on L180 relys on running dbsync on a server that has an ironic.conf with enabled_interfaces in it.","commit_id":"d7532ca02855f707afc556ea6bb1478627e4bec5"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"8f44c846cf91be9bb65404711cdf230268028093","unresolved":false,"context_lines":[{"line_number":192,"context_line":"  nodes are using classic drivers. As the list of classic drivers will not be"},{"line_number":193,"context_line":"  available at that time (they will be removed from the tree), maintain the"},{"line_number":194,"context_line":"  list of classic driver names that used to be in tree and check nodes against"},{"line_number":195,"context_line":"  this list. Remove this check in the release after Rocky."},{"line_number":196,"context_line":""},{"line_number":197,"context_line":"Alternatives"},{"line_number":198,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7f96bb07_47f724f7","line":195,"in_reply_to":"9f91af0f_5b341bde","updated":"2018-01-10 17:22:11.000000000","message":"I could be wrong, but doesn\u0027t \u0027fast-forward\u0027 mean that they\u0027d have to update the DB per release. Eg, they\u0027d have to run dbsync upgrade for each release? If so, then this check would not be needed after Rocky cuz they would have had to run successfully the rock version of \u0027ironic-dbsync upgrade\u0027.","commit_id":"d7532ca02855f707afc556ea6bb1478627e4bec5"},{"author":{"_account_id":6637,"name":"Sam Betts","email":"sam@code-smash.net","username":"sambetts"},"change_message_id":"c41da1dfb16dab6a4099fb2e95702af4bce10d42","unresolved":false,"context_lines":[{"line_number":192,"context_line":"  nodes are using classic drivers. As the list of classic drivers will not be"},{"line_number":193,"context_line":"  available at that time (they will be removed from the tree), maintain the"},{"line_number":194,"context_line":"  list of classic driver names that used to be in tree and check nodes against"},{"line_number":195,"context_line":"  this list. Remove this check in the release after Rocky."},{"line_number":196,"context_line":""},{"line_number":197,"context_line":"Alternatives"},{"line_number":198,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9f91af0f_9c55affc","line":195,"in_reply_to":"9f91af0f_5b341bde","updated":"2018-01-10 11:51:22.000000000","message":"I don\u0027t see a requirement to remove the check either. In fact it might be pretty good to maintain a check in the migration that all nodes are configured to a hardware type that is available in the next release, so if the case when a hardware type was removed in a later release occurs, it should catch that too right?","commit_id":"d7532ca02855f707afc556ea6bb1478627e4bec5"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"e7912f308a207ad1e577c3d94d2698476ac4b22f","unresolved":false,"context_lines":[{"line_number":192,"context_line":"  nodes are using classic drivers. As the list of classic drivers will not be"},{"line_number":193,"context_line":"  available at that time (they will be removed from the tree), maintain the"},{"line_number":194,"context_line":"  list of classic driver names that used to be in tree and check nodes against"},{"line_number":195,"context_line":"  this list. Remove this check in the release after Rocky."},{"line_number":196,"context_line":""},{"line_number":197,"context_line":"Alternatives"},{"line_number":198,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9f91af0f_5f439942","line":195,"in_reply_to":"9f91af0f_5c2ac7da","updated":"2018-01-10 12:36:25.000000000","message":"\u003e it can load the list like we load the list of classic drivers on line 173, and I think we\u0027re relying on the node running dbsync having all the drivers/hardware types installed for the check on L180 right? \n\nRight, but we don\u0027t fail upgrade if something is missing. Here we risk having false negatives.","commit_id":"d7532ca02855f707afc556ea6bb1478627e4bec5"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"048f15a90e104ceb5fc023004daf5e848b92ae58","unresolved":false,"context_lines":[{"line_number":192,"context_line":"  nodes are using classic drivers. As the list of classic drivers will not be"},{"line_number":193,"context_line":"  available at that time (they will be removed from the tree), maintain the"},{"line_number":194,"context_line":"  list of classic driver names that used to be in tree and check nodes against"},{"line_number":195,"context_line":"  this list. Remove this check in the release after Rocky."},{"line_number":196,"context_line":""},{"line_number":197,"context_line":"Alternatives"},{"line_number":198,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9f91af0f_bcac339f","line":195,"in_reply_to":"9f91af0f_9c55affc","updated":"2018-01-10 12:08:19.000000000","message":"I don\u0027t want to maintain a list of all hardware types somewhere in our dbsync code, to be honest. This is why I prefer to check for classic drivers - we more or less know the list. I\u0027m fine with not removing the check soon or ever.","commit_id":"d7532ca02855f707afc556ea6bb1478627e4bec5"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"cd4f0dd74a856bfd0fbdf66c70e1fffc1c52d41c","unresolved":false,"context_lines":[{"line_number":192,"context_line":"  nodes are using classic drivers. As the list of classic drivers will not be"},{"line_number":193,"context_line":"  available at that time (they will be removed from the tree), maintain the"},{"line_number":194,"context_line":"  list of classic driver names that used to be in tree and check nodes against"},{"line_number":195,"context_line":"  this list. Remove this check in the release after Rocky."},{"line_number":196,"context_line":""},{"line_number":197,"context_line":"Alternatives"},{"line_number":198,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9f91af0f_1cc43f3f","line":195,"in_reply_to":"9f91af0f_9cb04fdf","updated":"2018-01-10 12:11:48.000000000","message":"We cannot guarantee that the node where we are running dbsync has all hardware types enabled. Different conductors may have different hardware types.","commit_id":"d7532ca02855f707afc556ea6bb1478627e4bec5"},{"author":{"_account_id":6637,"name":"Sam Betts","email":"sam@code-smash.net","username":"sambetts"},"change_message_id":"74b30a9ea38daa188e192877020d89e2a122f246","unresolved":false,"context_lines":[{"line_number":192,"context_line":"  nodes are using classic drivers. As the list of classic drivers will not be"},{"line_number":193,"context_line":"  available at that time (they will be removed from the tree), maintain the"},{"line_number":194,"context_line":"  list of classic driver names that used to be in tree and check nodes against"},{"line_number":195,"context_line":"  this list. Remove this check in the release after Rocky."},{"line_number":196,"context_line":""},{"line_number":197,"context_line":"Alternatives"},{"line_number":198,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9f91af0f_9cb04fdf","line":195,"in_reply_to":"9f91af0f_bcac339f","updated":"2018-01-10 12:10:45.000000000","message":"We don\u0027t need to maintain a list of all hardware types in the dbsync code though, we can load it via stevedore from setup.cfg, which will mean it works for out of tree hardware types too.","commit_id":"d7532ca02855f707afc556ea6bb1478627e4bec5"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"0d296febcb39d14de65e3a8e2164ebef3504bcef","unresolved":false,"context_lines":[{"line_number":192,"context_line":"  nodes are using classic drivers. As the list of classic drivers will not be"},{"line_number":193,"context_line":"  available at that time (they will be removed from the tree), maintain the"},{"line_number":194,"context_line":"  list of classic driver names that used to be in tree and check nodes against"},{"line_number":195,"context_line":"  this list. Remove this check in the release after Rocky."},{"line_number":196,"context_line":""},{"line_number":197,"context_line":"Alternatives"},{"line_number":198,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9f91af0f_5b341bde","line":195,"in_reply_to":"9f91af0f_da2b4e92","updated":"2018-01-09 22:17:15.000000000","message":"Semi -1 to pulling the check immediately after rocky, since there would be no fast-forward ability then. It would require operators and vendors step release to release... but there is no standard behind that or lts releases at this point, so *shrug*","commit_id":"d7532ca02855f707afc556ea6bb1478627e4bec5"}]}