openstack/nova - nova - OpenDev: Free Software Needs Free Tools

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

Looks like the fix for #884915 only works with RHEL6. Make it work
correctly on Fedora 16.
Change-Id: I8c996f20d49db688fd8e692bcd836dee693d362a

This adds a patch to fix the broken eventlet code that's installed in the
virtualenv.
Fixes bug 884915
Change-Id: I6dbf755abbc5a52208de3dd892257ce39686d396

Broaden Fedora check to include RHEL and others.
Fixes bug 884885
Change-Id: Ifab330a7f866add91d01c8cf2470e5a12fb4cd4d

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

Change-Id: I924975170c9e3a1ef23b5195cb3a6eed675ec043

... 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

... and use it to install virtualenv with yum if it's not available.
Change-Id: Ibfeeb9c23324724bc26895504e6229076d793c6d

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

Subsequent runs of install_venv.sh should upgrade packages to the
latest available.
Change-Id: Ib9c9ee270b778363900d92398f00c1cab3508578

We don't need to pass the -E argument since we're already running
inside the virtualenv.
Change-Id: Idd77b9bdc067e2288d0fa694a2bb6769675065cf

more user-friendly and not depend on PIP while not in the virtual
environment.

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 :-)

Also adds some tools for dealing with virtualenvs to the tools
directory.