)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":27339,"name":"Michal Arbet","email":"michal.arbet@ultimum.io","username":"michalarbet"},"change_message_id":"666c70b18c763fd9e3db55572eafcc6cf667e211","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"3b78af18_7841cb08","updated":"2024-01-03 10:18:36.000000000","message":"Hmm, I am just curious, why were we proposed /var/lib/neutron/kolla in the past instead of /var/lib/neutron ? \n\nThat means that on kolla based deployment there are data in /var/lib/neutron\n\n(neutron-l3-agent)[root@controller0 /]# ls -la /var/lib/neutron/\ntotal 36\ndrwxr-xr-x 1 neutron neutron 4096 Jan  3 09:50 .\ndrwxr-xr-x 1 root    root    4096 Oct  9 07:13 ..\ndrwxr-xr-x 3 neutron neutron 4096 Jan  3 09:50 .cache\ndrwxr-xr-x 3 neutron neutron 4096 Jan  3 09:50 dhcp\ndrwxr-xr-x 3 neutron neutron 4096 Jan  3 09:50 external\ndrwxr-xr-x 3 neutron neutron 4096 Jan  3 09:50 ha_confs\nsrwxr-xr-x 1 neutron neutron    0 Jan  3 09:50 keepalived-state-change\ndrwxr-xr-x 2 neutron neutron 4096 Jan  3 09:50 kolla\ndrwxr-xr-x 2 neutron neutron 4096 Jan  3 09:50 tmp\n(neutron-l3-agent)[root@controller0 /]# ls -la /var/lib/neutron/kolla/\ntotal 8\ndrwxr-xr-x 2 neutron neutron 4096 Jan  3 09:50 .\ndrwxr-xr-x 1 neutron neutron 4096 Jan  3 09:50 ..\nsrw-r--r-- 1 neutron neutron    0 Jan  3 09:50 metadata_proxy\n(neutron-l3-agent)[root@controller0 /]# \n\n\nSo, if we will change the configuration, data will be in /var/lib/neutron/kolla ... but why ? It should be enough to just remount to /var/lib/neutron ? As other services ? \n\nI think we should have two volumes, \n\n1. state path for neutron \n\nFrom config it\u0027s : \n\n#state_path \u003d /var/lib/neutron\n\n2. Metadata socket path \n\nFrom config it\u0027s \n\n#metadata_proxy_socket \u003d $state_path/metadata_proxy\n\n\nSooooo : \n\n1. Create and mount neutron state volume to /var/lib/neutron_state\n2. Set config to state_path \u003d /var/lib/neutron_state\n3. Mount socket volume to /var/lib/neutron_metadata\n4. Set config to metadata_proxy_socket \u003d /var/lib/neutron_metadata/metadata_proxy\n\nWhat do you think ?","commit_id":"bf9ed407316eb335beea30bd5a35dc0e6b4cddb3"},{"author":{"_account_id":22629,"name":"Michal Nasiadka","email":"mnasiadka@gmail.com","username":"mnasiadka"},"change_message_id":"219eec57424adc3ec62bb8777d2e2a5b85af6a12","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"40f629c8_f9a42149","in_reply_to":"1e5d0571_bef117c2","updated":"2024-01-03 13:01:29.000000000","message":"Reworking in https://review.opendev.org/c/openstack/kolla-ansible/+/904512 for master only and merging backports","commit_id":"bf9ed407316eb335beea30bd5a35dc0e6b4cddb3"},{"author":{"_account_id":22629,"name":"Michal Nasiadka","email":"mnasiadka@gmail.com","username":"mnasiadka"},"change_message_id":"cbb42d9719636ca573d8eeac87cbd9d8c7d3371a","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"87531c5b_e0671643","in_reply_to":"22e76b3c_dfa28e26","updated":"2024-01-03 11:17:28.000000000","message":"so, metadata_proxy_socket will land under /var/lib/neutron/kolla/metadata_proxy and all other services will use /var/lib/neutron/kolla as state_path - what\u0027s the problem with it?\nChanging the volume mount point was the original proposal, but it could have some unwanted effects on operators when back ported to stable branches - e.g. we would need to manage the volume (ideally use a new volume and delete the old one).\nI don\u0027t think there\u0027s a requirement to have a volume per service - it has been living really without any state up until now.","commit_id":"bf9ed407316eb335beea30bd5a35dc0e6b4cddb3"},{"author":{"_account_id":27339,"name":"Michal Arbet","email":"michal.arbet@ultimum.io","username":"michalarbet"},"change_message_id":"7ca225172e5b8de19493f21b52512ad1991aa521","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"22e76b3c_dfa28e26","in_reply_to":"3b78af18_7841cb08","updated":"2024-01-03 10:41:50.000000000","message":"Or, just provide neutron volume and mount to /var/lib/neutron ..and that\u0027s it...","commit_id":"bf9ed407316eb335beea30bd5a35dc0e6b4cddb3"},{"author":{"_account_id":27339,"name":"Michal Arbet","email":"michal.arbet@ultimum.io","username":"michalarbet"},"change_message_id":"f7274318b7351551619e47f271238fadbc5ecca6","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"1e5d0571_bef117c2","in_reply_to":"87531c5b_e0671643","updated":"2024-01-03 11:25:23.000000000","message":"Yes it was living - but now I understand why neutron-l3-agent upgrade hurts during upgrades ... Neutron need to recreate everything which can cause problems when there are many resources ...\n\nNormally with non-containerzed environment /var/lib/neutron is shared between neutron services, so ..\n\nSolution is to just mount volume to /var/lib/neutron for every neutron service - I just don\u0027t like that name is neutron_metadata_socket ..which don\u0027t corespond with it\u0027s purpose ..because there are files for agent\u0027s state..","commit_id":"bf9ed407316eb335beea30bd5a35dc0e6b4cddb3"}]}