I am looking at the API docs. Apparently they group records in to "record sets". So if you have multiple records with the same name and type (like multiple A records for round-robin DNS, or multiple MX records), those get lumped together into a single "record set". Since the libcloud dns driver handles individual records, I was thinking I would just take the set and flatten it into multiple records with the same id and then have the designate driver internally handle the create/update/delete logic on individual records by merging them into record sets for the API. I could expose the record sets directly as extension methods (ex_iterate_record_sets, etc) for people who wanted to leverage the sets, but leave the builtin methods in terms of records.
Any objections to that approach? https://wiki.openstack.org/wiki/Designate/APIv2 Greg On 12/4/15, 2:29 PM, "Patrick Galbraith" <p...@patg.net> wrote: >Hi there ‹ KIall would knowŠ. > > >> On Dec 4, 2015, at 2:59 PM, Greg Hill <greg.h...@rackspace.com> wrote: >> >> Designate is the Openstack DNS API. I don't think libcloud supports it >>yet. Is anyone working on this? If not, I can probably get to it >>soon(ish). >> >> Greg >
