Open Stack

Hi,

This week I've tried to install devstack with zmq. So small status update:

The main problem is that Neutron fails with "redis connection refused". 
Maybe [1] and [2] will fix this.

Smaller ones (I've managed them locally):

[6] No redis, pyzmq in requirements.txt - 
https://bugs.launchpad.net/oslo.messaging/+bug/1417505
[7] Permission denied creating IPC folder /var/run/openstack - 
https://bugs.launchpad.net/devstack/+bug/1417141

Regards,
Oleksii Zamiatin

On 04.02.15 17:07, Li Ma wrote:
> Sorry for the late reply. Your proposal is interesting. According to
> the previous discussion of works on zeromq driver, we should first
> make zeromq driver completed for all the OpenStack projects and CI.
> During these days, lots of patches are submitted to upstream. But some
> critical ones are still in review, [1], [2]. I'm also working on
> devstack support and documentation [3-5]. So, IMO we should make it
> maintainable in the current release cycle. And we can try to improve
> it in the next release cycle.
>
> [1] https://review.openstack.org/#/c/142651/
> [2] https://review.openstack.org/#/c/150286/
> [3] https://review.openstack.org/#/c/143533/
> [4] https://review.openstack.org/#/c/145722/
> [5] https://review.openstack.org/#/c/130943/
>
> Regards,
> Nick
>
> On Fri, Dec 26, 2014 at 10:58 PM, Ilya Pekelny <ipekelny at mirantis.com> wrote:
>> Hi, all!
>>
>> Unexpectedly I met a pretty significant issue when I have been solving a
>> small bug
>> https://bugs.launchpad.net/ubuntu/+source/oslo.messaging/+bug/1367614. The
>> problem is in several parts:
>>
>> * Topics used for several purposes: to set subscriptions and to determine a
>> type of sockets.
>> * Topics is a strings which are modifying inline everywhere where it is
>> needed. So, the topic feature is very distributed and uncoordinated.
>>
>> My issue with the bug was: "It is impossible just hash topic somewhere and
>> not to crash all the driver".  Second part of the issue is: "It is very
>> painful process to trace all the topic modifications which are distributed
>> though all the driver code".
>>
>> After several attempts to fix the bug "with small losses" I concluded that I
>> need to create a control/entry point for topic string. Now I have a
>> proposal:
>>
>> Blueprint —
>> https://blueprints.launchpad.net/oslo.messaging/+spec/zmq-topic-object
>> Spec — https://review.openstack.org/#/c/144149/
>> Patch — https://review.openstack.org/#/c/144120/
>>
>> I want to discuss this feature and receive a feedbacks from a more
>> experienced rpc-Jedi.
>>
>> Thanks!
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>