The toctree was globbing a nonexistent directory, and not producing
useful output. This patch lists the contents correctly.
Change-Id: I414120d948bd3eeeec84ac279bab11c276ef5eee
In the absence of a specified fixed address with which to associate a
floating IP, the first IPv4 address on the port should be associated.
Without the check for IPv4, IPv6 ports can be associated with a (IPv4)
floating IP, which is not supported.
Change-Id: Ib66a9109cc1c7999474daca5970d0af1f70886e4
Closes-Bug: 1437855
During live migration _post_live_migration and
post_live_migration_at_destination_method are executed
simultaneously, because second one is called over rpc.cast
In _post_live_migration method there was setup_network_on_host
call with teardown=True, which expects new host in instances
table db field. This update could be happened later, as it
executes on destination node in second method. To guarantee
execution order setup_network_on_host call, which cleans
dhcp-hostfile is moved to destination node.
Closes-Bug: #1444497
Change-Id: I55f0c0148c937601e78f0beecc21b30a1164a690
service.py had some code where the child process would catch the
SIGTERM from the parent just so it could exit with 1 status rather
than with an indication that it exited due to SIGTERM. When
shutting down the parent doesn't care in what way the child ended,
only that they're all gone, so this code is unnecessary.
Also, for some reason this caused the child to never exit while
there was an open connection from a client. Probably something
with eventlet and signal handling.
Syncs commit: 702bc569987854b602ef189655c201c348de84cb
Change-Id: I3c5249f5e59bb396bcb50964907ea61ebb2a3c8a
Closes-Bug: #1446583
The TC approved a cross project spec to stop putting db downgrade into
project migration repos:
https://github.com/openstack/openstack-specs/blob/master/specs/no-downward-sql-migration.rst
This was done after quite a bit of feedback from the operator community,
and everyone was good with it.
This implements that spec for Nova, adjust the tests to pass
accordingly, and changes the test which requires downgrade functions
to one that prohibits them.
Implements bp nova-no-downward-sql-migration
Change-Id: I972e1d79e570d57baac613e56570b49e1b1da28d
oslo_utils some routines to handle module importation, we
should use them in our code base insteadof invoking
the private built-in __import__
Change-Id: I5647ec4864e6202e7886c2923cdde30f8736ae29
Currently, the check for cpu pinning is a little broad and
it doesn't allow pinning for discrete online pcpu sets if the
cpuset ID exceeds the total number of online pcpus.
The fix is for NUMA topology enabled hosts, where the list of
online pcpus are obtained and compared with the list of IDs which
are requested as a part of cpu pinning. If the IDs form a subset
of the total online pcpus on the host, pinning is allowed.
If not, old behavior is retained.
Change-Id: I8cbd938f99e1eae9eeaa3bb27f492c95734bbfab
Closes-Bug: #1442546
The way the query was being performed previously, we would not see any
instances that didn't have a row in instance_extra. This could happen if
an instance hasn't been touched for several releases, or if the data
set is old.
The fix is a simple change to use outerjoin instead of join. This patch
includes a test that ensures that instances with no instance_extra rows
are included in the migration. If we query an instance without such a
row, we create it before doing a save on the instance.
Closes-Bug: #1447132
Change-Id: I2620a8a4338f5c493350f26cdba3e41f3cb28de7
The substitution wasn't being done resulting in the following being
printed:
%(total)i instances matched query, %(done)i completed {'total': 0, 'done': 0}
Change-Id: Iebc6de6a677f5a46671f6a497786a3013b1d925e
The max_number was not being set correctly due to mapping from
--max-number onto max_number in the params not being set up.
Also the migrate_flavor_data db API doesn't require a max-number to
process. If None is given all instances will have their flavor data
migrated. Support this option by not requiring the --max-number
param from the cli.
Change-Id: Ic2ded8d498b34cb1212fb6fa1c8f1a60f0581a76
The TC approved a cross project spec to stop putting db downgrade into
project migration repos:
https://github.com/openstack/openstack-specs/blob/master/specs/no-downward-sql-migration.rst
This was done after quite a bit of feedback from the operator
community, and everyone was good with it.
This implements that spec for Nova, adjust the tests to pass
accordingly, and changes the test which requires downgrade functions
to one that prohibits them.
Implements bp nova-no-downward-sql-migration
Change-Id: I9b164b748998530d62bbc6baf356a9c3f61584cc
The permissions of create/delete flavor api is currently broken
and expects the user to be always an admin, instead of controlling
the permissions by the rules defined in the nova policy.json.
Change-Id: Ide3c9ec2fa674b4fe3ea9d935cd4f7848914b82e
Closes-Bug: 1445335
When running OpenStack in an environment where there
is network latency the administrator will be unable to use the instance
console. Please see http://goo.gl/gKTqYZ for explanations.
DocImpact:
A new configuration variable in the vmware section will be added. This
is 'console_delay_seconds'. If set the instance created will have the
keyboard.typematicMinDelay set to this value.
Closes-bug: #1443082
Change-Id: I1b4e89d8b4a236e5f1e328be3d8ee54eceb37e2a
Matthew Gilliard