[Metaplugin] fails with VIF extension

[Nachi Ueno]

Current metaplugin didn't implements get_ports or get_port to proxy request for actual plugins.
so extension such as VIF extension will not be added the result of port.

[Itsuro Oda (oda-g)]

I found this report when I tried to report the same issue.
I have a fix locally. I will post the fix after some other bug fixes of metaplugin which I will post are merged.

[OpenStack Infra (hudson-openstack)]

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

commit 7a67a5676fb82ddb717e6b606cc702c31523b9fa
Author: Itsuro Oda <email address hidden>
Date: Thu Dec 19 10:51:19 2013 +0900

    Fix lack of extended port's attributes in Metaplugin

    Previously, there are some extended port's attributes did not
    appear in the result of GET port API when using Metaplugin.
    This become a critial issue currently since lack of port binding
    information disturbs normal port binding operation in a compute
    node, for example.

    Metaplugin did not delegate get_port/get_ports to target plugins.
    This is cause of the problem because right plugin instance is not
    passed to a hook which handles extended attributes.
    Now, get_port/get_ports of target plugins are called so that
    extended port's attributes are handled properly.

    Change-Id: Ifed2505a97ceca56c4cedd22efa49adcdf3317b8
    Closes-Bug: #1136252