Repository navigation
Migrate to KVM - #160
Merged
Merged
Migrate to KVM#160
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces a comprehensive Ansible-based solution for provisioning and managing bare-metal KVM virtual machines (VMs) for SKALE node deployment. It adds new playbooks, roles, and documentation to automate VM lifecycle management (creation, configuration, and destruction), making it possible to run node infrastructure on self-hosted servers as an alternative to cloud providers.
The most important changes are:
Bare-metal KVM VM provisioning support:
skale-nodes/ansible/vms.yaml) to automate the creation, configuration, and destruction of KVM VMs on user-provided servers, including first-boot handling and cloud-init waits.vmsrole with tasks for planning, SSH key management, host preparation (KVM/libvirt setup), VM creation, and destruction (roles/vms/tasks/*.yaml). This includes checks for KVM availability, network configuration, storage setup, and image downloading. [1] [2] [3] [4] [5] [6]Configuration and customization:
roles/vms/defaults/main.yaml, allowing customization of CPU, RAM, disk sizes, network interfaces, and SSH keys.Integration and documentation:
README.mdwith detailed instructions for using the new bare-metal KVM provisioning features, including inventory setup, playbook usage, and customization tips. [1] [2]base.yamlplaybook to exclude KVM host servers from node provisioning, preventing accidental configuration of the hypervisor as a node.Cloud-init and network configuration:
meta-data.j2,user-data.j2,network-config.j2) to automate VM initialization, static IP assignment, and SSH key setup. [1] [2] [3]These changes provide a robust, flexible foundation for running SKALE node infrastructure on bare-metal servers using KVM virtualization, with full automation for VM lifecycle and configuration.