)]}'
{"nova/db/sqlalchemy/api.py":[{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"d807dbec853fcd8ed57645ce4d53c3bbad29fa57","unresolved":false,"context_lines":[{"line_number":591,"context_line":"    # not make sense to be able to disable non-compute services like"},{"line_number":592,"context_line":"    # nova-scheduler or nova-osapi_compute since that does nothing."},{"line_number":593,"context_line":"    if not CONF.enable_new_services and values.get(\u0027binary\u0027) \u003d\u003d \u0027nova-compute\u0027:"},{"line_number":594,"context_line":"        msg \u003d _(\"New compute service disabled due to config option.\")"},{"line_number":595,"context_line":"        service_ref.disabled \u003d True"},{"line_number":596,"context_line":"        service_ref.disabled_reason \u003d msg"},{"line_number":597,"context_line":"    try:"}],"source_content_type":"text/x-python","patch_set":1,"id":"7f231b9d_8d7f3214","line":594,"updated":"2017-06-14 17:07:01.000000000","message":"I kinda feel like this sort of logic should be in the object layer at this point. I know it started here, but that was a long time ago.\n\nAlso, in the object layer, we could never show disabled\u003dTrue for any service where self.binary !\u003d \u0027nova-compute\u0027...","commit_id":"38cca9d90506a577025a4bc2c9b023f54123a252"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"a28dfe44477191cfbd3afc7d136514b4e6afc77a","unresolved":false,"context_lines":[{"line_number":591,"context_line":"    # not make sense to be able to disable non-compute services like"},{"line_number":592,"context_line":"    # nova-scheduler or nova-osapi_compute since that does nothing."},{"line_number":593,"context_line":"    if not CONF.enable_new_services and values.get(\u0027binary\u0027) \u003d\u003d \u0027nova-compute\u0027:"},{"line_number":594,"context_line":"        msg \u003d _(\"New compute service disabled due to config option.\")"},{"line_number":595,"context_line":"        service_ref.disabled \u003d True"},{"line_number":596,"context_line":"        service_ref.disabled_reason \u003d msg"},{"line_number":597,"context_line":"    try:"}],"source_content_type":"text/x-python","patch_set":1,"id":"7f231b9d_d2b38109","line":594,"in_reply_to":"7f231b9d_8d7f3214","updated":"2017-06-14 21:12:23.000000000","message":"\u003e Also, in the object layer, we could never show disabled\u003dTrue for any service where self.binary !\u003d \u0027nova-compute\u0027...\n\nWell, except you could have older non-compute services that are currently marked disabled. Abstracting that in the object layer would on GET would hide some things, which isn\u0027t the intent of this change.","commit_id":"38cca9d90506a577025a4bc2c9b023f54123a252"}],"releasenotes/notes/enable_new_services-compute-only-0abf5d3cbec40eb2.yaml":[{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"e0384ee843214fcfafef4eabea70ce8b530bc640","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"other:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    The ``[DEFAULT]/enable_new_services`` configuration option will now only be"},{"line_number":5,"context_line":"    used to auto-disable new nova-compute services. Other services like"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"3f1d235d_3fa655c3","line":2,"range":{"start_line":2,"start_character":0,"end_line":2,"end_character":5},"updated":"2017-06-30 13:27:04.000000000","message":"Sounds like \u0027upgrade\u0027, tbh","commit_id":"38cca9d90506a577025a4bc2c9b023f54123a252"}]}