Modules

While different modules perform different tasks, their interfaces all follow the same pattern as much as possible. For instance, all Hypercore action modules do not support check_mode, most of them can have their state set to either present or absent, and they identify the resource to operate by using the name (or equivalent) parameter.

The API of each module is composed of two parts. The cluster_instance parameter contains the pieces of information that are related to the Hypercore backend that the module is connecting to. All other parameters hold the information related to the resource that we are operating on.

Authentication parameters

Descrcription about instance parameter.

Module reference

• quickstart – Get started with Hypercore
• api – API interaction with Scale Computing HyperCore
• iso – Manage ISO images on HyperCore API
• iso_info – Retrieve ISO images
• node_info – Returns information about the nodes in a cluster.
• remote_cluster_info – Retrieve a list of remote clusters.
• snapshot_schedule – Manage snap schedule to configure the desired schedule of snapshot creation.
• snapshot_schedule_info – Retrieve information about an automated VM snapshot schedule.
• task_wait – Wait for a HyperCore TaskTag to be finished.
• vm – Create, update or delete a VM.
• vm_boot_devices – Manage HyperCore VM’s boot devices
• vm_clone – Handles cloning of the VM
• vm_disk – Manage VM’s disks
• vm_export – Handles export of the virtual machine
• vm_import – Handles import of the virtual machine
• vm_info – Retrieve information about the VMs.
• vm_nic – Handles actions over network interfaces
• vm_nic_info – Returns info about NIC
• vm_node_affinity – Update virtual machine’s node affinity
• vm_params – Manage VM’s parameters
• vm_replication – Handles VM replications
• vm_replication_info – Returns info about replication of a specific VM