| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
With this change nova.virt.fake.FakeDriver can be used for scale testing
using devstack. By setting 'compute_driver = nova.virt.fake.FakeDriver'
in nova.conf and disabiling quota and other limits, we can load up nova
to think it is running 1000's of instances. This particular scenario is
analagous to how the baremetal driver will work (one machine managing
100's to 1000's of instances).
Make nova.virt.fake.FakeDriver use CONF.host for hostname.
Change-Id: I731ca2968176b4e39dd2fe7fc99f479cc568398b
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The cfg API is now available via the oslo-config library, so switch to
it and remove the copied-and-pasted version.
Add the 2013.1b4 tarball to tools/pip-requires - this will be changed
to 'oslo-config>=2013.1' when oslo-config is published to pypi. This
will happen in time for grizzly final.
Add dependency_links to setup.py so that oslo-config can be installed
from the tarball URL specified in pip-requires.
Remove the 'deps = pep8==1.3.3' from tox.ini as it means all the other
deps get installed with easy_install which can't install oslo-config
from the URL.
Make tools/hacking.py include oslo in IMPORT_EXCEPTIONS like it already
does for paste. It turns out imp.find_module() doesn't correct handle
namespace packages.
Retain dummy cfg.py file until keystoneclient middleware has been
updated (I18c450174277c8e2d15ed93879da6cd92074c27a).
Change-Id: I4815aeb8a9341a31a250e920157f15ee15cfc5bc
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Most of the allocation for floating ips can be done on the calling
side, including finding the proper host to send the message to.
This saves us from making an rpc call for allocate/deallocate and
makes sure that we only need 1 call for associate/disassociate by
finding the proper host to send the message to immediately.
Getting exceptions to work properly required pulling in the helper
that was used by the conductor to regenerate exceptions that are
wrapped for rpc. Since this is now a shared class, it was moved
to utils.
Also a few config options were moved to avoid circular imports.
Part of blueprint optimize-nova-network
Change-Id: I6ec65b1f3e8d00cab778b10eec620760886567e0
|
| |
|
|
|
|
|
|
| |
* Includes some general tools/hacking cleanup
* Fix several N302 cases
* Disable N302 until all cases are fixed
Change-Id: Iddba07ff13e10dc41a6930749044bb8c0572d279
|
| |
|
|
|
|
|
|
|
|
|
| |
The my_ip, host and use_ipv6 options are used all over the codebase
and they're pretty well related to each other. Create a new netconf
module for them to live in.
There are now no options registered globally in nova.config!
blueprint: scope-config-opts
Change-Id: Ifde37839ae6f38e6bf99dff1e80b8e25fd68ed25
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We only ever do one of two things with the global path options:
1) Reference the option in the default of another option so that the
value can be interpolated it
2) Use the value of the option to build a path
Add helper methods for both these cases - e.g. basedir_def() for the
former case and basedir_rel() for the latter case. This makes it much
more obvious how and where these options are used.
Change-Id: I7fd94a329fe911761d02d94e5381e950c6668d56
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Move the global path config options (i.e. state_path, pybasedir and
bindir) into a new nova.paths module. A new module may seem like
overkill but some utility methods associated with these options follow
in a later commit.
Moving them to nova.paths means they are no longer globally defined
and it's more obvious which modules require these options.
Change-Id: I381d23f1bbe36dc6967a38a65062b0983e1661aa
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
The instance_dns_manager, instance_dns_domain and
floating_ip_dns_manager options are only used in nova.network.manager.
blueprint: scope-config-opts
Change-Id: Ic4dfe01ec87e0b9a4ba244f85cf0a81568f3f9bf
|
| |/
|
|
|
|
|
|
|
|
| |
This fixes test isolation errors where tests were running with
the wrong ipv6 backend and failing. The failures occured because
Python discovers tests in filesystem order rather than a sorted
order, and the test that was changing the backend had previously
always run later under nose, which does not use filesystem order.
Change-Id: Ife4370d0747b269c9bc9aabb50c531cb6c9fec13
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
The api_paste_config option is only used in nova.wsgi so we can
have it be registered there too.
blueprint: scope-config-opts
Change-Id: I438102b2524bd96faf8392f3ba600235ce7116a4
|
| |/
|
|
|
|
|
|
| |
There is a fair amount of indirection in place here, which could be
trimmed - this patch takes a minimal approach and only causes the
current top level entry to be called, fixing bug 1088761.
Change-Id: Ifd80f99561eb95257f2a1bf45a39f678a2c1f59c
|
|
|
Moving the test-case setup and teardown code into managed fixtures
so that we can better interact with them when we start running things
in parallel.
Part of blueprint grizzly-testtools
Change-Id: I406be0a88b14c0dba2d22b4957e26a53442bbae3
|
