<div dir="ltr"><div><div><div>Oslo folks,<br><br></div>This is summary of  oslo PTG schedule during one and half days. You can check the details in etherpad link:   <a href="https://etherpad.openstack.org/p/oslo-ptg-pike">https://etherpad.openstack.org/p/oslo-ptg-pike</a><br><br></div>1. oslo.messaging: consistent names for general driver configuration options<br></div>   Some of supported drviers have various option configuration names with for common usage, <span class="gmail-author-a-z78zcz81zz65zuz90zez86zapz90zkuz85zz86zz78z">This has led to a plethora of different configuration options that complicates the   development of Day 1 deployment and configuration tools. </span><span class="gmail-author-a-z78zcz81zz65zuz90zez86zapz90zkuz85zz86zz78z">We propose that 'scrub' the configuration namespace and come up with common generic names that can be shared among the various drivers. </span><span class="gmail-author-a-z78zcz81zz65zuz90zez86zapz90zkuz85zz86zz78z">Note: this is </span><span class="gmail-author-a-z78zcz81zz65zuz90zez86zapz90zkuz85zz86zz78z gmail-b"><b>not</b></span><span class="gmail-author-a-z78zcz81zz65zuz90zez86zapz90zkuz85zz86zz78z"> calling for moving these configuration items 'up' to the DEFAULT group.  Each driver should be able to have its own value for any given configuration setting.  This is necessary for the dual backend deployment scenario.</span><div><div><div><br>2. <span class="gmail-">Messaging Experiences towards hybrid backends<br>   </span><span class="gmail-"><span class="gmail-author-a-5z68zpoz70z2z65zz79z6z82zf4z67zz88zz77zr">Share experience and progress towards introducing dual messaging backend operation</span></span> : <span class="gmail-"></span><span class="gmail-author-a-5z68zpoz70z2z65zz79z6z82zf4z67zz88zz77zr gmail-url"><a href="https://docs.google.com/presentation/d/1Y-3gH8rxrU5KagvDQiqpByfvmgM8no-PLn1O0IT5PCs/edit?usp=sharing">https://docs.google.com/presentation/d/1Y-3gH8rxrU5KagvDQiqpByfvmgM8no-PLn1O0IT5PCs/edit?usp=sharing</a><br><br></span><span class="gmail-">3.</span><span class="gmail-">How to make oslo work done in an efficient way<br>   </span><span class="gmail-"><span class="gmail-author-a-z73z4nbz83zatdp3nz68zqz79zz89zi">1)Track bugs & reviews accoding to their priorities</span><br></span></div><div><span class="gmail-">   2)</span>Record general core reviewers' focus to help get help from them. <span class="gmail-author-a-z73z4nbz83zatdp3nz68zqz79zz89zi gmail-url"><a href="https://etherpad.openstack.org/p/oslo-pike-tracking">https://etherpad.openstack.org/p/oslo-pike-tracking</a><br></span><div class="gmail-" id="gmail-magicdomid86"><span class="gmail-author-a-z73z4nbz83zatdp3nz68zqz79zz89zi gmail-url">   3) Don't migrate to StoryBoard until that's a community goal .<br><br></span></div><span class="gmail-">4.</span><span class="gmail-author-a-z83z0sz84zpz72zz66zy7uz70zmt2z81zd">Add a new policy rule to check specific metadata key<br></span></div><div><span class="gmail-author-a-z83z0sz84zpz72zz66zy7uz70zmt2z81zd">  Decide to change nova codes instead of oslo.policy  </span><span class="gmail-author-a-z83z0sz84zpz72zz66zy7uz70zmt2z81zd gmail-url"><a href="https://etherpad.openstack.org/p/policy_support_for_specific_metadata_keys">https://etherpad.openstack.org/p/policy_support_for_specific_metadata_keys</a></span></div><div><span class="gmail-author-a-z83z0sz84zpz72zz66zy7uz70zmt2z81zd"><br>5. </span><span class="gmail-author-a-q2z81zez77zbz78zz122zt0hz80zaz87zp8">Discuss oslo_messaging.rpc message encryption and security</span><div><div><div>    Trove implements this function in its code base, wan to code be included in oslo.messaging.<br></div><div>    <span class="gmail-author-a-z78zcz81zz65zuz90zez86zapz90zkuz85zz86zz78z">kgiusti - followup with amrith on possible API (message digest)<br><br></span></div><div>6. <span class="gmail-author-a-z73z4nbz83zatdp3nz68zqz79zz89zi">Feature updates & collect ideas<br></span></div><div><span class="gmail-author-a-z73z4nbz83zatdp3nz68zqz79zz89zi">   1) Josh propose a new library to handle remote exceptions in an united way: </span><span class="gmail-author-a-cn0z73zxz87zz74z7z69zz80zz67zz68zifz65z1"></span><span class="gmail-author-a-cn0z73zxz87zz74z7z69zz80zz67zz68zifz65z1 gmail-url"><a href="http://pypi.python.org/pypi/failure">http://pypi.python.org/pypi/failure</a><br></span></div><div><span class="gmail-author-a-cn0z73zxz87zz74z7z69zz80zz67zz68zifz65z1 gmail-url">       Need improve it in code and documentation , test in gate , then adop it .<br></span></div><div><span class="gmail-author-a-cn0z73zxz87zz74z7z69zz80zz67zz68zifz65z1 gmail-url">       gcb will talk with Nova PTL if nova want to adopt it.<br>  2) </span><span class="gmail-author-a-z78zcz81zz65zuz90zez86zapz90zkuz85zz86zz78z">new functions from neutron</span><span class="gmail-author-a-z73z4nbz83zatdp3nz68zqz79zz89zi">(ihrachys)</span><span class="gmail-author-a-z78zcz81zz65zuz90zez86zapz90zkuz85zz86zz78z">: ability to cancel in progress/blocked RPC requests in oslo.messaging</span><span class="gmail-author-a-cn0z73zxz87zz74z7z69zz80zz67zz68zifz65z1 gmail-url"><br></span></div><div><span class="gmail-author-a-cn0z73zxz87zz74z7z69zz80zz67zz68zifz65z1 gmail-url">      ihrachys will file a bug, describe use cases to track this.<br><br></span></div><div><span class="gmail-author-a-cn0z73zxz87zz74z7z69zz80zz67zz68zifz65z1 gmail-url">we also did bug smash to reduce bug numbers in rest of time.   <br></span></div><div><span class="gmail-author-a-cn0z73zxz87zz74z7z69zz80zz67zz68zifz65z1 gmail-url"><br></span></div><div><span class="gmail-author-a-cn0z73zxz87zz74z7z69zz80zz67zz68zifz65z1"> </span></div><div>-- <br><div class="gmail_signature"><div dir="ltr"><div>ChangBo Guo(gcb)</div></div></div>
</div></div></div></div></div></div></div>