openstack team mailing list archive

[Dmitry Makovey <dmakovey@xxxxxxxxx>]

Thanks for reply,

1. checked DB and have mysql:cinder:services listing both cinder hosts running cinder-volume, cinder-api and cinder-scheduler. I think I should be running cinder-volume only but that doesn't work either. I tried running :
nodeA: cinder-{api,volume,sheduler}, keystone,nova*
nodeB: cinder-volume
but that seems to be wrong.

2. do you mean I should skip "--availability-zone" flag and just overflow one cinder instance and to see whether second will pick up the slack?

BTW - with "--availability-zone={nova-volume,nova,cinder}:nodeB" I keep on getting:

WillNotSchedule: Host nodeB is not up or doesn't exist.


Quite possibly I forgot to setup something simple, but what?

What is the right sequence to install 2 cinder nodes that I can use from my nova nodes? (I don't care about HA/redundancy at this point).



>________________________________
> From: Daniels Cai <danxcai@xxxxxxxxx>
>To: Dmitry Makovey <dmakovey@xxxxxxxxx> 
>Cc: Dmitry Mescheryakov <dmescheryakov@xxxxxxxxxxxx>; "openstack@xxxxxxxxxxxxxxxxxxx" <openstack@xxxxxxxxxxxxxxxxxxx> 
>Sent: Friday, April 19, 2013 6:21 PM
>Subject: Re: [Openstack] Multinode setup?
> 
>
>
>hi Dmitry
>Cinder service is not managed by nova-manage service list 
>Mq is only needed to be installed once 
>
>
>You can do the following to check whether multi node works 
>
>
>1.check MySQL db cinder database , there should be a table named "service" which record all the available cinder services. 
>If not please check your cinder config file,make sure the service record is created and do step2 
>
>
>2. tail -f /var/log/cinder/cinder-volume in all of your cinder scheduler service host 
>And then create as many empty cinder volume as you can 
>A log will be generated when a cinder-volume works 
>
>
>
>
>
>发自我的 iPhone
>
>在 2013-4-20，3:18，Dmitry Makovey <dmakovey@xxxxxxxxx> 写道：
>
>
># cinder-manage host list
>>
>>host                            zone           
>>primary.bar.com           nova           
>>foo.bar.com          nova           
>>
>>
>>however 
>># nova-manage service list 
>>only shows nova services on primary node (since that's the only place that has it installed) 
>>
>>
>>
>>>________________________________
>>> From: Dmitry Mescheryakov <dmescheryakov@xxxxxxxxxxxx>
>>>To: Dmitry Makovey <dmakovey@xxxxxxxxx> 
>>>Cc: "openstack@xxxxxxxxxxxxxxxxxxx" <openstack@xxxxxxxxxxxxxxxxxxx> 
>>>Sent: Friday, April 19, 2013 11:41 AM
>>>Subject: Re: [Openstack] Multinode setup?
>>> 
>>>
>>>
>>>Did you try running
>>>nova-manage service list
>>>?
>>>
>>>
>>>It should show services status relatively to node on which you run that command.
>>>
>>>
>>>
>>>2013/4/19 Dmitry Makovey <dmakovey@xxxxxxxxx>
>>>
>>>played with --availability-zone, so after specifying:
>>>>
>>>># cinder  create --availability-zone nova:foo.bar.com 10
>>>>
>>>>
>>>>I get:
>>>>
>>>># cinder show c1e4bcc1-c8aa-4bc6-93a8-88e362028f9a
>>>>+---------------------+--------------------------------------+
>>>>|       Property      |                Value                 |
>>>>+---------------------+--------------------------------------+
>>>>|     attachments     |                  []                  |
>>>>|  availability_zone  |     nova:foo.bar.com               |
>>>>|      created_at     |      2013-04-19T17:06:40.000000      |
>>>>| display_description |                 None                 |
>>>>|     display_name    |                 None                 |
>>>>|          id         | c1e4bcc1-c8aa-4bc6-93a8-88e362028f9a |
>>>>|       metadata      |                  {}                  |
>>>>|         size        |                  10                  |
>>>>|     snapshot_id     |                 None                 |
>>>>|        status       |                error                 |
>>>>|     volume_type     |                 None                 |
>>>>+---------------------+--------------------------------------+
>>>>
>>>>I can create volumes just fine without --availability-zone, however they are always created on "primary" cinder node that runs cinder-api, cinder-scheduler and cinder-volume and not on secondary that runs cinder-api and cinder-volume. 
>>>>
>>>>I have added to /etc/cinder/cinder.conf:
>>>>
>>>>iscsi_ip_prefix= 1.1.1.2
>>>>
>>>>and 
>>>>
>>>>iscsi_ip_prefix= 1.1.1.3
>>>>
>>>>
>>>>on both hosts but I get nothing. creation with availability zone specified fails every time. 
>>>>
>>>>from /var/log/cinder/scheduler.log on primary node I get:
>>>>
>>>>2013-04-19 11:06:40 13525 ERROR cinder.openstack.common.rpc.amqp [-] Exception during message handling
>>>>2013-04-19 11:06:40 13525 TRACE cinder.openstack.common.rpc.amqp Traceback (most recent call last):
>>>>2013-04-19 11:06:40 13525 TRACE cinder.openstack.common.rpc.amqp   File "/usr/lib/python2.6/site-packages/cinder/openstack/common/rpc/amqp.py", line 276, in _process_data
>>>>2013-04-19 11:06:40 13525 TRACE cinder.openstack.common.rpc.amqp     rval = self.proxy.dispatch(ctxt, version, method, **args)
>>>>2013-04-19 11:06:40 13525 TRACE cinder.openstack.common.rpc.amqp   File "/usr/lib/python2.6/site-packages/cinder/openstack/common/rpc/dispatcher.py", line 145, in dispatch
>>>>2013-04-19 11:06:40 13525 TRACE cinder.openstack.common.rpc.amqp     return getattr(proxyobj, method)(ctxt, **kwargs)
>>>>2013-04-19 11:06:40 13525 TRACE cinder.openstack.common.rpc.amqp   File "/usr/lib/python2.6/site-packages/cinder/scheduler/manager.py", line 98, in _schedule
>>>>2013-04-19 11:06:40 13525 TRACE cinder.openstack.common.rpc.amqp     db.volume_update(context, volume_id, {'status': 'error'})
>>>>2013-04-19 11:06:40 13525 TRACE cinder.openstack.common.rpc.amqp   File "/usr/lib64/python2.6/contextlib.py", line 23, in __exit__
>>>>2013-04-19 11:06:40 13525 TRACE cinder.openstack.common.rpc.amqp     self.gen.next()
>>>>2013-04-19 11:06:40 13525 TRACE cinder.openstack.common.rpc.amqp   File "/usr/lib/python2.6/site-packages/cinder/scheduler/manager.py", line 94, in _schedule
>>>>2013-04-19 11:06:40 13525 TRACE cinder.openstack.common.rpc.amqp     return driver_method(*args, **kwargs)
>>>>2013-04-19 11:06:40 13525 TRACE cinder.openstack.common.rpc.amqp   File "/usr/lib/python2.6/site-packages/cinder/scheduler/simple.py", line 59, in schedule_create_volume
>>>>2013-04-19 11:06:40 13525 TRACE cinder.openstack.common.rpc.amqp     raise exception.WillNotSchedule(host=host)
>>>>2013-04-19 11:06:40 13525 TRACE cinder.openstack.common.rpc.amqp WillNotSchedule: Host foo.bar.com is not up or doesn't exist.
>>>>
>>>>does that mean I have to run Qpid on secondary as well?
>>>>
>>>>
>>>>
>>>>>________________________________
>>>>> From: Dmitry Makovey <dmakovey@xxxxxxxxx>
>>>>>To: "dmescheryakov@xxxxxxxxxxxx" <dmescheryakov@xxxxxxxxxxxx>
>>>>>Cc: "openstack@xxxxxxxxxxxxxxxxxxx" <openstack@xxxxxxxxxxxxxxxxxxx>
>>>>>Sent: Thursday, April 18, 2013 10:37 PM
>>>>
>>>>>Subject: Re: [Openstack] Multinode setup?
>>>>>
>>>>>
>>>>>
>>>>
>>>>>thanks for the pointer. cinder indeed has --availability-zone switch. I'll try to play with that one
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>_______________________________________________
>>Mailing list: https://launchpad.net/~openstack
>>Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>>Unsubscribe : https://launchpad.net/~openstack
>>More help   : https://help.launchpad.net/ListHelp
>>
>
>