)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":1653,"name":"garyk","email":"gkotton@vmware.com","username":"garyk"},"change_message_id":"e89b57180b9209a78e18b759a73f11ba4b2feab6","unresolved":false,"context_lines":[{"line_number":22,"context_line":"Hostname, on the other hand, is a kind of special and up until"},{"line_number":23,"context_line":"recently nova-compute manager would even delete all instances, if the"},{"line_number":24,"context_line":"hostname changed (see #1471887 for details). Thus, when running in"},{"line_number":25,"context_line":"active/passive mode nova-compute often has the same hostname (set"},{"line_number":26,"context_line":"by the means of `host\u0027 config option), no matter on which node of"},{"line_number":27,"context_line":"the OpenStack cluster it\u0027s currently running."},{"line_number":28,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"1a4dcd0f_bb8567d0","line":25,"updated":"2015-08-13 16:17:29.000000000","message":"in and active/active model this will cause race conditions with one compute node maybe aging an image and another spinning one up.\n\nWhy not use the value - https://github.com/openstack/nova/blob/master/nova/virt/vmwareapi/vmops.py#L65\n\nThat will work for the use case that you have here.\n\nThis has upgrade impact - that is if someone is using and version that has the my_ip support then that will cause the images to be reloaded - and not aged. So please add UpgradeImpact","commit_id":"96228f01444ca2cb48248a4280329ff84c9c4f74"},{"author":{"_account_id":6849,"name":"Roman Podoliaka","email":"roman.podoliaka@gmail.com","username":"rpodolyaka"},"change_message_id":"de7bfcba2feabe80d5b6462399022a27cff4b174","unresolved":false,"context_lines":[{"line_number":22,"context_line":"Hostname, on the other hand, is a kind of special and up until"},{"line_number":23,"context_line":"recently nova-compute manager would even delete all instances, if the"},{"line_number":24,"context_line":"hostname changed (see #1471887 for details). Thus, when running in"},{"line_number":25,"context_line":"active/passive mode nova-compute often has the same hostname (set"},{"line_number":26,"context_line":"by the means of `host\u0027 config option), no matter on which node of"},{"line_number":27,"context_line":"the OpenStack cluster it\u0027s currently running."},{"line_number":28,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"1a4dcd0f_d4181e21","line":25,"in_reply_to":"1a4dcd0f_bb8567d0","updated":"2015-08-14 09:45:59.000000000","message":"Thank you for the feedback, Gary!\n\nThat\u0027s a good point: I initially created this patch for stable/juno, which didn\u0027t have `cache_prefix\u0027 config option, which seems to be the best way to deal with this problem.","commit_id":"96228f01444ca2cb48248a4280329ff84c9c4f74"}]}