With the potential use of entry points, code from the current tree needs to
be installed into a venv created by install_venv.py via setup.py develop.
This will ensure that the appropriate meta-data and paths are set in the
virtualenv.
Change-Id: I1ca15959c98a24629d2f5b2c385296c4e2fe770c
The most recent version of pip (1.2.1 as of a couple days ago) fails
to install the required Nova .venv packages. Nailing the installed
pip version when using run_tests.sh seems like a reasonable solution
to this issue.
Fixes LP Bug #1047120.
Change-Id: Ic947c04603cf9423c0cf2835351785d4fe795c4b
This required rewriting our Diffie-Hellman-Merkle implementation for
set_admin_password in xen. Fixes bug 917851.
Change-Id: Ic4cdcc06221f003aec2dcd5ba05a1a9ad19d39c9
Rather than just giving users the sudo password prompt immediately,
actually tell them what is about to be installed, so they know
whether it is reasonable to be entering their password.
Change-Id: Ic0c1de812be119384753895531a008075b13494e
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
This simplifies a number of Jenkins jobs which currently, other
than directory names, could be the same for all OpenStack
projects. By renaming the virtualenv directory, the redundant
Jenkins virtualenv build and copy jobs can be eliminated.
Change-Id: Ieaf1dac3207ecb34b911c7edcd2086809abdf49e
Ubuntu Oneiric has a problem with the pip installed version of m2crypto.
This fix installs python-m2crypto via apt-get on Oneiric.
Change-Id: I8290a74b614eb0d0b8d620dbad19d2cc6843de8b
This adds a patch to fix the broken eventlet code that's installed in the
virtualenv.
Fixes bug 884915
Change-Id: I6dbf755abbc5a52208de3dd892257ce39686d396
Added a flag to run_tests.sh to allow user to optionally install venv with --no-site-packages.
This fixes bug 880905
Change-Id: Ic645e0ec56c90b72fef526ebc9f55975d446e2ae
When you create a virtualenv, pip and setuptools/distribute is
installed.
When we later run install_venv.py to update the venv, we should
be sure to grab the latest versions of pip and distribute otherwise
issues like this one are masked:
http://code.google.com/p/sqlalchemy-migrate/issues/detail?id=131
Change-Id: Id206be478ea6c5216dcee6f2f58dc91858c843f5
... so use the system m2crypto library instead.
M2Crypto won't build on Fedora because of some bizarre differences with
Fedora's OpenSSL headers. I can get it to build by doing e.g.
$> python ./tools/install_venv.py
$> cd .nova-venv/build/M2Crypto
$> for i in SWIG/_ec.i SWIG/_evp.i; do sed -i -e "s/opensslconf/opensslconf-x86_64/" $i ; done
$> cd -
$> SWIG_FEATURES=-cpperraswarn ./tools/with_venv.sh pip install M2Crypto
but that's clearly no fun. It should be fine to just use the system
version.
Change-Id: I94c7464bf60ae586e16a2f38b7440cea8dc110e5
libvirt isn't listed in pip-requires because (a) it's not in PyPi and
(b) you always want to use libvirt's python bindings that matches the
version of libvirt installed on the system.
Currently, running nova-compute in virtualenv fails because libvirt
can't be imported. The --no-site-packages flag is what prevents this.
Everything seems to work fine without it. To verify, try deleting the
no-global-site-packages.txt from your .nova-venv.
Change-Id: I1df5e8e3c4426ca333c2d6b5b4fa8ece144dddf3
Also added some more instructive messages to install_venv.py, because otherwise people that don't know what they're doing will install the wrong pip... i.e. I did :-)
