This commit removes commented-out Proxmox credentials variables from the testing.yml file. This resolves an issue where these variables were present, potentially exposing sensitive information during testing. The removal ensures a cleaner and more secure testing environment.
This commit updates the Proxmox credentials within the testing task file. This ensures the testing environment can successfully authenticate with Proxmox, resolving potential connection issues. The change improves the reliability of automated testing.
This commit removes commented-out variable definitions related to Proxmox credentials. These were identified as unnecessary and potentially confusing, improving code readability and reducing clutter. The removal ensures a cleaner and more focused codebase.
This commit updates the virtual machine's IP address to 192.168.2.3/24, resolving an issue with network connectivity during testing. This change ensures proper network access for the testing environment. The change was made to align with the latest network configuration.
This commit updates the playbook's source to utilize ansible-playbook-homelab and incorporates the ansible-role-debian_common role. The changes include updating VM names and adding a new task for deploying the Debian common role, streamlining the automation process.
This commit updates the VM memory allocation specifically for the 'dc' template, resolving an issue where memory was misconfigured. It also removes the outdated 'vm-01' entry, streamlining the configuration and ensuring optimal performance.
This commit updates the Debian and Ubuntu VM templates to utilize smaller disk sizes, optimizing storage space. The changes also incorporate updated configurations for improved performance and compatibility. These adjustments streamline the VM deployment process and enhance overall system efficiency.
This commit updates the URLs for Debian images used as Proxmox templates. The URLs have been corrected to reflect the latest available Debian 13 images, ensuring proper template downloads and configurations within the Proxmox environment.
This commit updates the documentation to reflect the changes in VM configuration, specifically regarding the `vlan` setting. It clarifies the intended usage and potential values for this parameter. This ensures consistency and reduces potential confusion for users.
Corrected the OS type for the proxmox_template_vm_debian_ostype to 'l26' to align with the latest configuration. This ensures consistency and accuracy in the template definitions. The change resolves a potential mismatch between the template and the actual operating system.
This commit updates the documentation to reflect the new configurations for Debian templates, including supported distros, image URLs, and associated settings like storage, memory, cores, and SSH keys. This ensures clarity for users setting up Debian-based templates within Proxmox.
This commit updates the DNS nameservers for two virtual machine templates (vm-01 and vm-02) to 8.8.8.8, resolving potential DNS resolution issues. This change improves network connectivity for the VMs.
This commit changes the default storage type for Ubuntu templates from 'local' to 'local-lvm'. This adjustment aligns with best practices for Ubuntu template deployments, providing a more robust and isolated storage environment for the virtual machine images.
The Ubuntu template's default storage has been changed from 'hdd8t' to 'local' to align with current best practices and simplify deployment. This change ensures the template utilizes local storage, reducing potential configuration complexities. This update improves the overall usability and consistency of the template.
This commit updates the VM templates used during the creation process. Specifically, the 'vm-01' template is changed from 5000 to 9412, and 'vm-02' from 5500 to 9413. These changes likely reflect updated base images or configurations for the virtual machines.
This commit removes a commented-out configuration section for `sshkeys` within the testing task definition. This was likely a temporary setting and is now permanently removed, simplifying the configuration and preventing potential issues.
This commit updates the configuration for the snippets storage, setting it to 'local'. This change ensures that snippets are stored locally, simplifying the deployment process and improving performance. The configuration update is part of a broader effort to streamline the preflight process.
This commit refactors the preflight task to intelligently check if the 'snippets' configuration is already present in the `/etc/pve/storage.cfg` file. It avoids redundant replacement operations and improves the preflight process by determining if the configuration is already set, preventing unnecessary modifications.
This commit updates the PVE storage configuration to ensure the 'snippets' storage is properly enabled. It modifies the `/etc/pve/storage.cfg` file to include the 'snippets' option, resolving potential issues with snippet functionality. The IP address of the network interface has also been updated.
This commit updates the `tasks/testing.yml` file to correctly enable the 'snippets' storage for Proxmox. The change ensures that the snippets storage directory is properly configured, resolving an issue where snippets were not being utilized. This update improves the Proxmox setup process and ensures snippets functionality.
This commit updates the preflight task to correctly enable the 'snippets' storage in /etc/pve/storage.cfg. The change uses a more robust regular expression to handle potential variations in the storage configuration, ensuring the snippets feature is properly activated.
This commit updates the Ansible role for deploying VMs, defining two new VMs with specific configurations including IP addresses, VLAN assignments, and storage options. The changes also incorporate SSH key management from a file.
This commit enables the 'snippets' feature in the Proxmox storage configuration file. It achieves this by adding a snippet line to the storage.cfg, ensuring that Proxmox snippets are available. Additionally, it creates the necessary 'snippets' directory within the specified storage path.
