)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"205022e2192374afa309ebe9d12e846641ec9068","unresolved":false,"context_lines":[{"line_number":8,"context_line":""},{"line_number":9,"context_line":"This commit moves the ipv6 option into the proper config group."},{"line_number":10,"context_line":"Previously, there was an ipv6_enabled option under the network group."},{"line_number":11,"context_line":"This was the incorrect location for this type of option since, ipv6"},{"line_number":12,"context_line":"is an optional feature it should be in the feature enabled group."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Change-Id: I35769cf4d18363fad56ed5150b4d01d8a5ad17e7"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":6,"id":"AAAAVn%2F%2FzCc%3D","line":11,"updated":"2014-03-04 03:05:48.000000000","message":"To be honest, I thought about it when I added this option, but at the time I came up with the conclusion that the ability to switch on/off v6 should be closer to where the other v6 options are, like tenant_network_v6_cidr; furthermore, network-feature-enabled does not seem the right place as IPv6 support is not really a feature or an extension per se.\n\nThat said, I am not particularly fussed as to where this goes so long and devstack\u0027s relevant patch complies with this change. For reference, see: https://review.openstack.org/#/c/74938/","commit_id":"e2e33cf78ad345865b688d2d537099e1a23ca3b7"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"03fc482b77d1139bc5e9f563f78b46e871069b90","unresolved":false,"context_lines":[{"line_number":8,"context_line":""},{"line_number":9,"context_line":"This commit moves the ipv6 option into the proper config group."},{"line_number":10,"context_line":"Previously, there was an ipv6_enabled option under the network group."},{"line_number":11,"context_line":"This was the incorrect location for this type of option since, ipv6"},{"line_number":12,"context_line":"is an optional feature it should be in the feature enabled group."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Change-Id: I35769cf4d18363fad56ed5150b4d01d8a5ad17e7"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":6,"id":"AAAAVn%2F%2Fylo%3D","line":11,"in_reply_to":"AAAAVn%2F%2Fy7Q%3D","updated":"2014-03-04 04:36:24.000000000","message":"I see now, thanks for clarifying this.\n\nHowever, I am concerned that this is not going to be first or last example of potential confusion going forward. After all my change was only approved a few days ago by the same person who approved your blueprint. I\u0027d suggest to clearly state the purpose of each section, in place in tempest.conf, and even then I am not even sure that guarantees that things will remain clean compared the case where only a single section is used per service.","commit_id":"e2e33cf78ad345865b688d2d537099e1a23ca3b7"},{"author":{"_account_id":5196,"name":"Matthew Treinish","email":"mtreinish@kortar.org","username":"treinish"},"change_message_id":"e1b2933d37a8ef2be25878a61da9c7a5ef7627d8","unresolved":false,"context_lines":[{"line_number":8,"context_line":""},{"line_number":9,"context_line":"This commit moves the ipv6 option into the proper config group."},{"line_number":10,"context_line":"Previously, there was an ipv6_enabled option under the network group."},{"line_number":11,"context_line":"This was the incorrect location for this type of option since, ipv6"},{"line_number":12,"context_line":"is an optional feature it should be in the feature enabled group."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Change-Id: I35769cf4d18363fad56ed5150b4d01d8a5ad17e7"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":6,"id":"AAAAVn%2F%2Fy7Q%3D","line":11,"in_reply_to":"AAAAVn%2F%2FzCc%3D","updated":"2014-03-04 03:47:41.000000000","message":"The section isn\u0027t just for extensions, in fact the only other option in there now should cover all the extensions. For an example see the other services equivalent groups. The feature enabled groups are exactly for this kind of thing, to specify features that are not required to be enabled, whether that\u0027s because of a service config option, a byproduct of a driver or backend choice(which really shouldn\u0027t make a difference ever unless there is a config option in the service), or a testing environment limitation. The original intent of the groups was to remove all of the XXX_enabled or XXX_available options and put them in one place with consistent naming.\n\nThe regular network section is for implementation specific configurations. (things like network ids and cidrs, keystone catalog info, etc) Yeah it\u0027s a subtle and probably poorly defined difference, but this option is a clear case because it actually fits in with the original guidelines for the feature groups in:\nhttps://blueprints.launchpad.net/tempest/+spec/config-cleanup","commit_id":"e2e33cf78ad345865b688d2d537099e1a23ca3b7"}]}