)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":28619,"name":"Dmitriy Rabotyagov","email":"noonedeadpunk@gmail.com","username":"noonedeadpunk"},"change_message_id":"82bbcea05a9c54495f9aee0000835928e1b89873","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":7,"id":"1387c077_6635ba72","updated":"2026-11-16 13:22:23.000000000","message":"looks quite reasonable to me overall, and makes sense to implement.\nI think naming convention might have some extra love here, but well.","commit_id":"3d3c20242a7c0c3cdcffc76dec7686e42774278b"},{"author":{"_account_id":13425,"name":"Simon Dodsley","email":"simon@everpuredata.com","username":"sdodsley"},"change_message_id":"49adaf60dd4f014558fecce469efe5ad3b24ce32","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":8,"id":"afca939c_2a2b7e43","updated":"2026-11-16 18:55:56.000000000","message":"PS8 is a condensation pass driven by your readability comment on 1010774: the same rules and interfaces, stated once each, with the mechanism moved to the implementation plan, tables for every enumeration and concrete examples. The names changed as you suggested: the feature is \"compliance\" throughout (namespace, record, policies, events, exceptions, option, driver methods and the API action), and \"eradication hold\" is now \"retention lock\" with compliance:retention_days as its key; details on each inline comment. The spec files are renamed to match; the blueprint slug volume-sovereignty stays until I rename it on Launchpad.","commit_id":"4edd38bdd9c3769d30ccd7af79ab944c0a3cfcad"}],"specs/2027.1/sovereignty-extra-specs-namespace.rst":[{"author":{"_account_id":28619,"name":"Dmitriy Rabotyagov","email":"noonedeadpunk@gmail.com","username":"noonedeadpunk"},"change_message_id":"82bbcea05a9c54495f9aee0000835928e1b89873","unresolved":true,"context_lines":[{"line_number":10,"context_line":""},{"line_number":11,"context_line":"https://blueprints.launchpad.net/cinder/+spec/volume-sovereignty"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Introduce a reserved ``sovereignty:`` namespace in Cinder volume-type"},{"line_number":14,"context_line":"extra-specs.  The namespace allows operators to express sovereignty policy"},{"line_number":15,"context_line":"requirements (immutable snapshot protection, eradication hold periods, data"},{"line_number":16,"context_line":"residency constraints, replication residency constraints) in a standardised,"}],"source_content_type":"text/x-rst","patch_set":7,"id":"bb5218d9_9e27245a","line":13,"range":{"start_line":13,"start_character":21,"end_line":13,"end_character":37},"updated":"2026-11-16 13:22:23.000000000","message":"right of the bat, I personally don\u0027t like this name... It feels it\u0027s describes the very high-level goal and objective to reach through this property, but not a property for the volume which operators should manage.\n\nI check term in wikipedia, and it returned `supreme, independent control and lawmaking authority over a territory` which is not really explanatory enough.\n\n\nWhy don\u0027t we go with `compliance:`? As this ultimately what\u0027s being achieved here?\nAnd there\u0027s already `compliance` terminology in Keystone, Ceph, S3 API, etc.\nI think it better suits here...\nTo have that said - you mention `compliance` plenty of times in this doc as well:)","commit_id":"3d3c20242a7c0c3cdcffc76dec7686e42774278b"},{"author":{"_account_id":13425,"name":"Simon Dodsley","email":"simon@everpuredata.com","username":"sdodsley"},"change_message_id":"49adaf60dd4f014558fecce469efe5ad3b24ce32","unresolved":true,"context_lines":[{"line_number":10,"context_line":""},{"line_number":11,"context_line":"https://blueprints.launchpad.net/cinder/+spec/volume-sovereignty"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Introduce a reserved ``sovereignty:`` namespace in Cinder volume-type"},{"line_number":14,"context_line":"extra-specs.  The namespace allows operators to express sovereignty policy"},{"line_number":15,"context_line":"requirements (immutable snapshot protection, eradication hold periods, data"},{"line_number":16,"context_line":"residency constraints, replication residency constraints) in a standardised,"}],"source_content_type":"text/x-rst","patch_set":7,"id":"76bedda0_6a6a5a02","line":13,"range":{"start_line":13,"start_character":21,"end_line":13,"end_character":37},"in_reply_to":"bb5218d9_9e27245a","updated":"2026-11-16 18:55:56.000000000","message":"Agreed and done in PS8: the namespace is `compliance:`, and everything named after the feature follows. The blueprint slug volume-sovereignty stays until I rename it on Launchpad.","commit_id":"3d3c20242a7c0c3cdcffc76dec7686e42774278b"},{"author":{"_account_id":28619,"name":"Dmitriy Rabotyagov","email":"noonedeadpunk@gmail.com","username":"noonedeadpunk"},"change_message_id":"82bbcea05a9c54495f9aee0000835928e1b89873","unresolved":true,"context_lines":[{"line_number":224,"context_line":"    are absent and the backend offers no hold.  A driver therefore needs"},{"line_number":225,"context_line":"    no code for the Cinder tier."},{"line_number":226,"context_line":""},{"line_number":227,"context_line":"``sovereignty:data_residency``"},{"line_number":228,"context_line":"    Free-form string (e.g. ``eu-west``, ``us-gov``, ``au-sydney``).  The"},{"line_number":229,"context_line":"    scheduler performs an exact match against the value the backend"},{"line_number":230,"context_line":"    advertises; the volume API also enforces it when data moves (failover,"},{"line_number":231,"context_line":"    migration, retype).  Operators are responsible for a consistent tag"},{"line_number":232,"context_line":"    vocabulary within their deployment."},{"line_number":233,"context_line":""},{"line_number":234,"context_line":"``sovereignty:replication_residency``"},{"line_number":235,"context_line":"    Comma-separated list of residency tags into which a replica of this"},{"line_number":236,"context_line":"    volume may legitimately be placed (e.g. ``eu-west,eu-central``).  A"},{"line_number":237,"context_line":"    candidate backend is permitted as a replication target if **that"}],"source_content_type":"text/x-rst","patch_set":7,"id":"31768e29_ef3ca507","line":234,"range":{"start_line":227,"start_character":0,"end_line":234,"end_character":37},"updated":"2026-11-16 13:22:23.000000000","message":"I wonder if it make sense to move these under a different key, like `locality:` or smth, as this sounds like serving a little bit different purpose from others?\nI mean, it\u0027s related, but I again not liking `sovereignty` for these 2 options at all.","commit_id":"3d3c20242a7c0c3cdcffc76dec7686e42774278b"},{"author":{"_account_id":13425,"name":"Simon Dodsley","email":"simon@everpuredata.com","username":"sdodsley"},"change_message_id":"49adaf60dd4f014558fecce469efe5ad3b24ce32","unresolved":true,"context_lines":[{"line_number":224,"context_line":"    are absent and the backend offers no hold.  A driver therefore needs"},{"line_number":225,"context_line":"    no code for the Cinder tier."},{"line_number":226,"context_line":""},{"line_number":227,"context_line":"``sovereignty:data_residency``"},{"line_number":228,"context_line":"    Free-form string (e.g. ``eu-west``, ``us-gov``, ``au-sydney``).  The"},{"line_number":229,"context_line":"    scheduler performs an exact match against the value the backend"},{"line_number":230,"context_line":"    advertises; the volume API also enforces it when data moves (failover,"},{"line_number":231,"context_line":"    migration, retype).  Operators are responsible for a consistent tag"},{"line_number":232,"context_line":"    vocabulary within their deployment."},{"line_number":233,"context_line":""},{"line_number":234,"context_line":"``sovereignty:replication_residency``"},{"line_number":235,"context_line":"    Comma-separated list of residency tags into which a replica of this"},{"line_number":236,"context_line":"    volume may legitimately be placed (e.g. ``eu-west,eu-central``).  A"},{"line_number":237,"context_line":"    candidate backend is permitted as a replication target if **that"}],"source_content_type":"text/x-rst","patch_set":7,"id":"5d9e59e3_70b9ffdd","line":234,"range":{"start_line":227,"start_character":0,"end_line":234,"end_character":37},"in_reply_to":"31768e29_ef3ca507","updated":"2026-11-16 18:55:56.000000000","message":"I considered `locality:` but kept the two residency keys under the one namespace, as `compliance:data_residency` and `compliance:replication_residency`. Data residency is itself a compliance requirement, and a single reserved prefix keeps the ratchet, the record, the metadata mirror, inheritance and the Glance property-protection rules single; a second prefix would need every one of them applied twice. PS8 says so in one sentence of the Namespace definition section. The `sovereignty` word you objected to is gone from both keys.","commit_id":"3d3c20242a7c0c3cdcffc76dec7686e42774278b"},{"author":{"_account_id":28619,"name":"Dmitriy Rabotyagov","email":"noonedeadpunk@gmail.com","username":"noonedeadpunk"},"change_message_id":"82bbcea05a9c54495f9aee0000835928e1b89873","unresolved":true,"context_lines":[{"line_number":254,"context_line":"   first drafted against one vendor\u0027s capability model and some carry that"},{"line_number":255,"context_line":"   vendor\u0027s connotations (\"eradication\" is one vendor\u0027s word for the"},{"line_number":256,"context_line":"   mandatory delay before permanent destruction, where others say"},{"line_number":257,"context_line":"   \"retention\", \"compliance lock\" or \"SnapLock\").  Maintainers of other"},{"line_number":258,"context_line":"   backends (NetApp, Dell, IBM, Hitachi, Ceph and others) are asked to"},{"line_number":259,"context_line":"   propose names during review that read as describing their own"},{"line_number":260,"context_line":"   capability.  The enforcement logic in both specs is unaffected by the"}],"source_content_type":"text/x-rst","patch_set":7,"id":"79880714_a0fb8b58","line":257,"range":{"start_line":257,"start_character":4,"end_line":257,"end_character":13},"updated":"2026-11-16 13:22:23.000000000","message":"I would probably prefer `retention`. `eradication` is not in my vocabulary at least, while `retention` or `compliance_lock` are way more natural, imo.\n\nActually if we\u0027d rename `sovereignty`-\u003e`compliance`, then name could be just `compliance:lock`.\nSounds way better then `sovereignty:eradication`, imo.","commit_id":"3d3c20242a7c0c3cdcffc76dec7686e42774278b"},{"author":{"_account_id":13425,"name":"Simon Dodsley","email":"simon@everpuredata.com","username":"sdodsley"},"change_message_id":"49adaf60dd4f014558fecce469efe5ad3b24ce32","unresolved":true,"context_lines":[{"line_number":254,"context_line":"   first drafted against one vendor\u0027s capability model and some carry that"},{"line_number":255,"context_line":"   vendor\u0027s connotations (\"eradication\" is one vendor\u0027s word for the"},{"line_number":256,"context_line":"   mandatory delay before permanent destruction, where others say"},{"line_number":257,"context_line":"   \"retention\", \"compliance lock\" or \"SnapLock\").  Maintainers of other"},{"line_number":258,"context_line":"   backends (NetApp, Dell, IBM, Hitachi, Ceph and others) are asked to"},{"line_number":259,"context_line":"   propose names during review that read as describing their own"},{"line_number":260,"context_line":"   capability.  The enforcement logic in both specs is unaffected by the"}],"source_content_type":"text/x-rst","patch_set":7,"id":"ac5d2913_1292de6e","line":257,"range":{"start_line":257,"start_character":4,"end_line":257,"end_character":13},"in_reply_to":"79880714_a0fb8b58","updated":"2026-11-16 18:55:56.000000000","message":"Agreed; \"eradication\" is one vendor\u0027s word and is gone from both specs. PS8 takes your first preference. \"Legal hold\" stays as the name of the indefinite primitive left to Manila.","commit_id":"3d3c20242a7c0c3cdcffc76dec7686e42774278b"},{"author":{"_account_id":28619,"name":"Dmitriy Rabotyagov","email":"noonedeadpunk@gmail.com","username":"noonedeadpunk"},"change_message_id":"82bbcea05a9c54495f9aee0000835928e1b89873","unresolved":true,"context_lines":[{"line_number":1372,"context_line":"  that would otherwise strengthen or introduce a recorded constraint is"},{"line_number":1373,"context_line":"  refused with HTTP 400 and no override; recreate the volume from itself"},{"line_number":1374,"context_line":"  under the stronger type."},{"line_number":1375,"context_line":"* A volume created from a sovereign image, snapshot or volume inherits its"},{"line_number":1376,"context_line":"  source\u0027s constraints and may be undeletable until an inherited hold"},{"line_number":1377,"context_line":"  expires; the ``sovereignty_*`` metadata on the new volume says so from"},{"line_number":1378,"context_line":"  the moment it is created."}],"source_content_type":"text/x-rst","patch_set":7,"id":"bc12ce8c_ba08f6d5","line":1375,"range":{"start_line":1375,"start_character":26,"end_line":1375,"end_character":62},"updated":"2026-11-16 13:22:23.000000000","message":"or volume backup","commit_id":"3d3c20242a7c0c3cdcffc76dec7686e42774278b"},{"author":{"_account_id":13425,"name":"Simon Dodsley","email":"simon@everpuredata.com","username":"sdodsley"},"change_message_id":"49adaf60dd4f014558fecce469efe5ad3b24ce32","unresolved":true,"context_lines":[{"line_number":1372,"context_line":"  that would otherwise strengthen or introduce a recorded constraint is"},{"line_number":1373,"context_line":"  refused with HTTP 400 and no override; recreate the volume from itself"},{"line_number":1374,"context_line":"  under the stronger type."},{"line_number":1375,"context_line":"* A volume created from a sovereign image, snapshot or volume inherits its"},{"line_number":1376,"context_line":"  source\u0027s constraints and may be undeletable until an inherited hold"},{"line_number":1377,"context_line":"  expires; the ``sovereignty_*`` metadata on the new volume says so from"},{"line_number":1378,"context_line":"  the moment it is created."}],"source_content_type":"text/x-rst","patch_set":7,"id":"497d3b38_a8eecc87","line":1375,"range":{"start_line":1375,"start_character":26,"end_line":1375,"end_character":62},"in_reply_to":"bc12ce8c_ba08f6d5","updated":"2026-11-16 18:55:56.000000000","message":"Done. Every list of inheritance sources in PS8 reads \"image, snapshot, volume or backup\", and the Inheritance table has a Backup row stating what a backup contributes (the source volume\u0027s record, found by `backup.volume_id` with deleted rows visible) and that no attribute of the backup itself is an input.","commit_id":"3d3c20242a7c0c3cdcffc76dec7686e42774278b"}]}
