beaker-project / beaker-in-a-box Goto Github PK

At this moment beaker-box defining PXE boot settings in libvirt network.
It would be better if we can move this to master for example. It will be easier for users to change configuration, reload it and try new things. For example, start using UEFI instead of pxelinux.0

Beaker Ansible playbooks should use virt ansible module[0] instead of running commands for virt-* execution.

[0] https://docs.ansible.com/ansible/latest/modules/virt_module.html

At this moment roles are depending on each other and steps performed in the machine before.

This may suit a small deployment, but in case that someone will try to create Server - Lab Controller combination this will be a headache. It would be great if we can reorganize roles.

I was thinking about the following roles:

• Server
• Lab Controller
• Archive
• Database

In our playbook, we would still run it in a single node, but we will allow users to deploy them on multiple VMs.

Firefox version included in 7.7 is not working properly.
We should downgrade Firefox in play.

At this moment we are providing 2 times of playbooks.
One is called setup_beaker and the second one setup_sandbox.

Setup_beaker is focused more on the full experience of beaker and setup_sandbox is more suitable for developers. Right now setup_beaker is working fine, however, due to changes for setup_beaker we broke setup_sandbox. This needs to be addressed.

At this moment we are importing F29 and F30. Make it better.

I had to install the following RPMS in order to run the Server/run-tests.sh script in the develop branch.

# yum install python2-mock python-pwquality python2-qpid-proton