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

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 =

Port cells extension to v3 API Part 2 Ports the cells extensions and the corresponding unittests to the v3 framework. Merges in functionality of the os-cells-capacities extension to be the default behavior. Does not yet address v3 TODO of returning capacity information in the cell detail method Partially implements blueprint nova-v3-api Change-Id: I24df708b9d6504a355fca0eacd0ffaeb6586610d

2013年06月14日 13:05:56 +09:30

cells = nova.api.openstack.compute.plugins.v3.cells:Cells

Port certificates API to v3 Part 2 This patch contains the changes required to adapt the certificates extension and the corresponding unittests to the v3 framework Partially implements blueprint nova-v3-api Change-Id: If4fe7e8524ba0181b50722281f594e0a80cd49ed

2013年06月13日 14:48:02 +09:30

certificates = nova.api.openstack.compute.plugins.v3.certificates:Certificates

Alphabetize v3 API extension entry point list Alphabetize the v3 API extension point list in setup.cfg. With lots of extensions being ported to V3 and an entry needed in setup.cfg for each one and multiple people working on the ports if we always just add an entry to the end of the list we are going to get a lot of merge conflicts. To minimise the number of conflicts we'll try keeping the list in alphabetical order and the number of conflicts should drop as the list gets longer. Change-Id: I386ec9bdb99660861d80f47923855e73f474a15f

2013年06月06日 21:58:43 +09:30

consoles = nova.api.openstack.compute.plugins.v3.consoles:Consoles

Port evacuate API to v3 Part 2 This patch contains the changes required to adapt the evacuate extension and the corresponding unittest to the v3 framework Partially implements blueprint nova-v3-api Change-Id: Id9ca6a7a92a087cb063fe265af1ad6a626c63510

2013年06月07日 12:57:30 +09:30

evacuate = nova.api.openstack.compute.plugins.v3.evacuate:Evacuate

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

Alphabetize v3 API extension entry point list Alphabetize the v3 API extension point list in setup.cfg. With lots of extensions being ported to V3 and an entry needed in setup.cfg for each one and multiple people working on the ports if we always just add an entry to the end of the list we are going to get a lot of merge conflicts. To minimise the number of conflicts we'll try keeping the list in alphabetical order and the number of conflicts should drop as the list gets longer. Change-Id: I386ec9bdb99660861d80f47923855e73f474a15f

2013年06月06日 21:58:43 +09:30

fixed_ips = nova.api.openstack.compute.plugins.v3.fixed_ips:FixedIPs

Port flavors core API to v3 tree Port flavors core API (which does *not* include all extensions, like flavor create) to the V3 API, adapting the way it's loaded to fit with the new extension framework and, of course, its tests. This also change the flavors requests and responses links on unit tests since project_id is no longer present on v3 url Partially implements blueprint v3-api-core-as-extensions Change-Id: Ide2eb22a89be3bd9adcf5e09cbef23e824a83fc1

2013年05月10日 14:03:51 -04:00

flavors = nova.api.openstack.compute.plugins.v3.flavors:Flavors

Port flavor_access extension to v3 API Part 2 Ports the flavor_access extension and the corresponding unittests to the v3 framework. Partially implements blueprint nova-v3-api Change-Id: I671f490bad2daaaae06d48328f4fff10076ab0ed

2013年06月26日 17:53:57 +03:00

flavor_access = nova.api.openstack.compute.plugins.v3.flavor_access:FlavorAccess

Port flavor_disabled extension to v3 API Part 2 Ports the flavor_disabled extension and the corresponding unittests to the v3 framework. Partially implements blueprint nova-v3-api Change-Id: I8af3f69ebc0584b79499e2695d6120c7c0833d24

2013年06月27日 10:52:45 +03:00

flavor_disabled = nova.api.openstack.compute.plugins.v3.flavor_disabled:FlavorDisabled

Port images functionality to v3 API Part 2 The images functionality is moved for the V3 API from core to an extension and is now accessed via /os-images instead of /images. Consensus appears to be that we continue to need this functionality for v3 because some deployers disable the public image endpoint due security concerns and whether this will be fixed in glance for Havana. Deployers can disable this extension if they do not want it. A further changeset will follow which changes the view builder to correctly handle the lack of project id in the path with the v3 API. Partially implements blueprint nova-v3-api Change-Id: I1237ad1ab5c58bb2d7cd9460b14666b4b97ef7fc

2013年06月27日 20:30:45 +09:30

images = nova.api.openstack.compute.plugins.v3.images:Images

Ports ips api to v3 API Port the core ips api to the V3 API as plugins along with the corresponding tests for the ips and servers API. Partially implements blueprint v3-api-core-as-extensions Change-Id: I6e9f8ab71745791e6bc18999810f39764cd40116

2013年05月09日 18:54:22 +09:30

ips = nova.api.openstack.compute.plugins.v3.ips:IPs

Alphabetize v3 API extension entry point list Alphabetize the v3 API extension point list in setup.cfg. With lots of extensions being ported to V3 and an entry needed in setup.cfg for each one and multiple people working on the ports if we always just add an entry to the end of the list we are going to get a lot of merge conflicts. To minimise the number of conflicts we'll try keeping the list in alphabetical order and the number of conflicts should drop as the list gets longer. Change-Id: I386ec9bdb99660861d80f47923855e73f474a15f

2013年06月06日 21:58:43 +09:30

keypairs = nova.api.openstack.compute.plugins.v3.keypairs:Keypairs

Port quota API into v3 part2 This patch contains the changes required to adapt the service extension and the corresponding unittest to the v3 framework Partially implements bp v3-api-extension-versioning Change-Id: If5438d5bef5da1832e81c0b80523f9f419d5e3d5

2013年06月25日 16:07:23 +08:00

quota_sets = nova.api.openstack.compute.plugins.v3.quota_sets:QuotaSets

Port rescue API to v3 Part 2 This patch contains the changes required to adapt the rescue extension and the corresponding unittest to the v3 framework Partially implements blueprint nova-v3-api Change-Id: Iaa6d0cf7708b0887512db952b1e26ccde75d24ef

2013年06月04日 21:57:18 +09:30

rescue = nova.api.openstack.compute.plugins.v3.rescue:Rescue

Port server_diagnostics extension to v3 API Part2 Ports the server_diagnostics extensions and the corresponding unittests to the v3 framework. Partially implements blueprint nova-v3-api Change-Id: I2ddf626a539d47884e845d73ec67e9f9169dcb2b

2013年06月17日 11:32:10 +09:30

server_diagnostics = nova.api.openstack.compute.plugins.v3.server_diagnostics:ServerDiagnostics

Alphabetize v3 API extension entry point list Alphabetize the v3 API extension point list in setup.cfg. With lots of extensions being ported to V3 and an entry needed in setup.cfg for each one and multiple people working on the ports if we always just add an entry to the end of the list we are going to get a lot of merge conflicts. To minimise the number of conflicts we'll try keeping the list in alphabetical order and the number of conflicts should drop as the list gets longer. Change-Id: I386ec9bdb99660861d80f47923855e73f474a15f

2013年06月06日 21:58:43 +09:30

servers = nova.api.openstack.compute.plugins.v3.servers:Servers

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 =

keypairs_create = nova.api.openstack.compute.plugins.v3.keypairs:Keypairs

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

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

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

100 lines 3.5 KiB INI Raw Normal View History Unescape Escape

100 lines

3.5 KiB

INI

Raw Normal View History