Streamline variables and configuration

[maxbyte9p]

There's a lot of variables like 'ipaadmin_password' defined everywhere in the Ansible playbooks. Looks kinda messy and should be made a little prettier pronto.

• Go through each Ansible playbook and look for ugly variable definitions
  • A configuration file could be written to hold these variable definitions
    • Not sure where to put the configuration file though
    • Could be put into ansible-oelabox-management or the root directory
• Run QA tests after changes to catch unexpected behavior and ensure all components are working correctly.

[maxbyte9p]

I want to create some documentation about configuring Oela Box once I streamline this. Will have to determine if the current Ansible vars files are confusing or not.

[maxbyte9p]

This is going to be tough and it may require a redesign of the Ansible playbooks. I remembered the reason why this is so messy. "ansible.builtin.import_playbook" doesn't support including vars files. It only supports defining vars.

I want to make some kind of global config file that makes configuration super easy and allows more flexibility. This is made difficult due to the current design. I'm gonna be honest the way Ansible playbooks are handled right now is super hacky. A lot of code is duplicated. If I redesign the playbooks I may have to change some documentation as well.

[maxbyte9p]

I've got a new directory tree scoped out for the playbooks. Documentation may have to be rewritten. We'll see how this goes.

[maxbyte9p]

Doing tests on the new directory tree structure for the DNS and IPA server now.

[maxbyte9p]

I've got the DNS and IPA server playbooks working correctly. Koji playbooks still need to be tested thoroughly.

[maxbyte9p]

The new directory tree allows greater flexibility with provisioning playbooks. The new tree is also a lot more organized and easy tread through.

[maxbyte9p]

The Koji playbooks seem to be working correctly. Koji appears to have been provisioned correctly. A test build of Bash from the OpenELA Main SCM has also passed.

Will begin to do QA testing in a Rocky 9.3 Minimal virtual machine. Will also create a new GitHub issue reminding me to update documentation to reflect the changes.

[maxbyte9p]

I'm running another QA test for the new directory tree. Hopefully this test will pass and I can begin switching over to the new tree for the GitHub repo.

[maxbyte9p]

First phase of QA testing passed. Second phase of QA testing is now being ran. A test build of bash from the OpenELA SCM as been initiated in Koji to verify if Koji is ready for package builds.

[maxbyte9p]

Second phase of QA testing passed. Closing issue.