[Openstack] icehouse cinder on multiple nodes problem
Anatoly Oreshkin
Anatoly.Oreshkin at pnpi.spb.ru
Wed Jun 25 14:44:22 UTC 2014
Hello,
I have openstack icehouse running on 2 nodes under Centos 6.5 . One node is
controller/network node, other node - compute node.
Cinder is installed and running on both nodes.
Controller/network node has hostname labosctrl (10.76.254.220), compute node has
hostname labos02 (10.76.254.222)
command 'cinder service-list' shows that cinder on labos02 is down, however cinder
services are really running on labos02.
| Binary | Host | Zone | Status | State |
Updated_at | Disabled
Reason |
+------------------+---------------------------+-----------+---------+-------+----------------------------+-----------------+
| cinder-backup | labos02 | labos02 | enabled | down |
2014-06-24T15:23:27.000000 | None
|
| cinder-backup | labosctrl.lss.emc.com | labosctrl | enabled | up |
2014-06-24T15:25:12.000000 | None
|
| cinder-scheduler | labos02 | labos02 | enabled | down |
2014-06-24T15:23:26.000000 | None
|
| cinder-scheduler | labosctrl.lss.emc.com | labosctrl | enabled | up |
2014-06-24T15:25:10.000000 | None
|
| cinder-volume | labos02 at lvm | labos02 | enabled | down |
2014-06-24T15:23:27.000000 | None
|
|
| cinder-volume | labosctrl.lss.emc.com at lvm | labosctrl | enabled | up |
2014-06-24T15:25:02.000000 | None
|
command 'cinder-manage service list' shows
Binary Host Zone Status
State Updated At
cinder-scheduler labosctrl labosctrl enabled
:-) 2014-06-24 15:24:30
cinder-backup labosctrl labosctrl enabled
:-) 2014-06-24 15:24:32
cinder-volume labosctrl labosctrl enabled
:-) 2014-06-24 15:24:32
cinder-scheduler labos02 labos02 enabled
XXX 2014-06-24 15:22:46
cinder-backup labos02 labos02 enabled
XXX 2014-06-24 15:22:47
cinder-volume labos02 at lvm labos02 enabled
XXX 2014-06-24 15:22:47
/etc/cinder/cinder.conf on labosctrl(10.76.254.220) has such parameters:
---------------------------------------------------
enabled_backends=lvm
host=labosctrl.lss.emc.com
storage_availability_zone=labosctrl
default_availability_zone=labosctrl
volume_driver=cinder.volume.drivers.lvm.LVMISCSIDriver
iscsi_ip_address=10.76.254.220
iscsi_helper=tgtadm
/etc/cinder/cinder.conf on labos02(10.76.254.222):
-------------------------------------------------
enabled_backends=lvm
host=labos02
storage_availability_zone=labos02
default_availability_zone=labos02
volume_driver=cinder.volume.drivers.lvm.LVMISCSIDriver
iscsi_ip_address=10.76.254.222
iscsi_helper=tgtadm
'cinder endpoints' shows
+-------------+---------------------------------------------------------------+
| cinder_v2 | Value |
+-------------+---------------------------------------------------------------+
| adminURL | http://10.76.254.220:8776/v2/81b280570f994c3eb9d7bb563096b49a |
| id | 2313e8b0c09249909f0f6c104afa364e |
| internalURL | http://10.76.254.220:8776/v2/81b280570f994c3eb9d7bb563096b49a |
| publicURL | http://10.76.254.220:8776/v2/81b280570f994c3eb9d7bb563096b49a |
| region | RegionOne |
+-------------+---------------------------------------------------------------+
+-------------+---------------------------------------------------------------+
| cinder | Value |
+-------------+---------------------------------------------------------------+
| adminURL | http://10.76.254.220:8776/v1/81b280570f994c3eb9d7bb563096b49a |
| id | 02696554a0fd473292e93834f9269086 |
| internalURL | http://10.76.254.220:8776/v1/81b280570f994c3eb9d7bb563096b49a |
| publicURL | http://10.76.254.220:8776/v1/81b280570f994c3eb9d7bb563096b49a |
| region | RegionOne |
+-------------+---------------------------------------------------------------+
tgt service is also runnung on both nodes.
/etc/tgt/targets.conf has parameters:
include /etc/cinder/volumes/*
default-driver iscsi
Should the nodes have DNS records or /etc/hosts records enough ?
Why don't cinder commands see cinder services being up on labos02 ?
Can anybody help me ?
More information about the Openstack
mailing list