I don't like the idea that uses bind9 views to split networks, due to
follow reasons:
the designate may not or hard to know the router's public address
non-router may exist for some isolate networks
there is no routes in our dhcp namespace currently
I suggest run one bind9 instance for each
We don't actually envisage a bind9 views solution in the near future.
I would imagine (this has not yet been discussed) that we would have
service VMs (one per network / tenant) connected to the neutron network,
and a control network (like how Trove are doing the neutron
integration).
Designate
kazuhiro MIYASHITA,
I have done a lot of thinking about this. I have a blueprint on hold
until Kilo for Neutron/Designate integration [1].
However, my blueprint doesn't quite address what you are going after
here. An assumption that I have made is that Designate is an external
or internet
kazuhiro MIYASHITA,
As designate progresses with server pools, we aim to have support for a
'private' dns server, that could run within a neutron network - is that
the level of integration you were referring to?
That is, for the time being, a long term goal, and not covered by Carl's
Kilo
