Deletion of DHCP should be notified to the security group rpc
Bug #1103840 reported by
Nachi Ueno
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Nachi Ueno |
Bug Description
Deletion of DHCP should be notified to the security group rpc.
Note: This common logic should be in security_
Changed in quantum: | |
milestone: | none → grizzly-3 |
assignee: | nobody → Nachi Ueno (nati-ueno) |
tags: | added: l3-ipam-dhcp |
tags: | added: sg-fw |
Changed in quantum: | |
milestone: | grizzly-3 → grizzly-rc1 |
Changed in quantum: | |
importance: | High → Medium |
Changed in quantum: | |
status: | Fix Committed → Fix Released |
Changed in quantum: | |
milestone: | grizzly-rc1 → 2013.1 |
To post a comment you must log in.
This is based on the comment https:/ /review. openstack. org/#/c/ 19436/14/ quantum/ plugins/ openvswitch/ ovs_quantum_ plugin. py
-----
We need to inform dhcp ip address when a port for dhcp server is deleted. enable_dhcp in subnet may be changed by update_subnet. The same thing can say to linux bridge plugin.
The logic like this is important, so it should be implemented as a common logic even if the logic is very short. security_ group_rpc_ base is a good place.
Don't we need to take care the same thing for update_port? IMO, we do not need to take care of it since update device_owner is set by programs (nova vif plugiing, dhcp-agent or so on).
-----