<div dir="ltr"><p dir="ltr">Thanks! </p>
<div class="gmail_quote">I've dropped a few comments around on reviews & the blueprints so people not watching the mailing list will see.</div><div class="gmail_quote"><br></div><div class="gmail_quote"><br></div>
<div class="gmail_quote">On Feb 6, 2014 7:32 PM, "Davanum Srinivas" <<a href="mailto:davanum@gmail.com" target="_blank">davanum@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Shawn,<br>
<br>
We are waiting on this infra review to pass - to create the<br>
oslo.vmware git repo.<br>
<a href="https://review.openstack.org/#/c/70761/" target="_blank">https://review.openstack.org/#/c/70761/</a><br>
<br>
-- dims<br>
<br>
On Thu, Feb 6, 2014 at 5:23 PM, Shawn Hartsock <<a href="mailto:hartsock@acm.org" target="_blank">hartsock@acm.org</a>> wrote:<br>
> Hi folks,<br>
><br>
> Just following up on what we were talking about in IRC.<br>
><br>
> The BP: <a href="https://blueprints.launchpad.net/nova/+spec/vmware-soap-session-management" target="_blank">https://blueprints.launchpad.net/nova/+spec/vmware-soap-session-management</a><br>
><br>
> Is supposed to capture some of this work/discussion. Earlier in<br>
> Icehouse we had thought that having some kind of pseudo transaction<br>
> that could encompass a set of calls would be a nice way to allow a<br>
> method to "roll back" to some point and re-try a set of API calls as a<br>
> unit. This proved to be messy so I've abandoned that line of work.<br>
> Instead, (as pointed out by Matthew) the session details should not be<br>
> exposed at all above the Vim object. I think this is generally a good<br>
> direction the only problems would be timing of releases and refactors.<br>
><br>
> The core change I would like to propose to fit well with this idea of<br>
> restructuring around the Vim object revolves around how to verify and<br>
> terminate a session.<br>
><br>
> In particular, vim.SessionIsActive and vim.TerminateSession ... these<br>
> are intended as a system administrator's control API so a root user<br>
> could evict other users. Think of administrating a session through<br>
> these API as using 'kill -KILL <pid>' where this might be appropriate<br>
> if you were a root or super user cleaning out a session list. If you<br>
> were to log out of SSH using 'kill -KILL -1' it would work but it<br>
> would also be a little silly and would by pass logout scripts.<br>
><br>
> Individual users have the ability to check if their session is logged<br>
> in by using vim.CurrentTime or<br>
> ServiceContent.sessionManager.currentSession (you should see that<br>
> sessionManager and currentSession are not None). To log out your own<br>
> session there's a method you can used called vim.Logout which will<br>
> only affect the current session. The vim.TerminateSession can force<br>
> *any* open session off line so if there was a session ID bug in your<br>
> code you could randomly knock other driver instances off line which<br>
> could cause interesting unreproducible bugs for other users of the<br>
> system.<br>
><br>
> References (reading very carefully):<br>
> * <a href="http://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.wssdk.apiref.doc/vim.SessionManager.html" target="_blank">http://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.wssdk.apiref.doc/vim.SessionManager.html</a><br>
> * <a href="http://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.wssdk.apiref.doc/vim.SessionManager.html%23logout" target="_blank">http://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.wssdk.apiref.doc/vim.SessionManager.html#logout</a><br>
> * <a href="http://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.wssdk.apiref.doc/vim.SessionManager.html%23sessionIsActive" target="_blank">http://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.wssdk.apiref.doc/vim.SessionManager.html#sessionIsActive</a><br>
><br>
> ... IN PROGRESS ...<br>
> <a href="https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:session-management-refactor,n,z" target="_blank">https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:session-management-refactor,n,z</a><br>
><br>
> I will be shuffling this patch set around to reflect these changes.<br>
> I've tried to communicate the real purpose of this refactor, not to<br>
> introduce new API but to change how sessions are logged out and/or<br>
> validated.<br>
><br>
> As for<br>
> <a href="https://blueprints.launchpad.net/oslo/+spec/vmware-api" target="_blank">https://blueprints.launchpad.net/oslo/+spec/vmware-api</a><br>
><br>
> I know we're trying to keep this a light weight fork-lift but as we<br>
> address other problems it's becoming clear to me we need to<br>
> incorporate certain key fixes.<br>
><br>
> I emailed with Vipin about <a href="https://review.openstack.org/#/c/65075/" target="_blank">https://review.openstack.org/#/c/65075/</a> he<br>
> is currently waiting for someone to direct him toward the correct<br>
> place to start committing this code. I'll have to refactor<br>
> <a href="https://review.openstack.org/#/c/63229/" target="_blank">https://review.openstack.org/#/c/63229/</a> so it can be used along side<br>
> that library.<br>
><br>
> I do have a question:<br>
> * if Vipin manages to ship an Oslo lib in icehouse is it too late for<br>
> us to change Nova over to that lib in Nova since the BP proposal<br>
> deadlines are past?<br>
><br>
> --<br>
> # Shawn.Hartsock<br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
<br>
--<br>
Davanum Srinivas :: <a href="http://davanum.wordpress.com" target="_blank">http://davanum.wordpress.com</a><br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div>
</div>