)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":8864,"name":"Artom Lifshitz","email":"notartom@gmail.com","username":"artom"},"change_message_id":"20f9f5e643a97cf7654a016a938bc7e650540dd0","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"83ca50fc_dbc1cc28","updated":"2023-04-15 13:06:12.000000000","message":"I want to get Sean\u0027s input here because I don\u0027t want to blindly push my idea, but I feel like when you\u0027re at the point of having 3 dictionary-types in your config, all keyed on the compute hosts in the deployment, a separate declarative file, perhaps nodes.yaml, is a cleaner solution. I would imagine it looking something like this:\n\n    --\n    - nodes:\n        compute-0:\n          libvirt_container: nova_libvirt\n          services:\n            nova_compute:\n              start_command: systemctl start tripleo-nova-compute\n        compute-1:\n          libvirt_container: nova_libvirtqemud\n          services:\n            nova_compute:\n              start_command: systemctl start \u003cwhatever\u003e\n              \nWe could keep the existing config option as the fallback defaults if what we need isn\u0027t found in nodes.yaml\n\nI suspect it would be easy enough to have a global singleton called NODES or something that will parse nodes.yaml the first time it\u0027s called...","commit_id":"7be1d0915ef3d953aec28deeed769059524dca7e"},{"author":{"_account_id":31033,"name":"James Parker","email":"jparker@redhat.com","username":"jparker"},"change_message_id":"4405f7267e55f8dbb56593b50e842921d3d063fc","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"82ff5076_ef747517","in_reply_to":"83ca50fc_dbc1cc28","updated":"2023-04-19 19:19:37.000000000","message":"+1 to this approach.  I\u0027m doing some testing with the current proposed methodology now but afterwards I\u0027ll explore the suggested approach.","commit_id":"7be1d0915ef3d953aec28deeed769059524dca7e"}]}