Comments inline:
I kind of liked having everything in one directory before
(quantum/...) and that's the way that nova does it but I see how the
way you've split it makes it easier for packaging. Not a big deal.
The problem is that in order to install things as separate packages
(quantum-client, quantum-server, etc) AND have everything all install
correctly the the same namespace, they need to be broken up.
I don't see anyway around this, but if anyone has a suggestion I can
look into it.
I like the idea of the packages on pypi but you've got some typos in
the descriptions (thw -> the) and the description for the sample
plugin says that it is cisco specific.
Before uploading the "final" packages on pypi somebody will want to
change all the package info to the correct version, author, description,
etc. What I have is just filler.
I'm pushing a fix for the sample plugin now.
This still doesn't work in the github branch (I just pulled 5 minutes ago):
ubuntu ~/src/git/tyler-quantum-packaging (55)$ ./run_tests.sh -N
Traceback (most recent call last):
File ".//run_tests.py", line 9, in<module>
from quantum.run_tests import main as tests
ImportError: No module named run_tests
I want to be able to run the tests without installing..
We should do the same thing as nova here instead of the alien
conversion: http://wiki.openstack.org/Packaging/Ubuntu
(i.e. have a debian directory and build packages from that)
If you aren't familiar with debian packaging let me know and I can
handle that part.
I'm not, but that link you sent is exactly the kind of thing I've been
looking for. I'll give it a shot and let you know if I run into any snags.
(I didn't actually install it .. I'm just trying to run the pieces
from the source tree)
ubuntu ~/src/git/tyler-quantum-packaging (55)$ bin/quantum
Traceback (most recent call last):
File "bin/quantum", line 10, in<module>
from quantum.cli import main as cli
ImportError: cannot import name main
ubuntu ~/src/git/tyler-quantum-packaging (57)$ bin/quantum-server
Traceback (most recent call last):
File "bin/quantum-server", line 10, in<module>
from quantum.server import main as server
ImportError: No module named server
This is exactly why I'm glad to get it tested on other systems. I can't
recreate his error. You shouldn't need to install anything (other than
dependencies obviously). In run-tests.py and quantum-server both,
before importing anything it adds the source paths to sys.path. You
don't by chance have any other "quantum" modules in your sys.path? I'm
not sure why you would unless you have a venv sourced, or perhaps left
over outdated packages from before?.
Try:
# Or wherever your Python packages are installed
ls /usr/lib/python2.6/site-packages | grep ^q
If they're there, try removing them and trying to again.
Maybe some files were missed in the commit? (I don't see an
__init__.py inside of common, etc)
The directories quantum/{common|client|sever|} don't have any python
code except setup.py. All of the actual code is in
quantum/{common|client|sever|}/lib/quantum which have proper __init__.py
files.
-Tyler
--
Mailing list: https://launchpad.net/~netstack
Post to : netstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~netstack
More help : https://help.launchpad.net/ListHelp
