)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"06474ea925f10257c987222efdb0b6f8b8d7f199","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"14206958_e9e0e63b","updated":"2026-08-27 11:31:31.000000000","message":"im not a cidner core so ill refaine form +2\n\nbut my undersning is this is correct and required for using cinder standalone\n\neffectivlly when you are creating a cinder voluem for use out side fo nova\nsuch as when cidner is used in standalone mode you still need to be able to create an attachment but its not assocated with a nova instnace\n\npreviosly this was possibel via the cinder clint cli as it treated the service as an optional postional arg and in earler iterations as a keyword argument\n\nthis can also be useful for cinder with standalone ironic\n\nironic has some native supprot for cinder volusm but in any context where the storage network is accabel directly with this change a user can use there normal credital to create the volume and then mount it themselvs usign the attachment info\n\ni have personally done this in the past to attach my steam libary on my desktop to iscis volume created on cidner lvm.\n\nthe openstack/python-brick-cinderclient-ext extention evne automated this witha local-attach and local-detach command\n\nhttps://opendev.org/openstack/python-brick-cinderclient-ext/src/branch/master/brick_cinderclient_ext/__init__.py#L65-L104\nhttps://opendev.org/openstack/python-brick-cinderclient-ext/src/branch/master/releasenotes/notes/local-attach-feature-474283267873f091.yaml\n\nim not sure that including that in osc is a good idea beucase it actully invokein os-brick but it is nice to be able to at least manally create the attachment.","commit_id":"ffa5533b408a9dd1be9c71012968d933ba76b50f"}]}