)]}'
{"neutron_lbaas/services/loadbalancer/agent/v2/agent_device_driver.py":[{"author":{"_account_id":11302,"name":"Phillip Toohill","email":"phillip.toohill@rackspace.com","username":"ptoohill1"},"change_message_id":"834ead295f4d5b72ff07effe8f3776db837daac6","unresolved":false,"context_lines":[{"line_number":80,"context_line":"    @abc.abstractmethod"},{"line_number":81,"context_line":"    def delete_member(self, member):"},{"line_number":82,"context_line":"        pass"},{"line_number":83,"context_line":""},{"line_number":84,"context_line":"    @abc.abstractmethod"},{"line_number":85,"context_line":"    def create_pool_health_monitor(self, health_monitor, pool_id):"},{"line_number":86,"context_line":"        pass"}],"source_content_type":"text/x-python","patch_set":2,"id":"da86d52c_476f2afc","line":83,"updated":"2015-02-12 04:29:26.000000000","message":"I believe we no longer have to reference the pool id when creating a health monitor. There would also be no more associations to worry about and the methods could simply be labled {CUD}_health_monitor.\n\nThis applies to the following health monitor operations.","commit_id":"872273efa028c6fa0b53bcd6d28738bd6d6df9ea"},{"author":{"_account_id":10850,"name":"German Eichberger","email":"german.eichberger@gmail.com","username":"german"},"change_message_id":"fc2d41bb17d06c16b4854380cd45a0c6102e9fe1","unresolved":false,"context_lines":[{"line_number":80,"context_line":"    @abc.abstractmethod"},{"line_number":81,"context_line":"    def delete_member(self, member):"},{"line_number":82,"context_line":"        pass"},{"line_number":83,"context_line":""},{"line_number":84,"context_line":"    @abc.abstractmethod"},{"line_number":85,"context_line":"    def create_pool_health_monitor(self, health_monitor, pool_id):"},{"line_number":86,"context_line":"        pass"}],"source_content_type":"text/x-python","patch_set":2,"id":"da86d52c_23f3b3a0","line":83,"in_reply_to":"da86d52c_476f2afc","updated":"2015-02-13 18:40:17.000000000","message":"sorry, this is confusing me: the data model still has the healthmonitor hanging on a pool...","commit_id":"872273efa028c6fa0b53bcd6d28738bd6d6df9ea"}],"neutron_lbaas/services/loadbalancer/agent/v2/agent_manager.py":[{"author":{"_account_id":11302,"name":"Phillip Toohill","email":"phillip.toohill@rackspace.com","username":"ptoohill1"},"change_message_id":"834ead295f4d5b72ff07effe8f3776db837daac6","unresolved":false,"context_lines":[{"line_number":292,"context_line":"    def delete_member(self, context, member):"},{"line_number":293,"context_line":"        driver \u003d self._get_driver(member[\u0027pool_id\u0027])"},{"line_number":294,"context_line":"        driver.delete_member(member)"},{"line_number":295,"context_line":""},{"line_number":296,"context_line":"    def create_pool_health_monitor(self, context, health_monitor, pool_id):"},{"line_number":297,"context_line":"        driver \u003d self._get_driver(pool_id)"},{"line_number":298,"context_line":"        assoc_id \u003d {\u0027pool_id\u0027: pool_id, \u0027monitor_id\u0027: health_monitor[\u0027id\u0027]}"}],"source_content_type":"text/x-python","patch_set":2,"id":"da86d52c_0769b2f8","line":295,"updated":"2015-02-12 04:29:26.000000000","message":"I believe we no longer have to reference the pool id when creating a health monitor. There would also be no more associations to worry about and the methods could simply be labled {CUD}_health_monitor.\n\nThis applies to the following health monitor operations.","commit_id":"872273efa028c6fa0b53bcd6d28738bd6d6df9ea"}]}