)]}'
{"doc/source/user/cellsv2_layout.rst":[{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"68b272978798c6f12595bf54e7e9afbef59c247b","unresolved":false,"context_lines":[{"line_number":307,"context_line":"- Scheduler instance info reporting from the compute nodes"},{"line_number":308,"context_line":"- The late anti-affinity check"},{"line_number":309,"context_line":""},{"line_number":310,"context_line":"The first is simple: if you boot an instance, it gets scheduled to a"},{"line_number":311,"context_line":"compute node, fails, it would normally be re-scheduled to another"},{"line_number":312,"context_line":"node. That requires scheduler intervention and thus it will not work"},{"line_number":313,"context_line":"in Pike with a multi-cell layout. If you do not rely on reschedules"},{"line_number":314,"context_line":"for covering up transient compute-node failures, then this will not"},{"line_number":315,"context_line":"affect you."},{"line_number":316,"context_line":""},{"line_number":317,"context_line":"The second two are related. The summary is that some of the facilities"},{"line_number":318,"context_line":"that Nova has for ensuring that affinty/anti-affinity is preserved"}],"source_content_type":"text/x-rst","patch_set":1,"id":"df3967d1_e96af417","line":315,"range":{"start_line":310,"start_character":0,"end_line":315,"end_character":11},"updated":"2017-08-03 18:17:17.000000000","message":"We could mention considering setting [scheduler]/max_attempts\u003d1 to avoid any noise or confusion in the logs when a retry does not work.","commit_id":"c3f30347231df68243f00c5e22522be28fc54416"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"68b272978798c6f12595bf54e7e9afbef59c247b","unresolved":false,"context_lines":[{"line_number":317,"context_line":"The second two are related. The summary is that some of the facilities"},{"line_number":318,"context_line":"that Nova has for ensuring that affinty/anti-affinity is preserved"},{"line_number":319,"context_line":"between instances does not function in Pike with a multi-cell"},{"line_number":320,"context_line":"layout. If you don\u0027t use (or depend on perfect) affinity operations,"},{"line_number":321,"context_line":"then this will not affect you."}],"source_content_type":"text/x-rst","patch_set":1,"id":"df3967d1_c9fa9041","line":321,"range":{"start_line":320,"start_character":8,"end_line":321,"end_character":30},"updated":"2017-08-03 18:17:17.000000000","message":"A couple of things we could mention here if we wanted:\n\n1. You should set [workarounds]/disable_group_policy_check_upcall\u003dTrue.\n\n2. The \"or depend on perfect\" part is a bit confusing since Tempest does run a test using the ServerGroupAffinityFilter and it passes in the multi-node job, so either we\u0027re just getting lucky there or it\u0027s less of an issue than we think. The ServerGroupAntiAffinityFilter seems to be more problematic, and I\u0027m testing and trying to debug that here:\n\nhttps://review.openstack.org/#/c/489754/\n\nI\u0027m not sure why the affinity stuff would work but anti-affinity wouldn\u0027t.\n\nNot sure if we want to mention something about checking your [scheduler]/enabled_filters options since the affinity/anti-affinity filters are enabled by default. There is additional complexity if you do that because users could create affinity/anti-affinity server groups but they won\u0027t be enforced, so an operator that doesn\u0027t care and disables those scheduler filters may want to also consider disabling the server groups create API by changing os_compute_api:os-server-groups:create?\n\nThis gets pretty weird given how much configuration is involved in trying to make things work, like the [filter_scheduler]/track_instance_changes option too.","commit_id":"c3f30347231df68243f00c5e22522be28fc54416"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"0b94ba3fe6a58dab24319761f13eadfdb2edf472","unresolved":false,"context_lines":[{"line_number":317,"context_line":"The second two are related. The summary is that some of the facilities"},{"line_number":318,"context_line":"that Nova has for ensuring that affinty/anti-affinity is preserved"},{"line_number":319,"context_line":"between instances does not function in Pike with a multi-cell"},{"line_number":320,"context_line":"layout. If you don\u0027t use (or depend on perfect) affinity operations,"},{"line_number":321,"context_line":"then this will not affect you."}],"source_content_type":"text/x-rst","patch_set":1,"id":"df3967d1_fcfab472","line":321,"range":{"start_line":320,"start_character":8,"end_line":321,"end_character":30},"in_reply_to":"df3967d1_5c0b00d5","updated":"2017-08-03 18:37:12.000000000","message":"I\u0027d probably hedge \"If you depend on this, don\u0027t expect it to work\" with at least \"don\u0027t expect it to work with server multi-create requests\".","commit_id":"c3f30347231df68243f00c5e22522be28fc54416"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"7d8802ad8a7e27689fa1a2fdc0173973fc113feb","unresolved":false,"context_lines":[{"line_number":317,"context_line":"The second two are related. The summary is that some of the facilities"},{"line_number":318,"context_line":"that Nova has for ensuring that affinty/anti-affinity is preserved"},{"line_number":319,"context_line":"between instances does not function in Pike with a multi-cell"},{"line_number":320,"context_line":"layout. If you don\u0027t use (or depend on perfect) affinity operations,"},{"line_number":321,"context_line":"then this will not affect you."}],"source_content_type":"text/x-rst","patch_set":1,"id":"df3967d1_5c0b00d5","line":321,"range":{"start_line":320,"start_character":8,"end_line":321,"end_character":30},"in_reply_to":"df3967d1_c9fa9041","updated":"2017-08-03 18:26:03.000000000","message":"Right, I think affinity and anti-affinity should \"work\" if you do it slowly, like boot an instance, then wait until it\u0027s done, and then boot another with some sort of affinity. I think the place it breaks down is booting two in parallel with some policy. That\u0027s the thing the upcall is intended to verify, at least. So,  I can just take out the \"(or depend on perfect)\" part and just say: If you depend on this, don\u0027t expect it to work\". I surely don\u0027t want this to be a page-long analysis of that issue.","commit_id":"c3f30347231df68243f00c5e22522be28fc54416"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"ad5a2f1d0328ca88782ec924e1a7077e74f3198a","unresolved":false,"context_lines":[{"line_number":304,"context_line":"following:"},{"line_number":305,"context_line":""},{"line_number":306,"context_line":"- Instance reschedules during boot"},{"line_number":307,"context_line":"- Scheduler instance info reporting from the compute nodes"},{"line_number":308,"context_line":"- The late anti-affinity check"},{"line_number":309,"context_line":""},{"line_number":310,"context_line":"The first is simple: if you boot an instance, it gets scheduled to a"}],"source_content_type":"text/x-rst","patch_set":2,"id":"df3967d1_35b84fe3","line":307,"updated":"2017-08-03 20:22:02.000000000","message":"Reading this makes me wonder, what is missing here? Obviously we have some instance info reporting from compute nodes (allocations, others?) that works fine, but something is missing related to affinity?\n\nI understand we\u0027re trying to keep things simple but this sentence seems super broad and I can\u0027t imagine what it\u0027s talking about.","commit_id":"b8cc885ff9e602fcc117d96ee0b25f2a68a3cca0"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"78756249172ad918003d48b2d33c1bdd381e7041","unresolved":false,"context_lines":[{"line_number":304,"context_line":"following:"},{"line_number":305,"context_line":""},{"line_number":306,"context_line":"- Instance reschedules during boot"},{"line_number":307,"context_line":"- Scheduler instance info reporting from the compute nodes"},{"line_number":308,"context_line":"- The late anti-affinity check"},{"line_number":309,"context_line":""},{"line_number":310,"context_line":"The first is simple: if you boot an instance, it gets scheduled to a"}],"source_content_type":"text/x-rst","patch_set":2,"id":"df3967d1_353defdc","line":307,"in_reply_to":"df3967d1_35b84fe3","updated":"2017-08-03 20:49:35.000000000","message":"The second paragraph below doesn\u0027t help?\n\nOtherwise see my comments in an earlier patchset about the same thing - we risk over-documenting the issue here if we go into too much detail.","commit_id":"b8cc885ff9e602fcc117d96ee0b25f2a68a3cca0"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"8368ce0394470896415b0ea0842829de0f31b204","unresolved":false,"context_lines":[{"line_number":322,"context_line":"affect you. To make sure you don\u0027t make futile attempts at the"},{"line_number":323,"context_line":"affinity check, you should set"},{"line_number":324,"context_line":"``[workarounds]/disable_group_policy_check_upcall\u003dTrue`` in"},{"line_number":325,"context_line":"``nova.conf`` and ``[scheduler]/track_instance_changes\u003dFalse``."}],"source_content_type":"text/x-rst","patch_set":3,"id":"df3967d1_10de796c","line":325,"range":{"start_line":325,"start_character":21,"end_line":325,"end_character":30},"updated":"2017-08-03 20:59:18.000000000","message":"filter_scheduler!\n\nAlso: https://review.openstack.org/#/c/490627/","commit_id":"83ada5c230165c234f441a25509ef90e978b16f2"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"5eb9f2d09a5e8fba62e860f8bd8e93b686590869","unresolved":false,"context_lines":[{"line_number":321,"context_line":"layout. If you don\u0027t use affinity operations, then this will not"},{"line_number":322,"context_line":"affect you. To make sure you don\u0027t make futile attempts at the"},{"line_number":323,"context_line":"affinity check, you should set"},{"line_number":324,"context_line":"``[workarounds]/disable_group_policy_check_upcall\u003dTrue`` in"},{"line_number":325,"context_line":"``nova.conf`` and"},{"line_number":326,"context_line":"``[filter_scheduler]/track_instance_changes\u003dFalse``."}],"source_content_type":"text/x-rst","patch_set":4,"id":"df3967d1_b0420daa","line":325,"range":{"start_line":324,"start_character":57,"end_line":325,"end_character":13},"updated":"2017-08-03 21:20:18.000000000","message":"this should really probably come after mentioning both of the options...","commit_id":"c3fa4b1f4c7da9b6273d7c458e0385ed6b8b09b5"}]}