)]}'
{"nova/conf/scheduler.py":[{"author":{"_account_id":7111,"name":"hadi esiely","email":"hadi.esiely-barrera@jhuapl.edu","username":"HEsiely"},"change_message_id":"12f3c7cccd60042f67e331701766545235b4222c","unresolved":false,"context_lines":[{"line_number":244,"context_line":"        help\u003d\"\"\""},{"line_number":245,"context_line":"The scheduler host manager class to use. Aside from the default, the other"},{"line_number":246,"context_line":"option currently is \u0027nova.scheduler.ironic_host_manager.IronicHostManager\u0027,"},{"line_number":247,"context_line":"which should be used if you\u0027re using Ironic to provision bare-metal instances."},{"line_number":248,"context_line":""},{"line_number":249,"context_line":"* Services that use this:"},{"line_number":250,"context_line":""}],"source_content_type":"text/x-python","patch_set":1,"id":"7a740942_c10290b4","line":247,"updated":"2015-12-09 23:04:24.000000000","message":"Does it make sense to specify \"currently\" when explaining the IronicHostManager as the other option? If there is no assurance that these doc strings will be updated if another host manager were to be added I think mentioning the specific name release of Nova for which this statement is true would be the way to go. Otherwise it risks providing wrong information if this were to change in the future.\n\ni.e.:\n\"\u003c...\u003e the other option as of the Mitaka-X release is \u003c...\u003e\"","commit_id":"45b4c350c984bfb83fdc33bef415974ed5f263ab"},{"author":{"_account_id":1063,"name":"Ed Leafe","email":"ed@leafe.com","username":"ed-leafe"},"change_message_id":"61feced4a561b93fb193fd5dbd0f2add4aead1b2","unresolved":false,"context_lines":[{"line_number":244,"context_line":"        help\u003d\"\"\""},{"line_number":245,"context_line":"The scheduler host manager class to use. Aside from the default, the other"},{"line_number":246,"context_line":"option currently is \u0027nova.scheduler.ironic_host_manager.IronicHostManager\u0027,"},{"line_number":247,"context_line":"which should be used if you\u0027re using Ironic to provision bare-metal instances."},{"line_number":248,"context_line":""},{"line_number":249,"context_line":"* Services that use this:"},{"line_number":250,"context_line":""}],"source_content_type":"text/x-python","patch_set":1,"id":"7a740942_547cebb4","line":247,"in_reply_to":"7a740942_c10290b4","updated":"2015-12-10 17:59:57.000000000","message":"Good point about docs getting stale. I like the \u0027as of the Mitaka release\u0027 wording.","commit_id":"45b4c350c984bfb83fdc33bef415974ed5f263ab"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"6386e127392caadfcf4c645b651758ce84414d2a","unresolved":false,"context_lines":[{"line_number":249,"context_line":""},{"line_number":250,"context_line":"* Services that use this:"},{"line_number":251,"context_line":""},{"line_number":252,"context_line":"    ``nova-scheduler``"},{"line_number":253,"context_line":""},{"line_number":254,"context_line":"* Related options:"},{"line_number":255,"context_line":""}],"source_content_type":"text/x-python","patch_set":3,"id":"7a740942_47cc14bb","line":252,"updated":"2015-12-11 11:22:32.000000000","message":"I\u0027ve done this for my own changes, per markus_z\u0027s suggestions, but this is going to get out of date exceptionally quickly. Can we not autogenerate this via introspection or whatnot?","commit_id":"25ad6d3b865fba5248686a6a2b0b65af8d5f8024"},{"author":{"_account_id":2271,"name":"Michael Still","email":"mikal@stillhq.com","username":"mikalstill"},"change_message_id":"6d6a2d9448c8ccee4da3c6ba89859ece6cf9f732","unresolved":false,"context_lines":[{"line_number":310,"context_line":"of the available physical disk, which can be useful for more efficiently"},{"line_number":311,"context_line":"packing instances on a host with compressed images. It can be set to a value"},{"line_number":312,"context_line":"between 0.0 and 1.0 in order to preserve a percentage of the disk for uses"},{"line_number":313,"context_line":"other than instances."},{"line_number":314,"context_line":""},{"line_number":315,"context_line":"This option is only used by the FilterScheduler and its subclasses; if you use"},{"line_number":316,"context_line":"a different scheduler, this option has no effect."}],"source_content_type":"text/x-python","patch_set":6,"id":"9a68dd71_e5480330","line":313,"updated":"2016-01-20 18:24:39.000000000","message":"You should mention sparse images here as well perhaps? i.e. setting this to something more than 1.0 implies that you know that instances are not going to use their entire virtual disk allocation.","commit_id":"a0e30bf05988f4a2c87ff1c97df218c125f98ed3"},{"author":{"_account_id":1063,"name":"Ed Leafe","email":"ed@leafe.com","username":"ed-leafe"},"change_message_id":"7a409171c52f4f4bb357d13c2633008d954cab84","unresolved":false,"context_lines":[{"line_number":310,"context_line":"of the available physical disk, which can be useful for more efficiently"},{"line_number":311,"context_line":"packing instances on a host with compressed images. It can be set to a value"},{"line_number":312,"context_line":"between 0.0 and 1.0 in order to preserve a percentage of the disk for uses"},{"line_number":313,"context_line":"other than instances."},{"line_number":314,"context_line":""},{"line_number":315,"context_line":"This option is only used by the FilterScheduler and its subclasses; if you use"},{"line_number":316,"context_line":"a different scheduler, this option has no effect."}],"source_content_type":"text/x-python","patch_set":6,"id":"9a68dd71_d2a8a88f","line":313,"in_reply_to":"9a68dd71_e5480330","updated":"2016-01-22 16:56:56.000000000","message":"Done","commit_id":"a0e30bf05988f4a2c87ff1c97df218c125f98ed3"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"2c1d32417e727a17356d453119401e1088dc177c","unresolved":false,"context_lines":[{"line_number":272,"context_line":""},{"line_number":273,"context_line":"    * \u0027nova.scheduler.caching_scheduler.CachingScheduler\u0027 which aggressively"},{"line_number":274,"context_line":"    caches the system state for better individual scheduler performance at"},{"line_number":275,"context_line":"    the risk of more retries when running multiple schedulers."},{"line_number":276,"context_line":""},{"line_number":277,"context_line":"    * \u0027nova.scheduler.chance.ChanceScheduler\u0027 which simply picks a host at"},{"line_number":278,"context_line":"    random."}],"source_content_type":"text/x-python","patch_set":9,"id":"7a5de9d1_455e7613","line":275,"updated":"2016-01-28 16:24:43.000000000","message":"It doesn\u0027t work at all with multiple schedulers. Well nor does the regular scheduler, really. But lets sort that later.","commit_id":"a943c8b833b40b81d08b6330903f7c7bca3ca6cf"}]}