)]}'
{"specs/xena/rDNS-nonoctet-boundary.rst":[{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"31cbfcb1ebeed191e2055c7f433c51e3d16d4e5f","unresolved":true,"context_lines":[{"line_number":20,"context_line":"Problem Description"},{"line_number":21,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"One can be given a delegation of a reverse zone with an unusual name, for"},{"line_number":24,"context_line":"instance ``0-25.2.0.192.in-addr.arpa`` (when assigned the ``192.0.2.0/25``"},{"line_number":25,"context_line":"prefix). This scheme is based on the fact that a DNS record for reverse"},{"line_number":26,"context_line":"resolution can be a CNAME to another record. This spec adds a generic mechanism"}],"source_content_type":"text/x-rst","patch_set":1,"id":"f37af970_3352a1ed","line":23,"updated":"2021-06-03 22:34:48.000000000","message":"This goes straight into the solution (RFC 2317), with little commentary on the problem that is being solved.\nAs neutron will create and manage reverse zones, it\u0027s not clear initially why this change is needed.\nIt would be helpful to have a problem description that describes the case where not all of a class \"C\" subnet is delegated to the OpenStack deployment, such that some of the reverse PTR records may live outside of the Designate controlled zones. I think you need a way to delegate portions of a reverse zone to neutron/designate from an existing or shared zone.","commit_id":"b676896cd5d6fdf238a4e0ca9be7a9a015c2c26f"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"31cbfcb1ebeed191e2055c7f433c51e3d16d4e5f","unresolved":true,"context_lines":[{"line_number":26,"context_line":"resolution can be a CNAME to another record. This spec adds a generic mechanism"},{"line_number":27,"context_line":"to properly handle such cases, as handling them is not currently possible."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"This specification does not deal with the \"provider\" part, i.e. the addition of"},{"line_number":30,"context_line":"CNAMEs and NS in the parent zone, which has no reason to be managed by"},{"line_number":31,"context_line":"Designate / Neutron."},{"line_number":32,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"0421ce86_6b6ac341","line":29,"updated":"2021-06-03 22:34:48.000000000","message":"I would like to see a small example of the configuration required in the parent zone here. It helps to frame the manual work required that is not addressed by this specification.\nFrom this spec, you cannot see end-to-end how this would work in practice.","commit_id":"b676896cd5d6fdf238a4e0ca9be7a9a015c2c26f"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"31cbfcb1ebeed191e2055c7f433c51e3d16d4e5f","unresolved":true,"context_lines":[{"line_number":64,"context_line":""},{"line_number":65,"context_line":"### First step: global Neutron configuration"},{"line_number":66,"context_line":""},{"line_number":67,"context_line":"The behavior described above would be configured with settings in the global"},{"line_number":68,"context_line":"neutron configuration file."},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"Raise an error in case of invalid setting configuration:"},{"line_number":71,"context_line":"* ``ipv4_ptr_zone_prefix_size`` is set and either ``ipv4_ptr_zone`` or"},{"line_number":72,"context_line":"``ipv4_ptr_record_template`` is set."}],"source_content_type":"text/x-rst","patch_set":1,"id":"553f4816_0a1c42f3","line":69,"range":{"start_line":67,"start_character":54,"end_line":69,"end_character":0},"updated":"2021-06-03 22:34:48.000000000","message":"Can we explicitly call out the proposed new settings in the neutron configuration file here?\n\nAre you proposing a \"ipv4_ptr_zone\" configuration setting for every possible subnet created in neutron?\n\nTo me, it\u0027s not clear that either of these settings could be set globally in the neutron configuration file. The parent delegation size could vary subnet to subnet right?","commit_id":"b676896cd5d6fdf238a4e0ca9be7a9a015c2c26f"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"31cbfcb1ebeed191e2055c7f433c51e3d16d4e5f","unresolved":true,"context_lines":[{"line_number":68,"context_line":"neutron configuration file."},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"Raise an error in case of invalid setting configuration:"},{"line_number":71,"context_line":"* ``ipv4_ptr_zone_prefix_size`` is set and either ``ipv4_ptr_zone`` or"},{"line_number":72,"context_line":"``ipv4_ptr_record_template`` is set."},{"line_number":73,"context_line":"* ``ipv4_ptr_zone`` is set and ``ipv4_ptr_record_template`` is not set."},{"line_number":74,"context_line":"* ``ipv4_ptr_zone`` is not set and ``ipv4_ptr_record_template`` is set."}],"source_content_type":"text/x-rst","patch_set":1,"id":"b476abfc_1513d742","line":71,"updated":"2021-06-03 22:34:48.000000000","message":"You need a blank line here to have the bulleted list render correctly.","commit_id":"b676896cd5d6fdf238a4e0ca9be7a9a015c2c26f"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"31cbfcb1ebeed191e2055c7f433c51e3d16d4e5f","unresolved":true,"context_lines":[{"line_number":76,"context_line":""},{"line_number":77,"context_line":"### Second step: per-IPAllocationPool configuration"},{"line_number":78,"context_line":""},{"line_number":79,"context_line":"Global settings could be overwritten for each ``IPAllocationPool``; however, it"},{"line_number":80,"context_line":"would require an update of both ``IPAllocationPool`` and ``IPAllocation``"},{"line_number":81,"context_line":"models (in ``neutron/db/models_v2.py``), as ``IPAllocation`` would need to keep"},{"line_number":82,"context_line":"track of ``IPAllocationPool`` rDNS settings."}],"source_content_type":"text/x-rst","patch_set":1,"id":"3b963198_434f4a80","line":79,"range":{"start_line":79,"start_character":0,"end_line":79,"end_character":36},"updated":"2021-06-03 22:34:48.000000000","message":"Do new global setting make sense here? Maybe all we need is settings on the subnet and/or IP allocation pool.","commit_id":"b676896cd5d6fdf238a4e0ca9be7a9a015c2c26f"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"31cbfcb1ebeed191e2055c7f433c51e3d16d4e5f","unresolved":true,"context_lines":[{"line_number":87,"context_line":""},{"line_number":88,"context_line":"    class IPAllocationPool(model_base.BASEV2, model_base.HasId):"},{"line_number":89,"context_line":"        # [snip]"},{"line_number":90,"context_line":"        ptr_zone \u003d sa.Column(sa.String(255), nullable\u003dTrue)"},{"line_number":91,"context_line":"        ptr_record_template \u003d sa.Column(sa.String(255), nullable\u003dTrue)"},{"line_number":92,"context_line":""},{"line_number":93,"context_line":"A reference to the originating ``IPAllocationPool`` could be kept into the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"2b3524a6_0315a871","line":90,"updated":"2021-06-03 22:34:48.000000000","message":"How is this exposed via the API to set?\nIs this set a subnet creation time? SubnetPool creation?\nIs this tied to a specific IPAM implementation?\n\nIt seems like the logical place to configure this would be at the subnet level, such that all of the addresses in the allocation pool would use the alternate ptr_zone.","commit_id":"b676896cd5d6fdf238a4e0ca9be7a9a015c2c26f"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"27d7c7ff45972d412f7092a6b76eee33ed88ffc6","unresolved":true,"context_lines":[{"line_number":104,"context_line":""},{"line_number":105,"context_line":"Add optional ``ptr_zone`` and ``ptr_record_template`` fields in"},{"line_number":106,"context_line":"``IPAllocationPool`` model, and ``ip_allocation_pool_id`` in ``IPAllocation``"},{"line_number":107,"context_line":"to be able to get the values of ``ptr_zone`` and ``ptr_record_template``."},{"line_number":108,"context_line":""},{"line_number":109,"context_line":"User use cases"},{"line_number":110,"context_line":"--------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"19448274_023d6210","line":107,"updated":"2021-05-31 08:20:27.000000000","message":"If this is config option change only, I don\u0027t see any reason why we need to store it in the db.\nIf You want to do it \"per subnetpool\" maybe You should make it as API extension to allow setting that template for each subnetpool per API?","commit_id":"b676896cd5d6fdf238a4e0ca9be7a9a015c2c26f"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"4d5b70103107aed24ebc3dea299b0217c8588297","unresolved":true,"context_lines":[{"line_number":104,"context_line":""},{"line_number":105,"context_line":"Add optional ``ptr_zone`` and ``ptr_record_template`` fields in"},{"line_number":106,"context_line":"``IPAllocationPool`` model, and ``ip_allocation_pool_id`` in ``IPAllocation``"},{"line_number":107,"context_line":"to be able to get the values of ``ptr_zone`` and ``ptr_record_template``."},{"line_number":108,"context_line":""},{"line_number":109,"context_line":"User use cases"},{"line_number":110,"context_line":"--------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"46cf267f_ea770757","line":107,"in_reply_to":"19448274_023d6210","updated":"2021-06-03 17:41:21.000000000","message":"I agree, the option would need to be per subnet, since there may be different schemes in use in parallel, and then the most reasonable approach would be to have an API extension for it.","commit_id":"b676896cd5d6fdf238a4e0ca9be7a9a015c2c26f"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"31cbfcb1ebeed191e2055c7f433c51e3d16d4e5f","unresolved":true,"context_lines":[{"line_number":106,"context_line":"``IPAllocationPool`` model, and ``ip_allocation_pool_id`` in ``IPAllocation``"},{"line_number":107,"context_line":"to be able to get the values of ``ptr_zone`` and ``ptr_record_template``."},{"line_number":108,"context_line":""},{"line_number":109,"context_line":"User use cases"},{"line_number":110,"context_line":"--------------"},{"line_number":111,"context_line":""},{"line_number":112,"context_line":"This specification addresses the specific case where the entity managing a"}],"source_content_type":"text/x-rst","patch_set":1,"id":"71819ba3_4e5ad0b4","line":109,"updated":"2021-06-03 22:34:48.000000000","message":"Can we see more of an end-user use case here?\n\nSomething like:\n\nUser requests a PTR zone delegation\nUser creates a subnet, specifying the ptr_zone that was delegated.\nUser sets \"dns_publish_fixed_ip\"\nUser creates a port on the network with a DNS name and IP\nUser can reverse look up the IP","commit_id":"b676896cd5d6fdf238a4e0ca9be7a9a015c2c26f"}]}