On 10/02/17 18:10, Joshua Harlow wrote: > Jay Pipes wrote: >> On 02/10/2017 12:21 PM, Joshua Harlow wrote: >>> Hayes, Graham wrote: >>>> The HTML version of this is here: >>>> http://graham.hayes.ie/posts/openstack-designate-where-we-are/ >>>> >>>> I have been asked a few times recently "What is the state of the >>>> Designate >>>> project?", "How is Designate getting on?", and by people who know >>>> what is >>>> happening "What are you going to do about Designate?". >>>> >>>> Needless to say, all of this is depressing to me, and the people that >>>> I have >>>> worked with for the last number of years to make Designate a truly >>>> useful, >>>> feature rich project. >>>> >>>> *TL;DR;* for this - Designate is not in a sustainable place. >>>> >>>> To start out - Designate has always been a small project. DNS does not >>>> have >>>> massive *cool* appeal - its not shiny, pretty, or something you see on >>>> the >>>> front page of HackerNews (unless it breaks - then oh boy do people >>>> become DNS >>>> experts). >>>> >>> >>> Thanks for posting this, I know it was not easy to write... >>> >>> Knowing where this is at and the issues. It makes me wonder if it is >>> worthwhile to start thinking about how we can start to look at 'outside >>> the openstack' projects for DNS. I believe there is a few that are >>> similar enough to designate (though I don't know well enough) for >>> example things like SkyDNS (or others which I believe there are a few). >>> >>> Perhaps we need to start thinking outside the openstack 'box' in regards >>> to NIH syndrome and accept the fact that we as a community may not be >>> able to recreate the world successfully in all cases (the same could be >>> said about things like k8s and others). >>> >>> If we got out of the mindset of openstack as a thing must have tightly >>> integrated components (over all else) and started thinking about how we >>> can be much more loosely coupled (and even say integrating non-python, >>> non-openstack projects) would that be beneficial (I think it would)? >> >> This is already basically what Designate *is today*. >> >> http://docs.openstack.org/developer/designate/support-matrix.html >> >> Just because something is written in Golang and uses etcd for storage >> doesn't make it "better" or not NIH. > > Agreed, do those other projects (written in golang, or etcd or other) > have communities that are growing; can we ensure better success (and > health of our own community) by partnering with them? That was the main > point (I don't really care what language they are written in or what > storage backend they use). > >> >> For the record, the equivalent to Designate in k8s land is Kube2Sky, the >> real difference being that Designate has a whole lot more options when >> it comes to the DNS drivers and Designate integrates with OpenStack >> services like Keystone. >> > > That's cool, thanks; TIL. > >> Also, there's more to cloud DNS services than service discovery, which >> is what SkyDNS was written for. > > Sure, it was just an example. > > The point was along the lines of if a project in our community is > struggling and there is a similar project outside of openstack (that is > trying to do similar things) is not struggling; perhaps it's better to > partner with that other project and enhance that other project (and then > recommend said project as the next-generation of ${whatever_project} was > struggling here).
As I said in my reply - there *is* no other project. > Said evaluation is something that we would likely have to do over time > as well (because as from this example, desigate was a larger group once, > it is now smaller). > >> >> best, >> -jay >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev