I8f09f9482736b496e3ad7117f170e476e92c2b7d enabled Nova for mutable
config. On approving, John Garbutt indicated he'd like a reno for it,
so here it is.
Change-Id: Id4fc27bda876a70d3e20372d5da336c88781db4e
The legacy v2 API code was removed. The policy rules which are used by legacy
v2 API code are useless anymore. This patch cleanup them.
Partially implements blueprint remove-legacy-v2-api-code
Change-Id: I64648bf97ec483981426086b81b2056928fa1b3e
This uses the new 'prlimit' parameter for oslo.concurrency execute
method, to set an address space limit of 1GB and CPU time limit
of 2 seconds, when running qemu-img.
This is a re-implementation of the previously reverted commit
commit da217205f53f9a38a573fb151898fbbeae41021d
Author: Tristan Cacqueray <tdecacqu@redhat.com>
Date: Wed Aug 5 17:17:04 2015 +0000
virt: Use preexec_fn to ulimit qemu-img info call
Closes-Bug: #1449062
Change-Id: I135b5242af1bfdcb0ea09a6fcda21fc03a6fbe7d
After modifying the evacuate action, we now add a new microversion
change for modifying the live-migrate call so that the scheduler is
called when the admin user provides an hostname unless the force
field is provided.
APIImpact
Implements: blueprint check-destination-on-migrations-newton
Change-Id: I212cbb44f46d7cb36b5d8c74a79065d38fc526d8
Adding a new microversion for changing the evacuate action behaviour
to call the scheduler anyway unless the admin user provides a force
flag that then keeps the previous behaviour by forcing the conductor
to call the destination without verifying it.
Implements: blueprint check-destination-on-migrations
APIImpact
Change-Id: I9ecbe3d481bf17b12072511da4bb106ff1b6404e
After this microversion Nova API the GET request to
/v2.1/os-hypervisors/{hypervisor_id} responses cpu_info
as regular JSON object instead of string.
Implements blueprint nova-api-hypervsor-cpu-info
Change-Id: I14db9017f69e70e759cc80d031f76af8be179e45
Microsoft RemoteFX enhances the visual experience in RDP connections,
including providing access to virtualized instances of a physical GPU to
multiple guests running on Hyper-V.
In order to use RemoteFX in Hyper-V 2012 R2, one or more DirectX 11 capable
display adapters must be present and the RDS-Virtualization server feature
must be installed.
This patch enables RemoteFX on Hyper-V Server / Windows Server 2012 R2
and above.
Co-Authored-By: Adelina Tuvenie <atuvenie@cloudbasesolutions.com>
Co-Authored-By: Claudiu Belu <cbelu@cloudbasesolutions.com>
DocImpact
Implements: blueprint hyper-v-remotefx
Change-Id: I91fabd5bce2564d48957e8aec1e50ff2625e5747
There was a substantial amount of code in the image cache devoted to
checksumming images. However, these checksums were never used beyond
the generation of a log message during the image cache manager's
periodic task of the form:
Corrupt base files: ...
This code was expensive to run, added significant complexity to the
image cache manager, and not actually used by anything. This patch
removes it. The only functional change should be that the above log
message is no longer generated.
We can't remove it completely in this pass because the image cache
may be on shared storage with an old compute host which expects these
files to exist. Consequently we retain the code to delete the image
metadata file when deleting an entry from the cache, and we don't
delete these files automatically when we find them. These vestiges can
be removed in Ocata.
Additional context can be found here:
http://lists.openstack.org/pipermail/openstack-dev/2016-May/095751.html
Change-Id: I3d84117809d5058cb2c779754523913347d5374b
In this change the new OpenStack-API-Version headers is allowed,
but not required, for requesting a microversion.
Both headers are accepted in the request and both headers are sent in
the response (both the header and its value, and the addition to the Vary
header).
Many tests which explicitly use a microversion header have been
updated to use both. This change is not 100% as most of the tests
are testing the handling of the value of the header, not which
header is involved.
Partially-Implements: blueprint modern-microversions
Change-Id: I68da13b5ba0c2f3357523e765a5b9db81899daf1
This patch removes the APIRouter because there is not any code
which uses the APIRouter. In addition, this patch update the
corresponding reno for explaining actual way for api-paste.ini.
Partially implements blueprint remove-legacy-v2-api-code
Change-Id: I136eb6ce7478f9ff692ebcbe1b14aa76222826bf
This removes db2 support from tree completely. This is an oddball non
open database that made doing live data migrations difficult. It is
used by 0% of users in the OpenStack User Survey.
Supporting commercial software that doesn't have users at the cost of
delivering features and fixes to our community is the wrong
tradeoff. This corrects that.
It rewrites migrations, which we typically don't ever do, but it is
better if newton fresh environments fail early in db creation instead
of very deep in the data migration process.
Change-Id: Ifeb9929e4515e3483eb65d371126afd7672b92a4
This moves keypairs from the main database to the API database in
an online migration. Note that it refuses to run until all of the
instances have keypair information, so that we don't strand instances
that might need to lazy-load those things.
Related to blueprint cells-keypairs-api-db
Change-Id: I97b72ae3e7e8ea3d6b596870d8da3aaa689fd6b5
Passing a compute_driver via nova.virt.foo worked in the past, and no
longer does after merging 8eb03de1eb83a6cd2d4d41804e1b8253f94e5400. Add
an upgrade note to make sure anyone using this doesn't get burned.
Change-Id: I89e6b669a5ba1232bde88821f40022314ba2541b
The config option "fatal_exception_format_errors" got introduced purely
for testing purposes with commit 2e80b297. This isn't an option the ops
would change from it's default value.
This change deprecates the option. When this option gets removed in the
future, we can hardcode that wrong formats should be fatal by default,
as it is already set today in "nova/conf_fixture.py".
Change-Id: I184b1b1cbd85f136cee120965e38e2ef87bb66ff
This option was deprecated in Grizzly, and explicitly marked for
removal in 13.0.0. We have reached this version, and it complicates
the cleanup of writing to the image cache, so now is the time to
remove it.
Change-Id: Iadfe21c956880d9cbe5c16a1e277e1c5362a5755
The "S3ImageService" class needed config options to set the
expected behavior. This class is not referenced in the code anymore,
as we deprecated S3 in Kilo and removed (most of) the code in Mitaka
with commit 4140eb4 with a proper release note.
This change deprecates the s3 image module related config options.
Change-Id: I65e2973b6660e36c791e1c644cfca9da7519d716
The ``default_flavor`` config option is now deprecated and may be
removed as early as the 15.0.0 release. It is an option which was only
relevant for the deprecated EC2 API and is not used in the Nova API.
Change-Id: I31683bd50745ae3c0e1573f43f9ee4165377b0dd
The 'memcached_server' option in DEFAULT section which was deprecated in
Mitaka has been completely removed in Newton. This has been replaced by
options from oslo cache section.
Change-Id: I0b23fd65a04de6a35e8ce9efd1110caad63ad562
Users need to mark as reserved some amount of pages for third party
components.
The most common use case for using huge/large pages is NFV. In the
current state of that feature we can't guarantee the necessary amount
of pages to allow OVS-DPDK to run properly on the compute node, which
result in the instance failing to boot on a well selected
compute-node. OVS-DPDK needs 1 GB hugepages reserved. Since Nova does
not take into account that page reserved for OVS-DPDK it results in
the process not being able to acquire the necessary memory which
results in a failed boot.
This commit adds a new option 'reserved_huge_pages' which takes a list
of string format to select on which host NUMA nodes and from which
pagesize we want to reserve a certain amount of pages. It also updates
NUMAPageTopology to contain a reserved memory pages attribute, which
helps compute the available pages size on host for scheduling/claiming
resources.
Change-Id: Ie04d6362a4e99dcb2504698fc831a366ba746b44
Closes-Bug: #1543149
In August 2013 the blueprint "image-multiple-location" got merged
with commit 6f9ed56. This commit introduced another way of
downloading images from glance, despite the normal way via HTTP.
After discussing this in IRC, we believe that this feature was never
used in any production environment (it was designed for a Rackspace
use case which never made it to reality) and that the plugin mechanism
of image downloaders isn't the way to go, this change will deprecate
the feature.
Change-Id: I67e2cbf956286132da90ad6a4c6d5075d99177a9
The config option "client_log_level" of the "ironic" section was
deprecated with commit d6baa2ae4d7f18dc2e4845af25c21b95767f46ef since
the Kilo release and this change removes this option.
Closes-Bug: 1365230
Change-Id: I605d4ca5b3924ecf013cbf7e228e713b864d7aa4
The api sample tests and functional tests already stopped to
run against with legacy v2 API. This patch removes the legacy
V2 API entry from api-paste.ini, it stops user from using
legacy V2 API. This patch also adds deprecated report in pipeline
factory method to notice the user update their api-paste.ini
after upgrade code.
Partially implements blueprint remove-legacy-v2-api-code
Change-Id: I1476b2e364032d7c98f71df0cd61f1d1c19e005d
This deprecates Nova Network as was decided in the Nova / Neutron
design summit session for the Newton summit.
Change-Id: I1304a605fc4b1a832036bd98b5bfd0d630d6fe56
Previously Nova only checked the minimum required libvirt
version. It should also be checking for a minimum required
QEMU version.
This picks QEMU version 1.5.3, since that is the oldest
QEMU version that exists in the distros that include
the minimum libvirt version 1.2.1.
No decision is made about a "next" QEMU version at this
time.
Change-Id: Ie9413338a2422cc876f48c5c477eb3cd0ffb13ec
As advertized during Mitaka, increase the min required
libvirt version to 1.2.1.
At this time there is no new "next" version planned.
The need to advertize a version increase for Ocata
will be decided later.
Change-Id: Ib73cfbd9fc01114ac513730d182ed127710a9e5d
This function dates back to I5eee3389c7719d5f361532b0eddaa249233283a5
when it was introduced to make it easier to seamlessly load drivers
from out of tree. This no long is something we want to do. Also, the
way this works it means that it makes it really hard to debug when an
import of a driver fails (as it's masked out).
This is the only use of the function in all of OpenStack, it should
just go away as an anti-pattern.
Tests were updated to pass, and the compute_driver flag was removed
from tests that passed even when they now had completely bogus values.
Change-Id: I65a537292aa8eda9f3d89e408caa50c445f2050a
Add a nova manage command to insert a cell mapping for cell0.
nova-manage cell_v2 map_cell0
blueprint cells-cell0
Change-Id: Ia000e970d66d75374fd7e4e8b9137e0c10939c8e
A new global option to handle input devices has
been introduced. The specifc option use_usb_tablet in the
group libvirt has been depecreated for Newton and should be
removed for O*
Related-To: blueprint virt-configure-usb-tablet-from-image
Change-Id: I51186530a94d86c8ed14783c7d42d0a3bd601f59
