Comment 4 for bug 1843218

Hi Gregoire,

Feel free to start coding. Be aware, though, that until the RFE is tagged as "rfe-confirmed" and we leave you a message explicitly indicating that it has been approved, it is still possible that we won't accept it. We are still in the clarification stage and you seem to be changing your proposal as you add responses above. So, let's first firm up your proposal:

1) Based on what you have stated in emails and here and the fact that you work for OVH, I have gleaned the following use case: you have users of a public cloud who all connect their VMs to a shared public cloud. Upon creation of these VMs, you want them to have a public DNS record published by Designate

2) The latest variation of your proposal is that you are going to associate a default zone name to the dns_domain attribute of the big shared public network

3) Every time a VM is created with a port in the public shared network, you are going to create a records in a zone named <tenantid>.<defaultzone>.com, <defaultzone> is the name associated to the public network's dns_domain attribute

Does this summarize your proposal?

Now, a couple of questions:

1) What is going to be the left part of your DNS record?

2) Currently, the Neutron - Designate integration has a number of behaviors, which we have to preserve. How are you going to enable the behavior you are proposing?