How eamartin96/ansible works
Main Components
• Ansible Control Node: This is the local (or designated) machine where Ansible is installed and configured. It uses the ansible.cfg and inventory.yml files to know about the target hosts.
• Docker Engine & Docker Compose: These are responsible for building and running the Docker containers. The build_images.sh script and docker-compose.yml file orchestrate container creation.
• Docker Images and Containers: Under the Docker directory, two Dockerfiles (one for Debian, one for Ubuntu) are used to build images. The containers are then the cluster nodes where the playbooks (found in the playbooks folder such as apache.yml, docker.yml, mysql.yml, users.yml) run.
• SSH Keys: The generate_keys.sh script indicates that secure (SSH) access is a fundamental part of how Ansible will connect to these containers.
Architectural Patterns & Key Technologies
• The project follows a separation of concerns typical for a full-stack or distributed system simulation: The control plane (Ansible) is clearly separated from the data plane (the containerized virtual nodes).
• The use of Docker Compose indicates that the containers are managed as a single multi-container application.
• SSH-based communication from Ansible to each container emphasizes a secure remote management pattern.
• Ansible’s modular playbooks demonstrate a layered/role-based configuration style.
• Use clear labels for each of the following components:
• Ansible Control Node (with ansible.cfg, inventory.yml, and playbooks)
• Docker Engine / Docker Compose layer
• Docker images (Debian-based and Ubuntu-based images indicated by the Docker folder files)
• Containerized nodes (each representing a virtual machine in the cluster)
• From the build scripts (build_images.sh) and SSH keys (generate_keys.sh) to their respective roles in setting up the environment.