<div dir="ltr"><div>Hi Yingxin,</div><div><br></div>+1 to joining the sprint.  <span style="font-size:13.1999998092651px;line-height:1.5">If you can't make the mid-cycle sprint in person, we're planning to have a remote option.  Keep in mind though that it will be harder to engage with everyone if you're remote.    </span><div><span style="font-size:13.1999998092651px;line-height:1.5"><br></span></div><div><span style="font-size:13.1999998092651px;line-height:1.5">We'll review your spec and get you feedback, but the purpose of the sprint (Aug 6-7) is to decide and hopefully build the next generation of communication between the policy engines and the datasources.</span></div><div><span style="font-size:13.1999998092651px;line-height:1.5"><br></span></div><div><span style="font-size:13.1999998092651px;line-height:1.5">Tim</span></div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Jul 23, 2015 at 1:22 AM Masahito MUROI <<a href="mailto:muroi.masahito@lab.ntt.co.jp">muroi.masahito@lab.ntt.co.jp</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Yingxin,<br>
<br>
I think moving Congress from dse to rpc is a good idea.<br>
<br>
Congress team will discuss its scalability in mid cycle sprint[1], [2].<br>
I guess using rpc is one of key item for congress to get the ability.<br>
Why don't you join the meetup?<br>
<br>
[1] <a href="https://wiki.openstack.org/wiki/Sprints/CongressLibertySprint" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Sprints/CongressLibertySprint</a><br>
[2]<br>
<a href="http://www.eventbrite.com/e/congress-liberty-midcycle-sprint-tickets-17654731778" rel="noreferrer" target="_blank">http://www.eventbrite.com/e/congress-liberty-midcycle-sprint-tickets-17654731778</a><br>
<br>
best regard,<br>
masa<br>
<br>
On 2015/07/23 16:07, Cheng, Yingxin wrote:<br>
> Hi all,<br>
><br>
><br>
> I have some thoughts about congress dse improvement after having read the code for several days.<br>
><br>
> Please refer to bp/rpc-for-dse<<a href="https://blueprints.launchpad.net/congress/+spec/rpc-for-dse" rel="noreferrer" target="_blank">https://blueprints.launchpad.net/congress/+spec/rpc-for-dse</a>>, its idea is to implement RPC in deepsix. Congress can benefit from lower-coupling between dse services. And the steps towards oslo-messaging integration can be milder too.<br>
><br>
> Eager to learn everything from Community. Anything wrong, please kindly point it out.<br>
><br>
><br>
> Thank you<br>
> Yingxin<br>
><br>
><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<br>
<br>
--<br>
室井 雅仁(Masahito MUROI)<br>
Software Innovation Center, NTT<br>
Tel: +81-422-59-4539，FAX: +81-422-59-2699<br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div>