Global requirements for OpenStack
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
Morgan Fainberg cb6c00c01f Bump flask to past 1.0 (current 1.0.2) 4 years ago
.zuul.d trigger requirements-check if the lower-constraints.txt file changes 4 years ago
babel-test Babel Integration tests 6 years ago
doc/source Fix bug URL for report a bug link 5 years ago
openstack_requirements make requirements check job check for minimum version definitions. 4 years ago
playbooks skip virtualenv setup when there is already a virtualenv 4 years ago
tools Fix typo in fix-lower-constraints.py 4 years ago
.gitignore add stestr directory to gitignore 4 years ago
.gitreview Added .gitreview 10 years ago
.stestr.conf Move requirements to the PTI 4 years ago
MANIFEST.in Make openstack.requirements installable. 9 years ago
README.rst remove readme content that moved to project-team-guide 4 years ago
bindep.txt Update bindep.txt for ubuntu-bionic 5 years ago
blacklist.txt Allow Pygments in openstack/requirements 4 years ago
detail.py Trivial: Update pypi url to new url 4 years ago
global-requirements.txt Bump flask to past 1.0 (current 1.0.2) 4 years ago
lower-constraints-xfails.txt remove mitmproxy 4 years ago
lower-constraints.txt Bump flask to past 1.0 (current 1.0.2) 4 years ago
projects.txt Merge "Add metalsmith to projects.txt" 4 years ago
requirements.txt Updated from global requirements 5 years ago
setup.cfg Update and replace http with https for doc links 5 years ago
setup.py Updated from global requirements 6 years ago
test-requirements.txt Move requirements to the PTI 4 years ago
tox.ini Move requirements to the PTI 4 years ago
update.py Move commands into cmds subdir. 7 years ago
upper-constraints-xfails.txt remove mitmproxy 4 years ago
upper-constraints.txt Bump flask to past 1.0 (current 1.0.2) 4 years ago

README.rst

Global Requirements for OpenStack Projects

image

Why Global Requirements?

Refer to the Dependency Management section of the Project Team Guide for information about the history of the project and the files involved.

Tools

All the tools require openstack_requirements to be installed (e.g. in a Python virtualenv). They all have help, which is the authoritative documentation.

update-requirements

This will update the requirements in a project from the global requirements file found in .. Alternatively, pass --source to use a different global requirements file:

update-requirements --source /opt/stack/requirements /opt/stack/nova

Entries in all requirements files will have their versions updated to match the entries listed in the global requirements. Excess entries will cause errors in hard mode (the default) or be ignored in soft mode.

generate-constraints

Compile a constraints file showing the versions resulting from installing all of global-requirements.txt:

generate-constraints -p /usr/bin/python2.7 -p /usr/bin/python3 \
  -b blacklist.txt -r global-requirements.txt > new-constraints.txt

edit-constraints

Replace all references to a package in a constraints file with a new specification. Used by DevStack to enable git installations of libraries that are normally constrained:

edit-constraints oslo.db "-e file://opt/stack/oslo.db#egg=oslo.db"

Proposing changes

Look at the Review Guidelines and make sure your change meets them.

All changes to global-requirements.txt may dramatically alter the contents of upper-constraints.txt due to adding or removing transitive dependencies. As such you should always generate a diff against the current merged constraints, otherwise your change may fail if it is incompatible with the current tested constraints.

A change to the minimum specified vesion of a library in global-requirements.txt currenty requires adjusting the lower-constraints.txt file alongside with the new constrainted coinstallable version of minimums.

Regenerating involves five steps.

  1. Install the dependencies needed to compile various Python packages:

    sudo apt-get install $(bindep -b)
  2. Create a reference file (do this without your patch applied):

    generate-constraints -p /usr/bin/python2.7 -p /usr/bin/python3 \
      -b blacklist.txt -r global-requirements.txt > baseline
  3. Apply your patch and generate a new reference file:

    generate-constraints -p /usr/bin/python2.7 -p /usr/bin/python3 \
      -b blacklist.txt -r global-requirements.txt > updated
  4. Diff them:

    diff -p baseline updated
  5. Apply the patch to upper-constraints.txt. This may require some fiddling. edit-constraint can do this for you when the change does not involve multiple lines for one package.

Resources