Closed CodyChengIOL closed 1 week ago
Note: Currently, I am testing using this Ansible playbook to setup the nodes and I am running to an issue where it seems like the network interfaces are being created in the Anaconda environment but then when it exits that Anaconda environment, they revert back to the original interfaces.
@CodyChengIOL Your second patch, labeled Cleanup, is missing the Signed-off-by: portion of the commit message and can't be merged without it. You can force push an update to the branch with the sign off added to that commit.
Update: This Ansible playbook works now by using beaker snippets to setup a systemd service which will run the Ansible playbook once on the first boot after the installation and setup.
This is now able to run the Ansible Playbook during the Beaker post installation stage using the system_post kickstart in this PR: https://github.com/OpenFabrics/fsdp_beaker_snippets/pull/27
This is the Ansible version of the fsdp_setup shell scripts and so each task file is named directly after each function in the rdma_functions.sh script.
The setup_host.yml playbook is the main file that is used to run every tasks necessary to setup the nodes. The setup_host.yml playbook runs the roles common, interfaces, dhcp, and nfs in the order that was listed. Each of these roles have a main.yml which runs the tasks that relate to that role's purpose. The common role runs tasks that edits configuration files, setup ssh, etc. The interfaces role creates the interfaces, and creates the Network Manager dispatcher scripts that go along with the interfaces. The dhcp role creates the dhcp client files and uploads them to builder-00.
I have left comments throughout some of the files about any questions I have.
Signed-off-by: Cody Cheng ccheng@iol.unh.edu