Hi Vish, Thank you for your response. I am running into another issue while restarting the cinder-volume and cinder-api:
root@bodega:~/ahmed/cinder# service cinder-api restart stop: Unknown instance: cinder-api start/running, process 25761 root@bodega:~/ahmed/cinder# I looked at the "/etc/init.d/cinder-api" file, and I see a "stop" action define in there. Any idea why I am getting this error? Is cinder-api restarted even with the error. Thank you, Ahmed. From: Vishvananda Ishaya <vishvana...@gmail.com<mailto:vishvana...@gmail.com>> Date: Monday, November 5, 2012 7:22 PM To: Ahmed Al-Mehdi <ah...@coraid.com<mailto:ah...@coraid.com>> Cc: "openstack@lists.launchpad.net<mailto:openstack@lists.launchpad.net>" <openstack@lists.launchpad.net<mailto:openstack@lists.launchpad.net>> Subject: Re: [Openstack] "keystone service-create/endpoint-create" for cinder you can't run nova volume and cinder but it uses all the same settings so you can use the same service entry. You just run cinder-api instead of nova-api-os-volume (or disable osapi_volume if you are using nova-api), run cinder-volume instead of nova-volume and run cinder-scheduler. Vish On Nov 5, 2012, at 5:26 PM, Ahmed Al-Mehdi <ah...@coraid.com<mailto:ah...@coraid.com>> wrote: Hello, I am trying to install cinder in my setup. I already issued a "keystone service-create …" and "keystone endpoint-create …" for nova-volume service, but I plan to install and use cinder. $ keystone --os-token 012345SECRET99TOKEN012345 \ --os-endpoint http://192.168.206.130:35357/v2.0/ \ service-create \ --name=volume \ --type=volume \ --description="Nova Volume Service" +-------------+----------------------------------+ | Property | Value | +-------------+----------------------------------+ | description | Nova Volume Service | | id | 1ff4ece13c3e48d8a6461faebd9cd38f | | name | volume | | type | volume | +-------------+----------------------------------+ $ keystone --os-token 012345SECRET99TOKEN012345 \ --os-endpoint http://192.168.206.130:35357/v2.0/ \ endpoint-create \ --region RegionOne \ --service-id=1ff4ece13c3e48d8a6461faebd9cd38f \ --publicurl='http://192.168.206.130:8776/v1/%(tenant_id)s' \ --internalurl='http://192.168.206.130:8776/v1/%(tenant_id)s' \ --adminurl='http://192.168.206.130:8776/v1/%(tenant_id)s' +-------------+----------------------------------------------+ | Property | Value | +-------------+----------------------------------------------+ | adminurl | http://192.168.206.130:8776/v1/%(tenant_id)s | | id | 1ff4ece13c3e48d8a6461faebd9cd38f | | internalurl | http://192.168.206.130:8776/v1/%(tenant_id)s | | publicurl | http://192.168.206.130:8776/v1/%(tenant_id)s | | region | RegionOne | | service_id | 8a70cd235c7d4a05b43b2dffb9942cc0 | +-------------+----------------------------------------------+ I can easily perform a "keystone service-create …" for cinder, I am a bit confused about "endpoint-create". What port number should I use for the admin/internal/public url? If the same value as nova-volume, will there not be some sort of a conflict. Should I remove/uninstall nova-volume? Purge nova-volume from keystone? Thank you, Ahmed. _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net<mailto:openstack@lists.launchpad.net> Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
