Ah, u might be able to do what u said. Try it out and see how far u can get :)
I would be interested to know how u plan on waiting for all existing operations
to finish. Maybe it's not so hard, not really sure...
Sent from my really tiny device...
On Dec 15, 2013, at 9:43 PM, iKhan
I don't know if this is being planned in Icehouse, if not probably
proposing an approach will help. We have seen cinder-volume service
initialization part. Similarly if we can get our hands on child process
that are running under cinder-volume service, if we terminate those process
and restart
It depends on the corruption that u are willing to tolerate. Sigterm means
the process just terminates, what if said process was 3/4 through some
operation (create_volume for example)??
Personally I am willing to tolerate zero corruption, reliability and
consistency are foundational things for
Hi All,
At present cinder driver can be only configured with adding entries in conf
file. Once these driver related entries are modified or added in conf file,
we need to restart cinder-volume service to validate the conf entries and
create a child process that runs in background.
I am thinking
