How dinhocamp/automation works
Project's Main Components
• Deployment Orchestrator and Automation Engine:
– This is primarily driven by Ansible (see files like ansible.cfg, ansible_installation.sh, ansible_modules.yml, and various *.yml playbooks).
– It is responsible for executing automation tasks such as VM creation (create_vm.sh, launch_vm.yml), configuration management (passwd.yml, ip_config.yml), and SSH connection management (ESXI_ssh_config.sh, ssh_config.yml, ssh.sh).
• Virtualization and Provisioning Modules:
– There are scripts specific for interacting with ESXi (e.g., check_ESXi_resources.sh, esxi_verif.sh) as well as for OpenStack (check_openstack_installation.yml, extract_openstack_conf.sh).
– The “test-openstack” directory contains playbooks and tests (create_openStack_vm.yml, create_tenant.yml, deploy.yml, test.sh) suggesting a dedicated module for OpenStack deployments.
• Custom ISO Installer Component:
– The “custom_iso_installers” directory contains files (config.cfg, grub.cfg, user-data, etc.) needed to generate or modify ISO images – a key part of provisioning.
– Additional preparatory scripts (prepare_iso_desktop.sh, prepare_iso_server.sh, prepare_iso_files.sh) hint toward specialized roles for building custom installer images.
• Utility and Verification Scripts:
– Scripts like ip_check.sh, check_openstack_installation.yml, and ssh_key_verification.yml serve as checks or supportive utilities.
– “dump.txt”, “result.txt”, “error.txt” indicate logging or result capturing.
Establish Component Relationships and Interactions
• The automation engine (Ansible-based) functions as the central controller that triggers various playbooks and scripts.
• It interfaces with both the ESXi and OpenStack environments:
– Through respective verification scripts and configuration files, it checks for availability, resources, and connectivity.
• Custom ISO installers feed into the provisioning process, creating images that are then deployed via the automation engine.
• Utility scripts and configuration files support and validate the connections (e.g., SSH configuration, IP checking) ensuring that the resources are in sync before and after deployment.
Incorporate Architectural Patterns and Design Principles
• Separation of concerns is evident: each component (deployment, testing, custom ISO creation, resource checking) is organized within its own file or folder, suggesting a modular approach.
• The usage of Ansible implies a declarative configuration pattern.
• Integration of testing (under test-openstack) demonstrates a commitment to ensuring reproducibility and reliability throughout automated deployments.
Notable Technologies and Frameworks
• Ansible: for task orchestration and configuration management.
• Shell Scripting: for direct system operations and utility tasks.
• Virtualization Technologies: ESXi and OpenStack are the target environments.
• ISO Customization: Tools/scripts to build customized boot/install images.