)]}'
{"specs/liberty/approved/default-disable-compute.rst":[{"author":{"_account_id":2033,"name":"Belmiro Moreira","email":"moreira.belmiro.email.lists@gmail.com","username":"moreira-belmiro-email-lists"},"change_message_id":"06dfdbda4450ed694b154c2be22b851fef54457d","unresolved":false,"context_lines":[{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Operators prefer to explicitly enable new compute capacity. Without default"},{"line_number":14,"context_line":"disable, there is no way to ensure new builds land on tested compute capacity."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":""},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"Problem description"}],"source_content_type":"text/x-rst","patch_set":1,"id":"dac4157f_9320744b","line":15,"updated":"2015-04-19 12:00:50.000000000","message":"Shouldn\u0027t this be for all the services (not only compute)?\nWe have the same problem when introducing a new scheduler, conductor, ...","commit_id":"dea97c13a5b3fcb0c81b435f214c73475f67cfa5"},{"author":{"_account_id":2033,"name":"Belmiro Moreira","email":"moreira.belmiro.email.lists@gmail.com","username":"moreira-belmiro-email-lists"},"change_message_id":"06dfdbda4450ed694b154c2be22b851fef54457d","unresolved":false,"context_lines":[{"line_number":38,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"* Change the compute service status to disabled by default"},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"Posting to get preliminary feedback on the scope of this spec."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":1,"id":"dac4157f_132c6449","line":41,"updated":"2015-04-19 12:00:50.000000000","message":"If I\u0027m understanding correctly the idea would be to change the default configuration option \"enable_new_services\" to False.\nCan you explicitly add this in the spec?","commit_id":"dea97c13a5b3fcb0c81b435f214c73475f67cfa5"},{"author":{"_account_id":6589,"name":"Jesse Keating","email":"jkeating@j2solutions.net","username":"jesse-keating"},"change_message_id":"a14209d7458ea46b801bfffe02401e52ce9b94ef","unresolved":false,"context_lines":[{"line_number":54,"context_line":"The default value of the Services table\u0027s disabled column would change"},{"line_number":55,"context_line":"to True. Migrations might be needed for new records to receive this"},{"line_number":56,"context_line":"default."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"REST API impact"},{"line_number":59,"context_line":"---------------"},{"line_number":60,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3ab451fb_91ba7fe0","line":57,"updated":"2015-04-17 20:11:55.000000000","message":"If we\u0027re going to set disabled to 1 instead of 0 by default, should we also set a default disabled_reason? Presumably disabled_at would be set to the timestamp of when the service gets added to the table?","commit_id":"dea97c13a5b3fcb0c81b435f214c73475f67cfa5"},{"author":{"_account_id":2033,"name":"Belmiro Moreira","email":"moreira.belmiro.email.lists@gmail.com","username":"moreira-belmiro-email-lists"},"change_message_id":"06dfdbda4450ed694b154c2be22b851fef54457d","unresolved":false,"context_lines":[{"line_number":54,"context_line":"The default value of the Services table\u0027s disabled column would change"},{"line_number":55,"context_line":"to True. Migrations might be needed for new records to receive this"},{"line_number":56,"context_line":"default."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"REST API impact"},{"line_number":59,"context_line":"---------------"},{"line_number":60,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"dac4157f_736f2093","line":57,"in_reply_to":"3ab451fb_91ba7fe0","updated":"2015-04-19 12:00:50.000000000","message":"See: https://review.openstack.org/#/c/136645/8","commit_id":"dea97c13a5b3fcb0c81b435f214c73475f67cfa5"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"367cca72061c33d4c5280324107b141d9cc1e3c0","unresolved":false,"context_lines":[{"line_number":83,"context_line":"Other deployer impact"},{"line_number":84,"context_line":"---------------------"},{"line_number":85,"context_line":""},{"line_number":86,"context_line":"Operators will have to explicitly enable new compute capacity."},{"line_number":87,"context_line":""},{"line_number":88,"context_line":"Developer impact"},{"line_number":89,"context_line":"----------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fabf19d9_43620cda","line":86,"updated":"2015-04-18 09:07:46.000000000","message":"Maybe there should be some config option which allow to set new compute as enabled right after deploy it?","commit_id":"dea97c13a5b3fcb0c81b435f214c73475f67cfa5"}],"specs/liberty/approved/default-disable-services.rst":[{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"65d160dcc4bb10a7f7799d83a54f51fd58b78f54","unresolved":false,"context_lines":[{"line_number":41,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"* Change the service status to disabled by default"},{"line_number":44,"context_line":"* Change enable_new_services to False"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"Posting to get preliminary feedback on the scope of this spec."},{"line_number":47,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"dac4157f_8d024c0a","line":44,"updated":"2015-04-21 11:55:57.000000000","message":"Erm, while I understand your views, I think we should leave the services being enabled by default but make sure that docs would explain how to disable them.\nIMHO if we add one step more for adding a service, it just give more difficulty for newcomers.\nOn the other side, big companies running lots of compute nodes are probably also running configuration mgmt systems like Puppet so they can easily put a new conf opt in there.","commit_id":"16165f4ded495d50ad9cabe0b60db5dedaf0fc8b"}]}
