openstack/nova - nova - OpenDev: Free Software Needs Free 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

[metadata]

name = nova

summary = Cloud computing fabric controller

setup.cfg: Resolve warning setuptools is now emitting the following warning when building nova: UserWarning: Usage of dash-separated 'python-requires' will not be supported in future versions. Please use the underscore name 'python_requires' instead Do as it says. While we're here, we update a few other options to use their new variants and add some additional metadata. This leaves one final warning: Warning: Unknown distribution option: 'requires_python' That unfortunately cannot be fixed here and requires a separate fix in pbr. Change-Id: I859bc89bc1ee80652f471c3463ef6562d720263b Signed-off-by: Stephen Finucane <stephenfin@redhat.com>

2021年03月09日 09:42:13 +00: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.cfg: Resolve warning setuptools is now emitting the following warning when building nova: UserWarning: Usage of dash-separated 'python-requires' will not be supported in future versions. Please use the underscore name 'python_requires' instead Do as it says. While we're here, we update a few other options to use their new variants and add some additional metadata. This leaves one final warning: Warning: Unknown distribution option: 'requires_python' That unfortunately cannot be fixed here and requires a separate fix in pbr. Change-Id: I859bc89bc1ee80652f471c3463ef6562d720263b Signed-off-by: Stephen Finucane <stephenfin@redhat.com>

2021年03月09日 09:42:13 +00:00

author_email = openstack-discuss@lists.openstack.org

url = https://docs.openstack.org/nova/latest/

project_urls =

Bug Tracker = https://bugs.launchpad.net/nova/

Documentation = https://docs.openstack.org/nova/

Source Code = https://opendev.org/openstack/nova

Update python testing as per zed cycle teting runtime In Zed cycle, we have dropped the python 3.6/3.7[1] testing and its support. Removing the py36 centos8 job as well as updating the python classifier also to reflect the same. [1] https://governance.openstack.org/tc/reference/runtimes/zed.html Change-Id: Iba5074ea6f981a7527e86cfc98edd1ed7dd3086f

2022年04月21日 14:16:55 -05:00

python_requires = >=3.8

setup.cfg: Resolve warning setuptools is now emitting the following warning when building nova: UserWarning: Usage of dash-separated 'python-requires' will not be supported in future versions. Please use the underscore name 'python_requires' instead Do as it says. While we're here, we update a few other options to use their new variants and add some additional metadata. This leaves one final warning: Warning: Unknown distribution option: 'requires_python' That unfortunately cannot be fixed here and requires a separate fix in pbr. Change-Id: I859bc89bc1ee80652f471c3463ef6562d720263b Signed-off-by: Stephen Finucane <stephenfin@redhat.com>

2021年03月09日 09:42:13 +00:00

classifiers =

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

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

Moving functional jobs to Victoria testing runtime As per Victoria testing runtime[1], we need to tests py3.6, py3.7, and py3.8. - py3.7 is being tested with integration jobs. - py3.6 and py3.8 are tested with unit test jobs. Nova functional tests are testing py3.6 which can be moved to the latest python available in this cycle which is 3.8. We do not need to run functional or integration tests on each supported python version. Testing them on the latest python version is enough. Coverage of all supported python version is achieved via unit tests job. [1] https://governance.openstack.org/tc/reference/runtimes/victoria.html Change-Id: I1d6a2986fcb0435cfabdd104d202b65329909d2b

2020年05月04日 14:11:40 -05:00

Programming Language :: Python :: 3.8

Updating tests with Yoga testing runtime Yoga testing runtime is updated now - https://governance.openstack.org/tc/reference/runtimes/yoga.html which needs to test py38 and py39. Unit tests update are handled by the job template change in openstack-zuul-job and this commit makes changes to fucntional job to run py39 as voting and updating the metdata in setup file. Change-Id: I314fd61f20f2c3551f6231d191b7dcaaefabd2b5

2021年11月24日 16:48:37 -06:00

Programming Language :: Python :: 3.9

Update gate jobs as per the 2023.1 cycle testing runtime As per 2023.1 testing runtime[1], we need to test on Ubuntu Jammy (which will be taken care by tempest and devstack patches to move base jobs to Jammy) and at least single job to run on Ubutnu Focal (for smooth upgrade). Also, python 3.10 testing is voting now. This commit adds a new job to run on focal which can be removed in future cycle when testing runtime drop the requirement of Focal testing. Also, make python 3.10 functional and unit test job as voting (openstack-tox-py310 is running as part of generic template so we do not need to explicitly add that) [1] https://governance.openstack.org/tc/reference/runtimes/2023.1.html Change-Id: Ia43f73dba00b0b5932939bcc7d11b97a83072ee3

2022年10月12日 16:16:21 -05:00

Programming Language :: Python :: 3.10

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: Ib6f14c4348c6fbb251c15c9982dfb2fb4b8d249c

2023年11月22日 16:26:13 +08:00

Programming Language :: Python :: 3.11

Stop testing Python 2 It's Ussuri. We can *finally* stop testing Python 2 [1]. Time to party. We don't attempt any cleanup but simply stop testing with Python 2, indicate that we only support Python 3 via 'setup.cfg' and remove any Python 2 only dependencies. Our 'tox.ini' is modified such that 'functional' now runs with 'python3', whatever that may point to, though the gate will only use a versioned variant (currently 'functional-py36'). This should free up a significant amount of resources from the gate and let us start using Python 3 idioms in our code. Win-win. [1] https://governance.openstack.org/tc/resolutions/20180529-python2-deprecation-timeline.html#python2-deprecation-timeline Change-Id: Ie1a0cbd82a617dbcc15729647218ac3e9cd0e5a9 Signed-off-by: Stephen Finucane <sfinucan@redhat.com>

2019年10月14日 12:14:35 +01:00

Programming Language :: Python :: 3 :: Only

Programming Language :: Python :: Implementation :: CPython

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

setup.cfg: Cleanup - pbr hasn't need the hook configuration since forever [1] - We don't distribute eggs, so there's no need to include configuration for same - nova-based entrypoints are grouped - The 'wheel' group is renamed to 'bdist_wheel' [2] [1] https://github.com/openstack/pbr/commit/c84876dc0f559a66fec19b2f81f5717204b253e2 [2] https://github.com/pypa/wheel/commit/f7c9878712390414c03c64e9afa55ea4f30e965b Change-Id: I1bc60eab58055bd6217ddb7c7c5c2e3bd6fb539e Signed-off-by: Stephen Finucane <sfinucan@redhat.com>

2019年08月22日 12:08:11 +01:00

[extras]

osprofiler =

osprofiler>=1.4.0 # Apache-2.0

Move optional build dependencies to 'extras' ...and start skipping the relevant tests in 'nova.tests.unit.virt' if these dependencies are not present. Thanks to hacking rules N311 and N312, which prevent virt drivers using code from other virt drivers, simply skipping the unit tests for a virt driver module is enough to ensure we never load those modules. This means users that want to use the powervm driver can install the required dependencies using e.g. 'pip install .[powervm]', and packagers can choose to skip packaging a dependency safe in the knowledge that the relevant tests will be skipped. Change-Id: I3787f9afd78cd0a7c7feb4dfe1bcb21437b5a128 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>

2021年12月22日 16:25:19 +00:00

zvm =

zVMCloudConnector>=1.3.0;sys_platform!='win32' # Apache 2.0 License

vmware =

oslo.vmware>=3.6.0 # Apache-2.0

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]

Add default configuration files to data_files In order to make it simpler to use the default configuration files when deploying services from source, the files are added to pbr's data_files section so that the files are included in the built wheels and therefore deployed with the code. Packaging and deployment tools can then more easily use the default files if they wish to. This pattern is already established with similar files for neutron and the glance metadefs as has been mentioned in the related bug report. Change-Id: I66e6525338e06f289a20ff2cdc2d108ffd6d30b2 Closes-Bug: #1718356

2017年09月21日 14:57:51 +01:00

data_files =

etc/nova =

etc/nova/api-paste.ini

etc/nova/rootwrap.conf

etc/nova/rootwrap.d = etc/nova/rootwrap.d/*

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

packages =

nova

[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 =

single point of entry for sample config generation To create a "nova.conf.sample" file, we use "tox -e genconfig". This command triggers the generator from "oslo.config" which needs entry points in "setup.cfg". Right now we have multiple entry points to "opts.py" files which are going to be consolidated to one single point of entry "nova/conf/opts.py". Until all config options are moved to that central place, we would often face merge conflicts when multiple contributors commit patches to that one "opts.py". To prevent that, and to make it easier for future config option moduls in "nova/conf/", the new "nova/conf/opts.py" module collects the config options in a dynamic way. Co-Author: EdLeafe <ed@leafe.com> bp centralize-config-options Change-Id: I4e5d643cd93bb2822ff59c71669cedf3de7f86fc

2015年12月21日 14:37:15 +01:00

nova.conf = nova.conf.opts:list_opts

Added Keystone and RequestID headers to CORS middleware This patch makes use of oslo.config's genconfig hooks to add nova-specific default config values to the generated configuration. It also adds this same method to nova's configuration parsing logic, to ensure that these default values are also the ones used at runtime. Closes-bug: 1551836 Change-Id: Ic799aea89f681ef8626e996f0357ade388f76ca9

2016年03月01日 10:49:32 -08:00

oslo.config.opts.defaults =

Fix config option default value for sample config file There are multiple places where nova set the new default value for other (than nova) namespace config option for example oslo lib config options. Examples: - https://github.com/openstack/nova/blob/20572809f2d8fefd72a7a059c4e82462a0d66262/nova/config.py#L62 - https://github.com/openstack/nova/blob/20572809f2d8fefd72a7a059c4e82462a0d66262/nova/policy.py#L48 and these defaults are reflected in code also which is working as expected. But when config sample file is generated via oslo-config-generator tool (tox -egenconfig) then these defaults which are set by Nova are not reflected as this tool take the raw defaults. To solve this issue oslo config provide a option to add hook to reflect the new default in config generator - https://docs.openstack.org/oslo.config/latest/cli/generator.html#modifying-defaults-from-other-namespaces We already doing it for middleware cors option - https://github.com/openstack/nova/blob/20572809f2d8fefd72a7a059c4e82462a0d66262/setup.cfg#L41 Fixing existing default value and if we find more or any future change for default value, we need to add those config generator hook. Change-Id: Ib0e926aec069dfb4ffd1bbfe8506d62464511b51 Closes-Bug: #1904250

2020年11月13日 17:10:05 -06:00

nova.conf = nova.config: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 =

nova = nova.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.

nova = nova.policies:list_rules

api: Add framework for extra spec validation Add the validation framework necessary to verify extra specs along with the definitions for every extra spec we currently recognize in-tree. None of this is currently used since we don't have the API microversions wired up, but that will come in a future patch. Note that we must add the H238 hacking check to the ignore list here, since this includes our first use of Python 3-type classes without the explicit 'object' subclass. This can be removed when that check is removed from hacking. Part of blueprint flavor-extra-spec-validators Change-Id: Ib64a1348cce1dca995746214616c4f33d9d664bd Signed-off-by: Stephen Finucane <sfinucan@redhat.com>

2020年01月20日 16:18:19 +00:00

nova.api.extra_spec_validators =

api: Add support for new cyborg extra specs There's currently only one, as noted at [1]. [1] https://specs.openstack.org/openstack/nova-specs/specs/train/approved/nova-cyborg-interaction.html Change-Id: Ie70a0aef4f6647510750b7e0bdd2f040331b79e8 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>

2020年03月31日 10:44:10 +01:00

accel = nova.api.validation.extra_specs.accel

api: Add framework for extra spec validation Add the validation framework necessary to verify extra specs along with the definitions for every extra spec we currently recognize in-tree. None of this is currently used since we don't have the API microversions wired up, but that will come in a future patch. Note that we must add the H238 hacking check to the ignore list here, since this includes our first use of Python 3-type classes without the explicit 'object' subclass. This can be removed when that check is removed from hacking. Part of blueprint flavor-extra-spec-validators Change-Id: Ib64a1348cce1dca995746214616c4f33d9d664bd Signed-off-by: Stephen Finucane <sfinucan@redhat.com>

2020年01月20日 16:18:19 +00:00

aggregate_instance_extra_specs = nova.api.validation.extra_specs.aggregate_instance_extra_specs

capabilities = nova.api.validation.extra_specs.capabilities

hw = nova.api.validation.extra_specs.hw

hw_rng = nova.api.validation.extra_specs.hw_rng

hw_video = nova.api.validation.extra_specs.hw_video

null = nova.api.validation.extra_specs.null

os = nova.api.validation.extra_specs.os

pci_passthrough = nova.api.validation.extra_specs.pci_passthrough

quota = nova.api.validation.extra_specs.quota

resources = nova.api.validation.extra_specs.resources

traits = nova.api.validation.extra_specs.traits

vmware = nova.api.validation.extra_specs.vmware

Use stevedore for loading monitor extensions The compute monitor plugins were being loaded using the nova.loadables module. This patch uses the stevedore library to load monitor extensions. We keep the same semantics as the previous loading mechanism: we use the CONF.compute_monitors configuration option to winnow the set of all monitor plugins, and we ensure that no two monitors that return the same set of metrics will be loaded. However, this patch deprecates the CONF.compute_available_monitors configuration option, since stevedore and setuptools entry points now allow a set of plugins to be specified without any further configuration options. Change-Id: I97bf8bcd43faf9f3fe40983497c2360233d5f599 Fixes-bug: 1468012 DocImpact: deprecates the CONF.compute_available_monitors option.

2015年06月26日 14:33:03 -04:00

nova.compute.monitors.cpu =

virt_driver = nova.compute.monitors.cpu.virt_driver:Monitor

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 =

nova-api = nova.cmd.api:main

nova-api-metadata = nova.cmd.api_metadata:main

nova-api-os-compute = nova.cmd.api_os_compute:main

nova-compute = nova.cmd.compute:main

nova-conductor = nova.cmd.conductor:main

nova-manage = nova.cmd.manage:main

nova-novncproxy = nova.cmd.novncproxy:main

trivial: Rename 'policy_check' -> 'policy' The executable is 'nova-policy' - not 'nova-policy-check'. Change-Id: I3e875a3284935cbb9607f01c7139982da0e11945 Signed-off-by: Stephen Finucane <sfinucan@redhat.com>

2017年10月25日 17:56:40 +01:00

nova-policy = nova.cmd.policy:main

Drop deprecated namespace for oslo.rootwrap The oslo team is recommending everyone to switch to the non-namespaced versions of libraries.[1] oslo.rootwrap suggests to use oslo_rootwrap.cmd:main.[2] [1]https://blueprints.launchpad.net/oslo-incubator/+spec/drop-namespace-packages [2]https://github.com/openstack/oslo.rootwrap#using Change-Id: I2e9b72c77316c8d097e7e49ab09fcb18ac33078c

2015年01月30日 23:02:27 +08:00

nova-rootwrap = oslo_rootwrap.cmd:main

Add rootwrap daemon mode support Add a configuration option 'use_rootwrap_daemon' to switch on the rootwrap daemon mode support. This option is switched off by default to keep the current behavior as is. The code honors the various options available in processutils.execute() like 'attempts', 'delay_on_retry' etc to ensure that we don't regress any current behavior. DocImpact Part of blueprint nova-rootwrap-daemon-mode Depends-On: I80c7b9dd8e9e0f940aa4e54a95b241dfc40d3574 Change-Id: I57dc2efa39b86fa1fa20730ad70d056e87617c96

2015年05月06日 15:35:02 -04:00

nova-rootwrap-daemon = oslo_rootwrap.cmd:daemon

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

nova-scheduler = nova.cmd.scheduler:main

cmd: add nova-serialproxy service Adds a websocket proxy that is compatible with Nova serial ports. Co-Authored-By: Vladan Popovic <vpopovic@redhat.com> Co-Authored-By: Ian Wells <iawells@cisco.com> Co-Authored-By: Sushma Korati <sushma_korati@persistent.co.in> Partial-Implements: blueprint serial-ports Change-Id: Ia944cb93945140e6341588063329a981f7e778f1

2014年08月25日 12:43:28 +00:00

nova-serialproxy = nova.cmd.serialproxy:main

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

nova-spicehtml5proxy = nova.cmd.spicehtml5proxy:main

Add nova-status upgrade check command framework This adds the basic framework for the nova-status upgrade check commands. Follow up patches will flesh this out to perform cells v2 and placement API related upgrade status checks. A man page is added for the new CLI and as part of that the man page index is sorted. Part of blueprint cells-scheduling-interaction Part of blueprint resource-providers-scheduler-db-filters Change-Id: I687dd7317703a1bb76c197ebba849ca368c0872e

2016年12月15日 16:01:41 -05:00

nova-status = nova.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 =

Register osapi_compute when nova-api is wsgi When the nova-api services starts from its own standalone binary it registers itself in the services table. The original wsgi script in nova/wsgi/nova-api.py did not, leading to the bug referenced below. The new wsgi script at nova.api.openstack.compute.wsgi, modelled on a similar thing used for the placement API, provides the necessary service registration. If a ServiceTooOld exception happens while trying to register the service then a very simple (currently very stubby) application is loaded instead of the compute api. This application returns a 500 and a message. Some caveats/todos: * wsgi apps managed under mod-wsgi (and presumably other containers) are not imported/compiled/run until the first request is made. In this case that means the service handling does not happen until that first request, somewhat defeating the purpose if the api is a bit idle. Change-Id: I7c4acfaa6c50ac0e4d6de69eb62ec5bbad72ff85 Closes-Bug: #1661360

2017年04月17日 16:38:49 +00:00

nova-api-wsgi = nova.api.openstack.compute.wsgi:init_application

Add pbr-installed wsgi application for metadata api Modify the wsgi application for the compute api so that it can be used by different services and use it for the metadata service, resulting in a wsgi script named nova-metadata-wsgi. Change-Id: Icb35fe2b94ab02c0ba8ba8129ae18aae0f794756

2017年04月24日 15:56:52 +00:00

nova-metadata-wsgi = nova.api.metadata.wsgi:init_application

tox: Integrate mypy mypy is an experimental optional static type checker for Python that aims to combine the benefits of dynamic (or "duck") typing and static typing. While still in development, most features are supported and it's already being used by real world projects like Sphinx. Let's start small by integrating it into some of the interfaces that nova exposes. We can further build upon this if it works out. This change sets up the boilerplate necessary to use mypy in nova. Type annotations are not included for any module - these will be added separately. We're calling mypy by way of a script, as this allows us to store a list of files that we have converted while we're in the process of adding type annotations where necessary. Change-Id: I75ab46a6768c4ca2050fdde2b7f8eeb90724c8c6 Signed-off-by: Stephen Finucane <sfinucan@redhat.com>

2017年06月02日 16:45:41 +01:00

[mypy]

show_column_numbers = true

show_error_context = true

ignore_missing_imports = true

follow_imports = skip

incremental = true

check_untyped_defs = true

warn_unused_ignores = true

pre-commit: Add mypy Add mypy so we can run these checks as part of our linting step. Note that mypy is the last item in the list of checks since flake8 is going to catch e.g. syntax issues which should be addressed first. This also allows us to drop use of mypywrap: rather than wrapping mypy, we can make use of mypy's configuration to specify the files we wish to run checks on. Change-Id: Ie51401ead4e31ccd70ab833c59cb397f802ff188 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>

2023年09月22日 11:44:48 +01:00

files =

nova/compute/manager.py,

nova/compute/pci_placement_translator.py,

nova/crypto.py,

nova/filesystem.py,

nova/limit/local.py,

nova/limit/placement.py,

nova/network/neutron.py,

nova/pci/*.py,

nova/privsep/path.py,

nova/scheduler/client/report.py,

nova/scheduler/request_filter.py,

nova/scheduler/utils.py,

nova/virt/driver.py,

nova/virt/hardware.py,

nova/virt/libvirt/machine_type_utils.py,

nova/virt/libvirt/__init__.py,

nova/virt/libvirt/cpu/__init__.py,

nova/virt/libvirt/cpu/api.py,

nova/virt/libvirt/cpu/core.py,

nova/virt/libvirt/driver.py,

nova/virt/libvirt/event.py,

nova/virt/libvirt/guest.py,

nova/virt/libvirt/host.py,

nova/virt/libvirt/utils.py

[codespell] start fixing all the typos this is the inital patch of applying codespell to nova. codespell is a programing focused spellchecker that looks for common typos and corrects them. i am breaking this into multiple commits to make it simpler to read and will automate the execution of codespell at the end of the series. Change-Id: If24a6c0a890f713545faa2d44b069c352655274e

2023年10月03日 00:51:35 +01:00

[codespell]

setup.cfg: Resolve warning setuptools is now emitting the following warning when building nova: UserWarning: Usage of dash-separated 'python-requires' will not be supported in future versions. Please use the underscore name 'python_requires' instead Do as it says. While we're here, we update a few other options to use their new variants and add some additional metadata. This leaves one final warning: Warning: Unknown distribution option: 'requires_python' That unfortunately cannot be fixed here and requires a separate fix in pbr. Change-Id: I859bc89bc1ee80652f471c3463ef6562d720263b Signed-off-by: Stephen Finucane <stephenfin@redhat.com>

2021年03月09日 09:42:13 +00:00

skip = *.po,*.js,*.css,*.html,*.svg,HACKING.py,*hacking*,*build*,*_static*,doc/dictionary.txt,*.pyc,*.inv,*.gz,*.jpg,*.png,*.vsd,*.graffle,*.json

[codespell] start fixing all the typos this is the inital patch of applying codespell to nova. codespell is a programing focused spellchecker that looks for common typos and corrects them. i am breaking this into multiple commits to make it simpler to read and will automate the execution of codespell at the end of the series. Change-Id: If24a6c0a890f713545faa2d44b069c352655274e

2023年10月03日 00:51:35 +01:00

count =

pre-commit: Add mypy Add mypy so we can run these checks as part of our linting step. Note that mypy is the last item in the list of checks since flake8 is going to catch e.g. syntax issues which should be addressed first. This also allows us to drop use of mypywrap: rather than wrapping mypy, we can make use of mypy's configuration to specify the files we wish to run checks on. Change-Id: Ie51401ead4e31ccd70ab833c59cb397f802ff188 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>

2023年09月22日 11:44:48 +01:00

quiet-level = 4

openstack/nova - nova - OpenDev: Free Software Needs Free Tools

133 lines 4.6 KiB INI Raw Normal View History Unescape Escape

133 lines

4.6 KiB

INI

Raw Normal View History