- Placeholder -
-- Complete guide for creating, publishing, and managing VM templates in Kamino through Proxmox integration -
-- Pools in Proxmox help organize and manage related VMs. All template VMs must be placed in a designated pool with the correct naming convention. -
-kamino_template_[template_name]kamino_template_test_linux → Template name will be “Test Linux”- Each template requires its own isolated network to prevent conflicts and ensure proper network segmentation. -
-VNet creation interface in Proxmox SDN
-VNet configuration dialog
-Applying SDN configuration changes
-- Set up all VMs within the created pool with your desired operating systems and configurations. Follow the specific steps below for different OS types. -
- - {/* ISO Upload */} -- Upload the necessary ISO files to your mufasa-proxmox. -
-Uploading ISO files to Proxmox storage
-- Follow these steps to create a Linux-based virtual machine. Ensure you select the appropriate settings for optimal performance. -
-Creating a new Linux VM from ISO
-General VM settings and pool assignment
-Operating system selection and configuration
-Disk configuration and storage allocation
-Network configuration with the template VNet
-- Windows VMs require specific drivers and configurations for optimal performance in a virtualized environment. Pay attention to driver selection and hardware compatibility. -
-Windows OS type selection
-Loading VirtIO drivers during installation
-Architecture and system type selection
-VirtIO driver configuration for optimal performance
-- Before converting VMs to templates, proper cleanup and optimization ensures better performance and smaller template sizes. -
-- Once your VMs are properly configured and prepared, use the Kamino admin panel to convert them into deployable templates. This process will convert the VMs to Proxmox templates and make them available for users to deploy. -
- -- In the Kamino admin panel, go to{' '} - - Publish Templates - -
-- Choose the Proxmox pool containing the VMs you wish to publish as a template from the dropdown selection. The template name will be auto-generated from the pool name. -
-- Provide a detailed description or steps to complete this template. This field supports markdown formatting. -
-
- {markdownExampleText}
-
- - Specify the authors or creators of the template (max 255 characters). For example if you are part of a club you could put the club name with your name as the author. EX (SWIFT, Maxwell Caron) -
-- Specify how many VMs the template contains (1-12) -
-- Optionally upload an image to represent the template visually (max 10MB). You will be able to crop your image upon upload. -
-Crop pod template image
-- View an exact preview of what your template will look like to users once published. You will be able to view both the small card view and the detailed view. -
-Small pod template preview
-Large popup pod template preview
-- The final step is to choose whether the template should be publicly visible to all users or kept private when published. This can be changed later in the template management section. -
-- Comprehensive guide for managing users and groups through Active Directory with automated Proxmox synchronization -
-- Users are created, modified, and removed through the Users Kamino admin panel page. All changes are synchronized with Active Directory and Proxmox to ensure consistent access control. -
-Usernames
-Passwords
-- Groups are created, modified, and removed through the Groups Kamino admin panel page. All changes are synchronized with Active Directory and Proxmox to ensure consistent access control. - Admins can use groups if they want to clone a single pod for multiple users to interact with. For example, if a competition were to be held, an admin could create a group for each team, clone a pod for each group, and add users to the appropriate groups instead of making a user for each team. -
-Group Names
-