)]}'
{"specs/kilo/vmware-vol-adapter-type.rst":[{"author":{"_account_id":170,"name":"Mike Perez","email":"thingee@gmail.com","username":"thingee"},"change_message_id":"84299afc9fae2a8a97d6bb8a690f45266789d5e2","unresolved":false,"context_lines":[{"line_number":135,"context_line":""},{"line_number":136,"context_line":"Documentation Impact"},{"line_number":137,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":138,"context_line":""},{"line_number":139,"context_line":"An additional extra spec can be specified to chose which storage controller"},{"line_number":140,"context_line":"the volume will use, i.e. vmware:adapter_type."},{"line_number":141,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"9aa7fdbe_78357045","line":138,"updated":"2014-10-19 06:05:06.000000000","message":"I\u0027m not sure what this sentence has to do with this section. You should explain here what will be done in documentation to take into account of this new feature.\n\nPlease take a look at:\n\nhttp://docs.openstack.org/trunk/config-reference/content/ch_configuring-openstack-block-storage.html\n\nYou should provide documentation here how types and extra-specs can be created so your driver can take advantage of this feature.","commit_id":"ee786d6eafef4b96fcf2ccd6e6f3330139038bd9"},{"author":{"_account_id":8247,"name":"Thang Pham","email":"thang.g.pham@gmail.com","username":"thang.pham"},"change_message_id":"62b9ba08817364b40608ee6f4db2d9ff797e483c","unresolved":false,"context_lines":[{"line_number":135,"context_line":""},{"line_number":136,"context_line":"Documentation Impact"},{"line_number":137,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":138,"context_line":""},{"line_number":139,"context_line":"An additional extra spec can be specified to chose which storage controller"},{"line_number":140,"context_line":"the volume will use, i.e. vmware:adapter_type."},{"line_number":141,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"9aa7fdbe_deed528d","line":138,"in_reply_to":"9aa7fdbe_78357045","updated":"2014-10-20 14:19:56.000000000","message":"Ok, I will update it with more details.","commit_id":"ee786d6eafef4b96fcf2ccd6e6f3330139038bd9"},{"author":{"_account_id":9171,"name":"Vipin Balachandran","email":"vipin.bl@gmail.com","username":"vbala"},"change_message_id":"d35ca44451f18d4bc0d3f54680e5a2252bcc8a06","unresolved":false,"context_lines":[{"line_number":10,"context_line":""},{"line_number":11,"context_line":"https://blueprints.launchpad.net/cinder/+spec/vmware-vol-adapter-type"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Today, if you create a vmdk volume, \"lsiLogic\" is the default hard-coded"},{"line_number":14,"context_line":"adapter_type.  Other adapter types supported are: busLogic, ide, lsiLogicsas,"},{"line_number":15,"context_line":"and paraVirtual.  The purpose of this blueprint is to allow the user to"},{"line_number":16,"context_line":"specify the adapter_type as an extra spec in the cinder volume type, so that"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da86d52c_5013c60c","line":13,"updated":"2015-02-10 08:29:11.000000000","message":"This is not entirely true. We honour vmware_adaptertype glance meta-data while creating volume from an image.","commit_id":"3b6ed8c464550a0ff27cdefc2d55d7569b35f046"},{"author":{"_account_id":170,"name":"Mike Perez","email":"thingee@gmail.com","username":"thingee"},"change_message_id":"1924a693fea67da3034afef455074af5715d20b6","unresolved":false,"context_lines":[{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Today, if you create a vmdk volume, \"lsiLogic\" is the default hard-coded"},{"line_number":14,"context_line":"adapter_type.  Other adapter types supported are: busLogic, ide, lsiLogicsas,"},{"line_number":15,"context_line":"and paraVirtual.  The purpose of this blueprint is to allow the user to"},{"line_number":16,"context_line":"specify the adapter_type as an extra spec in the cinder volume type, so that"},{"line_number":17,"context_line":"any new cinder volume of that type will have the specified adapter_type."},{"line_number":18,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"da86d52c_2804357d","line":15,"updated":"2015-02-10 00:58:15.000000000","message":"\"user\" here is cloud administrator, not the actual end user. Please specific in your spec about that.","commit_id":"3b6ed8c464550a0ff27cdefc2d55d7569b35f046"},{"author":{"_account_id":9171,"name":"Vipin Balachandran","email":"vipin.bl@gmail.com","username":"vbala"},"change_message_id":"d35ca44451f18d4bc0d3f54680e5a2252bcc8a06","unresolved":false,"context_lines":[{"line_number":40,"context_line":"vmware:vmdk_type\u003dthick.  This implementation will introduce another"},{"line_number":41,"context_line":"extra spec called \"vmware:adapter_type\", where it can be set as \"busLogic\","},{"line_number":42,"context_line":"\"ide\", \"lsiLogic\", \"lsiLogicsas\", or \"paraVirtual\".  If vmware:adapter_type is"},{"line_number":43,"context_line":"not specified, the default adapter_type will be as before, lsiLogic."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"Alternatives"},{"line_number":46,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da86d52c_9090de4f","line":43,"updated":"2015-02-10 08:29:11.000000000","message":"We need to handle the case where glance image meta containing vmware_adaptertype.","commit_id":"3b6ed8c464550a0ff27cdefc2d55d7569b35f046"},{"author":{"_account_id":170,"name":"Mike Perez","email":"thingee@gmail.com","username":"thingee"},"change_message_id":"3e4dc6f63bae912a1e70ad064c1e63b490e989d6","unresolved":false,"context_lines":[{"line_number":129,"context_line":"Documentation Impact"},{"line_number":130,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":131,"context_line":""},{"line_number":132,"context_line":"Today, when creating a volume type, only \"vmware:vmdk_type\" and"},{"line_number":133,"context_line":"\"vmware:clone_type\" extra specs can be specified.  vmware:vmdk_type defines"},{"line_number":134,"context_line":"the VMDK disk file type (thin, lazyZeroedThick, or eagerZeroedThick)."},{"line_number":135,"context_line":"vmware:clone_type defines how to create a volume from another source volume or"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5a890539_fb0a7f88","line":132,"updated":"2014-11-17 03:32:25.000000000","message":"The point of this section is to explain where you\u0027re going to put this documentation. (i.e. what documentation that exists now does your proposal impact) Please see my previous comment.","commit_id":"3b6ed8c464550a0ff27cdefc2d55d7569b35f046"},{"author":{"_account_id":8247,"name":"Thang Pham","email":"thang.g.pham@gmail.com","username":"thang.pham"},"change_message_id":"b46e2d715128c881a459b6971001c2c6622cbd53","unresolved":false,"context_lines":[{"line_number":129,"context_line":"Documentation Impact"},{"line_number":130,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":131,"context_line":""},{"line_number":132,"context_line":"Today, when creating a volume type, only \"vmware:vmdk_type\" and"},{"line_number":133,"context_line":"\"vmware:clone_type\" extra specs can be specified.  vmware:vmdk_type defines"},{"line_number":134,"context_line":"the VMDK disk file type (thin, lazyZeroedThick, or eagerZeroedThick)."},{"line_number":135,"context_line":"vmware:clone_type defines how to create a volume from another source volume or"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5a890539_c98abd63","line":132,"in_reply_to":"5a890539_fb0a7f88","updated":"2014-12-01 17:21:35.000000000","message":"I do not understand your comment here.  In patch #2, you said to \"explain here what will be done in documentation to take into account of this new feature...you should provide documentation here how types and extra-specs can be created so your driver can take advantage of this feature\".  I thought this is what I did here - I am confused.","commit_id":"3b6ed8c464550a0ff27cdefc2d55d7569b35f046"},{"author":{"_account_id":9171,"name":"Vipin Balachandran","email":"vipin.bl@gmail.com","username":"vbala"},"change_message_id":"d35ca44451f18d4bc0d3f54680e5a2252bcc8a06","unresolved":false,"context_lines":[{"line_number":130,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":131,"context_line":""},{"line_number":132,"context_line":"Today, when creating a volume type, only \"vmware:vmdk_type\" and"},{"line_number":133,"context_line":"\"vmware:clone_type\" extra specs can be specified.  vmware:vmdk_type defines"},{"line_number":134,"context_line":"the VMDK disk file type (thin, lazyZeroedThick, or eagerZeroedThick)."},{"line_number":135,"context_line":"vmware:clone_type defines how to create a volume from another source volume or"},{"line_number":136,"context_line":"a snapshot point (full or linked).  With this implementation, an additional"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da86d52c_d0edf6b8","line":133,"updated":"2015-02-10 08:29:11.000000000","message":"There is one more option \"vmware:storage_profile\".","commit_id":"3b6ed8c464550a0ff27cdefc2d55d7569b35f046"},{"author":{"_account_id":9171,"name":"Vipin Balachandran","email":"vipin.bl@gmail.com","username":"vbala"},"change_message_id":"4ab27b85808749992e38c937e6becb1b06bec98f","unresolved":false,"context_lines":[{"line_number":48,"context_line":"not specified, the default adapter_type will be as before, lsiLogic.  If the"},{"line_number":49,"context_line":"cinder volume is created from a Glance image, the adapter_type will be defined"},{"line_number":50,"context_line":"using the image metadata (i.e. vmware_adaptertype), if one is specified."},{"line_number":51,"context_line":"Otherwise, it should default to lsiLogic."},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"Alternatives"},{"line_number":54,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"da86d52c_871dd5c0","line":51,"updated":"2015-02-11 05:55:05.000000000","message":"When there is no adapter type in image meta-data, we should consider vmware:adapter_type in volume type before using the default adapter type. What do you think?","commit_id":"2bf0abb366149123e80186d19eaad68b8fbfa3b2"},{"author":{"_account_id":8247,"name":"Thang Pham","email":"thang.g.pham@gmail.com","username":"thang.pham"},"change_message_id":"d3298741450f90c59bd8c54a7954fba5579916a4","unresolved":false,"context_lines":[{"line_number":48,"context_line":"not specified, the default adapter_type will be as before, lsiLogic.  If the"},{"line_number":49,"context_line":"cinder volume is created from a Glance image, the adapter_type will be defined"},{"line_number":50,"context_line":"using the image metadata (i.e. vmware_adaptertype), if one is specified."},{"line_number":51,"context_line":"Otherwise, it should default to lsiLogic."},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"Alternatives"},{"line_number":54,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"da86d52c_58956d31","line":51,"in_reply_to":"da86d52c_871dd5c0","updated":"2015-02-11 14:33:41.000000000","message":"Sounds like a good idea.  I will update it.","commit_id":"2bf0abb366149123e80186d19eaad68b8fbfa3b2"}]}
