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
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 ``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
The ability to load the scheduler_host_manager from a random
classpath was deprecated in Mitaka. This removes that ability
so that only the entrypoints in Nova's setup.cfg can be used
to load the scheduler host manager.
The scheduler_host_manager config option is updated to only
allow the choices that are currently in the setup.cfg.
And a release note is added for the upgrade impact of dropping
the deprecated classpath loading ability.
Change-Id: I886c74afac02d100d472b78522e8295748276e4d
Related-Bug: #1403020
The novaclient already has the following service commands:
service-disable Disable the service.
service-enable Enable the service.
service-list Show a list of all running services.
host-describe Describe a specific host
This covers what the serivce subcommand of nova-manage provides.
Therefore the service subcommand was deprecated in 13.0 and now
it is removed.
Implements: bp remove-service-management-from-nova-manage
Change-Id: If61875ec78e0e8cd78ea915d8da7362f502d4ca7
In a time long ago and a land far far away, someone thought it was a
good idea to populate the database with default flavors. That was
probably reasonable at the time, but it no longer makes sense and
in fact causes us some pain now.
This patch removes those default flavors from the database. That means
that new deploys will not have them, but doesn't actually rewrite
history in any way.
This will require changes to our docs, which largely assume the presence
of these default flavors from time zero.
DocImpact
Depends-On: Ic275887e97221d9ce5ce6f12cdcfb5ac94e300b0
Change-Id: I80b63ce1ebca01be61ac0f43d26a2992ecf16678
oslo.config provides parameter choices for class cfg.StrOpt to
make sure user's input must be in the choices. Option
notify_on_state_change only allow three values, so let's use
parameter choices.
UpgradeImpact: option notify_on_state_change allows three values:
'vm_state', 'vm_and_task_state', None, default value is None.
Change-Id: I94b2a8ab2584a4a31ef9644ad4f614a15636de8d
This makes Flavor.create() fail until the main database has had all
of its flavors migrated. Since we want to avoid any overlap or clashes
in integer ids we need to enforce this. The flavor API was poorly
designed in that it exposes this internal id. Luckily, flavor creation
is infrequent and flavor migration is fast.
The flavors in our database are hard-coded in the first migration,
which means we have to basically do the migration during every
unit test in order to avoid having a legacy environment. Since that
leaves us with deleted flavors in the DB (which screws up the DB
archiving tests), this adds a hard_delete flag to the migration to
do an actual purge of those from our database. What a mess.
Related to blueprint flavor-cell-api
Depends-On: I8ab03af9d2f4974f26a7f8487ec978caea957e45
Change-Id: Iea063448f43da1043d16dd521d255dd29a0e1bc5
If proxy service (VNC, spice, serial) is started with the 'record'
option, an exception is thrown. This is because WebSocketProxy
expects a file path for the record argument instead of boolean
value. This patch fixes this by changing 'record' to be string
option. An empty string means no recording.
Closes-Bug: #1559026
Change-Id: Id6cf7c65191bdaa579f7cdadea43230897436de6
The option to enable (and thus possibly disable) v2.1 was deprecated
in Mitaka. It should now be removed. v2.1 is a required part of the
API and it was default on.
Change-Id: Ia446040e3b4e87438712e7d8c1bafda0a6e53999
This removes the very old glance config options which were deprecated
in I9054bcfb7f5a4a31f0bbfd770c00c767f3d165ba in favor of
glance.api_servers config option. This is required to clear out any
default glance servers so that we could pull from the service catalog
as a default in the future.
Change-Id: Ie2d767c4422ef339d6dcb826f3c8ba3c7cf79f85
Now that the WSGI opts have been added to a group, there's no longer
any reason to keep the 'wsgi_' prefix for some of these opts around.
Remove it, ensuring the old names are stored as deprecated names.
Change-Id: If39bed3ed2335b6f96455870f1a47cb868d21f39
In somes cases we need to have network without any security rules
applied, unfortunatly nova does not provide way to remove l3
assignements and always at least expose the default security group.
This commit updates code to clear security groups applied to the
network when option port_security_enabled=False is activated on the
network.
Change-Id: I630008a9733624a9d9b59b7aa3b8b2a3f8985d61
Closes-Bug: #1460630
Related-Bug: #1175464
