Designate

Naming Convention for Records

Registered by Kumar Acharya on 2015-12-09

If we can specify two formats like "formatv4" and "formatv6" in designate.conf and implement those in designate code also, we can have two naming conventions for IPv4 and IPv6 networks. This will help us to separate IPv4 and IPv6 which right now we cannot do.

Read the full specification

Blueprint information

Status:: Complete

Approver:: None

Priority:: Undefined

Drafter:: Kumar Acharya

Direction:: Needs approval

Assignee:: Kumar Acharya

Definition:: Approved

Series goal:: None

Implementation:: Implemented

Milestone target:: newton-3

Started by: Kumar Acharya on 2016-07-01

Completed by: Kumar Acharya on 2016-07-26

Related branches

Won't Fix

Sprints

Whiteboard

changes in designate.conf:

formatv4 = 'z%(instance_id)0.8s-%(counter)02d.%(domain)s'
formatv6 = 'z%(instance_id)0.8s-IPv6-%(counter)02d.%(domain)s'
#formatv6 = '%(hostname)s-%(octet0)s-%(octet1)s-%(octet2)s-%(octet3)s-%(octet4)s-%(octet5)s-%(octet6)s-%(octet7)s.%(tenant_id)0.8s.%(domain)s'

instead of just

format = '%(hostname)s-%(octet0)s-%(octet1)s-%(octet2)s-%(octet3)s.%(tenant_id)0.8s.%(domain)s'

To implement this in designate.conf we need to change the code in designate/notification_handler/base.py, designate/notification_handler/nova.py and /designate/notification_handler/neutron.py.

Gerrit topic: https://review.openstack.org/#q,topic:bp/different-format-for-ipv4-and-ipv6,n,z

Addressed by: https://review.openstack.org/337416
different-format-for-ipv4-and-ipv6

(?)

Work Items

Work items:
[ma501v] Define the format for IPV4 and IPv6 FQDN.and Implement it in designate.conf: DONE
[ma501v] Code changes required in designate: DONE

This blueprint contains Public information

Everyone can see this information.

Subscribers

No subscribers.