Make vmwareapi.VMwareESXDriver use the current network model

Bug #1112655 reported by Amir Sadoughi on 2013-02-01
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Undecided
Amir Sadoughi

Bug Description

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

Chuck Short (zulcss) on 2013-02-04
Changed in nova:
status: New → Confirmed
tags: added: vmware
Changed in nova:
assignee: nobody → Amir Sadoughi (amir-sadoughi)

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

Changed in nova:
status: Confirmed → In Progress

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

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2013-02-21
Changed in nova:
milestone: none → grizzly-3
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2013-04-04
Changed in nova:
milestone: grizzly-3 → 2013.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers