I've skimmed through 4.0 sources and they didn't look too different from
3.x in this sense.
Perhaps I need to dig deeper.
Thanks,
Valentine
On 28.08.2017 20:15, Harshad Nakil wrote:
There is no point in making external DNS resolution of private IP space. Open
contrail DNS was designed to have DNS functionality for private networks.
For external connectivity you should still use Designate. you can still make
contrail DNS as authoritative DNS for public network in Designate. The
floating IP(s) will be automatically added as dashed ip address for public
network.
I think in 4.0 all three(or more) nodes have were suppose to be made as
active/active. Yes there were some flaky design decisions in pre 4.0 releases.
Regards
-Harshad
On Aug 28, 2017, at 6:34 AM, Valentine Sinitsyn <valentine.sinit...@gmail.com>
wrote:
Hi Robert,
Thanks for sharing your experience and your advices.
On 28.08.2017 18:24, Van Leeuwen, Robert wrote:
Only thing I forgot to mention:
The Contrail implementation has one thing going for it: it allows for working
reverse DNS with duplicate IP space.
(e.g. multiple tenants are using 192.168.1.0/24)
You will not be able to set that up with anything else.
(Note that you cannot extend this outside of your Contrail)
You mean, it won't work for external queries (provided that I enabled the
feature in Virtual DNS config)?
Valentine
If you can get away with not supporting that I would highly recommend looking
at Designate.
Cheers,
Robert van Leeuwen
On 8/28/17, 3:02 PM, "Dev on behalf of Van Leeuwen, Robert"
<dev-boun...@lists.opencontrail.org on behalf of rovanleeu...@ebay.com> wrote:
> Consider you have a cluster with >=3 control nodes running (let's call
> them Cn). Think you also have a Virtual DNS configured which allows
> dynamic records from a vRouter agent (that's the default).
>
>
> I would expect all of C1, C2 and C3 to resolve both "foo" and "bar".
> However, with data flows shown above, C1 would know nothing of "foo",
> and C3 won't resolve "bar".
>
> What do I miss here?
Nothing!
It indeed works like this. It will only update the active master and
active slave.
In a 3 node setup this is a problem since the third inactive node will not
get any updates.
We eventually switched to using designate for DNS usage (via a
link-local service) because we had quite a lot of headaches with the contrail
DNS implementation.
This also gives OpenStack users an interface to manage DNS records which
is a nice addition.
One other noteworthy thing is that the DNS vrouter functionality is not
supporting the full RFC like queries over TCP which is needed for large DNS
result sets.
I have not looked at the 4.0 product yet but IMHO this part of the product
needs either a LOT of attention / rework or it should be ripped out of the
product if there is no capacity to support it properly.
Cheers,
Robert van Leeuwen
_______________________________________________
Dev mailing list
Dev@lists.opencontrail.org
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.opencontrail.org%2Fmailman%2Flistinfo%2Fdev_lists.opencontrail.org&data=02%7C01%7Crovanleeuwen%40ebay.com%7C20c72f5ebfbf4e909a4a08d4ee15487d%7C46326bff992841a0baca17c16c94ea99%7C0%7C0%7C636395222552678883&sdata=j3zmLeXYISQUkJuJsiCPDQHxOAHTfw8751uzxf%2F6Cro%3D&reserved=0
_______________________________________________
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
_______________________________________________
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
