expose DHCP server IP
in order for firewall logic to be able to poke a hole allowing traffic to/from a DHCP server, we need to expose the IP being used for DHCP in a subnet to external entities. This could be done by introduce device_owner attribute to the port.
Blueprint information
- Status:
- Complete
- Approver:
- dan wendlandt
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Nachi Ueno
- Definition:
- New
- Series goal:
- Accepted for folsom
- Implementation:
-
Implemented
- Milestone target:
-
2012.2
- Started by
- Thierry Carrez
- Completed by
- dan wendlandt
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
- Updated -
Add attribute 'device_owner' for port.
dhcp-agent will update device_owner to 'dhcp-agent'.
Client can query port which is used by dhcp using device_owner.
----- from dan ----
I actually liked your previous idea better, which is having a notion of the port owner. I had already suggested something like this in the past. I would phrase the field as device_owner, as it does hand-in-hand with the device_id (in fact, it sets the scope for interpreting the device-id.
My concern is that a "group" attribute is too vague... it could mean anything and be used for anything. Such ambiguity tends to lead to bad APIs in my opinion, as different implementations will use it for different things.
----- from dan----
I got it. I updated spec to device_owner. (nati)
Addressed by: https:/
Add device_owner attribute to port
