This project provides the bits to setup a developer environment based on ManageIQ documentation.

This repository provides two playbooks:

• manageiq_create_vm.yml
• manageiq_install.yml

The first one builds a virtual machine and runs the second playbook on it:

• Create the virtual machine in oVirt/RHV,
• Add it to the Ansible in-memory inventory,
• Install git and ansible packages,
• Clone the current git repository,
• Generate the inventory on the virtual machine,
• Launch the manageiq_install.yml playbook.

The second one does the actual deployment and can be used autonomously:

• Install the YUM repositories,
• Install dependencies,
• Configure the database and logs disks,
• Clone the ManageIQ and Patrick Riley's repositories
• Bootstrap the ManageIQ setup
• Start ManageIQ

If you want to build from scratch, run the manageiq_create_vm.yml playbook, passing your config file, preferably encrypted by ansible-vault:

$ ansible-playbook manageiq_create_vm.yml \
    -i localhost,
    -e @config/manageiq_vm.yml \
    -e @config/ovirt_auth.yml \
    --ask-vault-pass

If you already have a CentOS 7 or RHEL 7 VM, you can run manageiq_install.yml playbook from that VM, after setting the inventory (name it inventory.yml).

# ansible-playbook manageiq_install.yml

If you take a look at the playbooks, the main prerequisite is a virtual machine running CentOS 7 or RHEL 7. Currently, only CentOS 7 has been tested.

To use the playbook that creates the VM, you will need a VM template in your oVirt / RHV4 environment. This template will have to support cloud-init. Here is a small how-to, based on a CentOS 7 minimal install.

First, let's install some commonly used packages.

# yum -y install vim-enhanced screen bash-completion yum-utils

Then, we install the oVirt agent for a better integration.

# yum -y install centos-release-ovirt42
# yum -y install ovirt-guest-agent-common
# systemctl enable --now ovirt-guest-agent.service

Now, we install cloud-init.

# yum -y install cloud-init

Due to a race condition in dbus startup and cloud-init, all operations using hostnamectl as a backend fail. To workaround this, we move them to a later stage.

# sed -i \
    -e "/set_hostname/d" \
    -e "/update_hostname/d" \
    -e "/^cloud_config_modules:/a \ - set_hostname\n - update_hostname" \
    /etc/cloud/cloud.cfg

Finally, we seal the VM and shut it down.

# yum clean all
# rm -rf /var/cache/yum/
# for i in /etc/sysconfig/network-scripts/ifcfg-eth* ; do
    sed -i -e '/^UUID=/d' -e '/^ONBOOT=/s/=.*$/=yes/' ${i}
done
# rm -f /etc/ssh/ssh_host_*
# echo > ~/.bash_history
# history -c
# halt -p

The manageiq_create_vm.yml allows a few variables to be passed. Some of them are passwords, so you may want to use vault files to store them. Personally, I use three configuration based on the following example files.

config/manageiq_vm.example.yml

config/ovirt_auth.example.yml

config/rhel_custom_repos.example.yml There's only one variable rhel_custom_repos, so take a look at the example.

The playbook that creates the VM generates the inventory and sets default variables. However, it is possible to override these defaults, when running the manageiq_install.yml playbook on a virtual machine deployed separately. The inventory.example.yml file shows the options one can set.

Apart from the disks, you shouldn't have to set these options.

As we're deploying from source, we don't have a systemd service to handle ManageIQ. So, we have to manually start and stop the service:

$ cd /home/miq/manageiq
$ bundle exec rake evm:start

$ cd /home/miq/manageiq
$ bundle exec rake evm:stop