Files
f953e2062207c0b39e48d8d297eebc48f8d1b13d
nova /setup.cfg

147 lines
7.3 KiB
INI
Raw Normal View History

[metadata]
name = nova
version = 2013.2
summary = Cloud computing fabric controller
description-file =
README.rst
author = OpenStack
author-email = openstack-dev@lists.openstack.org
home-page = http://www.openstack.org/
classifier =
Environment :: OpenStack
Intended Audience :: Information Technology
Intended Audience :: System Administrators
License :: OSI Approved :: Apache Software License
Operating System :: POSIX :: Linux
Programming Language :: Python
Programming Language :: Python :: 2
Programming Language :: Python :: 2.7
Programming Language :: Python :: 2.6
[global]
setup-hooks =
pbr.hooks.setup_hook
[files]
packages =
nova
[entry_points]
Add plug-in modules for direct downloads of glance locations Glance can expose direct URL locations to its clients. In current versions of nova the only URL that can be accessed directly is file://. This patch adds a notion of download plug-ins. With this new download protocol modules can be added without disruption to the rest of the code base. Based on the scheme of the URL returned from Glance a plug-in will be loaded and used to download the data directly, instead of first routing it through Glance. If anything fails in the process the image will be downloaded by way of Glance. Handlers are loaded with stevedore. To add a new module follow the example in nova.image.downloads.file.py. The module is required to have two functions: get_download_hander(): This must return a child of nova.image.download.TransferBase get_scheme(): Return the URL scheme that this module handles (ex: 'file') If additional configuration is needed it can be added by the specific plug-in (as shown by file_download_module_config included with this patch submission). Once the module is created it must be added as an entry point to the python installation. For those included with nova this can be done by adding the following it setup.cfg: [entry_points] nova.download.modules = file = nova.image.xfers.file Additionally, as part of the multiple-locations work in Glance meta data comes back with each location describing it. As an example, this is needed for direct access to file URLs. Nova cannot assume that every file URL is accessible on its mounted file systems, nor can it assume that the mount points are the same. This patch solves that problem for direct access to files. blueprint image-multiple-location Change-Id: I79b863c0075cebaadce5b630f22b81d2959ddbb1
2013年07月18日 10:39:33 -10:00
nova.image.download.modules =
file = nova.image.download.file
console_scripts =
nova-all = nova.cmd.all:main
nova-api = nova.cmd.api:main
nova-api-ec2 = nova.cmd.api_ec2:main
nova-api-metadata = nova.cmd.api_metadata:main
nova-api-os-compute = nova.cmd.api_os_compute:main
nova-baremetal-deploy-helper = nova.cmd.baremetal_deploy_helper:main
nova-baremetal-manage = nova.cmd.baremetal_manage:main
nova-rpc-zmq-receiver = nova.cmd.rpc_zmq_receiver:main
nova-cells = nova.cmd.cells:main
nova-cert = nova.cmd.cert:main
nova-clear-rabbit-queues = nova.cmd.clear_rabbit_queues:main
nova-compute = nova.cmd.compute:main
nova-conductor = nova.cmd.conductor:main
nova-console = nova.cmd.console:main
nova-consoleauth = nova.cmd.consoleauth:main
nova-dhcpbridge = nova.cmd.dhcpbridge:main
nova-manage = nova.cmd.manage:main
nova-network = nova.cmd.network:main
nova-novncproxy = nova.cmd.novncproxy:main
nova-objectstore = nova.cmd.objectstore:main
nova-rootwrap = nova.openstack.common.rootwrap.cmd:main
nova-scheduler = nova.cmd.scheduler:main
nova-spicehtml5proxy = nova.cmd.spicehtml5proxy:main
nova-xvpvncproxy = nova.cmd.xvpvncproxy:main
API extensions framework for v3 API This is the initial patch for the new extension framework to be used by the Nova v3 API. It will only be used by v3 API extensions and not v2 API extensions. v3 API extensions will only use this plugin framework and will not be compatible with the old one. - Sets up a /v3 url prefix - Looks in an entry point namespace of nova.api.extensions - The fixed_ips extensions is ported to /v3 as an example of a resource extensions. Required changes are very minor. - All extensions must derive from the V3APIExtensionBase class - Drops updated field from extensions, replaced with version field - Ports tests for fixed_ips extension - None of the core has been ported in this patch, though the example extension works without it. The intent is to port the core code over as plugins as well. There will still be a conceptual core however I don't think we need a separate directory for core. This is the first of a series of patches to add support for the new extension framework. Future direction including support for controller extensions, removal of extension code in core code etc can be seen here: https://github.com/cyeoh/nova/tree/v3_api_extension_framework Partially implements blueprint v3-api-extension-framework Change-Id: I88aa6353ad1d74cac51abbb6aac7274b1567485a
2013年04月23日 02:15:27 +09:30
nova.api.v3.extensions =
admin_actions = nova.api.openstack.compute.plugins.v3.admin_actions:AdminActions
admin_password = nova.api.openstack.compute.plugins.v3.admin_password:AdminPassword
agents = nova.api.openstack.compute.plugins.v3.agents:Agents
aggregates = nova.api.openstack.compute.plugins.v3.aggregates:Aggregates
attach_interfaces = nova.api.openstack.compute.plugins.v3.attach_interfaces:AttachInterfaces
availability_zone = nova.api.openstack.compute.plugins.v3.availability_zone:AvailabilityZone
baremetal_nodes = nova.api.openstack.compute.plugins.v3.baremetal_nodes:BaremetalNodes
cells = nova.api.openstack.compute.plugins.v3.cells:Cells
certificates = nova.api.openstack.compute.plugins.v3.certificates:Certificates
Port config_drive API to v3 Part 2 Ports the config_drive extensions and the corresponding unittests to the v3 framework. Moves the commented out tests from the v3 version of test_servers to the config drive extension unittests. Adds entrypoint infrastructure to allow extensions to extend the way that the servers extension performs xml deserialization so extension specific deserialization does not require changes to the core servers extension. The blacklist/whitelist settings for extensions generally also apply to server extension point loading. Also merges in updates to config drive functionality which were applied to the v2 API while this changeset has been in review https://review.openstack.org/#/c/31314 Partially implements blueprint nova-v3-api Change-Id: Ic8b75cc8b353a6e22cbaf354317a78c4df8d937e
2013年06月13日 13:20:36 +09:30
config_drive = nova.api.openstack.compute.plugins.v3.config_drive:ConfigDrive
console_output = nova.api.openstack.compute.plugins.v3.console_output:ConsoleOutput
consoles = nova.api.openstack.compute.plugins.v3.consoles:Consoles
coverage = nova.api.openstack.compute.plugins.v3.coverage:Coverage
deferred_delete = nova.api.openstack.compute.plugins.v3.deferred_delete:DeferredDelete
evacuate = nova.api.openstack.compute.plugins.v3.evacuate:Evacuate
extended_availability_zone = nova.api.openstack.compute.plugins.v3.extended_availability_zone:ExtendedAvailabilityZone
extended_server_attributes = nova.api.openstack.compute.plugins.v3.extended_server_attributes:ExtendedServerAttributes
extended_status = nova.api.openstack.compute.plugins.v3.extended_status:ExtendedStatus
extended_volumes = nova.api.openstack.compute.plugins.v3.extended_volumes:ExtendedVolumes
API Extensions framework for v3 API Part 2 This is the second patch for the new extension framework which is only to be used by the Nova v3 API. - Adds tracking of extensions loaded and allows extensions access to this information - Adds core API functionality as extensions - 'server' - Adds an entry point that other extensions can use to modify the server create arguments without having to modify the server extension itself - TODO: Will have to add more entry points as other extensions are ported. Delaying adding entry points now so they can be tested as they are added. - Adds port of os-keypairs extension - This is an example of a controller extension in the new framework - This is an example of using the server extension entry point to add functionality without modify the core API code - Ports tests for the os-keypairs extensions - Adds v3 API fake specific code for tests This completes the bulk of the new extension framework. Porting of the server tests will be done in future changesets as more of the core API is ported across as the tests are dependent on multiple core APIs. Partially implements blueprint v3-api-extension-framework Change-Id: Ibadb5bbe808c27d2f4afebe65c06a92576397085
2013年05月06日 22:39:13 +09:30
extension_info = nova.api.openstack.compute.plugins.v3.extension_info:ExtensionInfo
fixed_ips = nova.api.openstack.compute.plugins.v3.fixed_ips:FixedIPs
flavors = nova.api.openstack.compute.plugins.v3.flavors:Flavors
flavors_extraspecs = nova.api.openstack.compute.plugins.v3.flavors_extraspecs:FlavorsExtraSpecs
flavor_access = nova.api.openstack.compute.plugins.v3.flavor_access:FlavorAccess
flavor_rxtx = nova.api.openstack.compute.plugins.v3.flavor_rxtx:FlavorRxtx
hide_server_addresses = nova.api.openstack.compute.plugins.v3.hide_server_addresses:HideServerAddresses
hosts = nova.api.openstack.compute.plugins.v3.hosts:Hosts
hypervisors = nova.api.openstack.compute.plugins.v3.hypervisors:Hypervisors
image_metadata = nova.api.openstack.compute.plugins.v3.image_metadata:ImageMetadata
images = nova.api.openstack.compute.plugins.v3.images:Images
instance_actions = nova.api.openstack.compute.plugins.v3.instance_actions:InstanceActions
ips = nova.api.openstack.compute.plugins.v3.ips:IPs
instance_usage_audit_log = nova.api.openstack.compute.plugins.v3.instance_usage_audit_log:InstanceUsageAuditLog
keypairs = nova.api.openstack.compute.plugins.v3.keypairs:Keypairs
limits = nova.api.openstack.compute.plugins.v3.limits:Limits
migrations = nova.api.openstack.compute.plugins.v3.migrations:Migrations
multinic = nova.api.openstack.compute.plugins.v3.multinic:Multinic
quota_classes = nova.api.openstack.compute.plugins.v3.quota_classes:QuotaClasses
quota_sets = nova.api.openstack.compute.plugins.v3.quota_sets:QuotaSets
remote_consoles = nova.api.openstack.compute.plugins.v3.remote_consoles:RemoteConsoles
rescue = nova.api.openstack.compute.plugins.v3.rescue:Rescue
scheduler_hints = nova.api.openstack.compute.plugins.v3.scheduler_hints:SchedulerHints
security_groups = nova.api.openstack.compute.plugins.v3.security_groups:SecurityGroups
server_diagnostics = nova.api.openstack.compute.plugins.v3.server_diagnostics:ServerDiagnostics
server_metadata = nova.api.openstack.compute.plugins.v3.server_metadata:ServerMetadata
server_password = nova.api.openstack.compute.plugins.v3.server_password:ServerPassword
server_usage = nova.api.openstack.compute.plugins.v3.server_usage:ServerUsage
servers = nova.api.openstack.compute.plugins.v3.servers:Servers
services = nova.api.openstack.compute.plugins.v3.services:Services
simple_tenant_usage = nova.api.openstack.compute.plugins.v3.simple_tenant_usage:SimpleTenantUsage
used_limits = nova.api.openstack.compute.plugins.v3.used_limits:UsedLimits
API Extensions framework for v3 API Part 2 This is the second patch for the new extension framework which is only to be used by the Nova v3 API. - Adds tracking of extensions loaded and allows extensions access to this information - Adds core API functionality as extensions - 'server' - Adds an entry point that other extensions can use to modify the server create arguments without having to modify the server extension itself - TODO: Will have to add more entry points as other extensions are ported. Delaying adding entry points now so they can be tested as they are added. - Adds port of os-keypairs extension - This is an example of a controller extension in the new framework - This is an example of using the server extension entry point to add functionality without modify the core API code - Ports tests for the os-keypairs extensions - Adds v3 API fake specific code for tests This completes the bulk of the new extension framework. Porting of the server tests will be done in future changesets as more of the core API is ported across as the tests are dependent on multiple core APIs. Partially implements blueprint v3-api-extension-framework Change-Id: Ibadb5bbe808c27d2f4afebe65c06a92576397085
2013年05月06日 22:39:13 +09:30
nova.api.v3.extensions.server.create =
availability_zone = nova.api.openstack.compute.plugins.v3.availability_zone:AvailabilityZone
Port config_drive API to v3 Part 2 Ports the config_drive extensions and the corresponding unittests to the v3 framework. Moves the commented out tests from the v3 version of test_servers to the config drive extension unittests. Adds entrypoint infrastructure to allow extensions to extend the way that the servers extension performs xml deserialization so extension specific deserialization does not require changes to the core servers extension. The blacklist/whitelist settings for extensions generally also apply to server extension point loading. Also merges in updates to config drive functionality which were applied to the v2 API while this changeset has been in review https://review.openstack.org/#/c/31314 Partially implements blueprint nova-v3-api Change-Id: Ic8b75cc8b353a6e22cbaf354317a78c4df8d937e
2013年06月13日 13:20:36 +09:30
config_drive = nova.api.openstack.compute.plugins.v3.config_drive:ConfigDrive
API Extensions framework for v3 API Part 2 This is the second patch for the new extension framework which is only to be used by the Nova v3 API. - Adds tracking of extensions loaded and allows extensions access to this information - Adds core API functionality as extensions - 'server' - Adds an entry point that other extensions can use to modify the server create arguments without having to modify the server extension itself - TODO: Will have to add more entry points as other extensions are ported. Delaying adding entry points now so they can be tested as they are added. - Adds port of os-keypairs extension - This is an example of a controller extension in the new framework - This is an example of using the server extension entry point to add functionality without modify the core API code - Ports tests for the os-keypairs extensions - Adds v3 API fake specific code for tests This completes the bulk of the new extension framework. Porting of the server tests will be done in future changesets as more of the core API is ported across as the tests are dependent on multiple core APIs. Partially implements blueprint v3-api-extension-framework Change-Id: Ibadb5bbe808c27d2f4afebe65c06a92576397085
2013年05月06日 22:39:13 +09:30
keypairs_create = nova.api.openstack.compute.plugins.v3.keypairs:Keypairs
scheduler_hints = nova.api.openstack.compute.plugins.v3.scheduler_hints:SchedulerHints
user_data = nova.api.openstack.compute.plugins.v3.user_data:UserData
API extensions framework for v3 API This is the initial patch for the new extension framework to be used by the Nova v3 API. It will only be used by v3 API extensions and not v2 API extensions. v3 API extensions will only use this plugin framework and will not be compatible with the old one. - Sets up a /v3 url prefix - Looks in an entry point namespace of nova.api.extensions - The fixed_ips extensions is ported to /v3 as an example of a resource extensions. Required changes are very minor. - All extensions must derive from the V3APIExtensionBase class - Drops updated field from extensions, replaced with version field - Ports tests for fixed_ips extension - None of the core has been ported in this patch, though the example extension works without it. The intent is to port the core code over as plugins as well. There will still be a conceptual core however I don't think we need a separate directory for core. This is the first of a series of patches to add support for the new extension framework. Future direction including support for controller extensions, removal of extension code in core code etc can be seen here: https://github.com/cyeoh/nova/tree/v3_api_extension_framework Partially implements blueprint v3-api-extension-framework Change-Id: I88aa6353ad1d74cac51abbb6aac7274b1567485a
2013年04月23日 02:15:27 +09:30
Port config_drive API to v3 Part 2 Ports the config_drive extensions and the corresponding unittests to the v3 framework. Moves the commented out tests from the v3 version of test_servers to the config drive extension unittests. Adds entrypoint infrastructure to allow extensions to extend the way that the servers extension performs xml deserialization so extension specific deserialization does not require changes to the core servers extension. The blacklist/whitelist settings for extensions generally also apply to server extension point loading. Also merges in updates to config drive functionality which were applied to the v2 API while this changeset has been in review https://review.openstack.org/#/c/31314 Partially implements blueprint nova-v3-api Change-Id: Ic8b75cc8b353a6e22cbaf354317a78c4df8d937e
2013年06月13日 13:20:36 +09:30
nova.api.v3.extensions.server.create.deserialize =
availability_zone = nova.api.openstack.compute.plugins.v3.availability_zone:AvailabilityZone
Port config_drive API to v3 Part 2 Ports the config_drive extensions and the corresponding unittests to the v3 framework. Moves the commented out tests from the v3 version of test_servers to the config drive extension unittests. Adds entrypoint infrastructure to allow extensions to extend the way that the servers extension performs xml deserialization so extension specific deserialization does not require changes to the core servers extension. The blacklist/whitelist settings for extensions generally also apply to server extension point loading. Also merges in updates to config drive functionality which were applied to the v2 API while this changeset has been in review https://review.openstack.org/#/c/31314 Partially implements blueprint nova-v3-api Change-Id: Ic8b75cc8b353a6e22cbaf354317a78c4df8d937e
2013年06月13日 13:20:36 +09:30
config_drive = nova.api.openstack.compute.plugins.v3.config_drive:ConfigDrive
scheduler_hints = nova.api.openstack.compute.plugins.v3.scheduler_hints:SchedulerHints
user_data = nova.api.openstack.compute.plugins.v3.user_data:UserData
Port config_drive API to v3 Part 2 Ports the config_drive extensions and the corresponding unittests to the v3 framework. Moves the commented out tests from the v3 version of test_servers to the config drive extension unittests. Adds entrypoint infrastructure to allow extensions to extend the way that the servers extension performs xml deserialization so extension specific deserialization does not require changes to the core servers extension. The blacklist/whitelist settings for extensions generally also apply to server extension point loading. Also merges in updates to config drive functionality which were applied to the v2 API while this changeset has been in review https://review.openstack.org/#/c/31314 Partially implements blueprint nova-v3-api Change-Id: Ic8b75cc8b353a6e22cbaf354317a78c4df8d937e
2013年06月13日 13:20:36 +09:30
[build_sphinx]
all_files = 1
build-dir = doc/build
source-dir = doc/source
[egg_info]
tag_build =
tag_date = 0
tag_svn_revision = 0
Get rid of distutils.extra. We moved to DistUtilsExtra because it promised a more automatic workflow from setup.py. It doesn't actually deliver though, and it also vomits warnings during setup.py usage, and also breaks pip integration. So this is going back to babel. Mostly folks shouldn't need to know anything about this. We'll need to update the translations import jobs in Jenkins, and we might need to add a corresponding translations upload job that runs post-merge. Translations installation doesn't fully work - but it actually wasn't fully working before. Getting this part of the project done now though is a pre-requisite for using tox for multi-python testing (tox starts by creating an sdist tarball and then installing it into the venv, which is just 100% broken with DistUtilsExtra) Change-Id: I126e1bcfab0656eab6ca10de67d3d2aaa8b844f3
2012年02月07日 14:32:15 -08:00
[compile_catalog]
directory = nova/locale
Get rid of distutils.extra. We moved to DistUtilsExtra because it promised a more automatic workflow from setup.py. It doesn't actually deliver though, and it also vomits warnings during setup.py usage, and also breaks pip integration. So this is going back to babel. Mostly folks shouldn't need to know anything about this. We'll need to update the translations import jobs in Jenkins, and we might need to add a corresponding translations upload job that runs post-merge. Translations installation doesn't fully work - but it actually wasn't fully working before. Getting this part of the project done now though is a pre-requisite for using tox for multi-python testing (tox starts by creating an sdist tarball and then installing it into the venv, which is just 100% broken with DistUtilsExtra) Change-Id: I126e1bcfab0656eab6ca10de67d3d2aaa8b844f3
2012年02月07日 14:32:15 -08:00
domain = nova
[update_catalog]
domain = nova
output_dir = nova/locale
input_file = nova/locale/nova.pot
Get rid of distutils.extra. We moved to DistUtilsExtra because it promised a more automatic workflow from setup.py. It doesn't actually deliver though, and it also vomits warnings during setup.py usage, and also breaks pip integration. So this is going back to babel. Mostly folks shouldn't need to know anything about this. We'll need to update the translations import jobs in Jenkins, and we might need to add a corresponding translations upload job that runs post-merge. Translations installation doesn't fully work - but it actually wasn't fully working before. Getting this part of the project done now though is a pre-requisite for using tox for multi-python testing (tox starts by creating an sdist tarball and then installing it into the venv, which is just 100% broken with DistUtilsExtra) Change-Id: I126e1bcfab0656eab6ca10de67d3d2aaa8b844f3
2012年02月07日 14:32:15 -08:00
[extract_messages]
keywords = _ gettext ngettext l_ lazy_gettext
Get rid of distutils.extra. We moved to DistUtilsExtra because it promised a more automatic workflow from setup.py. It doesn't actually deliver though, and it also vomits warnings during setup.py usage, and also breaks pip integration. So this is going back to babel. Mostly folks shouldn't need to know anything about this. We'll need to update the translations import jobs in Jenkins, and we might need to add a corresponding translations upload job that runs post-merge. Translations installation doesn't fully work - but it actually wasn't fully working before. Getting this part of the project done now though is a pre-requisite for using tox for multi-python testing (tox starts by creating an sdist tarball and then installing it into the venv, which is just 100% broken with DistUtilsExtra) Change-Id: I126e1bcfab0656eab6ca10de67d3d2aaa8b844f3
2012年02月07日 14:32:15 -08:00
mapping_file = babel.cfg
output_file = nova/locale/nova.pot