Create Jetlag roles documentation

[agurenko]

All roles added to Jetlag should have documentation with at least minimal variables description, flow and results.

I suggest we start with roles from the setup-bastion, hv-setup, hv-vm-create, hv-vm-delete, sno-deploy, mno-deploy.

Respective Issues/PR can be created

/label Documentation

[openshift-ci]

@agurenko: The label(s) /label Documentation cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, ux-approved, no-qe, rebase/manual, cluster-config-api-changed, run-integration-tests, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, jira/valid-bug, ok-to-test, stability-fix-approved, staff-eng-approved. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

Details

In response to this:

All roles added to Jetlag should have documentation with at least minimal variables description, flow and results.

I suggest we start with roles from the setup-bastion, hv-setup, hv-vm-create, hv-vm-delete, sno-deploy, mno-deploy.

Respective Issues/PR can be created

/label Documentation

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.