As per the community goal of migrating the policy file
the format from JSON to YAML[1], we need to do two things:
1. Change the default value of '[oslo_policy] policy_file''
config option from 'policy.json' to 'policy.yaml' with
upgrade checks.
2. Deprecate the JSON formatted policy file on the project side
via warning in doc and releasenotes.
Also replace policy.json to policy.yaml ref from doc and tests.
[1]https://governance.openstack.org/tc/goals/selected/wallaby/migrate-policy-format-from-json-to-yaml.html
Change-Id: I1d74949c9d19ff543571382f887b5ed40756ecb9
This repo is now testing only with Python 3, so let's make
a few cleanups:
- Remove obsolete sections from setup.cfg
- Remove babel.cfg, this is not needed here at all
- Update requirements, no need for python_version anymore
- Switch to using sphinx-build
- Use newer openstackdocstheme and Sphinx versions
- Cleanup */source/conf.py to remove now obsolete content.
- Remove install_command from tox.ini, the default is fine
- Use TOX_CONSTRAINTS_FILE, UPPER_CONSTRAINTS_FILE is obsolete
Change-Id: Ie04a0c0c5270ae49097c3784bac3467c8e43acca
Now that we are running the Victoria tests that include a
voting py38, we can now add the Python 3.8 metadata to the
package information to reflect that support.
Change-Id: I296bd778de7c7698c71c24584c019511e91afbf1
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Make a few cleanups:
- Remove python 2.7 stanza from setup.py
- Add requires on python >= 3.6 to setup.cfg so that pypi and pip
know about the requirement
- Remove obsolete sections from setup.cfg:
* Wheel is not needed for python 3 only repo
* Some other sections are obsolete
- Update classifiers
- Update requirements, no need for python_version anymore
Change-Id: I29117a38a43a445eb21bb5cfa920f0e50324a5b3
This adds basic framework for solum-status upgrade
check commands. For now it has only "check_placeholder"
check implemented.
Real checks can be added to this tool in the future.
Change-Id: Icd92e2105e99354a8b184d9be086cc97ce4c12fa
Story: 2003657
Task: 26155
warning-is-error should be set for doc building. This change sets
the flag and corrects the warnings.
Change-Id: Ic7b007219c1351519b0d37567870c7477b239fa6
The gating on python 3.4 is restricted to <= Mitaka. This is due to
the change from Ubuntu Trusty to Xenial, where only python3.5 is
available. There is no need to continue to keep these settings.
Change-Id: I2d8a2ceb58e94bbb6706ca21cadae2cbca322a92
Now that there is a passing gate job, we can claim support for
Python 3.5 in the classifier. This patch also adds the
convenience py35 venv.
Change-Id: Ia827cfe406e77c06e84b0bf48e015e03e9d55f08
No config generator hooks should ever be registered with a name that
belongs to another project. In this case, using oslo.middleware.cors
means that *every other project* that loads the middleware gets this
application's defaults when the generator is run on a system with
everything installed (such as a dev box with devstack). Use the name
of the app instead, to ensure that the defaults are only set when this
app's sample config and documentation are being generated.
Change-Id: I6a8c7d44b9db9325003ff2fdb667b0ced7739e96
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
The default values needed for solum's implementation of cors
middleware have been moved from paste.ini into the configuration
hooks provided by oslo.config. Furthermore, these values have been
added to the default configuration parsing. This ensures
that if a value remains unset in solum.conf, it will be set
to use sane defaults, and that an operator modifying the
configuration file will be presented with a default set of
necessary sane headers.
Change-Id: I6f30224ac1b11fc4019dbc5ae5ec1e1fedbfe97d
Closes-Bug: 1551836
- Defined "list_opts" method in relevant files.
- Defined a new config-generator.conf to drive the configurator.
- Added config entry points for "list_opts" to setup.cfg.
- Deleted the old generator script and the oslo incubator files.
Change-Id: I4bdbf4f6769fa7e02689bd24f3e4b3734502aa17
Closes-Bug: 1476839
"Python 3.3 support is being dropped since OpenStack Liberty."
written in following URL.
https://wiki.openstack.org/wiki/Python3
And already the infra team and the oslo team are dropping py33
support from their projects.
Since we rely on oslo for a lot of our work, and depend on infra
for our CI, we should drop py33 support too.
Change-Id: I453abf7ed4ff7ed0996bfb1578e68a791c3b40a5
Closes-Bug: #1526170
As of https://wiki.openstack.org/wiki/python3 openstack
is targeted to py34 and py27 and also dropping py26
for mitaka. And also added solum docs in setup.cfg
Change-Id: Idb2810569321e29bd5d3e09b737d0b2e69552c1c
Closes-Bug: #1523188
pbr pre-versioning causes current sdist to have versions leading up to
2014.1.0, but that is a release in the past... already released - we
should be leading up to 2014.2, but solum already has a tag of
2014.2.0 (which is equivalent to 2014.2) so we need to increment the
minor version getting 2014.2.1.
Change-Id: Id2a89ec88a8b8b721abddd5f42d2e53069ebd8b5
Some notes:
- mysql_traditional_mode is now a configuration option (on by default)
- the objects classes must be late imported as the db config options
are registered a bit later.
- solum-db-manage needs log imported to avoid a configuration conflict
Change-Id: I94b44c4cbaeeb61882c94ff1e5480eaa917fb5a2
Also added skeletons of three services
Co-Authored-by: Angus Salkeld <angus.salkeld@rackspace.com>
Change-Id: I21ff5e71273c421803fca917e5ee6294600879e4
This is a totally seperate endpoint so it can be deployed seperately
and we can abstract the implemention well away from the rest of
solum. Also this could be used seperatly from solum to simply
build images (once the implementation matures).
part of blueprint lang-pack
Change-Id: I42fc352e787e2d98f933016c0da7fd2f18fe262e
With that, building and uploading wheels to PyPI is only one "python
setup.py bdist_wheel" away.
Also, changes LC_ALL from C to UTF-8 to get around a bug in pip:
https://github.com/pypa/pip/issues/761
Change-Id: I508ab6436c29b23f6b8d56c0ec63eb26f3568819
There are a couple of reviews up for deciding on the REST API
infrastructure. Regardless which is picked, they will need a solum-api
command that serves up the API. This commit puts those base pieces in
place.
Part of blueprint rest-api-base
Change-Id: Ie7d22d3ece0e81eca7959ad2d3ba5d756264d797
zhurong