Re: [Openstack] OpenStack Havana with ZMQ

2014-03-27 Thread Rosa, Andrea (HP Cloud Services) 
Hi

>Well, we don't know yet. We are planning a mid-size installation (around 600
>nodes) and I'm looking for options. 

>From my experience I can tell you that for 600 nodes Rabbitmq is absolutely 
>fine.
Regards
--
Andrea Rosa

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] OpenStack Havana with ZMQ

2014-03-26 Thread Ken Peng 

于 2014-3-26 2:29, Antonio Messina 写道:

Well, we don't know yet. We are planning a mid-size installation
(around 600 nodes) and I'm looking for options. As far as I understand
ZMQ should scale better, and allows a more distributed deployment than
RabbitMQ.


AFAIK ZeroMQ doesn't have a broker, it's just server/client libraries.
How do you manage them?

Regards.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] OpenStack Havana with ZMQ

2014-03-25 Thread Antonio Messina 
On Tue, Mar 25, 2014 at 6:58 PM, Nick Maslov  wrote:
> hi,
>
> not related to your problem in particular - but why are you trying to setup
> ZMQ? RabbitMQ is not sufficient for you?

Well, we don't know yet. We are planning a mid-size installation
(around 600 nodes) and I'm looking for options. As far as I understand
ZMQ should scale better, and allows a more distributed deployment than
RabbitMQ.

I also like ZMQ more than RabbitMQ personally, but I still want to
test both solutions before making any decision :)

Antonio

-- 
antonio.s.mess...@gmail.com
antonio.mess...@uzh.ch +41 (0)44 635 42 22
GC3: Grid Computing Competence Center  http://www.gc3.uzh.ch/
University of Zurich
Winterthurerstrasse 190
CH-8057 Zurich Switzerland

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] OpenStack Havana with ZMQ

2014-03-25 Thread Nick Maslov 
hi,

not related to your problem in particular - but why are you trying to setup 
ZMQ? RabbitMQ is not sufficient for you?

cheers,
NM
-- 
Nick Maslov
Sent with Airmail

On March 25, 2014 at 5:47:14 PM, Antonio Messina (antonio.s.mess...@gmail.com) 
wrote:

Hi all,  

I am testing Havana with ZeroMQ but I'm unable to make it work.  

First of all, I have a few questions:  

* I gather that the nova-rpc-zmq-receiver *must* run on *all* nodes  
(including compute nodes), is that correct?  
* the nova-rpc-zmq-receiver is part (in Ubuntu) of the nova-scheduler  
package, should I install the package and disable nova-scheduler on  
the compute nodes? Is there an init script available for it or  
should I create my own?  
* How the communication works: the nova-compute services talk to the  
nova-rpc-zmq-receiver via `tcp://` and the services on the same node  
as the nova-rpc-zmq-receiver talk using `ipc://`?  

I am currently using two nodes: a controller node and a compute node.  
On both nodes I added to nova.conf:  

rpc_zmq_bind_address = *  
rpc_zmq_contexts = 1  
rpc_zmq_host = cloud2.gc3  
rpc_zmq_ipc_dir = /var/run/openstack  
rpc_zmq_matchmaker =  
nova.openstack.common.rpc.matchmaker_ring.MatchMakerRing  
rpc_zmq_port = 9501  

started nova-rpc-zmq-receiver with:  

nova-rpc-zmq-receiver --config-file /etc/nova/nova.conf  

and created a /etc/oslo/matchmaker_ring.json file containing:  

{  
"scheduler": ["cloud2"],  
"conductor": ["cloud2"],  
"cert": ["cloud2"],  
"consoleauth": ["cloud2"],  
"network": ["cloud2"],  
"compute": ["node-08-01-01"]  

}  

where `cloud2` is my controller and `node-08-01-01` is my compute node.  

However, when I run `nova service-list` (or `nova-manage service  
list`) I don't see the compute node:  

+--+---+--+-+---++-+
  
| Binary | Host | Zone | Status | State |  
Updated_at | Disabled Reason |  
+--+---+--+-+---++-+
  
| nova-consoleauth | cloud2 | internal | enabled | up |  
2014-03-25T15:23:49.00 | None |  
| nova-cert | cloud2 | internal | enabled | up |  
2014-03-25T15:24:13.00 | None |  
| nova-scheduler | cloud2 | internal | enabled | up |  
2014-03-25T15:23:36.00 | None |  
| nova-conductor | cloud2 | internal | enabled | up |  
2014-03-25T15:23:56.00 | None |  
+--+---+--+-+---++-+
  

When I start the nova-compute service I see only the following lines  
in the nova-compute.log:  

2014-03-25 16:27:05.158 7791 DEBUG  
nova.openstack.common.rpc.common  
[req-9bf7fc72-6419-4b62-aaa9-b1a7fac964ac None None] Sending  
message(s) to: [(u'conductor.cloud2', u'cloud2')] _multi_send  
/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/impl_zmq.py:725  
2014-03-25 16:27:05.159 7791 DEBUG  
nova.openstack.common.rpc.common  
[req-9bf7fc72-6419-4b62-aaa9-b1a7fac964ac None None] Creating payload  
_call 
/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/impl_zmq.py:650  
2014-03-25 16:27:05.159 7791 DEBUG  
nova.openstack.common.rpc.common  
[req-9bf7fc72-6419-4b62-aaa9-b1a7fac964ac None None] Creating queue  
socket for reply waiter _call  
/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/impl_zmq.py:663  
2014-03-25 16:27:05.162 7791 DEBUG  
nova.openstack.common.rpc.common  
[req-9bf7fc72-6419-4b62-aaa9-b1a7fac964ac None None] Subscribing to  
0a9babcb7ba14b1180621583031a4223 subscribe  
/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/impl_zmq.py:158  
2014-03-25 16:27:05.162 7791 DEBUG  
nova.openstack.common.rpc.common  
[req-9bf7fc72-6419-4b62-aaa9-b1a7fac964ac None None] Connecting to  
ipc:///var/run/openstack/zmq_topic_zmq_replies.node-08-01-01.gc3 with  
SUB __init__ 
/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/impl_zmq.py:136  
2014-03-25 16:27:05.162 7791 DEBUG  
nova.openstack.common.rpc.common  
[req-9bf7fc72-6419-4b62-aaa9-b1a7fac964ac None None] -> Subscribed to  
0a9babcb7ba14b1180621583031a4223 __init__  
/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/impl_zmq.py:137  
2014-03-25 16:27:05.162 7791 DEBUG  
nova.openstack.common.rpc.common  
[req-9bf7fc72-6419-4b62-aaa9-b1a7fac964ac None None] -> bind: False  
__init__ 
/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/impl_zmq.py:138  
2014-03-25 16:27:05.163 7791 DEBUG  
nova.openstack.common.rpc.common  
[req-9bf7fc72-6419-4b62-aaa9-b1a7fac964ac None None] Sending cast  
_call 
/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/impl_zmq.py:676  
2014-03-25 16:27:05.163 7791 DEBUG  
nova.openstack.common.rpc.common  
[req-9bf7fc72-6419-4b62-aaa9-b1a7fac964ac None None] Connecting to  
tcp://cloud2:9501 with PUSH __init__  
/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/impl_zmq.py:136  
2014-03-25 16:27:05.163 7791 DEBU

[Openstack] OpenStack Havana with ZMQ

2014-03-25 Thread Antonio Messina 
Hi all,

I am testing Havana with ZeroMQ but I'm unable to make it work.

First of all, I have a few questions:

* I gather that the nova-rpc-zmq-receiver *must* run on *all* nodes
  (including compute nodes), is that correct?
* the nova-rpc-zmq-receiver is part (in Ubuntu) of the nova-scheduler
  package, should I install the package and disable nova-scheduler on
  the compute nodes? Is there an init script available for it or
  should I create my own?
* How the communication works: the nova-compute services talk to the
  nova-rpc-zmq-receiver via `tcp://` and the services on the same node
  as the nova-rpc-zmq-receiver talk using `ipc://`?

I am currently using two nodes: a controller node and a compute node.
On both nodes I added to nova.conf:

rpc_zmq_bind_address = *
rpc_zmq_contexts = 1
rpc_zmq_host = cloud2.gc3
rpc_zmq_ipc_dir = /var/run/openstack
rpc_zmq_matchmaker =
nova.openstack.common.rpc.matchmaker_ring.MatchMakerRing
rpc_zmq_port = 9501

started nova-rpc-zmq-receiver with:

nova-rpc-zmq-receiver --config-file /etc/nova/nova.conf

and created a /etc/oslo/matchmaker_ring.json file containing:

{
  "scheduler": ["cloud2"],
  "conductor": ["cloud2"],
  "cert": ["cloud2"],
  "consoleauth": ["cloud2"],
  "network": ["cloud2"],
  "compute": ["node-08-01-01"]

}

where `cloud2` is my controller and `node-08-01-01` is my compute node.

However, when I run `nova service-list` (or `nova-manage service
list`) I don't see the compute node:


+--+---+--+-+---++-+
| Binary   | Host  | Zone | Status  | State |
Updated_at | Disabled Reason |

+--+---+--+-+---++-+
| nova-consoleauth | cloud2| internal | enabled | up|
2014-03-25T15:23:49.00 | None|
| nova-cert| cloud2| internal | enabled | up|
2014-03-25T15:24:13.00 | None|
| nova-scheduler   | cloud2| internal | enabled | up|
2014-03-25T15:23:36.00 | None|
| nova-conductor   | cloud2| internal | enabled | up|
2014-03-25T15:23:56.00 | None|

+--+---+--+-+---++-+

When I start the nova-compute service I see only the following lines
in the nova-compute.log:

2014-03-25 16:27:05.158 7791 DEBUG
nova.openstack.common.rpc.common
[req-9bf7fc72-6419-4b62-aaa9-b1a7fac964ac None None] Sending
message(s) to: [(u'conductor.cloud2', u'cloud2')] _multi_send
/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/impl_zmq.py:725
2014-03-25 16:27:05.159 7791 DEBUG
nova.openstack.common.rpc.common
[req-9bf7fc72-6419-4b62-aaa9-b1a7fac964ac None None] Creating payload
_call /usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/impl_zmq.py:650
2014-03-25 16:27:05.159 7791 DEBUG
nova.openstack.common.rpc.common
[req-9bf7fc72-6419-4b62-aaa9-b1a7fac964ac None None] Creating queue
socket for reply waiter _call
/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/impl_zmq.py:663
2014-03-25 16:27:05.162 7791 DEBUG
nova.openstack.common.rpc.common
[req-9bf7fc72-6419-4b62-aaa9-b1a7fac964ac None None] Subscribing to
0a9babcb7ba14b1180621583031a4223 subscribe
/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/impl_zmq.py:158
2014-03-25 16:27:05.162 7791 DEBUG
nova.openstack.common.rpc.common
[req-9bf7fc72-6419-4b62-aaa9-b1a7fac964ac None None] Connecting to
ipc:///var/run/openstack/zmq_topic_zmq_replies.node-08-01-01.gc3 with
SUB __init__ 
/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/impl_zmq.py:136
2014-03-25 16:27:05.162 7791 DEBUG
nova.openstack.common.rpc.common
[req-9bf7fc72-6419-4b62-aaa9-b1a7fac964ac None None] -> Subscribed to
0a9babcb7ba14b1180621583031a4223 __init__
/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/impl_zmq.py:137
2014-03-25 16:27:05.162 7791 DEBUG
nova.openstack.common.rpc.common
[req-9bf7fc72-6419-4b62-aaa9-b1a7fac964ac None None] -> bind: False
__init__ 
/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/impl_zmq.py:138
2014-03-25 16:27:05.163 7791 DEBUG
nova.openstack.common.rpc.common
[req-9bf7fc72-6419-4b62-aaa9-b1a7fac964ac None None] Sending cast
_call /usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/impl_zmq.py:676
2014-03-25 16:27:05.163 7791 DEBUG
nova.openstack.common.rpc.common
[req-9bf7fc72-6419-4b62-aaa9-b1a7fac964ac None None] Connecting to
tcp://cloud2:9501 with PUSH __init__
/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/impl_zmq.py:136
2014-03-25 16:27:05.163 7791 DEBUG
nova.openstack.common.rpc.common
[req-9bf7fc72-6419-4b62-aaa9-b1a7fac964ac None None] -> Subscribed to
None __init__ 
/usr/lib/python2.7/dist-packages/