There are relative imports in NVP plugin

[Salvatore Orlando]

We all know how bad this is in terms of HACKING rules:

import NvpApiClient
import nvplib

However, as of the Folsom release, we saw unit test failures if we made those imports absolute.
This is not a good excuse for violating HACKING rules, so these relative imports must now go

[dan wendlandt (danwent)]

I'll move this to G-3 later this week unless I see a patch by then. thx.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/18928
Committed: http://github.com/openstack/quantum/commit/20ea05f5d230d1bf9e70c9cc79a1089c2e4595df
Submitter: Jenkins
Branch: master

commit 20ea05f5d230d1bf9e70c9cc79a1089c2e4595df
Author: Aaron Rosen <email address hidden>
Date: Thu Jan 3 16:52:42 2013 -0800

    Remove relative imports from NVP plugin

    The majority of relative imports in the nvp plugin will be fixed in
    blueprint nvp-api-client-loadbalance-request. This patch removes the
    rest of them in and moves the vim tabstop line to the top of the
    header file to be consistent with the rest of the files in quantum.
    Fixes bug 1091596

    Change-Id: I6c8299ca73ae5df75c87f302680908f863f81f02