← Back to team overview

openstack team mailing list archive

Re: Multinode setup?

 

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
>
>


Follow ups

References