Open Stack

Hi Kyle,

I have conflicts for 13 UTC - Thursday is already full for me, but I'll try
anyway, to join the convo on IRC.

I agree the 3 blueprints you've mentioned are the ones we should really
merge for Juno.
To this aim, I wonder why [1] has not been set to high. Nevertheless it
does not matter a lot. The code for this blueprint has been thoroughly
reviewed and we're just facing a little problem with RPC versioning.
Akihiro has stepped in to help with [2], which should merge before the RPC
refactor.

I have not followed l3-high-availability, however I see only 3 patches
merged and there a still a bunch in progress/abandoned. Do we have enough
reviewer coverage there?

Finally, the ipsets patch [3] has not been updated in a while. Probably
just because the owner is waiting for reviews, even if imho this should be
seralized on top of [1].

I'm sure we'll be able to identify more blueprints as "highly likely"
candidates for juno. On the other hand I would like to ensure the meeting
agenda is set up in a way that we won't spend all the time discussing
inclusion of a few contented blueprints.

Salvatore

[1]
https://blueprints.launchpad.net/neutron/+spec/security-group-rules-for-devices-rpc-call-refactor
)
[2]
https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bug/1359416,n,z
[3] https://review.openstack.org/#/c/111877/


On 27 August 2014 00:00, Kyle Mestery <mestery at mestery.com> wrote:

> I'd like to propose a meeting at 1300UTC on Thursday in
> #openstack-meeting-3 to discuss Neutron BPs remaining for Juno at this
> point. We're taking specifically about medium and high priority ones,
> with a focus on these three:
>
> https://blueprints.launchpad.net/neutron/+spec/l3-high-availability)
> https://blueprints.launchpad.net/neutron/+spec/add-ipset-to-security)
>
> https://blueprints.launchpad.net/neutron/+spec/security-group-rules-for-devices-rpc-call-refactor
> )
>
> These three BPs will provide a final push for scalability in a few
> areas and are things we as a team need to work to merge this week. The
> meeting will allow for discussion of final issues on these patches
> with the goal of trying to merge them by Feature Freeze next week. If
> time permits, we can discuss other medium and high priority community
> BPs as well.
>
> Let me know if this works by responding on this thread and I hope to
> see people there Thursday!
>
> Thanks,
> Kyle
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140827/c92f7dd3/attachment.html>