add ironic support to trunk extension

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

Related fix proposed to branch: master
Review: https://review.openstack.org/436695

Related fix proposed to branch: master
Review: https://review.openstack.org/436738

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

Reviewed: https://review.openstack.org/436738
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=f2eb0ecb89001fb403c907b6d96b0e24385a9eef
Submitter: Jenkins
Branch: master

commit f2eb0ecb89001fb403c907b6d96b0e24385a9eef
Author: Armando Migliaccio <email address hidden>
Date: Tue Feb 21 18:58:31 2017 -0800

    Tweak trunk extension to support Ironic use case

    To support the Ironic use case, the trunk extension
    needs to know about provider details for the network.

    This patch documents this relationship, and it adds
    support for the 'inherit' segmentation type that
    acts as a flag that a user can use to signal his/her
    request in having the segmentation details derived
    from the underlying network.

    The API has not practically changed, and thus no
    release note or API extension shim is required for
    this patch.

    Related-bug: #1648129

    Change-Id: Ib510aade1716e6ca92940b85245eda7d0c84a070

Change abandoned by Vasyl Saienko (<email address hidden>) on branch: master
Review: https://review.openstack.org/409778
Reason: The other patch proposed https://review.openstack.org/#/c/436756/.
Thanks for picking this Armando!

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

commit ec84c84910516783ad2e0bf9ce5e7c4fb6775645
Author: Armando Migliaccio <email address hidden>
Date: Tue Feb 21 13:38:26 2017 -0800

    Prepare trunk rules module to deal with the Ironic use case

    There is a chance the _validate method might grow to be
    unmaneagable to support the ironic user case. Break it
    down before it's too late.

    Related-bug: #1648129

    Change-Id: I511d48f4702c3f0dd1013067ae1ceb82cf41d9a3

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

commit 4a6d06550bd98b473bdcf5e58dcfb7f5ca9424ef
Author: Armando Migliaccio <email address hidden>
Date: Tue Feb 21 18:43:38 2017 -0800

    Inherit segmentation details for trunk subports if requested

    This patch introduces support for requests where the user does
    not know the segmentation details of a subport and by specifying
    segmentation_type=inherit will let the trunk plugin infer these
    details from the network to which the subport is connected to, thus
    ignoring the segmentation_id in case it were to be specified.

    This type of request is currently expected to have correct results
    when the network segmentation type is 'vlan', and the network has
    only one segment (provider-net extension use case).

    DocImpact: Extend trunk documentation to include Ironic use case.

    Closes-bug: #1648129

    Depends-on: Ib510aade1716e6ca92940b85245eda7d0c84a070
    Change-Id: I3be2638fddf3a9723dd852a3f9ea9f64eb1d0dd6

This issue was fixed in the openstack/neutron 11.0.0.0b1 development milestone.