V2 code is gone , there is no need to talk about this
in our document any more.
Partially implements blueprint remove-legacy-v2-api-code
Change-Id: Ibca00e3e862c1487f0a440fdcc7d11d09026c7a8
The last caller of this was removed in
Ieb8374bff81b26c680cae6e6ca92ab736209570d but this was left behind.
Partially implements blueprint remove-legacy-v2-api-code
Change-Id: Ibcf826e081d061cc6a9b963981edd16d31e0cc37
to track result of conductor actions
wrap_instance_event decorator is moved to
compute_utils and is added to migrate_server
method on conductor.manager
bp: async-live-migration-rest-check
Change-Id: I01e6ba9c9d8df8690d2cecea2cc48e45cf7a53c4
This removes the support for legacy v2 extensions which were allowed
to be generators to have a pre / post processing phase. The modern
compute api stack never supported this construct.
Because of the remove of the 'pre' phase, the 'post_process' phase is
just renamed to 'process'.
All pre_process and generator tests are removed.
Change-Id: Ia34c1f814fb938915d74c6845dfa5135cba29d0a
Removes the test class that tested the "periodic update resource"
functionality in test_resource_tracker.py. This wasn't testing any code
paths that were not already being tested by test_tracker.py's
TestUpdateComputeNode and TestUpdateAvailableResource test case classes.
Change-Id: Ie7c565ebb39c4644a304f53a73853d6ca51b1334
Improve api samples for os-instance_usage_audit_log
and fix a parameter.
Change-Id: I8436a6ab0610e41d8c6c95c55a263fdfbbf58476
Implements: blueprint api-ref-in-rst
A new versioned notification is emitted from the wrap_exception
decorator.
Change-Id: I8fcbce111537dae6ad3ba0961fb761540ae800ed
Partially-Implements: bp versioned-notification-transformation-newton
Gives the opportunity to set the pointer type from image properties.
Implements: blueprint virt-configure-usb-tablet-from-image
Change-Id: I11d3e031c202c39258263212401a0f035ec67d88
If we're explicitly told to not allocate networks, then
don't, skip network allocation.
This also skips network deallocation if we can tell that
we wouldn't have allocated networks because 'none' was
requested for networking. Note, however, that this is just
an optimization when requested_networks is available - which
is not the case with a local delete from the compute API.
Even if we didn't check in the deallocate case it would be fine
since deallocate_for_instance in nova-network and neutron
network APIs won't find any resources to delete since none
were allocated to begin with. But at least we can try to save
ourselves some RPC/DB (nova-network) and REST API (neutron)
traffic.
Part of blueprint get-me-a-network
Change-Id: Ia0d5189453df825805dab028cc81de7dfa0d6c84
Move the version test of the notification objects to a separate
test case to avoid mixing normal and notification ovos.
Change-Id: I997235020f28adadaa2e8772ec888e2f1bf7f3ef
Partially-Implements: bp versioned-notification-transformation-newton
jichenjc