Technical Prerequisites

Outbound open ports:

Ports for data plane: Volumez needs to have outbound open ports from media to the application nodes, and from application to the media nodes, so that NVMe (port 8009) and/or iSCSI (port 3260) traffic can flow between applications and volumes.

There are no inbound connections required, to work with Volumez.

 Ports for control plane: Volumez needs the outbound standard https port (443) to be open to volumez.com, so that the Volumez connectors can poll for orchestration commands from the Volumez service.

Inbound open ports:

Ports for data plane: Volumez needs to have inbound open ports from media to the application nodes, and from application to the media nodes, so that NVMe (port 8009) and/or iSCSI (port 3260) traffic can flow between applications and volumes. Inbound traffic is needed only locally between the instances inside your VPC.

• For NVMe connectivity, you need to configure the Azure Network security group of the instances with inbound rules to open the Custom TCP port 8009 to the source 172.0.0.0/8.

• For iSCSI, it is also possible to define connectivity by opening the Custom TCP port 3260 to the source 172.0.0.0/8.

  Ports for management: In order to install the Volumez connectors, you need to have ssh access (port 22) to your application and media instances. There is no need for ssh access to the instances after the installation step, except for optionally performing troubleshooting operations.

  Ports for control plane: Volumez does not require any inbound ports for its control operations.

   Here is a sample list Inbound rules in a security group created for Volumez:

  

  
  

  Cloud instances:

  Application Nodes are cloud instances which run your applications. Each has a Volumez connector installed on it.

  Volumez supports all Azure VMs that run a supported operating system and contain NVMe.

  Minimum requirements: 2 vCPU, 8 GB RAM.

  • Azure VM Types:

    • Lasv3, Lsv3, Lsv2 series Azure Virtual Machines for both App and Media nodes.

  Media Nodes are cloud instances that hold raw media (disks that the Volumez service uses to build logical volumes).

  Media Nodes hold the data managed by the Volumez service to serve the Application Node requirements.

  We recommend that you use Media Nodes that have only one SSD media. Having multiple media disks is supported, but media utilization and balancing the workloads across media may not be optimal. In addition, for optimal resiliency, using multiple instances with one disk in each instance is preferred over using fewer instances with multiple disks. Recommended nodes include:

  • Azure: Standard_L8s_v3, Standard_L8as_v3

  After you install a Volumez Connector on a cloud instance, you must assign it to operate as a Media Node.

  Permissions:

  The following actions are required to manage resources by Volumez.

  "Microsoft.Compute/virtualMachines/write", "Microsoft.Compute/virtualMachines/delete", "Microsoft.Compute/virtualMachines/read"

  We use app registration and associate it with a custom role that has permissions for these actions.

  See more details here.

  Setup guide:

  https://github.com/VolumezTech/volumez

  1. Azure VMs: VMs ready for volumes

  2. For Kuberentes check out this section