Ask Your Question
0

quantum essex milestone-3 install procedure (fail)

asked 2012-01-30 20:32:35 -0500

alejandro-comisario gravatar image

Hi, we are trying to install quantum server and python quantum client.

We downloaded : python-quantumclient-2012.1~e3.tar.gz and quantum-2012.1~e3.tar.gz.

Installed both , and after installation, when we executed quantum-server we received :

root@ism16vms:~# quantum-server Traceback (most recent call last): File "/usr/local/bin/quantum-server", line 9, in <module> load_entry_point('quantum==2012.1', 'console_scripts', 'quantum-server')() File "/usr/local/lib/python2.6/dist-packages/pkg_resources.py", line 337, in load_entry_point return get_distribution(dist).load_entry_point(group, name) File "/usr/local/lib/python2.6/dist-packages/pkg_resources.py", line 2279, in load_entry_point return ep.load() File "/usr/local/lib/python2.6/dist-packages/pkg_resources.py", line 1989, in load entry = __import__(self.module_name, globals(),globals(), ['__name__']) File "/usr/local/lib/python2.6/dist-packages/quantum-2012.1-py2.6.egg/quantum/server/__init__.py", line 36, in <module> from quantum import service File "/usr/local/lib/python2.6/dist-packages/quantum-2012.1-py2.6.egg/quantum/service.py", line 19, in <module> from quantum.common import config ImportError: No module named common

And when we executed quantum, we had :

root@ism16vms:~# quantum Traceback (most recent call last): File "/usr/local/bin/quantum", line 9, in <module> load_entry_point('python-quantumclient==2012.1', 'console_scripts', 'quantum')() File "/usr/local/lib/python2.6/dist-packages/pkg_resources.py", line 337, in load_entry_point return get_distribution(dist).load_entry_point(group, name) File "/usr/local/lib/python2.6/dist-packages/pkg_resources.py", line 2279, in load_entry_point return ep.load() File "/usr/local/lib/python2.6/dist-packages/pkg_resources.py", line 1989, in load entry = __import__(self.module_name, globals(),globals(), ['__name__']) ImportError: No module named client.cli

So, after linking "/usr/local/lib/python2.6/dist-packages/python_quantumclient-2012.1-py2.6.egg/quantum/common" and "/usr/local/lib/python2.6/dist-packages/python_quantumclient-2012.1-py2.6.egg/quantum/client" to "/usr/local/lib/python2.6/dist-packages/quantum-2012.1-py2.6.egg/quantum" quantum-server worked.

So, did we install wrong both python-quantumclient and quantum that we needed to make this links to make it work ?

edit retag flag offensive close merge delete

4 answers

Sort by ยป oldest newest most voted
0

answered 2012-02-16 22:47:38 -0500

Following the instructions in the essex-3 admin guide I still had the issue describe by Alejandro. Linking the common and client directories from python client to quantum solved the issue.

Here is the python path:

Python 2.7.2+ (default, Oct 4 2011, 20:06:09) [GCC 4.6.1] on linux2 Type "help", "copyright", "credits" or "license" for more information.

import sys print sys.path ['', '/usr/local/lib/python2.7/dist-packages/keystone-2012.1-py2.7.egg', '/usr/local/lib/python2.7/dist-packages/python_keystoneclient-2012.1-py2.7.egg', '/usr/local/lib/python2.7/dist-packages/python_quantumclient-2012.1-py2.7.egg', '/usr/local/lib/python2.7/dist-packages/quantum-2012.1-py2.7.egg', '/usr/local/lib/python2.7/dist-packages/WebTest-1.3.3-py2.7.egg', '/usr/local/lib/python2.7/dist-packages/pep8-0.6.1-py2.7.egg', '/usr/lib/pymodules/python2.7', '/usr/lib/python2.7', '/usr/lib/python2.7/plat-linux2', '/usr/lib/python2.7/lib-tk', '/usr/lib/python2.7/lib-old', '/usr/lib/python2.7/lib-dynload', '/usr/local/lib/python2.7/dist-packages', '/usr/lib/python2.7/dist-packages', '/usr/lib/python2.7/dist-packages/gtk-2.0']

edit flag offensive delete link more
0

answered 2012-01-31 02:25:29 -0500

alejandro-comisario gravatar image

Perfect Dan! Thanks!

edit flag offensive delete link more
0

answered 2012-01-31 02:25:12 -0500

alejandro-comisario gravatar image

Thanks dan wendlandt, that solved my question.

edit flag offensive delete link more
0

answered 2012-01-30 21:31:39 -0500

danwent gravatar image

Hi Alejandro,

We actually discovered this issue on Friday, right after the we posted E-3. It was introduced by the last minute splitting of Quantum into separate client & server repos. You did not do anything wrong, and we're in the process of updating the documents to describe a work around.

One simple work around is to copy the __init__.py file from quantum-<version>/quantum/__init__.py (in the server tarball) to python-quantumclient-<version>/quantum/__init__.py, before you run setup.py in the python-quantumclient directory.

You can also probably copy that file into the appropriate location post install, but I haven't tested that exactly. Linking the directories should not be necessary, and we are fixing this issue in E-4. Sorry for the inconvenience on this one! Docs should be updated for this later today.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2012-01-30 20:32:35 -0500

Seen: 45 times

Last updated: Feb 16 '12