Ask Your Question
1

Which cinder service restart, when I added new backend

asked 2014-10-13 04:28:46 -0500

msuchy gravatar image

Hi, I just added new backend to cinder.conf (and now there are two backends) and I want to restart cinder, so it is aware of new configuration. However I see four services:

  • openstack-cinder-api
  • openstack-cinder-backup
  • openstack-cinder-scheduler
  • openstack-cinder-volume

I'm going to put this in script, therefore I want to restart as less services as possible. Which services I need to restart?

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
1

answered 2014-10-13 10:09:30 -0500

mpetason gravatar image

If you are on a RHEL variant you can check chkconfig to see which servers are supposed to be running on boot for run level 3:

chkconfig | grep -i openstack-cinder | grep "3:on" | while read n; do service $n restart; done

That will go through and restart Cinder services that are supposed to be on at boot. If you are on Ubuntu you can restart them based on the current status of the service:

/etc/init.d/openstack-cinder-(service-name) status
/etc/init.d/openstack-cinder-(service-name) restart

Usually modifications depend on the file you edit so you may be able to just restart openstack-cinder-volume. If it still isn't working properly then you can restart the API and Scheduler if they aren't aware of the updates.

edit flag offensive delete link more

Comments

This is not what I meant. I meant - Does openstack-cinder-api service knows about storage drivers? Or it just blindly forward request received over API to underlying cinder services?And therefore there is no need to restart it? Which services from those 4 actually have to know about storage drivers?

msuchy gravatar imagemsuchy ( 2014-10-14 11:35:29 -0500 )edit

The Cinder API uses the cinder.conf when it is loaded. If you edit cinder.conf then you need to restart the API or reload it so that it is aware of the updates in the conf file. You can view this information by using ps:

ps aux |grep cinder
mpetason gravatar imagempetason ( 2014-10-14 12:53:36 -0500 )edit
0

answered 2014-10-15 00:12:35 -0500

Beny gravatar image

updated 2014-10-15 00:15:45 -0500

You just need to restart the cinder-volume services. this will reload the configurations of backend and sync with the cinder-scheduler.

I did only that when i change the backend to netapp. http://youtu.be/whK76zg444c

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-10-13 04:28:46 -0500

Seen: 5,471 times

Last updated: Oct 15 '14