Comment 1 for bug 1563497

Related to same issue, the current OS::Designate::RecordSet document has "records" item(see below) which has a list of nameservers. This goes out of sync whenever a new nameserver is created in designate, since it only sends dns.poo.update event. The is no additional event for record "update". We need to check if we should update records in OS::Designate::RecordSet for every nameserver create/delete or just maintain a separate document type for nameservers.

{
            "_index": "searchlight-2016_03_29_19_02_27",
            "_type": "OS::Designate::RecordSet",
            "_id": "f884912f-da69-494f-98e5-d8a8d76153b4",
            "_score": 1,
            "_source": {
               "status": "PENDING",
               "zone_id": "2f647395-60dc-4949-9249-a5c6a03ce315",
               "description": null,
               "created_at": "2016-03-29T18:19:44.000000",
               "__searchlight-user-role": [
                  "user",
                  "admin"
               ],
               "updated_at": "2016-03-29T18:19:44.000000",
               "_parent": "2f647395-60dc-4949-9249-a5c6a03ce315",
               "records": [
                  {
                     "data": "ns.foo.com."
                  },
                  {
                     "data": "ns4.foo.com."
                  },
                  {
                     "data": "ns3.foo.com."
                  }
               ],
               "version": 3,
               "ttl": null,
               "action": "UPDATE",
               "project_id": "80264096ac454d3d904002491fafe2ec",
               "type": "NS",
               "id": "f884912f-da69-494f-98e5-d8a8d76153b4",
               "name": "designate-example.com."
            }
         }