-
Notifications
You must be signed in to change notification settings - Fork 898
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding classifications for V2V #17000
Adding classifications for V2V #17000
Conversation
@miq-bot add_label transformation |
db/fixtures/classifications.yml
Outdated
:syntax: string | ||
:show: true | ||
:name: v2v_transformation_host | ||
:example_text: The fact that the Transformation Host role is enabled for V2V. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggest: Transformation Host role enabled for V2V.
db/fixtures/classifications.yml
Outdated
:syntax: string | ||
:show: true | ||
:name: v2v_transformation_method | ||
:example_text: The transformation methods supported for V2V. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggest: Transformation methods supported for V2V.
@fdupont-redhat Please squash this PR down to a single commit. There is no reason to retain to separate commits in this case. |
362400b
to
178a2d8
Compare
Checked commit fabiendupont@178a2d8 with ruby 2.3.3, rubocop 0.52.0, haml-lint 0.20.0, and yamllint 1.10.0 |
…_tags Adding classifications for V2V (cherry picked from commit 69ca707)
Gaprindashvili backport details:
|
When transforming a VM from on provider to another, we configure some machines as transformation hosts. This consists in installing some mandatory packages, such as virt-v2v, nbdkit-plugin-vddk, etc..., as well as creating some filesystem tree where the transformation temporary files will be stored. This is done using Ansible playbooks and on enablement / disablement, we set tags on the transformation hosts.
Currently, we use two tags:
v2v_transformation_host
that is a boolean to identify the machine as a transformation hostv2v_transformation_method
that is a multi-value tag to store the available transformation methods on this host, i.e. the ones deployed via the playbook.