fusor/ansible-ovirt

Ansible scripts for deploying Ovirt/RHV

Fusor

Our issue tracker is located at http://bugzilla.redhat.com

Fusor API documentation is located here (or here for single-page).

To file bugs or enhancement requests, use https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Quickstart%20Cloud%20Installer (will require an account).

The form will be pre-filled with a template for filing a bug. If you are filing an RFE, an alternative template is provided below.

Request for Enhancement (RFE)

Motivation:

• Why do you want this feature?
• Is it a priority? Why?
• Who needs it (internal, customer, etc)?

Current Behavior:

• If you are proposing a change to an existing feature, where does the existing feature fall short?
• If it is too difficult to use in its current state, where does the difficulty lie?

Desired Behavior:

• If this feature did exist, how would you use it?
• If it has a UI component, how would you like it to be presented to you? How would you like to interact with it?
• If there are multiple options/paths/configurations, which ones are necessary for your use case?

Additional information:

• Relevant product/documentation links
• Caveats
• Contacts
• Communities
• Anything else that may be of use

ansible-ovirt's Issues

Demo environment VMs stuck waiting for IP

When I (cd demo ; vagrant up), most of the time one or more of the VMs will get stuck "Waiting for IP". If I run ip addr inside those VMs, I can see that they got an IP from the ansible_ovirt_demo_net network, but are still waiting for an IP from the vagrant-libvirt network.

Get the default timezone from ansible facts instead of defaulting to EDT

related to PR:
##50

I wonder if there's a good way to get the default timezone from the ansible facts or something rather than defaulting to east

datacenter role fails with oVirt 4.3

The ovirt-engine-sdk-python package which contain the ovirtsdk python module is no more installed by default on oVirt 4.3. This causes to fail the role (datacenter, storage) and the whole deploy process.

For use in oVirt 4+ there is new module ovirtsdk4 which is in the python-ovirt-engine-sdk4 package. This package is installed by default with oVirt.

If the ovirt-engine-sdk-python package (with ovirtsdk) is installed outside the role, the particular tasks run just fine.

Configuration of hosted engine with cloud-config should be done with ansible

All of the configuration happening in roles/self_hosted_first_host/templates/user-data.j2, other than the enabling of SSH and the installation of the engine, should be moved to an ansible role that can be run and be monitored. This would probably require us to pass an SSH key into the user-data for cloud-config, and update the self-hosted playbook to include an additional "hosted_engine" host with related roles.

Move OS checks to separate files

Rather than checking the OS a bunch of times all over the place, should have variable files that are conditionally loaded based on the OS.

i.e.: yum: name= '{{ "ovirt-engine-appliance" if ansible_distribution == "CentOS" else "rhevm-appliance" }}'

would become

include '{{ ansible_distribution }}'
yum: name='{{ appliance_package }}'

where appliance_package is defined in the 'CentOS.yml' variable file