Hi Neil,
You are correct about dns_name and dns_assignment.
Prior to adding this feature to Neutron, all your ports were getting
implicitly what I named "dns_assignment". It was created by the the DHCP
agent and pushed to the dnsmasq instance associated with the port's
network. This implicit
Hi Miguel,
I’ve just been looking at this, and have deduced the following summary of the
new dns_name and dns_assignment fields:
- dns_name is a simple name, like 'vm17'. It is a writable port field, and gets
combined with a dns_domain that is specified elsewhere.
- dns_assignment is a
Hi,
While #1 does improve things further it doesn't cover the use case where
you have 2 tenants and you would like to have the VMs spun up different dns
domains.
I suspect this was intentionally left out?
Dani
On Wed, Oct 14, 2015 at 11:39 PM, Miguel Lavalle
wrote:
> Zhi
Hi, Miguel
Thank you so much for your reply. You are so patient!
After reading your reply, I still have some questions to ask you. :-)
Below, is my opinion about the http://paste.openstack.org/show/476210/,
please read it and tell me whether I was right.
(1). Define a DNS domain
Zhi Chang,
You got all the steps correct. A few clarifications:
1. Address 104.130.78.191 is the ip address of my devstack VM. When you
deploy Designate in devstack, it starts an instance of PowerDNS for you.
Designate then pushes all its zones and records to that PowerDNS instance.
Zhi Chang,
Thank you for your questions. We are in the process of integrating Neutron
and Nova with an external DNS service, using Designate as the reference
implementation. This integration is being achieved in 3 steps. What you are
seeing is the result of only the first one. These steps are:
Hi, all
I install the latest devstack and create a vm by nova. I get the port's
info which created by Neutron. I'm confused that what the meaning of column
"dns_assignment" and column "dns_name".
First, column "dns_assignment" is a read-only attribute. What is it used
for? I think that