nova-api-metadata requires db access when configured with nova-network

[Vish Ishaya]

When nova-network is being used, nova-api-metadata requires db access which in some configurations means the compute nodes still connect to the database.

It connects to the db when trying to map the fixed ip address to an instance uuid:

fixed_ip = network.API().get_fixed_ip_by_address(ctxt, address)

This should be changed to do an rpc call to conductor.

[Vish Ishaya (vishvananda)]

Fix here: https://review.openstack.org/#/c/86643/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/86643
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=79ab96e34ba5b8dd3e4e542dd3a7f65624b13367
Submitter: Jenkins
Branch: master

commit 79ab96e34ba5b8dd3e4e542dd3a7f65624b13367
Author: Dan Smith <email address hidden>
Date: Thu Apr 10 09:26:08 2014 -0700

    Fix network-api direct database hits in metadata server

    The metadata server was using a couple of methods from the network
    api that caused direct-to-database accesses. Those are no longer
    necessary with the object modeling of network resources. This patch
    converts those to use objects and avoid the direct database
    traffic.

    Change-Id: Iea48f74387afa35af3889eebdfa1af169a52ad1d
    Closes-bug: #1306009

[OpenStack Infra (hudson-openstack)]

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

[Openstack Gerrit (openstack-gerrit)]

Reviewed: https://review.openstack.org/87348
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=20d0cef99376ca622294536485a5987385a717e3
Submitter: Jenkins
Branch: master

commit 20d0cef99376ca622294536485a5987385a717e3
Author: Dan Smith <email address hidden>
Date: Mon Apr 14 11:13:32 2014 -0700

    Remove metadata's network-api dependence on the database

    This makes the metadata server use instance.info_cache for getting
    an instance's info cache instead of going direct to the network-api
    (and thus, the database) for it. It also converts the network-api
    implementation of get_fixed_ip_by_address() to use and return an
    object. Since that translates to the same DB call in the end, none
    of the network tests need to change.

    Change-Id: Iab444b1669628604f7d96d9550eb684645c554cb
    Closes-bug: #1306009

[Openstack Gerrit (openstack-gerrit)]

Fix proposed to branch: stable/icehouse
Review: https://review.openstack.org/89422

[Openstack Gerrit (openstack-gerrit)]

Reviewed: https://review.openstack.org/89422
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=395ec823a540e0f2e25b29001edc6b8142b14103
Submitter: Jenkins
Branch: stable/icehouse

commit 395ec823a540e0f2e25b29001edc6b8142b14103
Author: Dan Smith <email address hidden>
Date: Mon Apr 14 11:13:32 2014 -0700

    Remove metadata's network-api dependence on the database

    This makes the metadata server use instance.info_cache for getting
    an instance's info cache instead of going direct to the network-api
    (and thus, the database) for it. It also converts the network-api
    implementation of get_fixed_ip_by_address() to use and return an
    object. Since that translates to the same DB call in the end, none
    of the network tests need to change.

    Conflicts:

            nova/tests/network/test_api.py

    Change-Id: Iab444b1669628604f7d96d9550eb684645c554cb
    Closes-bug: #1306009
    (cherry picked from commit 20d0cef99376ca622294536485a5987385a717e3)