We don't need to have the vi modelines in each source file,
it can be set in a user's vimrc if required.
Also a check is added to hacking to detect if they are re-added.
Change-Id: I347307a5145b2760c69085b6ca850d6a9137ffc6
Closes-Bug: #1229324
See I62ce43a330d7ae94eda4c7498782a655e63747fa for the gorey details on
why this exists.
As of this fix:
https://github.com/eventlet/eventlet/pull/34
which was released in eventlet 0.13, we no longer need the patch.
This has now been removed from oslo-incubator, so this is really just
syncing that removal.
Change-Id: I84267f3c6726cb2e750f615e107c48b12c6ed353
This is for Python 3 compatibility, since Python 3 does not support
the print statement, only the print function. (Python 2.6 and 2.7
support both, depending on whether a __future__ import is used.)
Paths containing "xen" were left alone, because of comments in a
couple of the files indicating that the XenServer code needed to be
compatible with Python 2.4.
Fixes bug 1226943
Change-Id: I23b804a4d99500b4acf81dd19645ab06dfcc9f1c
Rename tools/pip-requires to requirements.txt and tools/test-requires
to test-requirements.txt. These are standard files, and tools in the
general world are growing intelligence about them.
Change-Id: I68ece8406fb1d4e082a42db8e76e17b1aaa7e775
Fixes: bug #1179008
run_tests.sh, with_venv.sh, and the install_venv.py scripts now
support relocating the venv root to another location.
All 3 scripts now support new envinroment variables to configure
the location of the venv and the tools directory. To maintain
compatability the defaults are set to the current values.
venv_path = Location of the virtualenv directory
Default: $(pwd)
venv_name = Name of the virtualenv directory
Default: .venv
tools_path = Location of the tools directory
Default: $(pwd)
Additionally the run_tests.sh script also takes these value as
arguments and will pass them along accordingly.
--virtual-env-path <path> Location of the virtualenv directory
Default: $(pwd)
--virtual-env-name <name> Name of the virtualenv directory
Default: .venv
--tools-path <dir> Location of the tools directory
Default: $(pwd)
DocImpact
Change-Id: I1be036058227206ecca342f692cd3d6aadb24069
Fixes: bug #1116942
This commit syncs in the latest version of install_venv_common
from oslo, which fixes the import issue that was previously
addressed by change: I8a3df02a51c2c777d8f47cb8bc72d0644ae47095
which gets reverted by this commit.
Change-Id: I910610da5a4c413711819ca39627cb9ee94814ef
On systems that don't use devstack the nova directory
doesn't automatically get added to the python path. This
breaks tools/install_venv_common.py which imports from
nova.openstack.common. This fixes the issue by manually
adding the nova root directory to the python path before
tools/install_venv_common.py is imported.
Change-Id: I8a3df02a51c2c777d8f47cb8bc72d0644ae47095
This syncs install_venv_common.py from oslo and reworks the
tools/install_venv.py script to use the new library.
Change-Id: I020eae1ec9e3a6aae0ecc7825c0ef723ab247f39
Convert nova from using nosetests to testr for its test runner. Some
tests had to be modified to get them to run properly under testr.
run_tests.sh has been updated to run testr instead of nosetests.
Coverage is collected by running subunit.run under coverage.py when the
coverage environment is selected.
Note that you will need to rebuild your virtualenvs as nose is being
removed from the dependency lists and is being replaced by testr. Tests
will run in different processes once this test is merged so you cannot
use test classes to pass information between tests. Each test should be
a proper independent unit. Additionally the -x and -d flags to
run_tests.sh have been removed as there are currently no decent
approximations for those functions.
Change-Id: I019ca098972ca749b195f59968cf21edd5ba9109
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
