User should be able to not specify rpm nor repo of ovirt

rhevm-qe-automation / ovirt-ansible

Ansible playbooks for ovirt management

GNU General Public License v3.0

26 stars 28 forks source link

User should be able to not specify rpm nor repo of ovirt #92

Open StLuke opened 7 years ago

StLuke commented 7 years ago

User should be able to not specify rpm nor repo of ovirt and rather do it manually with his custom repositories

lukas-bednar commented 7 years ago

could you please elaborate on more details? thank you!

StLuke commented 7 years ago

Have preinstalled machine with correct repositories I want to use and install engine on it.

lukas-bednar commented 7 years ago

you can still do it with current status of repo. just omit 'ovirt-common' role from your playbook.

StLuke commented 7 years ago

:) I would love to have that though withough remembering it

name: install libselinux-python for ansible yum: name: libselinux-python state: "present"

lukas-bednar commented 7 years ago

hm, I don't know what to do with it, since ...

If you have SELinux enabled on remote nodes, you will also want to install libselinux-python on them before using any copy/file/template related functions in Ansible. You can of course still use the yum module in Ansible to install this package on remote systems that do not have it.

it looks like the role itself should be responsible for installation of this package when it is using above mentioned modules ... ok then you can not skip ovirt-common role ...

lukas-bednar commented 7 years ago

we can consider it as part of #83

KKoukiou commented 6 years ago

@StLuke is this still relevant?