openstack/nova
Code Issues Proposed changes
56f5172f33
nova/setup.cfg

82 lines
2.3 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]
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]
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
Update rootwrap with code from oslo. Change-Id: I30f1b8773840c098f1e38d09bf13f0863035289e
2013-05-02 10:26:37 -04:00
nova-rootwrap = nova.openstack.common.rootwrap.cmd: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-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 =
fixed_ips = nova.api.openstack.compute.plugins.v3.fixed_ips:FixedIPs
Added a config file to let setup.py drive building the sphinx docs.
2010-07-16 15:33:24 -05:00
[build_sphinx]
Updated setup.py file to install stuff on a python setup.py install command.
2010-07-27 21:41:07 -07:00
all_files = 1
build-dir = doc/build
Updated sphinx layout to a two-dir layout like swift. Updated a doc string to get rid of a Sphinx warning.
2010-07-24 18:06:22 -07:00
source-dir = doc/source
Updated setup.py file to install stuff on a python setup.py install command.
2010-07-27 21:41:07 -07:00
[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]
Move translations to babel locations. If we structure things like this, we can get things actually, you know, installed. Locales ast and oc aren't supported by babel. We'll re-import them from Launchpad once we get babel updated. If you want translations installed, run: python setup.py compile_catalog Before you run either setup.py sdist or setup.py install More work is needed to actually properly use the installed translations, but we're closer. Change-Id: I4a4bedd982c89063aa09688c9cbcf97054bcb34b
2012-02-08 00:16:50 -08:00
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
Move translations to babel locations. If we structure things like this, we can get things actually, you know, installed. Locales ast and oc aren't supported by babel. We'll re-import them from Launchpad once we get babel updated. If you want translations installed, run: python setup.py compile_catalog Before you run either setup.py sdist or setup.py install More work is needed to actually properly use the installed translations, but we're closer. Change-Id: I4a4bedd982c89063aa09688c9cbcf97054bcb34b
2012-02-08 00:16:50 -08:00
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]
Move translations to babel locations. If we structure things like this, we can get things actually, you know, installed. Locales ast and oc aren't supported by babel. We'll re-import them from Launchpad once we get babel updated. If you want translations installed, run: python setup.py compile_catalog Before you run either setup.py sdist or setup.py install More work is needed to actually properly use the installed translations, but we're closer. Change-Id: I4a4bedd982c89063aa09688c9cbcf97054bcb34b
2012-02-08 00:16:50 -08:00
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
Move translations to babel locations. If we structure things like this, we can get things actually, you know, installed. Locales ast and oc aren't supported by babel. We'll re-import them from Launchpad once we get babel updated. If you want translations installed, run: python setup.py compile_catalog Before you run either setup.py sdist or setup.py install More work is needed to actually properly use the installed translations, but we're closer. Change-Id: I4a4bedd982c89063aa09688c9cbcf97054bcb34b
2012-02-08 00:16:50 -08:00
output_file = nova/locale/nova.pot
Copy Permalink