Transition qos notification driver into qos driver

[OpenStack Infra]

https://review.openstack.org/396651
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

commit 38c1812015b6977f8212723d082222cefb0926e6
Author: Miguel Angel Ajo <email address hidden>
Date: Thu Nov 17 09:17:29 2016 -0500

    Transition qos notification driver into qos driver

    This will deprecate the notification_driver config setting,
    and no config setting will be needed.

    Also it lays down the foundation for a more decoupled interaction
    with mechanism drivers.

    Closes-Bug: #1657379
    Related-Bug: #1627749
    DocImpact

    Change-Id: I2f166a43f0b980ad22617f8a3f7b4cc7f4786c48

[Boden R (boden)]

Best I can tell, there's nothing needed herein from a neutron doc (devref or apiref) POV. The respective change that generated this bug already contained devref updates [1].

As per [2] the 'notification_drivers' config option is deprecated for QoS; therefore we need to update the associated config ref.

Moving this to openstack-manuals.

[1] https://review.openstack.org/#/c/396651/29/doc/source/devref/quality_of_service.rst
[2] https://review.openstack.org/#/c/396651/29/neutron/conf/services/qos_driver_manager.py

[Alexandra Settle (alexandra-settle)]

Moving to neutron as per doc migration.

[David Shaughnessy (david-shaughnessy)]

As Boden noted, the patch that triggered this bug included a documentation update in the devref folder.
Should this bug be marked as invalid?