)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"d185a12f77d5166035257999664cf5930b52ea2a","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"8d84d45d_a01ae4c1","updated":"2023-10-05 09:10:21.000000000","message":"As is seen in integration jobs, this beaks existing manifests which declares cinder::scheduler::filter after cinder::scheduler.\n\nIMO this is not within responsibility of puppet-cinder but a user-defined manifests.","commit_id":"e286d6e16b2013b29b87c2a97e1d439a6fde5802"},{"author":{"_account_id":21129,"name":"Alan Bishop","email":"abishopsweng@gmail.com","username":"ASBishop","status":"ex Red Hat"},"change_message_id":"c6ca9231d8fa4806528486e76c19662dd7d848e8","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"5b8ff22f_74f8c88b","in_reply_to":"8d84d45d_a01ae4c1","updated":"2023-10-05 15:17:38.000000000","message":"I agree. The proper way to deal with this is by having deployment tools that use puppet-cinder include the resource. For example, in the case of tripleo deployments, puppet-tripleo could include the cinder::scheduler::filter resource.","commit_id":"e286d6e16b2013b29b87c2a97e1d439a6fde5802"}]}