Make vmwareapi.VMwareESXDriver use the current network model

[Amir Sadoughi]

Related to bug 1044383, vmwareapi.VMwareESXDriver needs to use the current nova.network.model instead of being dependent on legacy().

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/21475
Committed: http://github.com/openstack/nova/commit/70c659059b8fbef811ce79700aecb01c60242ebd
Submitter: Jenkins
Branch: master

commit 70c659059b8fbef811ce79700aecb01c60242ebd
Author: Amir Sadoughi <email address hidden>
Date: Thu Feb 7 04:28:34 2013 +0000

    VMWare driver to use current nova.network.model

    * Updated tests to use classes from nova.network.model instead of legacy
      "network,mapping" tuple.
    * Modified vmwareapi/{driver,vif,vmops}.py to use classes from
      nova.network.model instead of legacy "network,mapping" tuple.

    Fixes: bug 1112655
    Change-Id: I7f4b39cd5add7d3cf7dcf485eb9855d0354f332c