# The order of packages is significant, because pip processes them in the order
# of appearance. Changing the order has an impact on the overall integration
# process, which may cause wedges in the gate later.
pbr>=1.8

Babel>=1.3
ncclient>=0.4.6,!=0.5.3;python_version<'3.0'
lxml>=3.3.3
ucsmsdk>=0.9.3.1
oslo.config>=3.7.0  # Apache-2.0
oslo.concurrency>=3.5.0         # Apache-2.0
oslo.db>=4.1.0  # Apache-2.0
oslo.i18n>=2.1.0  # Apache-2.0
oslo.log>=1.14.0  # Apache-2.0
oslo.messaging>=4.0.0 # Apache-2.0
oslo.serialization>=1.10.0              # Apache-2.0
oslo.service>=1.0.0                     # Apache-2.0
oslo.utils>=3.5.0                       # Apache-2.0
neutron-lib>=0.1.0 # Apache-2.0
python-neutronclient
pika>=0.10.0

# The order of packages is significant, because pip processes them in the order
# of appearance. Changing the order has an impact on the overall integration
# process, which may cause wedges in the gate later.
pbr>=1.8

Babel>=1.3
ncclient>=0.4.6,!=0.5.3,<=0.6.0;python_version<'3.0'
lxml>=3.3.3
ucsmsdk>=0.9.3.1
oslo.config>=3.7.0  # Apache-2.0
oslo.concurrency>=3.5.0         # Apache-2.0
oslo.db>=4.1.0  # Apache-2.0
oslo.i18n>=2.1.0  # Apache-2.0
oslo.log>=1.14.0  # Apache-2.0
oslo.messaging>=4.0.0 # Apache-2.0
oslo.serialization>=1.10.0              # Apache-2.0
oslo.service>=1.0.0                     # Apache-2.0
oslo.utils>=3.5.0                       # Apache-2.0
neutron-lib>=0.1.0 # Apache-2.0
python-neutronclient
pika>=0.10.0

Put upper constraint on ncclient version to prevent breakages
Put upper constraint on ncclient version to prevent breakages

ncclient version 0.6.2 just released and broke all our ASR CI, so
instead of picking up new ncclient versions we'll set a max version
which we can increase as required.

Change-Id: I08a60251078dea290f638f061bb96178e692a95c
