)]}'
{"doc/source/placement.rst":[{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"e2a47d40d9e849147183460072f3e771fd026b3f","unresolved":false,"context_lines":[{"line_number":190,"context_line":"~~~~~~~~~~~~~"},{"line_number":191,"context_line":""},{"line_number":192,"context_line":"* The ``nova.scheduler.filter_scheduler.FilterScheduler`` in Pike will"},{"line_number":193,"context_line":"  no longer fall back to not using the PlacementService, even if older"},{"line_number":194,"context_line":"  computes are running in the deployment."},{"line_number":195,"context_line":""},{"line_number":196,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"da36d5c6_bccacb9f","line":193,"range":{"start_line":193,"start_character":39,"end_line":193,"end_character":55},"updated":"2017-02-20 21:00:33.000000000","message":"nit: Placement service","commit_id":"f4286b62f9b87f42b6f84966037d0693d36659c8"}],"nova/scheduler/filter_scheduler.py":[{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"4036b430940bc2becd7a1d445b06bc42be542e94","unresolved":false,"context_lines":[{"line_number":167,"context_line":"        \"\"\"Template method, so a subclass can implement caching.\"\"\""},{"line_number":168,"context_line":"        filters \u003d {\u0027resources\u0027: self._get_resources_per_request_spec(spec_obj)}"},{"line_number":169,"context_line":"        reportclient \u003d self.scheduler_client.reportclient"},{"line_number":170,"context_line":"        rps \u003d reportclient.get_filtered_resource_providers(filters)"},{"line_number":171,"context_line":"        # NOTE(sbauza): In case the Placement service is not running yet or"},{"line_number":172,"context_line":"        # when returning an exception, we wouldn\u0027t get any ResourceProviders."},{"line_number":173,"context_line":"        # If so, let\u0027s return an empty list so _schedule would raise a"},{"line_number":174,"context_line":"        # NoValidHosts."},{"line_number":175,"context_line":"        if not rps:"},{"line_number":176,"context_line":"            return []"},{"line_number":177,"context_line":"        compute_uuids \u003d [rp.uuid for rp in rps]"},{"line_number":178,"context_line":"        return self.host_manager.get_host_states_by_uuids(context,"},{"line_number":179,"context_line":"                                                          compute_uuids)"}],"source_content_type":"text/x-python","patch_set":4,"id":"ba2be162_c7fa0abd","line":176,"range":{"start_line":170,"start_character":8,"end_line":176,"end_character":21},"updated":"2017-03-02 13:20:22.000000000","message":"This will also happen if placement is from newton and the 1.4 microversion isn\u0027t available. In Pike we need to require that placement is at least new enough to provide 1.4. We can build that into nova-status.","commit_id":"c604a6cf16441458df79654cb2cfbb551fa7d0b7"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"2667a08230b80488a5a1775d78e2b035404cb1f5","unresolved":false,"context_lines":[{"line_number":167,"context_line":"        \"\"\"Template method, so a subclass can implement caching.\"\"\""},{"line_number":168,"context_line":"        filters \u003d {\u0027resources\u0027: self._get_resources_per_request_spec(spec_obj)}"},{"line_number":169,"context_line":"        reportclient \u003d self.scheduler_client.reportclient"},{"line_number":170,"context_line":"        rps \u003d reportclient.get_filtered_resource_providers(filters)"},{"line_number":171,"context_line":"        # NOTE(sbauza): In case the Placement service is not running yet or"},{"line_number":172,"context_line":"        # when returning an exception, we wouldn\u0027t get any ResourceProviders."},{"line_number":173,"context_line":"        # If so, let\u0027s return an empty list so _schedule would raise a"},{"line_number":174,"context_line":"        # NoValidHosts."},{"line_number":175,"context_line":"        if not rps:"},{"line_number":176,"context_line":"            return []"},{"line_number":177,"context_line":"        compute_uuids \u003d [rp.uuid for rp in rps]"},{"line_number":178,"context_line":"        return self.host_manager.get_host_states_by_uuids(context,"},{"line_number":179,"context_line":"                                                          compute_uuids)"}],"source_content_type":"text/x-python","patch_set":4,"id":"ba2be162_a7eb56af","line":176,"range":{"start_line":170,"start_character":8,"end_line":176,"end_character":21},"in_reply_to":"ba2be162_c7fa0abd","updated":"2017-03-02 13:25:18.000000000","message":"https://bugs.launchpad.net/nova/+bug/1669433","commit_id":"c604a6cf16441458df79654cb2cfbb551fa7d0b7"}],"releasenotes/notes/no-placement-fallback-5db2d0645f51aca8.yaml":[{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"89dc10fb23c49ec5665f2b39beafa5da139db8fe","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"deprecations:"},{"line_number":3,"context_line":"  - In Ocata, the nova-scheduler would fall back to not calling the"},{"line_number":4,"context_line":"    placement service during instance boot if old computes were"},{"line_number":5,"context_line":"    running. That compatibility mode is no longer present in Pike, and"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"da36d5c6_7995c5e2","line":2,"range":{"start_line":2,"start_character":0,"end_line":2,"end_character":12},"updated":"2017-02-20 20:50:51.000000000","message":"This is for deprecating something, which we aren\u0027t doing. This should be the \u0027upgrades\u0027 section.\n\n--\n\nAlso, while this is fresh in our minds, let\u0027s add a Pike 16.0.0 section in the Placement devref here:\n\nhttps://docs.openstack.org/developer/nova/placement.html#ocata-15-0-0\n\ne.g. note the 2nd bullet in the Ocata notes, we can reinforce that in a Pike 16.0.0 section in that devref.","commit_id":"a66a7acb86af9c78ef82837e06f1fd022c862e6b"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"89dc10fb23c49ec5665f2b39beafa5da139db8fe","unresolved":false,"context_lines":[{"line_number":3,"context_line":"  - In Ocata, the nova-scheduler would fall back to not calling the"},{"line_number":4,"context_line":"    placement service during instance boot if old computes were"},{"line_number":5,"context_line":"    running. That compatibility mode is no longer present in Pike, and"},{"line_number":6,"context_line":"    as such, the scheduler fully depends on the placement service."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"da36d5c6_d9bb1171","line":6,"range":{"start_line":6,"start_character":17,"end_line":6,"end_character":26},"updated":"2017-02-20 20:50:51.000000000","message":"We could nit pick on filter vs caching scheduler, but best to pretend that it\u0027s required globally.","commit_id":"a66a7acb86af9c78ef82837e06f1fd022c862e6b"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"9e78fa301a0ccfc272629b5171373d0b3a144b63","unresolved":false,"context_lines":[{"line_number":3,"context_line":"  - In Ocata, the nova-scheduler would fall back to not calling the"},{"line_number":4,"context_line":"    placement service during instance boot if old computes were"},{"line_number":5,"context_line":"    running. That compatibility mode is no longer present in Pike, and"},{"line_number":6,"context_line":"    as such, the scheduler fully depends on the placement service."}],"source_content_type":"text/x-yaml","patch_set":4,"id":"da36d5c6_67e99c1a","line":6,"range":{"start_line":6,"start_character":12,"end_line":6,"end_character":66},"updated":"2017-02-20 21:33:04.000000000","message":"well, that\u0027s not true for other scheduler drivers but the FilterScheduler. The CachingScheduler does not, neither the ChanceScheduler. Leaving that phrase would scare lots of people, at least those using CachingScheduler for performance reasons.","commit_id":"c604a6cf16441458df79654cb2cfbb551fa7d0b7"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"25696e1ba74a5718effdc8d9be4c697e4e151ac9","unresolved":false,"context_lines":[{"line_number":3,"context_line":"  - In Ocata, the nova-scheduler would fall back to not calling the"},{"line_number":4,"context_line":"    placement service during instance boot if old computes were"},{"line_number":5,"context_line":"    running. That compatibility mode is no longer present in Pike, and"},{"line_number":6,"context_line":"    as such, the scheduler fully depends on the placement service."}],"source_content_type":"text/x-yaml","patch_set":4,"id":"da36d5c6_a7b0f4de","line":6,"range":{"start_line":6,"start_character":12,"end_line":6,"end_character":66},"in_reply_to":"da36d5c6_4753b8e1","updated":"2017-02-20 21:39:52.000000000","message":"Well, operators use the CachingScheduler for performance reasons, like I said. If we say \"now the scheduler is calling the placement API\", then they would wonder if that\u0027s all true or not and they could be scared.\n\nThat said, looks like a nit and I really don\u0027t want to block on that.","commit_id":"c604a6cf16441458df79654cb2cfbb551fa7d0b7"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"3f783af094b38e260d758c45794a3df4239eb5fe","unresolved":false,"context_lines":[{"line_number":3,"context_line":"  - In Ocata, the nova-scheduler would fall back to not calling the"},{"line_number":4,"context_line":"    placement service during instance boot if old computes were"},{"line_number":5,"context_line":"    running. That compatibility mode is no longer present in Pike, and"},{"line_number":6,"context_line":"    as such, the scheduler fully depends on the placement service."}],"source_content_type":"text/x-yaml","patch_set":4,"id":"da36d5c6_4753b8e1","line":6,"range":{"start_line":6,"start_character":12,"end_line":6,"end_character":66},"in_reply_to":"da36d5c6_67e99c1a","updated":"2017-02-20 21:34:06.000000000","message":"Yeah I pointed this out earlier, but figured it\u0027s better to hide the dirty details of this so we set expectations that placement is required and computes should be upgraded to use it.","commit_id":"c604a6cf16441458df79654cb2cfbb551fa7d0b7"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"c88cdf914f3fbbe30a91181e5e05436c6b782ec5","unresolved":false,"context_lines":[{"line_number":3,"context_line":"  - In Ocata, the nova-scheduler would fall back to not calling the"},{"line_number":4,"context_line":"    placement service during instance boot if old computes were"},{"line_number":5,"context_line":"    running. That compatibility mode is no longer present in Pike, and"},{"line_number":6,"context_line":"    as such, the scheduler fully depends on the placement service."}],"source_content_type":"text/x-yaml","patch_set":4,"id":"da36d5c6_a7e8f47d","line":6,"range":{"start_line":6,"start_character":12,"end_line":6,"end_character":66},"in_reply_to":"da36d5c6_a7b0f4de","updated":"2017-02-20 21:47:02.000000000","message":"Sure, but going forward we\u0027re going to be making assumptions in using Nova in Pike that computes are reporting into Placement and it\u0027s all required, we\u0027re going to probably forget that the caching scheduler doesn\u0027t use it yet, so I\u0027d rather just make the assumption it\u0027s there and required and being used. Plus part of the point of placement is to improve the performance of the filter scheduler, so hopefully it eventually replaces the need for the caching scheduler.","commit_id":"c604a6cf16441458df79654cb2cfbb551fa7d0b7"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"7a756320c2012d5f8139b9afd258e8c569948240","unresolved":false,"context_lines":[{"line_number":3,"context_line":"  - In Ocata, the nova-scheduler would fall back to not calling the"},{"line_number":4,"context_line":"    placement service during instance boot if old computes were"},{"line_number":5,"context_line":"    running. That compatibility mode is no longer present in Pike, and"},{"line_number":6,"context_line":"    as such, the scheduler fully depends on the placement service."}],"source_content_type":"text/x-yaml","patch_set":4,"id":"da36d5c6_e8f1b86b","line":6,"range":{"start_line":6,"start_character":12,"end_line":6,"end_character":66},"in_reply_to":"da36d5c6_a7e8f47d","updated":"2017-02-21 19:39:47.000000000","message":"Yeah, lets just ignore the details of this now.","commit_id":"c604a6cf16441458df79654cb2cfbb551fa7d0b7"}]}