Port data plane status extension implementation

[OpenStack Infra]

https://review.openstack.org/424340
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 89de63de05e296af583032cb17a3d76b4b4d6a40
Author: Carlos Goncalves <email address hidden>
Date: Mon Jan 23 19:53:04 2017 +0000

    Port data plane status extension implementation

    Implements the port data plane status extension. Third parties
    can report via Neutron API issues in the underlying data plane
    affecting connectivity from/to Neutron ports.

    Supported statuses:
      - None: no status being reported; default value
      - ACTIVE: all is up and running
      - DOWN: no traffic can flow from/to the Neutron port

    Setting attribute available to admin or any user with specific role
    (default role: data_plane_integrator).

    ML2 extension driver loaded on request via configuration:

      [ml2]
      extension_drivers = data_plane_status

    Related-Bug: #1598081
    Related-Bug: #1575146

    DocImpact: users can get status of the underlying port data plane;
    attribute writable by admin users and users granted the
    'data-plane-integrator' role.
    APIImpact: port now has data_plane_status attr, set on port update

    Implements: blueprint port-data-plane-status

    Depends-On: I04eef902b3310f799b1ce7ea44ed7cf77c74da04
    Change-Id: Ic9e1e3ed9e3d4b88a4292114f4cb4192ac4b3502

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/495941

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/495946

[Boden R (boden)]

After looking at the doc work already done as part of the data plane status extension patches, I noticed 2 potential spots that could use additional clarity:
- The API ref (in neutron-lib) for this ext didn't mention anything about the admin/data_plane_integrator w/r/t default rbac.
- The current ML2 config info (in neutron/doc) doesn't mention extension drivers.

[OpenStack Infra (hudson-openstack)]

Change abandoned by boden (<email address hidden>) on branch: master
Review: https://review.openstack.org/495946
Reason: This is already documented in-line for the PUT (update) operation on a port::

  Only admins and users with a specific role can update the data plane status (default role: data_plane_integrator).

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/495941
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d5a3b24bde15543001551458bedd9e245521bbd0
Submitter: Jenkins
Branch: master

commit d5a3b24bde15543001551458bedd9e245521bbd0
Author: Boden R <email address hidden>
Date: Mon Aug 21 11:57:43 2017 -0600

    add doc section for ml2 extension drivers

    Today the ML2 config reference doesn't mention anything about ML2
    extension drivers. While it likely doesn't make sense to clutter the
    primary ML2 driver types (type/mech) with extension drivers, this patch
    proposes we add a small section about them to link the concept to the
    config reference.

    Change-Id: Id964e6e4d13d400ea4cd8a1707ad0f08c52ef0b1
    Partial-Bug: #1683102

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/pike
Review: https://review.openstack.org/496311

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/496311
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=312fcd9faa4a6ec08a3f9d3ca471f772ce817a50
Submitter: Jenkins
Branch: stable/pike

commit 312fcd9faa4a6ec08a3f9d3ca471f772ce817a50
Author: Boden R <email address hidden>
Date: Mon Aug 21 11:57:43 2017 -0600

    add doc section for ml2 extension drivers

    Today the ML2 config reference doesn't mention anything about ML2
    extension drivers. While it likely doesn't make sense to clutter the
    primary ML2 driver types (type/mech) with extension drivers, this patch
    proposes we add a small section about them to link the concept to the
    config reference.

    Change-Id: Id964e6e4d13d400ea4cd8a1707ad0f08c52ef0b1
    Partial-Bug: #1683102
    (cherry picked from commit d5a3b24bde15543001551458bedd9e245521bbd0)