Hi Yingxin,
+1 to joining the sprint. 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.
We'll review your spec and get you feedback, but the purpose of the sprint
(Aug
OK, get it.
-Yingxin
From: Tim Hinrichs [mailto:t...@styra.com]
Sent: Thursday, July 23, 2015 11:18 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Congress] Need reviews of bp rpc-for-dse
Hi Yingxin,
We definitely want details for what you
23, 2015 9:43 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Congress] Need reviews of bp rpc-for-dse
Hi Yingxin,
+1 to joining the sprint. If you can't make the mid-cycle sprint in person,
we're planning to have a remote option. Keep in mind
Hi Yingxin,
We definitely want details for what you have in mind. In case you haven't
done this before, we write a 'spec' to explain the details. Here's some
info on how to do that.
https://wiki.openstack.org/wiki/Congress#How_To_Propose_a_New_Feature
Tim
On Thu, Jul 23, 2015 at 12:13 AM
Hi all,
I have some thoughts about congress dse improvement after having read the code
for several days.
Please refer to
bp/rpc-for-dsehttps://blueprints.launchpad.net/congress/+spec/rpc-for-dse,
its idea is to implement RPC in deepsix. Congress can benefit from
lower-coupling between dse
Hi Yingxin,
I think moving Congress from dse to rpc is a good idea.
Congress team will discuss its scalability in mid cycle sprint[1], [2].
I guess using rpc is one of key item for congress to get the ability.
Why don't you join the meetup?
[1]
