Skip to content

Commit bde5995

Browse files
Zuulopenstack-gerrit
authored andcommitted
Merge "libvirt: Deprecate live_migration_tunnelled"
2 parents f55f5da + 14071df commit bde5995

File tree

2 files changed

+25
-0
lines changed

2 files changed

+25
-0
lines changed

nova/conf/libvirt.py

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -285,6 +285,15 @@
285285
"""),
286286
cfg.BoolOpt('live_migration_tunnelled',
287287
default=False,
288+
deprecated_for_removal=True,
289+
deprecated_since='23.0.0',
290+
deprecated_reason="""
291+
The "tunnelled live migration" has two inherent limitations: it cannot
292+
handle live migration of disks in a non-shared storage setup; and it has
293+
a huge performance cost. Both these problems are solved by
294+
``live_migration_with_native_tls`` (requires a pre-configured TLS
295+
environment), which is the recommended approach for securing all live
296+
migration streams.""",
288297
help="""
289298
Enable tunnelled migration.
290299
Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
---
2+
deprecations:
3+
- |
4+
The ``[libvirt]live_migration_tunnelled`` option is deprecated as of
5+
Wallaby (23.0.0) release.
6+
7+
The "tunnelled live migration" has two inherent limitations: (a) it
8+
cannot handle live migration of disks in a non-shared storage setup,
9+
and (b) it has a huge performance overhead and latency, because it
10+
burns more CPU and memory during live migration.
11+
12+
Both these problems are addressed by the QEMU-native support in Nova
13+
-- this is the recommended approach for securing all live migration
14+
streams (guest RAM, device state, and disks). Assuming TLS
15+
environment is setup, this can be enabled by setting the config
16+
attribiute ``[libvirt]live_migration_with_native_tls``.

0 commit comments

Comments
 (0)