openstack/placement
Code Issues Proposed changes
ffbedd67a2
placement/setup.cfg

55 lines
2.0 KiB
INI
Raw Normal View History

Transition from openstack.common.setup to pbr. Declarative approach to packaging, obviates the need for copying files. Also, removes the need for setup.py to import files from the nova module. ./run_tests.sh now ensure's that nova.egg-info/entry_points.txt is up to date before running tests. Change-Id: I7b7a18e065a62491ade54fbed5d8400db1d4e6c7
2013-04-07 18:24:27 -04:00
[metadata]
Set the name of the package to openstack-placement This change was made based on discussion [1] on the dev ML shortly before the PTG. [1] http://lists.openstack.org/pipermail/openstack-dev/2018-September/134212.html Change-Id: I7bdcf8ebaf0bf8ce7a184e5483028f1ad8d04868
2018-09-12 16:26:39 -06:00
name = openstack-placement
Inspect and correct tox.ini, .stestr.conf and setup.cfg Begin the process of getting placement tests running, by getting the test harness opertional. Before we can expect the tests to be able to run the configuration for the placement package and its test harness needs to be adjusted for "nova" -> "placement". These changes are made by inspection and based on previous iterations of doing these kinds of cleanups, it won't be until later in this stack of change that actually passing tests will show up. However, the logs for attempted tests runs should be getting a little bit further than the parent. setup.cfg changes quite a bit because there are many things in it that are not relevant. placement (thus far) really only has one entry point. As noted, by a TODO, a placement-manage and placement-status will be desired in the near future. Change-Id: Iaa385c6e8653a9646a21bb65203deaa05ec43217
2018-09-03 12:12:23 +01:00
summary = Resource provider inventory usage and allocation service
setup: Replace dashes with underscores Resolves the following class of warnings issued when building the package sdist: UserWarning: Usage of dash-separated 'python-requires' will not be supported in future versions. Please use the underscore name 'python_requires' instead Change-Id: Ie4f6c7b17ace67669cdeec84ce4f163aededa8e4 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
2021-07-15 12:17:15 +01:00
description_file =
Transition from openstack.common.setup to pbr. Declarative approach to packaging, obviates the need for copying files. Also, removes the need for setup.py to import files from the nova module. ./run_tests.sh now ensure's that nova.egg-info/entry_points.txt is up to date before running tests. Change-Id: I7b7a18e065a62491ade54fbed5d8400db1d4e6c7
2013-04-07 18:24:27 -04:00
README.rst
author = OpenStack
setup: Replace dashes with underscores Resolves the following class of warnings issued when building the package sdist: UserWarning: Usage of dash-separated 'python-requires' will not be supported in future versions. Please use the underscore name 'python_requires' instead Change-Id: Ie4f6c7b17ace67669cdeec84ce4f163aededa8e4 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
2021-07-15 12:17:15 +01:00
author_email = openstack-discuss@lists.openstack.org
url = https://docs.openstack.org/placement/latest/
Update setup.cfg to include project_urls The content is based on what pbr does [1] and packaging docs [2]. The links chosen and the names used are whatever we like. project_urls are used when displaying packages on pypi, the links show up in the left sidebar under a project links section. pbr's example [3]. [1] https://docs.openstack.org/pbr/latest/user/using.html#setup-cfg [2] https://packaging.python.org/guides/distributing-packages-using-setuptools/#project-urls [3] https://pypi.org/project/pbr/ Change-Id: I0c8663b1ed495f141350fd023c78a6ff38bca29f Story: 2005170 Task: 30915
2019-09-10 13:17:50 +01:00
project_urls =
Bugtracker link update As discussed in the upstream meeting, update the placement bug tracker, link from storyboard to launchpad, so new bugs should be reported in launchpad instead storyboad. Whats not updated: - all links of storyboard which do not point to bugs - links of existing stories, features, docs etc Change-Id: I64b9d6feb4fb35f36c5a290b8b79d9b78736efd2
2023-03-07 16:56:21 +00:00
Bug Tracker = https://bugs.launchpad.net/placement
Update setup.cfg to include project_urls The content is based on what pbr does [1] and packaging docs [2]. The links chosen and the names used are whatever we like. project_urls are used when displaying packages on pypi, the links show up in the left sidebar under a project links section. pbr's example [3]. [1] https://docs.openstack.org/pbr/latest/user/using.html#setup-cfg [2] https://packaging.python.org/guides/distributing-packages-using-setuptools/#project-urls [3] https://pypi.org/project/pbr/ Change-Id: I0c8663b1ed495f141350fd023c78a6ff38bca29f Story: 2005170 Task: 30915
2019-09-10 13:17:50 +01:00
Documentation = https://docs.openstack.org/placement/latest/
API Reference = https://docs.openstack.org/api-ref/placement/
Source Code = https://opendev.org/openstack/placement
Release Notes = https://docs.openstack.org/releasenotes/placement/
Remove Python 3.8 support Python 3.8 is no longer part of the tested runtimes for 2024.2[1] because its EOL is coming soon. [1] https://governance.openstack.org/tc/reference/runtimes/2024.2.html Change-Id: Ifbde8ee88aa3d63389e65703a29d09962e9cfde8
2024-08-03 22:17:41 +09:00
python_requires = >=3.9
Transition from openstack.common.setup to pbr. Declarative approach to packaging, obviates the need for copying files. Also, removes the need for setup.py to import files from the nova module. ./run_tests.sh now ensure's that nova.egg-info/entry_points.txt is up to date before running tests. Change-Id: I7b7a18e065a62491ade54fbed5d8400db1d4e6c7
2013-04-07 18:24:27 -04:00
classifier =
setup: Replace dashes with underscores Resolves the following class of warnings issued when building the package sdist: UserWarning: Usage of dash-separated 'python-requires' will not be supported in future versions. Please use the underscore name 'python_requires' instead Change-Id: Ie4f6c7b17ace67669cdeec84ce4f163aededa8e4 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
2021-07-15 12:17:15 +01:00
Development Status :: 5 - Production/Stable
Transition from openstack.common.setup to pbr. Declarative approach to packaging, obviates the need for copying files. Also, removes the need for setup.py to import files from the nova module. ./run_tests.sh now ensure's that nova.egg-info/entry_points.txt is up to date before running tests. Change-Id: I7b7a18e065a62491ade54fbed5d8400db1d4e6c7
2013-04-07 18:24:27 -04:00
Environment :: OpenStack
Intended Audience :: Information Technology
Intended Audience :: System Administrators
License :: OSI Approved :: Apache Software License
Operating System :: POSIX :: Linux
Programming Language :: Python
Cleanup py27 support 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 Change-Id: I6f458fb60b5a33b5aa2ce3ab292862ab98eb4670
2020-04-05 10:23:26 +02:00
Programming Language :: Python :: Implementation :: CPython
Programming Language :: Python :: 3 :: Only
Fix a missing classifier Add Python 3 in classifier. TrivialFix Change-Id: Iaaee1776bbbb1f9dfa5d9ad3a238d0e1422394a0
2017-06-29 13:53:21 +09:00
Programming Language :: Python :: 3
Updating python testing as per Yoga testing runtime Yoga testing runtime[1] has been updated to add py39 testing as voting. Unit tests update are handled by the job template change in openstack-zuul-job - https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/820286 this commit makes other required changes in zuul.yaml and update the classifier in setup.cfg file. [1] https://governance.openstack.org/tc/reference/runtimes/yoga.html Change-Id: I50c125df4ee03377caf16da5824e2ed492d4b7da
2021-11-24 18:02:10 -06:00
Programming Language :: Python :: 3.9
Update python classifier in setup.cfg As per the current release tested runtime, we test till python 3.11 so updating the same in python classifier in setup.cfg Change-Id: Id0f37bebfb5298c5a84aa8f46f9b2d161b1f81ca
2024-01-03 19:22:50 -08:00
Programming Language :: Python :: 3.10
Programming Language :: Python :: 3.11
Move upper functional job to py312 Python 3.12 is now the maximum supported version. Change-Id: I2e332c098c944bcbfa3b0d24e6a0bbf6dd5ba0d3
2024-10-02 03:10:15 +09:00
Programming Language :: Python :: 3.12
Transition from openstack.common.setup to pbr. Declarative approach to packaging, obviates the need for copying files. Also, removes the need for setup.py to import files from the nova module. ./run_tests.sh now ensure's that nova.egg-info/entry_points.txt is up to date before running tests. Change-Id: I7b7a18e065a62491ade54fbed5d8400db1d4e6c7
2013-04-07 18:24:27 -04:00
[files]
packages =
Inspect and correct tox.ini, .stestr.conf and setup.cfg Begin the process of getting placement tests running, by getting the test harness opertional. Before we can expect the tests to be able to run the configuration for the placement package and its test harness needs to be adjusted for "nova" -> "placement". These changes are made by inspection and based on previous iterations of doing these kinds of cleanups, it won't be until later in this stack of change that actually passing tests will show up. However, the logs for attempted tests runs should be getting a little bit further than the parent. setup.cfg changes quite a bit because there are many things in it that are not relevant. placement (thus far) really only has one entry point. As noted, by a TODO, a placement-manage and placement-status will be desired in the near future. Change-Id: Iaa385c6e8653a9646a21bb65203deaa05ec43217
2018-09-03 12:12:23 +01:00
placement
Package db migration scripts in placement pypi dist Having the db migration scripts within the openstack-placement pypi distribution is desirable for deployment tools, such as openstack-ansible. It provides a known good location for the script, available with a pip install. There are several ways to distribute files with a python package. The method used here was chosen because it works both with tarballs and wheels (the files are already in the tarball, as a result of the way pbr works, but not in the wheel). Here's what's done: * The db migrate scripts are put in their own direcory, placement_db_tools, so that only they are packaged, not the other tools. * To preserve how grenade interacts with these files as well as not disrupt the docs, symlinks from tools to placement_db_tools have been created. * placement_db_tools is added to the list of packages included in the openstack-placement distro. This means that when 'pip install openstack-placement' happens, the python environment will then include placement and placement_db_tools directories. The end result is that the true path to the script can be found with: pkg_resources.resource_filename('placement_db_tools', 'mysql-migrate-db.sh') This has been noted in the to-stein.rst document. A different package was chosen to not muddy the waters of what is "actually placement". Similarly, the 'data_files' functionality provided by pbr was not used, because that requires the file be written to a location on the local filesystem, relative to the install prefix. Dirtying the filesystem outside the python lib with this sort of thing is inappropriate. Change-Id: Ie326ce8a2a0692d20793bc18be606e034fa94a44 Story: 2005535 Task: 30671
2019-05-01 16:05:23 -06:00
placement_db_tools
Transition from openstack.common.setup to pbr. Declarative approach to packaging, obviates the need for copying files. Also, removes the need for setup.py to import files from the nova module. ./run_tests.sh now ensure's that nova.egg-info/entry_points.txt is up to date before running tests. Change-Id: I7b7a18e065a62491ade54fbed5d8400db1d4e6c7
2013-04-07 18:24:27 -04:00
[entry_points]
Use oslo-config-generator instead of generate_sample.sh Oslo team is actively getting rid of the old style generator.py in openstack/common/config. So we should switch to the newer oslo-config-generator which is the way forward. For simplicity's sake, i used one single list_opts in opts.py. However we can split this up and add entrypoints in setup.cfg if we decide to do that instead. blueprint oslo-config-generator Change-Id: Ib7c72af7be47df08983708ac6da0ce103518b78c
2015-05-04 23:00:25 -04:00
oslo.config.opts =
Inspect and correct tox.ini, .stestr.conf and setup.cfg Begin the process of getting placement tests running, by getting the test harness opertional. Before we can expect the tests to be able to run the configuration for the placement package and its test harness needs to be adjusted for "nova" -> "placement". These changes are made by inspection and based on previous iterations of doing these kinds of cleanups, it won't be until later in this stack of change that actually passing tests will show up. However, the logs for attempted tests runs should be getting a little bit further than the parent. setup.cfg changes quite a bit because there are many things in it that are not relevant. placement (thus far) really only has one entry point. As noted, by a TODO, a placement-manage and placement-status will be desired in the near future. Change-Id: Iaa385c6e8653a9646a21bb65203deaa05ec43217
2018-09-03 12:12:23 +01:00
placement.conf = placement.conf.opts:list_opts
[goal] Deprecate the JSON formatted policy file 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: Ia7365cc3ae09e2ff916ab9f9ff0ba4fef0dc446b
2020-11-26 20:04:08 -06:00
oslo.config.opts.defaults =
nova.conf = placement.conf.base:set_lib_defaults
Add entry_point for oslo policy scripts There are two helper scripts in oslo.policy to help deployers understand their policy configuration better. With the setup.cfg entry these can be called directly from oslo.policy. Change-Id: I08dc33367401ec1f98e1795a52d4e981f09a07de Implements: bp policy-in-code
2016-06-29 16:59:20 -04:00
oslo.policy.enforcer =
Remove the import pathing for the old structure This commit is the result of running the following search and replace across the project. s/nova\.api\.openstack\.?//g Change-Id: I4974a28de541aace043504f788cf0d100f778cae
2018-08-30 23:07:27 +00:00
placement = placement.policy:get_enforcer
Add policy sample generation This adds the entry point and config file necessary for using the oslo.policy sample generation script. It also adds a tox target to simplify the usage of it. The command is also run in the docs tox target since the sample file can be considered documentation. Change-Id: I18a1fa567fc04b0e0a37c02f20024b2ce483f060 Partially-Implements: bp policy-in-code
2016-06-21 16:53:57 -04:00
oslo.policy.policies =
# The sample policies will be ordered by entry point and then by list
# returned from that entry point. If more control is desired split out each
# list_rules method into a separate entry point rather than using the
# aggregate method.
Remove the import pathing for the old structure This commit is the result of running the following search and replace across the project. s/nova\.api\.openstack\.?//g Change-Id: I4974a28de541aace043504f788cf0d100f778cae
2018-08-30 23:07:27 +00:00
placement = placement.policies:list_rules
Transition from openstack.common.setup to pbr. Declarative approach to packaging, obviates the need for copying files. Also, removes the need for setup.py to import files from the nova module. ./run_tests.sh now ensure's that nova.egg-info/entry_points.txt is up to date before running tests. Change-Id: I7b7a18e065a62491ade54fbed5d8400db1d4e6c7
2013-04-07 18:24:27 -04:00
console_scripts =
Add a placement-manage CLI This change adds a rudimentary command line tool, 'placement-manage' that can do three things: * placement-manage --version: report the current version of the software * placement-manage db sync: sync the db to the 'head' alembic version * placement-manage db version: report the current version of the db It is written following the examples set by both nova and ironic for using oslo config driven command line parsing. It is not as full featured as the nova version (with decorators for argument handling and help text etc) because we don't need that yet. There's plenty of room for improvement, but the intention here is to keep things simple until we need them to be otherwise. The provided unit tests cover that the arg parsing behaves as expected and that the right commands are connected the right args. The actual functionality of the 'db sync' command (a migration.upgrade) is tested in runs that use devstack as well as the test_migrations functional test. Errors during the migration simply raise exceptions which will output noisily to the console. At this stage this is desirable and suitable. A new doc for the cli is added, with basic information for placement-manage. Note that at this time the deployment documentation has not been updated. That will be done in a later change. Future changes may include (if we can't avoid it) tools for initiating online migrations from the command line. Needed-By: https://review.openstack.org/600162/ Change-Id: I1ff472106610150a587f5286f26a6bd7c1aa84f4
2018-09-05 18:28:10 +01:00
placement-manage = placement.cmd.manage:main
Add placement-status upgrade check command This adds the basic framework for the placement-status upgrade check command which is a community-wide goal for the Stein release. A simple placeholder check is added which should be replaced later when we have a real upgrade check. Change-Id: I9291386fe7fcbfc035c104ea9fdbe5eb875c4776 Story: 2003657 Task: 27518
2018-11-20 11:28:25 -05:00
placement-status = placement.cmd.status:main
create placement API wsgi entry point We want a wsgi_script as the entry point for our placement API actually getting run, this is wrapping in the smooth and mellow pbr patterns that make it sensible to also run just by starting it on the command line. This also actually initializes the logging subsystem for the placement API, and does the standard pattern of dumping the configuration if DEBUG is enabled. Pieces of this were cribbed/inspired by equivalent keystone code. The config directory is now setable via environment, which may be be needed by folks with venvs. Change-Id: I00d032554de273d7493cfb467f81687c08fd5389
2016-08-30 21:05:06 -04:00
wsgi_scripts =
Inspect and correct tox.ini, .stestr.conf and setup.cfg Begin the process of getting placement tests running, by getting the test harness opertional. Before we can expect the tests to be able to run the configuration for the placement package and its test harness needs to be adjusted for "nova" -> "placement". These changes are made by inspection and based on previous iterations of doing these kinds of cleanups, it won't be until later in this stack of change that actually passing tests will show up. However, the logs for attempted tests runs should be getting a little bit further than the parent. setup.cfg changes quite a bit because there are many things in it that are not relevant. placement (thus far) really only has one entry point. As noted, by a TODO, a placement-manage and placement-status will be desired in the near future. Change-Id: Iaa385c6e8653a9646a21bb65203deaa05ec43217
2018-09-03 12:12:23 +01:00
placement-api = placement.wsgi:init_application
Copy Permalink