)]}'
{"doc/source/configuration/block-storage/drivers/hpe-3par-driver.rst":[{"author":{"_account_id":29122,"name":"Raghavendra Tilay","email":"raghavendra-uddhav.tilay@hpe.com","username":"raghavendrat"},"change_message_id":"1fb10f6b961afde317634e7d4d2a05b1361ec42b","unresolved":false,"context_lines":[{"line_number":255,"context_line":"  if a compression is enabled and provisioning type requested is full,"},{"line_number":256,"context_line":"  the resulting volume defaults to thinly provisioned compressed volume."},{"line_number":257,"context_line":""},{"line_number":258,"context_line":"The HPE 3PAR driver supports when creating volume from snapshot supports"},{"line_number":259,"context_line":"independent copy operation by ``hpe3par:convert_to_base`` volume type extra"},{"line_number":260,"context_line":"specs extension module:"},{"line_number":261,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"7faddb67_deefd71a","line":258,"range":{"start_line":258,"start_character":0,"end_line":258,"end_character":72},"updated":"2019-07-31 09:00:18.000000000","message":"Thanks for Chiang for making an effort to add documentation.\nIt would be great if you can rephrase description as given below:\n\n\n``hpe3par:convert_to_base``\n\nThis extra-spec is used while creating volume from snapshot.\n\nIf set to ``True``, volume (from snapshot) is created independently i.e\nnew volume is decoupled from initial snapshot and original volume.\nUsage: where instances are launched for longer/unpredictable time frame.\n\nIf not set, value is considered as ``False``, volume (from snapshot)\nis created as child of snapshot.\nUsage: where many similar instances are launched for short time frame.","commit_id":"cbd7a060e626a2149683565b415b970a12152008"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"9977cfb001535c42afa739423e9e68d4cf55be98","unresolved":false,"context_lines":[{"line_number":108,"context_line":"* Additional Backend Capabilities."},{"line_number":109,"context_line":""},{"line_number":110,"context_line":"* Report Backend State in Service List."},{"line_number":111,"context_line":""},{"line_number":112,"context_line":"Volume type support for both HPE 3PAR drivers includes the ability to set the"},{"line_number":113,"context_line":"following capabilities in the OpenStack Block Storage API"},{"line_number":114,"context_line":"``cinder.api.contrib.types_extra_specs`` volume type extra specs extension"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7faddb67_6fa8e88b","line":111,"updated":"2019-08-08 12:27:18.000000000","message":"I suggest adding\n\n  Volume Type Support\n  ~~~~~~~~~~~~~~~~~~~\n\nbefore line 112.","commit_id":"424b5f5849174be19c7136f97d6c8bec6c6e6ddf"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"9977cfb001535c42afa739423e9e68d4cf55be98","unresolved":false,"context_lines":[{"line_number":267,"context_line":"is created as child of snapshot."},{"line_number":268,"context_line":"Usage: where many similar instances are launched for short time frame."},{"line_number":269,"context_line":""},{"line_number":270,"context_line":"LDAP and AD authentication is now supported in the HPE 3PAR driver."},{"line_number":271,"context_line":""},{"line_number":272,"context_line":"The 3PAR back end must be properly configured for LDAP and AD authentication"},{"line_number":273,"context_line":"prior to configuring the volume driver. For details on setting up LDAP with"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7faddb67_8f5e8474","line":270,"updated":"2019-08-08 12:27:18.000000000","message":"This whole block is confusing when you look at the rendered document.  I suggest moving this up to before line 174 and formatting it like this:\n\n  * ``hpe3par:xxx`` - Defaults to ``false``.\n\n    This extra-spec is used ...\n\n    If set to ``True`` ...\n\n    If not set, value is considered as ``False`` ...\n\nAlso, does the case of the setting matter?  Everywhere else in this section, \u0027true\u0027 and \u0027false\u0027 are always lowercased.","commit_id":"424b5f5849174be19c7136f97d6c8bec6c6e6ddf"},{"author":{"_account_id":4523,"name":"Eric Harney","email":"eharney@redhat.com","username":"eharney"},"change_message_id":"7420b76392b5311a3f46fa06071e24eed241ad0f","unresolved":false,"context_lines":[{"line_number":180,"context_line":""},{"line_number":181,"context_line":"  * If set to ``true``, volume (from snapshot) is created independently i.e"},{"line_number":182,"context_line":"    new volume is decoupled from initial snapshot and original volume."},{"line_number":183,"context_line":"    Usage: where instances are launched for longer/unpredictable time frame."},{"line_number":184,"context_line":""},{"line_number":185,"context_line":"  * If not set, value is considered as ``false``, volume (from snapshot)"},{"line_number":186,"context_line":"    is created as child of snapshot."}],"source_content_type":"text/x-rst","patch_set":4,"id":"7faddb67_e777d43a","line":183,"range":{"start_line":183,"start_character":44,"end_line":183,"end_character":76},"updated":"2019-08-13 13:49:29.000000000","message":"Explaining these use cases w.r.t. instance lifetime seems odd, and I\u0027m not sure it really gives a deployer useful info.\n\nWhat\u0027s really happening here is a tradeoff between ideal performance and operations behaving as expected later.  I think this should just explain that...","commit_id":"4697e230bc738d6113af2d9891a5a1dafd8ad79a"}]}