6f0da8a5be
The validation is intended mostly for tests and don't make much sense
when running the migration in production because likely there are
already running workloads. This patch changes the default to False so
migration validation must be explicitly asked for.
Change-Id: I5470f61a5e0b55bf682526208c3f57dc0ca6ffd5
Signed-off-by: Jakub Libosvar <libosvar@redhat.com>
(cherry picked from commit 0baf8841ee)
13 lines
685 B
YAML
13 lines
685 B
YAML
---
|
|
other:
|
|
- |
|
|
The OVN migration performs validation by default. This validation means an
|
|
instance is spawned and is tested by simple ping after the migration is
|
|
finished. Also it tries to create new workload post migration. This is
|
|
useful for very simple scenarios when migration is tested but is not
|
|
really useful in production since likely the production envrionments
|
|
already have running workloads. It makes more sense to require the
|
|
validation explicitly rather than implicitly run it as the migration
|
|
is mostly intended for production. The VALIDATE_MIGRATION now defaults to
|
|
False and needs to be changed to True if validation upon request.
|