Open question regarding andromeda vs designate usecases

[yanndegat]

Hi @notandy

this project seems really great, still i have a fundamental question regarding its role vs designate. It's not very clear in the README.

i perfectly understand the usecase of a gslb. And i know that designate is not (yet) capable of geo routing and cannot be used as
a building block for a gslb.

That said, in a typical openstack deployment, could andromeda completly replace designate ? or should it be seen as a complementary system, such as one would globally manage a zone with designate, and only declare NS records pointing to andromeda for the enpoints which requires georouting strategies ?

thanks a lot for clarification.

BR

[notandy]

or should it be seen as a complementary system, such as one would globally manage a zone with designate, and only declare NS records pointing to andromeda for the enpoints which requires georouting strategies ?

This ☝️
Andromeda itself doesn't manage DNS names, but uses third party services to accomplish it. Currently, there is no Designate backend existing, but it would be totally feasible to extend existing (static) Designate with the ability to deploy georouting strategies.

[yanndegat]

ok i see. but if designate is not capable of geo routing ( at least not yet ) and andromeda neither ( as it relies on its backend to achieve it). what's the best next move if you cant rely on F5 or akamai? add new design for georouting in designate and impl. a new andromeda backend? or something else more straightforward?

[notandy]

Yeah, Designate would've to implement some kind of geo-routing in this case, letting andromeda reply the DNS responses makes designate pretty useless.