These methods are un-needed. Their functionality is now provided by the
HostAPI and ComputeRPCProxyAPI.
Change-Id: I771f1e4669f8b7fb779a0fec0209c3e2a899a469
In change I35d4565389d03fce86103289cf6447f824efeba0 we changed the cidr/ip
address column size to 43 to be able to support ipv6 cidr values, although ips
doesn't need that much space so we're reverting it to keep it consistent.
Change-Id: Icd2d727fd0733ee0db23c1fa431df4b982cae7b4
For nova, forbid_dtd is going to be true always, however
if someone picks up this code and tries forbid_dtd = False
then the existing code is not good enough. we need to protect
against external entities/dtd and not allow notations as well.
Added a few more handlers and test cases to cover that use
case.
Change-Id: If50f690e015f2bf837b403edf552e35d7af8c907
Fixes bug #1133247
suds is used by the vmware driver and the dependency has always been
pinned to 0.4:
67e63ba8 (Sateesh Chodapuneedi 2011-03-07 18:10:48 +0530 17) suds==0.4
0.4 was released in September 2010 and there hasn't been a release
since. In fact, there has only been 16 commits since then and none of
them look to break the existing API.
If there's no reason to expect the next version to break us, we should
unpin. Indeed, we want to know early if upstream does break its API.
Change-Id: Icd2bdd021093293b2e4261a00d063239a3c42ce6
Fixes bug #1133216
We've been pinned to the same version of Cheetah since May 2011:
Cheetah==2.4.4
this was released in December 2010 and there hasn't been a release since:
https://pypi.python.org/pypi/Cheetah/2.4.4
There's no particular reason to believe a future release of Cheetah will break
us (only 6 commits since 2.4.4 and they all look like bugfixes), so we should
change to:
Cheetah>=2.4.4
Change-Id: Id3b22b84d2d693776f89ccb1d0c99d4e42fcab62
The zookeeper python module isn't widely available (e.g. not available
on Fedora), so allow the zk servicegroup driver be imported even if the
module isn't found.
This helps allow the generate_sample.sh script generate a sample config
file even without zookeeper installed.
Change-Id: Ic3b3bb75bcd2003150909ebd2c5724fa5093c346
Update the floating_ip_fixed_ip_associate method of the sqlalchemy db
API to retry if it fails because of a deadlock. The decorator that
handles this was introduced in e53e22271e.
The related bug report shows that this method could benefit from the use
of this decorator.
Fix bug 1090016.
Change-Id: I0159470e6eb2f8017bcb3e659e7b119194dda920
Fix missingImport logic to handle a module that cannot be imported, due
to a missing dependant module.
Due to the nature of this bug doctests cannot cover it.
Fix bug 1133103
Change-Id: Ia067bacc125b67e2d9e0cfc72495e4f13a8648ad
This module calls time.sleep(1), but was not importing the time module.
This fixes it.
Fix bug 1133056.
Change-Id: Ifbba2a98ccdd8d5e26ce466831618ccab9e0b462
In cases where a valid host is passed, the if
statement is always executed twice, not once like it should
Change-Id: I6a24bb4f85bfb94d2fdc5d1652ee371f296a10ef
First test_get_host_uptime was missing a parameter that the
second test contains. So remove first test.
Fixes bug 1133062
Change-Id: Id886f4e52f45505117fd8e7bf30bc4d77cacd47b
DB exceptions have moved to openstack/common/db/exception module so that
they can be shared with multiple DB implementations.
Deadlock checking was also added to oslo to consolidate with
DuplicateKey checking. This allows us to clean up our
_retry_on_deadlock decorator in sqlalchemy/api.py
Fixes unrelated pep8 issue with duplicate test in test_compute also.
Change-Id: I7e985b384d1ef345e0d67c919b84b4faff869699
Change 1c5518ba introduced different user/passwd for the baremetal CI
tests, which did not match the CI systems. Since then, all the baremetal
migration tests have been skipped or failing.
This patch sets the user/passwd back to 'openstack_citest'.
Change-Id: I88508d83d6e9e63f20c26704ec6b455c48a33e8f
we get failures in _reset_databases from time to time, and it's
hard to debug without understanding what command failed. Make
this show up in the assert message.
Now with even more output!
Change-Id: Ie82109cfb1745e7218e0906764db1fad0c8fc5f5
This patch adds support to linux_net and nova-dhcpbridge for
specifying and conveying multiple dhcpbridge_flagfile values.
The support is implemented as follows:
dhcpbridge_flagfile is now a "MultiStr" configuration file option
allowing the flag files to be defined over multiple configuration files.
The configured files are concatenated into a comma separated string and
assigned to the FLAGFILE environment variable when invoking
nova-dhcpbridge. nova-dhcpbridge splits the value of the environment
variable on the comma an initializes its configuration with the provided
files (the configuration system already supports loading configuration
from multiple files)
Fixes bug 1131932
Change-Id: Ic9cc57b8f7d9356606b9134ef5b63ab07b6099d9
Testr doesn't directly support running tests with pdb so the --debug
option was pulled from run_tests.sh during the testr switch. Add the
flag back into run_tests.sh and have it run tests with testtools.run
which allows users to import pdb in tests then run them without
interference from testr.
Example usage:
# First edit test file to import pdb.
run_tests.sh -d path.to.test
If the test is not given on the command line all tests will be run.
Change-Id: I4afca9ca997ccb6c575b714b778a9db8306c7891
Fixes bug #1132138
Only unused disk images are currently cleaned up by the image cache
manager but it seems logical to clean up unused kernels and ramdisks
too.
Achieve that by writing kernels and ramdisks to disk using the sha1
sum of their ID as the filename. This is the same scheme as used for
disk image filenames and causes the image cache manager to consider
them for cleanup. We also make the cache manager take note of in use
kernels and ramdisks when iterating over the list of instances.
A nasty upgrade concern is that if we immediately switch to writing
kernels to disk using this scheme then, where shared storage is used,
we can have older image cache managers on remote compute nodes cleaning
up kernels because they appear unused. To mitigate that, turn off this
behaviour by default and allow it to be enabled using a new config
option. This option will be removed in future and the behaviour enabled
by default.
DocImpact: new remove_unused_kernels option
Change-Id: I56bba9fa6596601104498e262c2e657f0eae2fa0
Jenkins