)]}'
{"specs/juno/vmware-new-vim.rst":[{"author":{"_account_id":1653,"name":"garyk","email":"gkotton@vmware.com","username":"garyk"},"change_message_id":"432bfc592c6848f4c52ed7e709ae9167c7cc2948","unresolved":false,"context_lines":[{"line_number":9,"context_line":"Openstack VMware drivers access vSphere using an internal api. This internal"},{"line_number":10,"context_line":"api shows all the signs of \u0027organic\u0027 growth:"},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"* Its implementation is hard to read, validate and debug"},{"line_number":13,"context_line":"* It is hard to use"},{"line_number":14,"context_line":"* It is lacking correctness features which consequently go mostly unimplemented"},{"line_number":15,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_8769f3bf","line":12,"updated":"2014-06-15 14:06:34.000000000","message":"Can you please provide example of this?","commit_id":"005a10972b968f0946ecf755f8f5957ef03188f4"},{"author":{"_account_id":1653,"name":"garyk","email":"gkotton@vmware.com","username":"garyk"},"change_message_id":"432bfc592c6848f4c52ed7e709ae9167c7cc2948","unresolved":false,"context_lines":[{"line_number":22,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"The vim API is split between api.py, vim.py and vim_util.py. The separation of"},{"line_number":25,"context_line":"responsibilities between api.py and vim.py is confused at best. Error handling"},{"line_number":26,"context_line":"in particular is extremely strange. vim_util.py is a collection of functions"},{"line_number":27,"context_line":"which rely heavily on details from the other 2, and is consequently not"},{"line_number":28,"context_line":"independent. Following any vim problem requires jumping continuously between"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_a7ab4fd4","line":25,"updated":"2014-06-15 14:06:34.000000000","message":"Agreed, the error handling is a little confusing. It is not clear how the proposal actually addresses that.","commit_id":"005a10972b968f0946ecf755f8f5957ef03188f4"},{"author":{"_account_id":9172,"name":"Radoslav Gerganov","email":"rgerganov@vmware.com","username":"rgerganov"},"change_message_id":"acffbd7ba6019fd1568144d0f47cd93f8f48ac40","unresolved":false,"context_lines":[{"line_number":28,"context_line":"independent. Following any vim problem requires jumping continuously between"},{"line_number":29,"context_line":"these 3 files."},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"The VMwareAPISession.invoke_api() method takes as arguments a module and a"},{"line_number":32,"context_line":"method name, which it introspects and calls. The module is always vim_util, and"},{"line_number":33,"context_line":"the thing which it calls is not a vSphere api, despite its name."},{"line_number":34,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_1a8b6c69","line":31,"updated":"2014-06-16 07:40:27.000000000","message":"I think you mean VMwareAPISession._call_method","commit_id":"005a10972b968f0946ecf755f8f5957ef03188f4"},{"author":{"_account_id":9555,"name":"Matthew Booth","email":"mbooth@redhat.com","username":"MatthewBooth"},"change_message_id":"65dc821cd21deaf25324033e0ae3ffb0a1cc4c65","unresolved":false,"context_lines":[{"line_number":28,"context_line":"independent. Following any vim problem requires jumping continuously between"},{"line_number":29,"context_line":"these 3 files."},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"The VMwareAPISession.invoke_api() method takes as arguments a module and a"},{"line_number":32,"context_line":"method name, which it introspects and calls. The module is always vim_util, and"},{"line_number":33,"context_line":"the thing which it calls is not a vSphere api, despite its name."},{"line_number":34,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_7302db0a","line":31,"in_reply_to":"1ae5cdf2_1a8b6c69","updated":"2014-06-16 08:48:43.000000000","message":"No, it was renamed in oslo.vmware.","commit_id":"005a10972b968f0946ecf755f8f5957ef03188f4"},{"author":{"_account_id":9172,"name":"Radoslav Gerganov","email":"rgerganov@vmware.com","username":"rgerganov"},"change_message_id":"acffbd7ba6019fd1568144d0f47cd93f8f48ac40","unresolved":false,"context_lines":[{"line_number":29,"context_line":"these 3 files."},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"The VMwareAPISession.invoke_api() method takes as arguments a module and a"},{"line_number":32,"context_line":"method name, which it introspects and calls. The module is always vim_util, and"},{"line_number":33,"context_line":"the thing which it calls is not a vSphere api, despite its name."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"The VMwareAPISession object does not encapsulate a VMware API session. In fact,"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_9a121c08","line":32,"updated":"2014-06-16 07:40:27.000000000","message":"actually it is either the vim_util module or the vim object. I agree this is confusing.","commit_id":"005a10972b968f0946ecf755f8f5957ef03188f4"},{"author":{"_account_id":9555,"name":"Matthew Booth","email":"mbooth@redhat.com","username":"MatthewBooth"},"change_message_id":"65dc821cd21deaf25324033e0ae3ffb0a1cc4c65","unresolved":false,"context_lines":[{"line_number":29,"context_line":"these 3 files."},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"The VMwareAPISession.invoke_api() method takes as arguments a module and a"},{"line_number":32,"context_line":"method name, which it introspects and calls. The module is always vim_util, and"},{"line_number":33,"context_line":"the thing which it calls is not a vSphere api, despite its name."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"The VMwareAPISession object does not encapsulate a VMware API session. In fact,"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_f30d0b37","line":32,"in_reply_to":"1ae5cdf2_9a121c08","updated":"2014-06-16 08:48:43.000000000","message":"Confusing isn\u0027t strong enough ;)\n\nAlso this is being compounded. garyk has been forced to add another hack to this code for pbm support.","commit_id":"005a10972b968f0946ecf755f8f5957ef03188f4"},{"author":{"_account_id":9172,"name":"Radoslav Gerganov","email":"rgerganov@vmware.com","username":"rgerganov"},"change_message_id":"acffbd7ba6019fd1568144d0f47cd93f8f48ac40","unresolved":false,"context_lines":[{"line_number":32,"context_line":"method name, which it introspects and calls. The module is always vim_util, and"},{"line_number":33,"context_line":"the thing which it calls is not a vSphere api, despite its name."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"The VMwareAPISession object does not encapsulate a VMware API session. In fact,"},{"line_number":36,"context_line":"the session is not strongly represented anywhere, despite being critical."},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"Proposed change"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_7aa9d08f","line":35,"updated":"2014-06-16 07:40:27.000000000","message":"It does encapsulate an API session but it in a poor way :)","commit_id":"005a10972b968f0946ecf755f8f5957ef03188f4"},{"author":{"_account_id":1653,"name":"garyk","email":"gkotton@vmware.com","username":"garyk"},"change_message_id":"432bfc592c6848f4c52ed7e709ae9167c7cc2948","unresolved":false,"context_lines":[{"line_number":33,"context_line":"the thing which it calls is not a vSphere api, despite its name."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"The VMwareAPISession object does not encapsulate a VMware API session. In fact,"},{"line_number":36,"context_line":"the session is not strongly represented anywhere, despite being critical."},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"Proposed change"},{"line_number":39,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_67a6a710","line":36,"updated":"2014-06-15 14:06:34.000000000","message":"I think that is missing from what you have written is/are use cases:\n\nThat is, if you could write the current interfaces and then explain how the new proposed ones would look like.\n\nThat would give a better overall picture.","commit_id":"005a10972b968f0946ecf755f8f5957ef03188f4"},{"author":{"_account_id":9172,"name":"Radoslav Gerganov","email":"rgerganov@vmware.com","username":"rgerganov"},"change_message_id":"acffbd7ba6019fd1568144d0f47cd93f8f48ac40","unresolved":false,"context_lines":[{"line_number":38,"context_line":"Proposed change"},{"line_number":39,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Vim and PBM are accessed through new Vim and PBM classes::"},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"  vim \u003d Vim(protocol, host, port, path, username, password,"},{"line_number":44,"context_line":"            max_retry_duration, max_sleep_time)"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_1a444cb6","line":41,"updated":"2014-06-16 07:40:27.000000000","message":"Having different classes for Vim and Pbm is a mistake that I am currently trying to fix. IMO, we need a single class that represents a vSphere service which we can configure for both Vim and Pbm:\n\n    transport \u003d suds.transport.http.HttpTransport()\n    vim \u003d Service(host, port, vim_url, vim_wsdl, transport)\n    pbm \u003d Service(host, port, pbm_url, pbm_wsdl, transport)\n\nusing a shared suds Transport is an elegant way to share the vSphere cookie between services","commit_id":"005a10972b968f0946ecf755f8f5957ef03188f4"},{"author":{"_account_id":9555,"name":"Matthew Booth","email":"mbooth@redhat.com","username":"MatthewBooth"},"change_message_id":"65dc821cd21deaf25324033e0ae3ffb0a1cc4c65","unresolved":false,"context_lines":[{"line_number":38,"context_line":"Proposed change"},{"line_number":39,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Vim and PBM are accessed through new Vim and PBM classes::"},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"  vim \u003d Vim(protocol, host, port, path, username, password,"},{"line_number":44,"context_line":"            max_retry_duration, max_sleep_time)"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_b3f623f8","line":41,"in_reply_to":"1ae5cdf2_1a444cb6","updated":"2014-06-16 08:48:43.000000000","message":"I like it.\n\nHowever, a potential concern is that this wouldn\u0027t allow a clean path to pyVmomi, which doesn\u0027t have a separate transport object afaik. Does that matter?\n\nHowever, I would have Service be the common base class I mention below, and still have separate Vim and PBM objects. There are a couple of reasons for this. Firstly, vim_util and pbm_util should both die, and be folded into the Vim and PBM objects. Secondly, there are useful helper objects we don\u0027t currently have which are API-specific, e.g. RetrievePropertiesEx with automatic continuation/cancellation.","commit_id":"005a10972b968f0946ecf755f8f5957ef03188f4"},{"author":{"_account_id":1653,"name":"garyk","email":"gkotton@vmware.com","username":"garyk"},"change_message_id":"432bfc592c6848f4c52ed7e709ae9167c7cc2948","unresolved":false,"context_lines":[{"line_number":47,"context_line":"These new classes would have a common base class which implemented all common"},{"line_number":48,"context_line":"functionality, which is almost everything described in this blueprint."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"N.B. I\u0027m currently undecided on session sharing between vim and pbm. The"},{"line_number":51,"context_line":"current implementation shares a cookie between the two. It\u0027s not clear to me"},{"line_number":52,"context_line":"exactly why we do this. If we continued sharing a session then PBM would take"},{"line_number":53,"context_line":"Vim as an argument instead of username and password. Discuss."}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_a7642fe5","line":50,"updated":"2014-06-15 14:06:34.000000000","message":"There should not be session sharing, they are two separate sessions to different end points.","commit_id":"005a10972b968f0946ecf755f8f5957ef03188f4"},{"author":{"_account_id":9555,"name":"Matthew Booth","email":"mbooth@redhat.com","username":"MatthewBooth"},"change_message_id":"65dc821cd21deaf25324033e0ae3ffb0a1cc4c65","unresolved":false,"context_lines":[{"line_number":47,"context_line":"These new classes would have a common base class which implemented all common"},{"line_number":48,"context_line":"functionality, which is almost everything described in this blueprint."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"N.B. I\u0027m currently undecided on session sharing between vim and pbm. The"},{"line_number":51,"context_line":"current implementation shares a cookie between the two. It\u0027s not clear to me"},{"line_number":52,"context_line":"exactly why we do this. If we continued sharing a session then PBM would take"},{"line_number":53,"context_line":"Vim as an argument instead of username and password. Discuss."}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_b312a307","line":50,"in_reply_to":"1ae5cdf2_a7642fe5","updated":"2014-06-16 08:48:43.000000000","message":"They currently share a session, and Radoslav\u0027s suggestion of a common transport would share a session.","commit_id":"005a10972b968f0946ecf755f8f5957ef03188f4"},{"author":{"_account_id":1653,"name":"garyk","email":"gkotton@vmware.com","username":"garyk"},"change_message_id":"432bfc592c6848f4c52ed7e709ae9167c7cc2948","unresolved":false,"context_lines":[{"line_number":57,"context_line":""},{"line_number":58,"context_line":"  results \u003d vim.api.RetrievePropertiesEx(pc, specSet\u003dspecs, options\u003doptions)"},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"This is a bare interface which does no session management. It raises any"},{"line_number":61,"context_line":"exceptions which occur without retrying."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"Session management is done through one of two interfaces, depending on the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_c75f7b0d","line":60,"updated":"2014-06-15 14:06:34.000000000","message":"Exceptions may be raised due to network issues. That is a use case where a retry may be relevant.","commit_id":"005a10972b968f0946ecf755f8f5957ef03188f4"},{"author":{"_account_id":9555,"name":"Matthew Booth","email":"mbooth@redhat.com","username":"MatthewBooth"},"change_message_id":"65dc821cd21deaf25324033e0ae3ffb0a1cc4c65","unresolved":false,"context_lines":[{"line_number":57,"context_line":""},{"line_number":58,"context_line":"  results \u003d vim.api.RetrievePropertiesEx(pc, specSet\u003dspecs, options\u003doptions)"},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"This is a bare interface which does no session management. It raises any"},{"line_number":61,"context_line":"exceptions which occur without retrying."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"Session management is done through one of two interfaces, depending on the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_d31d6f12","line":60,"in_reply_to":"1ae5cdf2_c75f7b0d","updated":"2014-06-16 08:48:43.000000000","message":"Good point. Only session errors should result in failure.","commit_id":"005a10972b968f0946ecf755f8f5957ef03188f4"},{"author":{"_account_id":9172,"name":"Radoslav Gerganov","email":"rgerganov@vmware.com","username":"rgerganov"},"change_message_id":"acffbd7ba6019fd1568144d0f47cd93f8f48ac40","unresolved":false,"context_lines":[{"line_number":68,"context_line":""},{"line_number":69,"context_line":"  results \u003d vim.auto.RetrievePropertiesEx(pc, specSet\u003dspecs, options\u003doptions)"},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"Sometimes a \u0027session transaction\u0027 is required. This is a block of code which"},{"line_number":72,"context_line":"must be re-executed in its entirety if any session-related failure occurs. This"},{"line_number":73,"context_line":"is implemented through the use of a transaction object::"},{"line_number":74,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_da1f446f","line":71,"updated":"2014-06-16 07:40:27.000000000","message":"Could you please give examples when this is needed?","commit_id":"005a10972b968f0946ecf755f8f5957ef03188f4"},{"author":{"_account_id":1653,"name":"garyk","email":"gkotton@vmware.com","username":"garyk"},"change_message_id":"432bfc592c6848f4c52ed7e709ae9167c7cc2948","unresolved":false,"context_lines":[{"line_number":97,"context_line":"As part of a general code cleanup, I would also move all vim_util functions"},{"line_number":98,"context_line":"into the vim object."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"I have additional proposals for:"},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"* Caching"},{"line_number":103,"context_line":"* Better interface to RetrievePropertiesEx"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_27a01ff3","line":100,"updated":"2014-06-15 14:06:34.000000000","message":"this does not seem relevant for this BP it was a little confusing reading it and trying to find context. I would suggest removing it and then proposing the new BP\u0027s","commit_id":"005a10972b968f0946ecf755f8f5957ef03188f4"},{"author":{"_account_id":1653,"name":"garyk","email":"gkotton@vmware.com","username":"garyk"},"change_message_id":"432bfc592c6848f4c52ed7e709ae9167c7cc2948","unresolved":false,"context_lines":[{"line_number":146,"context_line":"--------------------"},{"line_number":147,"context_line":""},{"line_number":148,"context_line":"max_retry_duration: Total length of time, in seconds, after which session"},{"line_number":149,"context_line":"failure retries will stop and a failure will be returned. Default: no limit."},{"line_number":150,"context_line":""},{"line_number":151,"context_line":"max_sleep_time: Retry will use incremental backoff. The maximum length of time,"},{"line_number":152,"context_line":"in seconds, between reconnection attempts. Default: 60."}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_2779ff92","line":149,"updated":"2014-06-15 14:06:34.000000000","message":"I am not sure I understand this point. Can you please clarify. This may lead to the driver haninging if I understand correctly - say for example you have a networking problem","commit_id":"005a10972b968f0946ecf755f8f5957ef03188f4"},{"author":{"_account_id":9555,"name":"Matthew Booth","email":"mbooth@redhat.com","username":"MatthewBooth"},"change_message_id":"65dc821cd21deaf25324033e0ae3ffb0a1cc4c65","unresolved":false,"context_lines":[{"line_number":146,"context_line":"--------------------"},{"line_number":147,"context_line":""},{"line_number":148,"context_line":"max_retry_duration: Total length of time, in seconds, after which session"},{"line_number":149,"context_line":"failure retries will stop and a failure will be returned. Default: no limit."},{"line_number":150,"context_line":""},{"line_number":151,"context_line":"max_sleep_time: Retry will use incremental backoff. The maximum length of time,"},{"line_number":152,"context_line":"in seconds, between reconnection attempts. Default: 60."}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_539f9f65","line":149,"in_reply_to":"1ae5cdf2_2779ff92","updated":"2014-06-16 08:48:43.000000000","message":"It would result in an api call hanging in the driver. Hmm, yes. Perhaps a conservative default of 60 seconds might be more appropriate.","commit_id":"005a10972b968f0946ecf755f8f5957ef03188f4"},{"author":{"_account_id":1653,"name":"garyk","email":"gkotton@vmware.com","username":"garyk"},"change_message_id":"432bfc592c6848f4c52ed7e709ae9167c7cc2948","unresolved":false,"context_lines":[{"line_number":159,"context_line":"achievable."},{"line_number":160,"context_line":""},{"line_number":161,"context_line":"If that were unpalatable, we could provide an implementation of the old api"},{"line_number":162,"context_line":"which could be used in parallel."},{"line_number":163,"context_line":""},{"line_number":164,"context_line":"Implementation"},{"line_number":165,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_e72c7795","line":162,"updated":"2014-06-15 14:06:34.000000000","message":"Tha API must be bawkward compatible - this is currently used by Glance and Celimoters","commit_id":"005a10972b968f0946ecf755f8f5957ef03188f4"},{"author":{"_account_id":9555,"name":"Matthew Booth","email":"mbooth@redhat.com","username":"MatthewBooth"},"change_message_id":"65dc821cd21deaf25324033e0ae3ffb0a1cc4c65","unresolved":false,"context_lines":[{"line_number":159,"context_line":"achievable."},{"line_number":160,"context_line":""},{"line_number":161,"context_line":"If that were unpalatable, we could provide an implementation of the old api"},{"line_number":162,"context_line":"which could be used in parallel."},{"line_number":163,"context_line":""},{"line_number":164,"context_line":"Implementation"},{"line_number":165,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_93e5a7de","line":162,"in_reply_to":"1ae5cdf2_e72c7795","updated":"2014-06-16 08:48:43.000000000","message":"The problem with the current API from a user perspective is that it doesn\u0027t represent a valid model of the problem. There is no fixing that.\n\nWe can provide 2 apis in parallel and deprecate the old one immediately.","commit_id":"005a10972b968f0946ecf755f8f5957ef03188f4"},{"author":{"_account_id":1653,"name":"garyk","email":"gkotton@vmware.com","username":"garyk"},"change_message_id":"432bfc592c6848f4c52ed7e709ae9167c7cc2948","unresolved":false,"context_lines":[{"line_number":182,"context_line":"----------"},{"line_number":183,"context_line":""},{"line_number":184,"context_line":"* Write new API"},{"line_number":185,"context_line":"* Implement in Glance"},{"line_number":186,"context_line":"* Implement in other projects, including Nova"},{"line_number":187,"context_line":""},{"line_number":188,"context_line":"Documentation Impact"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_a736efe4","line":185,"updated":"2014-06-15 14:06:34.000000000","message":"Glance has been released with the existing API\u0027s. Ceilometer too. The changes made will need to be backward compatible.","commit_id":"005a10972b968f0946ecf755f8f5957ef03188f4"},{"author":{"_account_id":1653,"name":"garyk","email":"gkotton@vmware.com","username":"garyk"},"change_message_id":"432bfc592c6848f4c52ed7e709ae9167c7cc2948","unresolved":false,"context_lines":[{"line_number":183,"context_line":""},{"line_number":184,"context_line":"* Write new API"},{"line_number":185,"context_line":"* Implement in Glance"},{"line_number":186,"context_line":"* Implement in other projects, including Nova"},{"line_number":187,"context_line":""},{"line_number":188,"context_line":"Documentation Impact"},{"line_number":189,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_c7313bee","line":186,"updated":"2014-06-15 14:06:34.000000000","message":"We were hoping to be able to get the Nova support for oslo.vmware in this cycle. From what you are suggesting this looks like we may have to reevaluate that again.","commit_id":"005a10972b968f0946ecf755f8f5957ef03188f4"},{"author":{"_account_id":1653,"name":"garyk","email":"gkotton@vmware.com","username":"garyk"},"change_message_id":"432bfc592c6848f4c52ed7e709ae9167c7cc2948","unresolved":false,"context_lines":[{"line_number":193,"context_line":""},{"line_number":194,"context_line":"Dependencies"},{"line_number":195,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":196,"context_line":""},{"line_number":197,"context_line":"None"},{"line_number":198,"context_line":""},{"line_number":199,"context_line":"pyVmomi under discussion."}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_873bb3cf","line":196,"updated":"2014-06-15 14:06:34.000000000","message":"is this None or pyVmomi?","commit_id":"005a10972b968f0946ecf755f8f5957ef03188f4"}]}
