)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":21757,"name":"Xing Zhang","email":"angeiv.zhang@gmail.com","username":"angeiv"},"change_message_id":"e7abcf882f30d8efe7e564d52a460f05c7c7376c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"65c75dea_e1702ad9","updated":"2022-03-24 01:49:09.000000000","message":"\u003e Patch Set 2:\n\u003e \n\u003e I\u0027ve proposed Ib46160b261508a6d530136777b6472dc34218b90 in order to set expectations, in hopes others won\u0027t get the mistaken impression that this repository exists for direct reconsumption in any environments other than configuring OpenDev\u0027s own services.\n\nMuch more clear for me, I\u0027ll abandon this patch and do more work in internal, thanks!","commit_id":"82954a296d5418d159c545addd970a4d46b09c98"},{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"68297f1015841e67eba819b66ae2abc7377f7418","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"f05f5b07_c966703d","updated":"2022-03-17 18:58:35.000000000","message":"Can you expand on the use case here? We decided after our experiments with puppet that our system-config is not really intended for external re-consumption. The effort required is significant and we weren\u0027t getting enough assistance to make it viable. Instead if you want to do this you should have your own docker-compose files and roles.","commit_id":"82954a296d5418d159c545addd970a4d46b09c98"},{"author":{"_account_id":21757,"name":"Xing Zhang","email":"angeiv.zhang@gmail.com","username":"angeiv"},"change_message_id":"e2cac3ffffa03c781a990f549b9cf028f8230875","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"94ccd02f_df975652","in_reply_to":"f05f5b07_c966703d","updated":"2022-03-23 03:43:19.000000000","message":"We have deployed the same architecture of infra system in our company for code development about more than 8 years, tracked with upstream of OpenInfra, from zuul v2 (jenkins + puppet) to zuul v3 (ansible + puppet + zuul), now managed by zuul with docker-compose.\n\nThe fact is in the internal production environment, we can\u0027t catch up with the new changes as quick as possible, because of some new version of the components are incompatible with the version that we use, and also we need to find maintenance time windows to upgrade, to put it another way, it will be much more friendly for us that we can pin \"stable\" version in production use.\n\nFor me about the internal maintenance work, the most ansible roles of system-config is good enough to use and can also to keep up with the new changes, except the tag in docker-compose file. So the purpose of this patch is to make image tags are configurable, so we can use ansible vars to control the upgrade work manually at the suitable time, other than the latest version.","commit_id":"82954a296d5418d159c545addd970a4d46b09c98"}]}