This task is for setting up monitoring for netapp that is used for data domains in MTV testing.
It allows consistent metric information on read rates from the luns in addition to understanding if other netapp volumes are in use, and how busy they are.
NAbox is supplied as qcow2 and has already been setup by Tzahi as a POC in our single vmware/esx environment.
This task is for setting up the nabox in our rhev-engine infra environment in order for it to be located in the same hosts as our other infra services.

The rhev/ovirt vm should use: 02:6E:57:A9:F4:1E / rhev-node-02.rdu2.scalelab.redhat.com

There are two options for doing this: migrating the vm from esx to ovirt, OR importing the qcow2 file directly.
Instructions for importing the qcow2 can be found here:
 

download nabox to the client your using ex: vm in rhev-engine-infra env (like: snowball or snowball avoid using rhev-gw)
source:  https://dl.nabox.org/nabox/NAbox-4.0.10.qcow2
 
Execute:
dnf install ovirt-imageio-client python3-ovirt-engine-sdk4 And upload the image: python3 /usr/share/doc/python3-ovirt-engine-sdk4/examples/upload_disk.py \ --engine-url https://rhev-engine-infra.rdu2.scalelab.redhat.com \ --username admin@internal \ --password-file /path/to/password/file \ --cafile /path/to/cafile \ --sd-name my-storage-domain \ --disk-sparse \ /path/to/nabox.qcow2
 
copy ca file from rhev-engine / f01-h11 host
 
After the qcow is imported and nabox is setup with users,  please share the admin creds with the vme+ team and a guest or read only user that we can share outside the immediate team.