Most elements in this repo are old, untested and no longer used, so
remove all those we're not using (as proven via CI).
I think there are some remaining things we build into the images but no
longer need, but those can be handled via follow-up patches.
Change-Id: I221c5a3f82a2500c90646fc69439a210cf64e5e1
The version of pbr we were using was having trouble parsing a new version
identifier for python-qpid, We have the pbr version hardcoded in many
places so update it to match whats currently in global-requirements.
Fixes bug #1470871
Change-Id: Ia5aec472555ad1368684b224a55c29242ae40b58
This was added in If3300a6b1ef1c633fc339f884e9dab0d82bc0720 and should
be removed now that the new setuptools version fixes our issues.
Change-Id: I3ded4f83918d74ca91a8c7a4aede9ef4d1d7a489
Setuptools 8.0 changed the way it parses version strings and many of our
openstack packages break when using it. Pinning this for now until our
packages are fixed.
Closes-Bug: #1402305
Change-Id: If3300a6b1ef1c633fc339f884e9dab0d82bc0720
As advised in I072cf8bf6748d0c910fecffdf2282bcc4656d038, code should
use 4 spaces for indentation.
This commit enforces the use of 4 spaces indentation.
In order to simplify the review process, this patch only cover the
following elements:
- nagios3
- network-utils
- neutron-openvswitch
- nova-api
- nova-baremetal
- nova-compute
- nova-kvm
- openstack-client
- openstack-db
- openstack-ssl
Change-Id: I489746d384c0c2c5a4f2b12444606e3bf8e3ce11
Install the openstack client libraries with 'pip install .' and
not python setup.py develop. The reason for this is that
python setup.py develop had the side effect of changing the
python path inside the virtualenv causing the problems whereas
pip install . doesn't.
I also want to delete the /opt/stack/python-client git directories
later.
Change-Id: Idc68e85c68f1c423f083e656d65d1654688dc84b
Updates install-openstack-clients so that it parses args rather than
using positional parameters.
Updates the various source install elements so that we use a
new {CLIENTNAME}_VENV_DIR variable (set via an environment.d hook)
to configure the virtualenv directory. The in element default is
the same as before (/opt/stack/venvs/python-clientname)
We also add support for controlling the virtualenv
--system-site-packages options by passing -s to the
install-openstack-client bin. This is externally
controllable by setting the {CLIENTNAME}_EXTRA_INSTALL_OPTS
variable. (defaults to "")
This is cleaner in that we aren't hard coding /opt/stack/venv
everywhere and also supports both isolated and shared
venvs (which some people would like to use).
Change-Id: Ieb90be14a5fb1a644d253777d6468870995372b0
Create the pip-manifest element to encapsulate the saving and use
of pip manifest files.
Ensure that it installs prior to any elements that should be able
to use it.
Write pip manifest files for installs in:
* os-svc-install
* os-apply-config
* os-collect-config
* os-refresh-config
* openstack-clients
Enable using a manifest file to reinstall exact versions of
packages in a subsequent run through the DIB_PIP_MANIFEST_*
environment variables.
Change-Id: I4d4ab5921c534727b48cb9969ec8ecfd2c26e6ed
When a pypi mirror is used with certain conditions installing pbr as a
dependency fails. This is a temporary fix until the underlying cause
is resolved.
This is also required for a wheels based pip mirror to work.
Change-Id: Ia08eb16b96d9897fa2f86239ea264b145ef0b9b5
Closes-Bug: #1293812
Each client has its own install type directory. This is needed because
of the multiple repositories with different names in
source-repository-clients.
The client install logic has been refactored into the
install-openstack-client script so that each source install can reuse
it.
An alternative implementation would be add the ability to the
source-repositories element to support an alternate repo override name
for elements that have multiple entries in their source-repository
configuration. For example, the source-repository file for
openstack-clients is called source-repository-clients. We could add
support to look for a clients-source-install or clients-package-install
directory. However, we'd lose the ability to mix source and package
install types from the same element. Given that, I went with the
implementation here.
Note that the ironic client is not broken out by install type, because
there are no packages that yet exist for it.
Change-Id: I2700490d139db47b69dd0f30cd46d9d7e72b7809
Steven Hardy