Fixing vmdk-opsd gettting stopped after multiple vmdkops_admin config init/rm operation

[shuklanirdesh82]

This PR fixes #1291

We don't need to restart vmdk_opsd when config changes since we reopen DB for each request from Docker client and thus we will pick up the change automatically.

With this PR following message from the vmdk_ops.log will be omitted too.

05/24/17 18:50:42 1386157 [MainThread] [ERROR  ] [Errno 38] Function not implemented: '/usr/lib/vmware/vmdkops/bin/vmdk_ops.py'
Traceback (most recent call last):
  File "/usr/lib/vmware/vmdkops/bin/vmdk_ops.py", line 1706, in main
    handleVmciRequests(port)
  File "/usr/lib/vmware/vmdkops/bin/vmdk_ops.py", line 1637, in handleVmciRequests
    c = lib.vmci_get_one_op(g_vmci_listening_socket, byref(cartel), txt, c_int(bsize))
  File "/usr/lib/vmware/vmdkops/bin/vmdk_ops.py", line 1530, in signal_handler_restart
    os.execve(__file__, sys.argv, os.environ)

Testing Done: locally (yes)

Running unit tests in /tmp/vmdk_ops_unittest18831/vmdkops_admin_test.py...
...................................................Nothing to do - Mode=NotConfigured (no local DB, no symlink to shared DB).
Warning: this feature is EXPERIMENTAL
Creating new DB at /etc/vmware/vmdkops/auth-db
=== Service: 
Version: 0.14.ec99c85-0.0.1
Status: Running
Pid: 117748
Port: 1019
LogConfigFile: /etc/vmware/vmdkops/log_config.json
LogFile: /var/log/vmware/vmdk_ops.log
LogLevel: INFO
=== Authorization Config DB: 
DB_LocalPath: /etc/vmware/vmdkops/auth-db
DB_SharedLocation: N/A
DB_Mode: SingleNode (local DB exists)
vmgroup access set succeeded
vmgroup access set succeeded
vmgroup access set succeeded
vmgroup access set succeeded
vmgrou...
----------------------------------------------------------------------
Ran 54 tests in 110.810s

OK

[govint]

Is the service restarted via the startup scripts then?

[msterin]

Please add a few words to the PR description and commit message
Something like we do not need to restart vmdk_opsd when config changes since we reopen DB for each request from Docker client and thus we will pick up the change automatically

[shuklanirdesh82]

Thanks @govint & @msterin for the approval!

#1382 (comment)

Yeah my bad .. I will add to the commit message while merging.

@govint Please have a look at #1382 (comment) we don't need to restart service while performing config changes as executeRequest is creating db connection per thread.