We have a working Open0 setup with our OpenStack VIM registered with ESR. We wish to demonstrate instantiation of a sample VM / VNF from a generic VNFM but corresponding docker image has issues. not sure, if the latest docker image has issues ? Kindly suggest.

On the basis of our observation, we see that redis server is never triggered. Kindly confirm if this is expected behaviour.

ubuntu@openo-16-test:~$ docker ps -a | grep vnfm
1331bb2b0bfe        openoint/nfvo-driver-vnfm-gvnfm          "/bin/sh -c /service/"   43 minutes ago      Up 42 minutes       8484/tcp                       nfvo-dvg
a0128b1c94a2        openoint/gvnfm-vnfmgr                    "/bin/sh -c /service/"   45 minutes ago      Up 45 minutes       8803/tcp                       gvnfm-vnfmgr
19c629bbe382        openoint/gvnfm-vnfres                    "/bin/sh -c /service/"   46 minutes ago      Up 45 minutes       8802/tcp                       gvnf-res
51974ea7167d        openoint/gvnfm-vnflcm                    "/bin/sh -c /service/"   About an hour ago   Up About an hour    8801/tcp                       nfvo-gvlcm
d9f5c8f25a06        openoint/nfvo-driver-vnfm-juju           "/bin/sh -c /service/"   5 days ago          Up 5 days           8483/tcp                       nfvo-vnfmd
ubuntu@openo-16-test:~$ docker logs 1331bb2b0bfe

Environment Variables:
SERVICE_IP=10.200.0.20
MSB_ADDR=10.200.0.1:80

Wait for MSB initialization

cat: GVNFM_DRIVER_CONFIG_PATH/config.py: No such file or directory
Collecting Django==1.9.6 (from -r requirements.txt (line 2))
  Downloading Django-1.9.6-py2.py3-none-any.whl (6.6MB)
    100% |################################| 6.6MB 110kB/s
Collecting djangorestframework==3.3.3 (from -r requirements.txt (line 3))
  Downloading djangorestframework-3.3.3-py2.py3-none-any.whl (662kB)
    100% |################################| 665kB 1.9MB/s
Collecting httplib2==0.9.2 (from -r requirements.txt (line 6))
  Downloading httplib2-0.9.2.zip (210kB)
    100% |################################| 215kB 5.2MB/s
Collecting coverage==4.2 (from -r requirements.txt (line 9))
  Downloading coverage-4.2.tar.gz (359kB)
    100% |################################| 368kB 3.5MB/s
Collecting mock==2.0.0 (from -r requirements.txt (line 10))
  Downloading mock-2.0.0-py2.py3-none-any.whl (56kB)
    100% |################################| 61kB 8.4MB/s
Collecting unittest_xml_reporting==1.12.0 (from -r requirements.txt (line 11))
  Downloading unittest_xml_reporting-1.12.0-py2.py3-none-any.whl
Collecting funcsigs>=1; python_version < "3.3" (from mock==2.0.0->-r requirements.txt (line 10))
  Downloading funcsigs-1.0.2-py2.py3-none-any.whl
Collecting pbr>=0.11 (from mock==2.0.0->-r requirements.txt (line 10))
  Downloading pbr-2.0.0-py2.py3-none-any.whl (98kB)
    100% |################################| 102kB 9.3MB/s
Collecting six>=1.9 (from mock==2.0.0->-r requirements.txt (line 10))
  Downloading six-1.10.0-py2.py3-none-any.whl
Installing collected packages: Django, djangorestframework, httplib2, coverage, funcsigs, pbr, six, mock, unittest-xml-reporting
  Running setup.py install for httplib2 ... done
  Running setup.py install for coverage ... done
Successfully installed Django-1.9.6 coverage-4.2 djangorestframework-3.3.3 funcsigs-1.0.2 httplib2-0.9.2 mock-2.0.0 pbr-2.0.0 six-1.10.0 unittest-xml-reporting-1.12.0
You are using pip version 8.1.2, however version 9.0.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
nohup: appending output to 'nohup.out'