)]}'
{"specs/mitaka/approved/pluggable-scheduler-reporting.rst":[{"author":{"_account_id":17139,"name":"Chuck Carmack","email":"carmack@us.ibm.com","username":"ccarmack"},"change_message_id":"8a98224c6c4f8a24cbd5f9207987dd95508b0cda","unresolved":false,"context_lines":[{"line_number":124,"context_line":"---------------------"},{"line_number":125,"context_line":""},{"line_number":126,"context_line":"Additional configuration options will be added to configure which"},{"line_number":127,"context_line":"SchedulerReport drivers are used. Deployers may need to be aware of these"},{"line_number":128,"context_line":"options as new drivers and experimental schedulers are added. This change"},{"line_number":129,"context_line":"will have no immidiate impact after merged. New drivers and schedulers"},{"line_number":130,"context_line":"will have to be explicitly enabled."}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a29b11f_480df635","line":127,"updated":"2015-10-20 20:25:02.000000000","message":"Drivers or one driver?\n\nWould these config options exist on both the scheduling node and the compute nodes?","commit_id":"af724979a3f587400252562cef8151ef3ed762c5"},{"author":{"_account_id":18247,"name":"Mark Doffman","email":"mdoffman@linux.vnet.ibm.com","username":"doffm"},"change_message_id":"78150ea8e812c3bc645e85aabd6914c87b71e0dc","unresolved":false,"context_lines":[{"line_number":124,"context_line":"---------------------"},{"line_number":125,"context_line":""},{"line_number":126,"context_line":"Additional configuration options will be added to configure which"},{"line_number":127,"context_line":"SchedulerReport drivers are used. Deployers may need to be aware of these"},{"line_number":128,"context_line":"options as new drivers and experimental schedulers are added. This change"},{"line_number":129,"context_line":"will have no immidiate impact after merged. New drivers and schedulers"},{"line_number":130,"context_line":"will have to be explicitly enabled."}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a29b11f_c8ffc6a8","line":127,"in_reply_to":"3a29b11f_480df635","updated":"2015-10-20 20:34:27.000000000","message":"Config options would only exist on the compute nodes. BUT config options already exist for which scheduler to use. These would generally be modified in conjunction.","commit_id":"af724979a3f587400252562cef8151ef3ed762c5"},{"author":{"_account_id":18247,"name":"Mark Doffman","email":"mdoffman@linux.vnet.ibm.com","username":"doffm"},"change_message_id":"4138ae5c03a1008b92748ff5c976eb8b535e5677","unresolved":false,"context_lines":[{"line_number":124,"context_line":"---------------------"},{"line_number":125,"context_line":""},{"line_number":126,"context_line":"Additional configuration options will be added to configure which"},{"line_number":127,"context_line":"SchedulerReport drivers are used. Deployers may need to be aware of these"},{"line_number":128,"context_line":"options as new drivers and experimental schedulers are added. This change"},{"line_number":129,"context_line":"will have no immidiate impact after merged. New drivers and schedulers"},{"line_number":130,"context_line":"will have to be explicitly enabled."}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a29b11f_c8a6e652","line":127,"in_reply_to":"3a29b11f_480df635","updated":"2015-10-20 20:44:36.000000000","message":"I have the crazy idea that its actually \u0027drivers\u0027 as multiple could be used in an upgrade scenario, but still need to think about that.","commit_id":"af724979a3f587400252562cef8151ef3ed762c5"},{"author":{"_account_id":17139,"name":"Chuck Carmack","email":"carmack@us.ibm.com","username":"ccarmack"},"change_message_id":"8a98224c6c4f8a24cbd5f9207987dd95508b0cda","unresolved":false,"context_lines":[{"line_number":126,"context_line":"Additional configuration options will be added to configure which"},{"line_number":127,"context_line":"SchedulerReport drivers are used. Deployers may need to be aware of these"},{"line_number":128,"context_line":"options as new drivers and experimental schedulers are added. This change"},{"line_number":129,"context_line":"will have no immidiate impact after merged. New drivers and schedulers"},{"line_number":130,"context_line":"will have to be explicitly enabled."},{"line_number":131,"context_line":""},{"line_number":132,"context_line":"Methods will be made available for continuous deployment and upgrade. The"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a29b11f_6d2c8402","line":129,"updated":"2015-10-20 20:25:02.000000000","message":"typo on immediate","commit_id":"af724979a3f587400252562cef8151ef3ed762c5"},{"author":{"_account_id":17139,"name":"Chuck Carmack","email":"carmack@us.ibm.com","username":"ccarmack"},"change_message_id":"8a98224c6c4f8a24cbd5f9207987dd95508b0cda","unresolved":false,"context_lines":[{"line_number":133,"context_line":"plan is to allow multiple reporting drivers to be enabled. This way compute"},{"line_number":134,"context_line":"nodes can be upgraded in a rolling manner while the scheduler remains on"},{"line_number":135,"context_line":"an older version. When all compute nodes have been upgraded schedulers using"},{"line_number":136,"context_line":"the new reporting methods can be deployed."},{"line_number":137,"context_line":""},{"line_number":138,"context_line":"Developer impact"},{"line_number":139,"context_line":"----------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a29b11f_8d99e021","line":136,"updated":"2015-10-20 20:25:02.000000000","message":"There might be some database impact to store the scheduler driver versions on the compute nodes.  Dan Smith can help here.  There might be some automation possible - like automatically using the new reporting driver in the scheduler once all the compute nodes are updated.","commit_id":"af724979a3f587400252562cef8151ef3ed762c5"},{"author":{"_account_id":18247,"name":"Mark Doffman","email":"mdoffman@linux.vnet.ibm.com","username":"doffm"},"change_message_id":"78150ea8e812c3bc645e85aabd6914c87b71e0dc","unresolved":false,"context_lines":[{"line_number":133,"context_line":"plan is to allow multiple reporting drivers to be enabled. This way compute"},{"line_number":134,"context_line":"nodes can be upgraded in a rolling manner while the scheduler remains on"},{"line_number":135,"context_line":"an older version. When all compute nodes have been upgraded schedulers using"},{"line_number":136,"context_line":"the new reporting methods can be deployed."},{"line_number":137,"context_line":""},{"line_number":138,"context_line":"Developer impact"},{"line_number":139,"context_line":"----------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a29b11f_08e4de0a","line":136,"in_reply_to":"3a29b11f_8d99e021","updated":"2015-10-20 20:34:27.000000000","message":"I guess the upgrade scenario isn\u0027t fleshed out. But the general idea would be to use BOTH reporting methods for a period of time. This should be safe as reporting should be idempotent.","commit_id":"af724979a3f587400252562cef8151ef3ed762c5"},{"author":{"_account_id":17139,"name":"Chuck Carmack","email":"carmack@us.ibm.com","username":"ccarmack"},"change_message_id":"8a98224c6c4f8a24cbd5f9207987dd95508b0cda","unresolved":false,"context_lines":[{"line_number":158,"context_line":" * Create the initial SchedulerReport driver that makes use of the"},{"line_number":159,"context_line":"   SchedulerClient API."},{"line_number":160,"context_line":""},{"line_number":161,"context_line":" * Switch to using the SchedulerReport API throughout the nova codebase."},{"line_number":162,"context_line":""},{"line_number":163,"context_line":"Dependencies"},{"line_number":164,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a29b11f_cd8fd8ca","line":161,"updated":"2015-10-20 20:25:02.000000000","message":"Would devstack be switched to the new driver?","commit_id":"af724979a3f587400252562cef8151ef3ed762c5"},{"author":{"_account_id":18247,"name":"Mark Doffman","email":"mdoffman@linux.vnet.ibm.com","username":"doffm"},"change_message_id":"78150ea8e812c3bc645e85aabd6914c87b71e0dc","unresolved":false,"context_lines":[{"line_number":158,"context_line":" * Create the initial SchedulerReport driver that makes use of the"},{"line_number":159,"context_line":"   SchedulerClient API."},{"line_number":160,"context_line":""},{"line_number":161,"context_line":" * Switch to using the SchedulerReport API throughout the nova codebase."},{"line_number":162,"context_line":""},{"line_number":163,"context_line":"Dependencies"},{"line_number":164,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a29b11f_888c6e36","line":161,"in_reply_to":"3a29b11f_cd8fd8ca","updated":"2015-10-20 20:34:27.000000000","message":"Yes. Devstack shouldn\u0027t change as the default driver would use the existing rpc / database implementation.","commit_id":"af724979a3f587400252562cef8151ef3ed762c5"}]}