)]}'
{"doc/source/user/cellsv2-layout.rst":[{"author":{"_account_id":10608,"name":"Matthew Edmonds","email":"edmondsw@us.ibm.com","username":"edmondsw"},"change_message_id":"7333786f0a9956c256305836e9e33db73e5229d3","unresolved":false,"context_lines":[{"line_number":371,"context_line":"top-level superconductor which would eliminate this AZ up-call check problem."},{"line_number":372,"context_line":""},{"line_number":373,"context_line":"The sixth is detailed in `bug 1781286`_ and similar to the first issue."},{"line_number":374,"context_line":"The issue is that for servers created without a specific availability zone"},{"line_number":375,"context_line":"will have their AZ calculated during a reschedule based on the alternate host"},{"line_number":376,"context_line":"selected. Determining the AZ for the alternate host requires an \"up call\" to"},{"line_number":377,"context_line":"the API DB."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f7c97a3_51330e62","line":374,"range":{"start_line":374,"start_character":18,"end_line":374,"end_character":22},"updated":"2018-07-13 18:18:36.000000000","message":"s/for //","commit_id":"9cd1e1dd1d3509943ec35d48ec86760deaf7b013"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"1e52bd14b0581096518d3513c1c8175a12b8c897","unresolved":false,"context_lines":[{"line_number":371,"context_line":"top-level superconductor which would eliminate this AZ up-call check problem."},{"line_number":372,"context_line":""},{"line_number":373,"context_line":"The sixth is detailed in `bug 1781286`_ and similar to the first issue."},{"line_number":374,"context_line":"The issue is that for servers created without a specific availability zone"},{"line_number":375,"context_line":"will have their AZ calculated during a reschedule based on the alternate host"},{"line_number":376,"context_line":"selected. Determining the AZ for the alternate host requires an \"up call\" to"},{"line_number":377,"context_line":"the API DB."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f7c97a3_28a8581f","line":374,"range":{"start_line":374,"start_character":18,"end_line":374,"end_character":22},"in_reply_to":"5f7c97a3_51330e62","updated":"2018-07-14 12:38:45.000000000","message":"Done","commit_id":"9cd1e1dd1d3509943ec35d48ec86760deaf7b013"},{"author":{"_account_id":5754,"name":"Alex Xu","email":"hejie.xu@intel.com","username":"xuhj"},"change_message_id":"5d7db61722f6bdbfe4734a2e6f31ad8b46d0fe4a","unresolved":false,"context_lines":[{"line_number":371,"context_line":"top-level superconductor which would eliminate this AZ up-call check problem."},{"line_number":372,"context_line":""},{"line_number":373,"context_line":"The sixth is detailed in `bug 1781286`_ and similar to the first issue."},{"line_number":374,"context_line":"The issue is that servers created without a specific availability zone"},{"line_number":375,"context_line":"will have their AZ calculated during a reschedule based on the alternate host"},{"line_number":376,"context_line":"selected. Determining the AZ for the alternate host requires an \"up call\" to"},{"line_number":377,"context_line":"the API DB."}],"source_content_type":"text/x-rst","patch_set":2,"id":"5f7c97a3_28e2fc9c","line":374,"range":{"start_line":374,"start_character":34,"end_line":374,"end_character":70},"updated":"2018-08-02 08:31:06.000000000","message":"emm...actually we re-calculated the AZ for every rescheduling just as the title of this patch https://review.openstack.org/#/c/446053/","commit_id":"1160ae7a6585c1567e2e91badb4c312533d15686"},{"author":{"_account_id":5754,"name":"Alex Xu","email":"hejie.xu@intel.com","username":"xuhj"},"change_message_id":"b739b84087213c7bfcd7c79a03475682d7c1ed07","unresolved":false,"context_lines":[{"line_number":371,"context_line":"top-level superconductor which would eliminate this AZ up-call check problem."},{"line_number":372,"context_line":""},{"line_number":373,"context_line":"The sixth is detailed in `bug 1781286`_ and similar to the first issue."},{"line_number":374,"context_line":"The issue is that servers created without a specific availability zone"},{"line_number":375,"context_line":"will have their AZ calculated during a reschedule based on the alternate host"},{"line_number":376,"context_line":"selected. Determining the AZ for the alternate host requires an \"up call\" to"},{"line_number":377,"context_line":"the API DB."}],"source_content_type":"text/x-rst","patch_set":2,"id":"5f7c97a3_1d0ba523","line":374,"range":{"start_line":374,"start_character":34,"end_line":374,"end_character":70},"in_reply_to":"5f7c97a3_0d9dcab8","updated":"2018-08-03 07:16:34.000000000","message":"oh, you are right, this only happens when rescheduling, I just read the code logic forget it only can be trigger by the rescheduling.","commit_id":"1160ae7a6585c1567e2e91badb4c312533d15686"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"a47dc4e5e702559abf3a1861a59fb2120cd87467","unresolved":false,"context_lines":[{"line_number":371,"context_line":"top-level superconductor which would eliminate this AZ up-call check problem."},{"line_number":372,"context_line":""},{"line_number":373,"context_line":"The sixth is detailed in `bug 1781286`_ and similar to the first issue."},{"line_number":374,"context_line":"The issue is that servers created without a specific availability zone"},{"line_number":375,"context_line":"will have their AZ calculated during a reschedule based on the alternate host"},{"line_number":376,"context_line":"selected. Determining the AZ for the alternate host requires an \"up call\" to"},{"line_number":377,"context_line":"the API DB."}],"source_content_type":"text/x-rst","patch_set":2,"id":"5f7c97a3_0d9dcab8","line":374,"range":{"start_line":374,"start_character":34,"end_line":374,"end_character":70},"in_reply_to":"5f7c97a3_28e2fc9c","updated":"2018-08-02 13:08:56.000000000","message":"I\u0027m not sure I\u0027m following you. This is the problem during a reschedule in a split MQ deployment where we\u0027re hitting the build_instances method in conductor:\n\nhttps://github.com/openstack/nova/blob/7125dcb9cb821faf3c68526ac34365a28141e480/nova/conductor/manager.py#L657\n\nWe\u0027ve got an alternate host for the reschedule but we make this up-call to determine the AZ for that alternate host, which is the issue I\u0027m documenting here. If the cell conductor doesn\u0027t have access to the API DB, that call will fail to get the host aggregates (which are in the API DB).","commit_id":"1160ae7a6585c1567e2e91badb4c312533d15686"}]}