We dont ever actually import this anywhere or depend on it as a python
dependency. Instead, its part of our diskimage-builder elements and
is largely an opinionated deployer choice we've made. The only purpose
having it in requirements.txt is to pull it in during installation, which
should be delegated to ansible/DIB instead.
This also manually sync's global-requirements along with the update.
Closes-bug: #1526527
Change-Id: I834efb47ccda02a5163c5083836ff29fdc3fdd6f
Syncs requirements with current liberty g-r using requirements/update.py
Note gunicorn is not in g-r and is appended to the list manually
Change-Id: Iaab5c9beeeb2f9055c53b94860d123be411faa8e
updated setup.cfg with sections and
setup.py with packaging pbr
Partialy Implements: blueprint ci-updates
Change-Id: Ie4707c1bba741cbeb16f02312d5db8cc0c134b6a
This change makes the MGT API service fully configurable to either IPv4
or IPv6 address.
Implements blueprint: cloud-init-provisioning
Change-Id: Ibff39030c4e3fe04c3f8cc238508e33d450a4398
fixes bug DHC-1286
There is an unstream bug in 1.2.1+ that causes IPv6 URLs not be
reassembled correctly. The change was recent, so pinning to a recent
older version that does not contain the bug.
1. Fix the names of the projects to be valid package names,
leaving the more verbose explanation for the description
field.
2. Wrap fpm with a little shell script to package everything,
overriding some default settings with values taken from
setup.py instead of whoever is running the tool.
Change-Id: I73ce54898311978b38d9ca769ec81ee45bfe5041
Signed-off-by: Doug Hellmann <doug.hellmann@dreamhost.com>
Move the files around so that requirements, testing, and source are
clustered for the router component. The new organization also modifies
import paths to move modules into the akanda.router namespace. Tests
are also moved into a single heirarchy.
Andreas Jaeger