Deploying IoT Controller on Proxmox Virtual Environment

Deploying the RUCKUS IoT Controller on Proxmox Virtual Environment (VE) provides a cost-effective and scalable virtualization solution. As an open-source platform, Proxmox VE offers a user-friendly interface, support for multiple disk formats, and efficient performance for both small and large deployments.

To deploy IoT Controller on a Proxmox VE, follow these steps:

  1. Log in to Proxmox VE and click OK to skip the No valid subscription.
  2. Click Create VM.

    The Create Virtual Machine window opens

    .

    Creating a Virtual Machine

    Creating a Virtual Machine
  3. Optionally, in the General tab, you can configure these options:
    1. VM ID: Proxmox assigns VM IDs starting from 100, with each new VM receiving the next sequential ID. You can modify this number, but RUCKUS recommends using the default value.
    2. Name: Enter a descriptive host name.
    3. Resource Pool: Select a resource pool using the drop-down menu.
    4. Click Next.

    Configuring a Virtual Machine

    Configuring a Virtual Machine
  4. In the OS tab, select Do not use any media and click Next.

    Configuring OS Settings

    Configuring OS options
  5. In the System tab, keep the default settings and click Next.

    Configuring System Settings

    Configuring System Options
  6. In the Disks tab, delete the default disk on the left side of the window and click Next.

    Configuring Disks Settings

  7. In the CPU tab, configure these options:
    1. In the Sockets drop-down menu, select 1.
    2. In the Cores drop-down menu, select 4.
    3. In the Type drop-down menu, select kvm64.
    4. Click Next.
  8. Note: You can adjust the number of CPU sockets and cores based on deployment requirements and the available hypervisor capacity. For more information, refer to System Requirements for Installing RUCKUS IoT Controller on a Hypervisor.

    Configuring CPU Settings

    Configuring CPU Settings
  9. In the Memory tab, go to Memory (MiB) drop-down menu, select 4096 as the required memory and Next.
  10. Configuring Memory Settings

    Configuring Memory Settings
  11. In the Network tab, configure these options:
    1. In the Bridge drop-down menu, select the bridge.
    2. In the Model drop-down menu, select VirtIO (paravirtualized).
    3. Click Next.

      Configuring a Network

      Configuring a Network
  12. In the Confirm tab, review the settings that you configured and click Finish.
    Important: Do not check the Start after created checkbox. You should verify the configuration, make any necessary changes, and click Finish.

    Reviewing the Settings

    Reviewing the Settings
  13. Download and unzip the QCOW2 file from https://support.ruckuswireless.com/.
  14. Log in through SSH or use the terminal on Web UI to operate on the command line of the root account.
    Optionally, you can create a temporary directory and place the image in it. For example:
    /root/ovafiles
  15. Download and place the QCOW2 image into the Proxmox Hypervisor. Use the following command to import the disk image into the virtual machine:
    Syntax:
    qm importdisk <VM ID> <qcow2 image> <storage name>
    Example :
    qm importdisk 101 /root/ovafiles/vriot-3.2.0.0.3.qcow2 local-lvm

    QCOW2 Image

    QCOW2 Image

  16. To add the imported disk to the VM configuration, run the following command:
    root@ruckus:~/ovafiles#
    root@ruckus:~/ovafiles#
    root@ruckus:~/ovafiles# qm set 101 --virtio0 local-lvm:vm-101-disk-1
    update VM 101: -virtio0 local-lvm:vm-101-disk-1
    root@ruckus:~/ovafiles#
    root@ruckus:~/ovafiles#
  17. To change the boot order of the virtual machine (VM), run the following command:
    root@ruckus:~/ovafiles#
    root@ruckus:~/ovafiles# qm set 101 --boot order=virtio0
    update VM 101: -boot order=virtio0
    root@ruckus:~/ovafiles#
  18. From the web page, select the VM, click Start, and select Console.

    Deploying the IoT controller on Proxmox VE

    Deploying the IoT controller on Proxmox VE

The RUCKUS IoT Controller boots as a virtual machine on Proxmox VE and is ready for use.