| opendevreview | Arkady Shtempler proposed openstack/designate-tempest-plugin master: New boundray scenario tests for a Quota test suite https://review.opendev.org/c/openstack/designate-tempest-plugin/+/860935 | 09:01 |
|---|---|---|
| opendevreview | OpenStack Release Bot proposed openstack/designate-dashboard stable/2023.1: Update .gitreview for stable/2023.1 https://review.opendev.org/c/openstack/designate-dashboard/+/875904 | 13:17 |
| opendevreview | OpenStack Release Bot proposed openstack/designate-dashboard stable/2023.1: Update TOX_CONSTRAINTS_FILE for stable/2023.1 https://review.opendev.org/c/openstack/designate-dashboard/+/875905 | 13:17 |
| opendevreview | OpenStack Release Bot proposed openstack/designate-dashboard master: Update master for stable/2023.1 https://review.opendev.org/c/openstack/designate-dashboard/+/875906 | 13:17 |
| opendevreview | Arkady Shtempler proposed openstack/designate-tempest-plugin master: Shared Zones - adding test cases for Admin related stuff https://review.opendev.org/c/openstack/designate-tempest-plugin/+/875919 | 13:39 |
| lhommeRares | johnsom: frickler: Hello :) , we have deployed the sink component but we can see here https://github.com/openstack/designate/blob/master/designate/notification_handler/neutron.py#L46 that a zone_id has to be configured in designate.conf to delete PTR ressource. Though in production, we have multiple subnet, so multiple in.addr-arpa. zones. Is this a missing feature of Designate that it doesn't lookup the reverse zone matching the floating | 15:46 |
| lhommeRares | ip ? | 15:46 |
| johnsom | Yeah, looking at that code, it assumes you are using a single zone for the PTR records. | 15:53 |
| zigo | johnsom: Right, so if we have multiple /24, then we must ... add some code in Designate ? :) | 15:56 |
| zigo | johnsom: We're deeply thinking about adding such code to do the PTR zone look-up... | 15:56 |
| zigo | Any advice on how to do the lookup, having the floating ip ID as unique entry point? | 15:56 |
| johnsom | Ok, you may want to do a list so that neutron doesn't trigger the delete of non managed PTR zones. | 15:57 |
| frickler | IMO the handler bundled with designate is just a simple example. in contrib/ there's an example how you can create your custom handler for your use case | 15:59 |
| johnsom | yeah, there is no reason you can't create a custom handler. It doesn't even need to be part of the designate code base | 16:01 |
| zigo | Thanks a lot for your precious answers. We're slowly getting the pieces together, at this point, I believe we can handle ! :) | 16:25 |
| zigo | We will probably end up with either a custom handler, or contribute a handler that will do the zone lookup. We've found this as a nice example: https://github.com/twc-openstack/cirrus-designate-sink-handler/blob/master/cirrus_designate_sink_handler/notification_handler/cirrus_floating_ip_handler.py#L56 | 16:26 |
| zigo | :) | 16:26 |
| eandersson | Custom handler is great | 17:52 |
| eandersson | The only downside is that if a hypervisor goes offline it won’t send a notification and you may need to do manual cleaning | 17:53 |
| eandersson | And that cleaning has to be done by an admin, or ideally a script | 17:54 |
| eandersson | eg a vm deleted on an offline hypervisor won’t send a vm deleted event so the dns record tied to that vm wont be deleted | 17:55 |
| eandersson | not sure if the same applies to neutron messages | 17:56 |
| opendevreview | Merged openstack/designate-dashboard stable/2023.1: Update .gitreview for stable/2023.1 https://review.opendev.org/c/openstack/designate-dashboard/+/875904 | 20:26 |
| opendevreview | Merged openstack/designate-dashboard stable/2023.1: Update TOX_CONSTRAINTS_FILE for stable/2023.1 https://review.opendev.org/c/openstack/designate-dashboard/+/875905 | 20:26 |
| opendevreview | Merged openstack/designate-dashboard master: Update master for stable/2023.1 https://review.opendev.org/c/openstack/designate-dashboard/+/875906 | 20:26 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!