Make nova.virt.firewall use the current network model

Bug #1112657 reported by Amir Sadoughi on 2013-02-01
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Undecided
Amir Sadoughi

Bug Description

Related to bug 1044383, nova.virt.firewall 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
Changed in nova:
assignee: nobody → Amir Sadoughi (amir-sadoughi)

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

Changed in nova:
status: Confirmed → In Progress
Joe Gordon (jogo) wrote :

Is this still valid?

Changed in nova:
status: In Progress → Incomplete
Sean Dague (sdague) on 2014-09-17
Changed in nova:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers