)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"fde873f51725149cf6501beea34345b6cf03b8bb","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"d4d74608_9a67b3f6","updated":"2026-07-17 04:53:33.000000000","message":"I wonder if we could use the retrying library, which is already widely used, to handle that retry logic instead of implementing our own version ?","commit_id":"f29448a52173186a948748652f22ce65eaf059ac"},{"author":{"_account_id":290,"name":"Antony Messerli","email":"antony@mes.ser.li","username":"antonym"},"change_message_id":"f9723194a41f08300030954b24770a0359c6cc5e","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"e08728ce_dee051d3","in_reply_to":"d4d74608_9a67b3f6","updated":"2026-09-01 21:41:29.000000000","message":"Happy to use a library rather than rolling our own. One thing though: retrying appears to be unmaintained upstream, and it\u0027s only listed in the testing section of global-requirements, masakari doesn\u0027t currently depend on it. Would tenacity make more sense (cinder/neutron/ironic/manila all use it), or could we leverage keystoneauth1.adapter.Adapter instead? novaclient\u0027s SessionClient subclasses it, and it already supports connect_retries / status_code_retries / retriable_status_codes with exponential backoff and Retry-After handling.","commit_id":"f29448a52173186a948748652f22ce65eaf059ac"}]}