designate client requires region name to fetch PTR records
Bug #1832769 reported by
Mithil Arun
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Incomplete
|
Undecided
|
Mithil Arun |
Bug Description
Enable neutron's designate driver to accept the region name as a parameter while making requests.
Changed in neutron: | |
assignee: | nobody → Mithil Arun (arun-mithil) |
To post a comment you must log in.
Hi,
Could you please clarify what do you mean by "designate client requires region name to fetch PTR records". Please look at the configuration guide of the Neutron / Designate integration: https:/ /docs.openstack .org/neutron/ latest/ admin/config- dns-int- ext-serv. html#configurin g-openstack- networking- for-integration -with-an- external- dns-service. In point 2 you can see the following sub-bullet: "region_name: the name of the region to be used by the Networking service to create and update reverse lookup (PTR) zones".
And in my development system I can create PTR records, as you can see here: http:// paste.openstack .org/show/ 752973/. I built this development system from master branch 1 day ago. Note that in this system, I am not even configuring explicitly the region name: https:/ /github. com/miguellaval le/dvrvagrant/ blob/0ec999a691 6f585eb11c2bd89 4d8ed7006e389d6 /provisioning/ setup-allinone. sh#L45- L56