Ask Your Question
0

Changes in nova.conf overwritten

asked 2014-11-12 17:45:59 -0500

GLaupre gravatar image

Hello everyone, I don't understand a thing, I am using devstack and I have the stack deployed. I don't want to ./unstack.sh to change some cfg in nova.conf.

Therefore I go onto the correct screen (screen -x) and I stop the service by ctrl+c. I change my nova.conf. I return onto the screen and I use the UP arrow to restart my service, "ENTER", 'bim', the service starts again. But the modifications I made in nova.conf are overwritten. Therefore how can I change the nova.conf file so that my changes are applied without ./unstack.

Thanks

edit retag flag offensive close merge delete

3 answers

Sort by ยป oldest newest most voted
0

answered 2014-11-13 12:23:11 -0500

GLaupre gravatar image

I actually changed configurations related to nova-networking. I just killed nova-compute but not nova-network...

Therefore the changes couldn't be updated because the service was still running..

That leads to another questions, if I change the nova.conf, to apply the changes, shall I stop all nova services or only the ones related to the variables I changed in the nova.conf files? tks

edit flag offensive delete link more

Comments

All services are not required to be restarted. Just the services you want to be updated needs restart. In your case you just restart nova-network for updating the changes you made in nova.conf.

yatin gravatar imageyatin ( 2014-11-13 21:24:42 -0500 )edit
0

answered 2014-11-13 09:43:42 -0500

yatin gravatar image

It is not required to run unstack.sh if you want to change configuration related to a particular component. You can do the way you are doing i.e. stop the service, change the configuration as required and rerun the command on the screen. I am able to do this and in my case the modified configuration are updated. If you are not able to do this, tell what configurations you updated and how you verified that configurations are overwritten.

edit flag offensive delete link more
0

answered 2014-11-12 21:28:45 -0500

rajiv-kumar gravatar image

Are you sure that you are killing the right process. I think it is better, If you kill your service by process id and then start. What you can do is, press ctrl + z, it will stop that service and then using ps -e | grep nova find out all the nova-services running and then use kill -9 processid to kill all the nova-services and after committing changes then you can start all the services in the screens different screens. Make sure you start all the services.

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-11-12 17:45:59 -0500

Seen: 256 times

Last updated: Nov 13 '14