Open Stack

Josh,

thanks. yes, the kombu vs pika is just a research thing someone should
look at. no blueprint, no spec, so not approved in anyway :)

-- dims

On Wed, May 27, 2015 at 1:24 PM, Joshua Harlow <harlowja at outlook.com> wrote:
> Thanks dims!
>
> Good write up,
>
> Other things I noted (more controversial ones); is that we need to come up
> with a concurrency strategy (and/or guidelines, and/or best practices). At
> least I feel this will be a way that works and imho implies that one
> concurrency strategy will (likely) not fit every project; at the best we can
> do is try to offer best practices.
>
> Also for the pika one, I'd really like to understand why not kombu. I don't
> know enough of the background, but from that session it looks like we need
> to do some comparative analysis (and imho get feedback from asksol[1] and
> others) before we go to deep down that rabbit hole (no jump to another
> 'greener pasture' imho should be done without all of this, to avoid pissing
> off the two [kombu, pika] communities).
>
> My 2 cents :-P
>
> [1] https://github.com/ask
>
> -Josh
>
> Davanum Srinivas wrote:
>>
>> Hi Team,
>>
>> Here are the etherpads from the summit[1].
>> Some highlights are as follows:
>> Oslo.messaging : Took status of the existing zmq driver, proposed a
>> new driver in parallel to the existing zmq driver. Also looked at
>> possibility of using Pika with RabbitMQ. Folks from pivotal promised
>> to help with our scenarios as well.
>> Oslo.rootwrap : Debated daemon vs a new privileged service. The Nova
>> change to add rootwrap as daemon is on hold pending progress on the
>> privsep proposal/activity.
>> Oslo.versionedobjects : We had a nice presentation from Dan about what
>> o.vo can do and a deepdive into what we could do in next release.
>> Taskflow : Josh and team came up with several new features and how to
>> improve usability
>>
>> We will also have several new libraries in Liberty (oslo.cache,
>> oslo.service, oslo.reports, futurist, automaton etc). We talked about
>> our release processes, functional testing, deprecation strategies and
>> debated a but about how best to move to async models as well. Please
>> see etherpads for detailed information.
>>
>> thanks,
>> dims
>>
>> [1] https://wiki.openstack.org/wiki/Design_Summit/Liberty/Etherpads#Oslo
>>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Davanum Srinivas :: https://twitter.com/dims