I have tracked error message to: # grep -nrF "service['updated_at']" /usr/lib/python2.6/site-packages/ /usr/lib/python2.6/site-packages/cinder/utils.py:929: last_heartbeat = service['updated_at'] or service['created_at']
but now I can't quite figure out what event would trigger update of 'updated_at' column in cinder.services. I see second server references in there though: *************************** 3. row *************************** created_at: 2013-04-17 20:18:33 updated_at: NULL deleted_at: NULL deleted: 0 id: 3 host: nodeB binary: cinder-volume topic: cinder-volume report_count: 0 disabled: 0 availability_zone: nova so it registered itself initially but didn't "update" the record? Now I'm a bit stuck as there are not too many references to updated_at and none of them seems to be relevant to me (most have something to do with glance and volume-to-image transition ?). >________________________________ > From: Dmitry Makovey <[email protected]> >To: Dmitry Makovey <[email protected]>; Daniels Cai <[email protected]> >Cc: "[email protected]" <[email protected]> >Sent: Monday, April 22, 2013 4:36 PM >Subject: Re: [Openstack] Multinode setup? > > > >BTW - I did add > > >iscsi_ip_prefix= 1.1.1.{2,3} >iscsi_ip_address= 1.1.1.{2,3} > > >in /etc/cinder/cinder.conf on both nodes (nodeA:1.1.1.2, nodeB:1.1.1.3) as per >https://lists.launchpad.net/openstack/msg21825.html . If I am to believe that >post my setup should "just work" at this point. Could it be because some >endpoints are defined as "localhost"? I've added non-127.0.0.0/8 entries for >most pertinent endpoints (keystone, cinder*) but I wonder if I need something >else as well? Does OpenStack take issue with multiple endpoints defined? > > > >>________________________________ >> From: Dmitry Makovey <[email protected]> >>To: Daniels Cai <[email protected]> >>Cc: "[email protected]" <[email protected]> >>Sent: Monday, April 22, 2013 4:16 PM >>Subject: Re: [Openstack] Multinode setup? >> >> >> >>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). >> >> > > _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
