How kalel-ifpb/projeto-devops-com-vagrant-e-ansible works
This repository defines an IaC workflow for creating and configuring four Debian VMs. The documented entry point is vagrant up: Vagrant manages the VirtualBox machines, and Ansible provisions them in order, beginning with the file server that supplies DHCP and DNS. The graph preserves the documented ARQ, DB, APP, and CLI roles. Source excerpts were unavailable, so relationships are limited to those stated in the README; the Ansible inventory and configuration files are shown without inferred connections.
Main entry points: playbook.yml Provisioning playbook · Vagrantfile Vagrant orchestration
Components 11
Provisioning
- Vagrant orchestration
Vagrantfile - Ansible settings
ansible/ansible.cfg - VM inventory
ansible/inventory.yml - Provisioning playbook
ansible/playbook.yml - Host DNS configuration
Network and Storage
- ARQ file server
ansible/playbook.yml
Application Services
- DB database server
ansible/playbook.yml - APP web server
ansible/playbook.yml
Client
- CLI test client
ansible/playbook.yml
Other components
- Operator
- VirtualBox
Connections 8
- Operator → Vagrant orchestration: runs up
README.md - Vagrant orchestration → VirtualBox: manages VMs
README.md - Vagrant orchestration → Provisioning playbook: provisions in order
README.md - Provisioning playbook → ARQ file server: configures first
README.md - Provisioning playbook → DB database server: configures second
README.md - Provisioning playbook → APP web server: configures third
README.md - Provisioning playbook → CLI test client: configures fourth
README.md - Operator → Host DNS configuration: sets DNS
README.md