)]}'
{"releasenotes/notes/privsep-rocky-35bdfe70ed62a826.yaml":[{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"84d21439076d7c63a959bcb3a013fd4b57cb76d6","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"security:"},{"line_number":3,"context_line":"    Privsep transitions. Cinder is transitioning from using the older style"},{"line_number":4,"context_line":"    rootwrap privilege escalation path to the new style Oslo privsep path."},{"line_number":5,"context_line":"    This should improve performance and security of Nova in the long term."},{"line_number":6,"context_line":"  - |"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5f7c97a3_332b11ec","line":3,"updated":"2018-05-07 12:57:35.000000000","message":"The formatting is off here, so the release note output will not be formatted right.\n\nI wonder whether most of this should even be in the release notes though. Most of this is internal detail that end users and deployers will have no idea what it\u0027s talking about.\n\nPlus, even though it\u0027s not the ideal the way it was done, Cinder has already transitioned to using privsep a few releases ago, so I don\u0027t think this is an accurate statement either.","commit_id":"39a2fbf2d4b8d2d83ca412e2f92bce0794223d3d"},{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"84d21439076d7c63a959bcb3a013fd4b57cb76d6","unresolved":false,"context_lines":[{"line_number":2,"context_line":"security:"},{"line_number":3,"context_line":"    Privsep transitions. Cinder is transitioning from using the older style"},{"line_number":4,"context_line":"    rootwrap privilege escalation path to the new style Oslo privsep path."},{"line_number":5,"context_line":"    This should improve performance and security of Nova in the long term."},{"line_number":6,"context_line":"  - |"},{"line_number":7,"context_line":"    privsep daemons are now started by Cinder when required. These daemons can"},{"line_number":8,"context_line":"    be started via rootwrap if required. rootwrap configs therefore need to"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"5f7c97a3_73c5093c","line":5,"range":{"start_line":5,"start_character":52,"end_line":5,"end_character":56},"updated":"2018-05-07 12:57:35.000000000","message":"Cinder?","commit_id":"39a2fbf2d4b8d2d83ca412e2f92bce0794223d3d"},{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"c587fc62b6481c4a6f4f0faab25fa459a5e0c967","unresolved":false,"context_lines":[{"line_number":4,"context_line":"    Privsep transitions. Cinder is transitioning from using the older style"},{"line_number":5,"context_line":"    rootwrap privilege escalation path to the new style Oslo privsep path."},{"line_number":6,"context_line":"    This should improve performance and security of Cinder in the long term."},{"line_number":7,"context_line":"    Privsep daemons are now started by Cinder when required. These daemons can"},{"line_number":8,"context_line":"    be started via rootwrap if required. rootwrap configs therefore need to"},{"line_number":9,"context_line":"    be updated to include new privsep daemon invocations."},{"line_number":10,"context_line":"upgrade:"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"5f7c97a3_166371b3","line":7,"updated":"2018-06-05 15:22:59.000000000","message":"I think the original had this section as a separate item so it would be listed on its own under the security section. It was just missing the first \"- |\" for the first section.\n\nCould you add that back in? I think that makes sense and would make it easier for release note consumers to pick out this part.","commit_id":"182e8b20fd8bb2ce0d3f0b40f29bcd83feb96ec3"}]}