)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"ce08c38c59f0f2e59cca43e139d9fcc111588997","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"1ea0935d_8c15c5b5","updated":"2026-06-18 18:58:27.000000000","message":"I\u0027m very sceptical about adding support for installing non-free software to devstack, but I don\u0027t want to -2 while this is still WIP anyway. maybe this could be done in a devstack plugin instead?","commit_id":"db06f6bfeb04462fa18ea26d6f76c7cdfe33a96d"},{"author":{"_account_id":33451,"name":"Yushiro Furukawa","display_name":"Yushiro Furukawa","email":"yushiro.furukawa@lycorp.co.jp","username":"yushiro2"},"change_message_id":"ca698f3e7c85169c32f98fc28722cf5c96500f08","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"c410d239_c677952c","in_reply_to":"1ea0935d_8c15c5b5","updated":"2026-06-19 02:31:28.000000000","message":"Thanks for your review.  Oh, I didn\u0027t know about devstack plugin.  Is this place different from devstack repository?","commit_id":"db06f6bfeb04462fa18ea26d6f76c7cdfe33a96d"},{"author":{"_account_id":22629,"name":"Michal Nasiadka","email":"mnasiadka@gmail.com","username":"mnasiadka"},"change_message_id":"a633e01f0b6493ad88c5de2f9217391bb940076d","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"57c7c270_ed117f02","in_reply_to":"520da1e0_a384ad74","updated":"2026-06-19 13:56:03.000000000","message":"Well, we have https://governance.openstack.org/tc/reference/licensing.html which states:\n\nProjects run as part of the OpenStack Infrastructure (in order to produce OpenStack software) may be licensed under any OSI-approved license. (https://opensource.org/license)\n\nThis includes tools that are run with or on OpenStack projects only during validation or testing phases of development (e.g., a source code linter).\n\nI don\u0027t think Business Source License is an OSI-approved license.","commit_id":"db06f6bfeb04462fa18ea26d6f76c7cdfe33a96d"},{"author":{"_account_id":33451,"name":"Yushiro Furukawa","display_name":"Yushiro Furukawa","email":"yushiro.furukawa@lycorp.co.jp","username":"yushiro2"},"change_message_id":"4451ab3412640362195641f75f03c5f58d140d65","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"a0e647de_92787058","in_reply_to":"57c7c270_ed117f02","updated":"2026-06-19 14:39:15.000000000","message":"Thanks.  I think the important point here is that Consul is not intended to be a\nmandatory dependency for oslo.messaging HTTP driver deployments.\n\nAs discussed in the merged spec[1], Consul is just one possible backend for\nservice discovery/registration. Other backends such as DNS or Kubernetes\ncan be used instead. So this does not make Consul a required component for\nOpenStack development, testing, or validation environments.\n\nAlso, the current HTTP driver backend implementation is being validated\nagainst Consul 1.10.4 as the target Consul version. That version predates\nthe more recent licensing change in current Consul releases, so I don\u0027t think it\nis accurate to treat it as equivalent to the currently BUSL-licensed Consul\nreleases.\n\nIn short, this series is not trying to introduce Consul as an OpenStack-wide\nmandatory dependency, but only supports it as one optional backend\nimplementation.\n\n[1] https://review.opendev.org/c/openstack/oslo-specs/+/885809","commit_id":"db06f6bfeb04462fa18ea26d6f76c7cdfe33a96d"},{"author":{"_account_id":33451,"name":"Yushiro Furukawa","display_name":"Yushiro Furukawa","email":"yushiro.furukawa@lycorp.co.jp","username":"yushiro2"},"change_message_id":"fa950d4722fc42b974ce1972b4b768f5676728cf","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"86aa7b29_18ab4cc9","in_reply_to":"6fa95aab_5936afc7","updated":"2026-06-19 16:12:14.000000000","message":"Because our first implementation used and verified Consul. Alternative backend is our future target. Anyway, I\u0027ll follow the devstack plugin structure. Thank you.","commit_id":"db06f6bfeb04462fa18ea26d6f76c7cdfe33a96d"},{"author":{"_account_id":22629,"name":"Michal Nasiadka","email":"mnasiadka@gmail.com","username":"mnasiadka"},"change_message_id":"fcdf0d584f7262ec211c984c639db0860889ea67","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"6fa95aab_5936afc7","in_reply_to":"a0e647de_92787058","updated":"2026-06-19 14:57:34.000000000","message":"If Kubernetes is one - why don\u0027t use the existing etcd deployment in devstack?","commit_id":"db06f6bfeb04462fa18ea26d6f76c7cdfe33a96d"},{"author":{"_account_id":33451,"name":"Yushiro Furukawa","display_name":"Yushiro Furukawa","email":"yushiro.furukawa@lycorp.co.jp","username":"yushiro2"},"change_message_id":"43d152d7bacef2df30300b93f63d6fce53d6f49a","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"e455eeff_25dc125d","in_reply_to":"c410d239_c677952c","updated":"2026-06-19 06:59:15.000000000","message":"I have one question.  This patch includes 3 projects to use HTTP driver for oslo.messaging.  Nova, Neutron and oslo.messaging.\n1. Install consul and configure HTTP driver for oslo.messaging\n2. nova: Update nova.conf for HTTP driver\n3. neutron: Update neutron.conf for HTTP driver\n\nYou mentioned about topic 1. is better to convert as devstack plugin.  How about 2 and 3 ?  These are just config change.","commit_id":"db06f6bfeb04462fa18ea26d6f76c7cdfe33a96d"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"4ef16824210f2f0bff39dee859a451d172647d2f","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"520da1e0_a384ad74","in_reply_to":"e455eeff_25dc125d","updated":"2026-06-19 13:12:52.000000000","message":"I think doing the iniset calls from a plugin should be possible as well. in this case likely the oslo.messaging repo itself could host the plugin? see https://docs.openstack.org/devstack/latest/plugins.html for more information\n\nbut I\u0027d also be willing to defer on other reviewers\u0027 opinion on whether the patch would be suited for devstack itself, will ping the qa channel","commit_id":"db06f6bfeb04462fa18ea26d6f76c7cdfe33a96d"}]}