To ensure that correct process is killed when using a rootwrap
script, we must recursively list the children of our top-level
process and kill the last one. This patch uses the psutil python
module which is already used in the heat-cfntools project.
Change-Id: I702bb9dd794c08fcaab637284ee303de1778cbb9
Now that 1.2.0 has been released, require it rather than one of the beta
release tarballs.
Closes-Bug: #1182861
Change-Id: I75ffc4a572d14488d19491a38742d6920951c171
Implements blueprint ipsec-vpn-reference
This patch implements reference driver implementation for VPNaaS.
The driver uses openswan to manage vpn connections.
Future work: Support ikepolicy and ipsec update
Support service type framework
Intelligent updating of resources
This commit adds jinja2 for requirements.txt for
generating cofig file.
Change-Id: I8c5ed800a71ca014dc7bdbb6a57c4f8d18fa82e0
This patch implements Arista's modular L2 mechanism driver to
automate the management of virtual networks along with physical networks
using Arista hardware devices (Spine and Leaf switches)
This driver uses ML2 Mechanism Driver-API to interface with Neutron ML2 Plugin.
implements: blueprint arista-ml2-mechanism-driver
Change-Id: I1c4ca36cf3d7af013b7b3353e7b7d89fe39f91bf
Define a new ML2 Mechanism Driver that replicates Neutron network/port
configuration changes to NCS: http://www.tail-f.com/network-control-system/
Configuration is sent using a HTTP/JSON interface.
Implements blueprint tailf-ncs
Change-Id: I1f73fa3f2e4eec8e5a0f2865aec2d934e25c76d1
Fixes bug: #1212385
The neutron project includes a setup hook that allows to dinamically
include setup dependencies.
Due to recent changes in the pbr project, the hook raises an exception
on Windows, which ends the setup process.
This fix solves the issue by adapting the hook to the recent pbr changes.
Change-Id: I4b00d74d23a7167a10ba86458943ff16ca51b0db
Babel is needed by code synced in from oslo-incubator, namely
neutron.openstack.common.gettextutils.
Fixes bug #1212135
Change-Id: I7f490fb8cf9a4fcba1711cf464f934d60d6d435e
Fix the alphabetical order in requirement files,
Bring into correspondence with other project,like
https://github.com/openstack/requirements/blob/ \
master/requirements.txt
Fixes bug #1207823
Change-Id: If70ff2a815343615870e54991aa0d3db3adc5147
Fixes bug #1194807
Firstly, we update the oslo.config dep to 1.2.0a3 because of the issue
with namespace packages (bug #1194742).
But the main issue here is that if you currently do:
$> pip install -r quantum/requirements.txt
then you end up with the oslo.config 1.1.1 code installed. This is
because oslo.config>=1.1.0 gets pulled in as a transitive dep and pip
gets confused. You can reproduce with e.g.
$> pip install \
http://.../oslo.config-1.2.0a3.tar.gz#egg=oslo.config-1.2.0a3 \
python-keystoneclient
$> pip freeze | grep oslo.config
oslo.config-1.2.0a3
$> python -c 'from oslo.config.cfg import DeprecatedOpt'
Traceback (most recent call last):
File "<string>", line 1, in <module>
ImportError: cannot import name DeprecatedOpt
This is because of a bug with pip where it sees oslo.config-1.2.0a3 and
oslo.config as two unrelated things. It should strip the version part of
the egg= fragment before using it as a package name, but it doesn't.
However, we can simply use the -f/--find-links pip option in our
requirements.txt to add the tarball URL to the list of URLs considered
and also add the oslo.config>=1.2.0a3 dependency:
$> pip install \
-f http://.../oslo.config-1.2.0a3.tar.gz#egg=oslo.config-1.2.0a3 \
'oslo.config>=1.2.0a3' \
python-keystoneclient
$> pip freeze | grep oslo.config
oslo.config-1.2.0a3
$> python -c 'from oslo.config.cfg import DeprecatedOpt'
This is actually exactly the semantics we want and we go to great
lengths in pbr to get these semantics while using a single tarball URL.
The only downside to this --find-links strategy is that we gain an extra
line in our requirements.txt ... but it does work around the pip bug.
Change-Id: I6f3eb5fd2c75615d9a1cae172aed859b36b27d4c
This change renames everything to Neutron while providing backwards
compatible adjustments for Grizzly configuration files.
implements blueprint: remove-use-of-quantum
Change-Id: Ie7d07ba7c89857e13d4ddc8f0e9b68de020a3d19
Version 0.3.2 resolves a bug that allowed generic "except
Exception:" clauses to catch GreenletExit exceptions.
bug 1097203
Change-Id: Ifc5a40dd1da8d115ccbe7fa4a948d12ff1c89099
Fixes bug #1189889
oslo.config-1.2.0 normalizes section names in config files to lowercase.
This means that simply by upgrading to oslo.config-1.2.0, users will now
be able to do e.g.
[default_servicetype]
description = ...
service_definition = ...
Change the default config files to make it clear we recommend the use of
lowercase section names.
Note, the use of an alpha tarball of oslo.config requires pbr>=0.5.15
but we already require >=0.5.16.
DocImpact
Change-Id: Ia47fb3d168da71d3221b25979f8c9257d70dd64d
Use a version of pbr greater then 0.5.15. Earlier versions have problems
when alpha tarballs are used as dependencies.
Fixes bug 1191155
Change-Id: I889358ae746761b282c5933c53bce10017be4c57
Use a version of stevedore that does not try to
install distribute.
The requirements change is in https://review.openstack.org/#/c/32738/
Change-Id: If39d886cb68044871617600650ef8546635143bc
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.
Fixes: bug #1179008
Change-Id: I6f8a11988982133249d443403f63b4f8724e156e