Requirements

Virtual Machine

Important

These ranges are reserved respectively for ARTESCA pods and services:

  • 10.233.0.0/16:

  • is the range of IP addresses allocated to the pods network;

  • is the network used by ARTESCA components;

  • has inter nodes traffic;

  • stays only in the ARTESCA cluster.

  • 10.96.0.0/12:

  • is the range of IP addresses allocated to the service network;

  • is the network for service IPs that facilitates communication between different services within a Kubernetes cluster where ARTESCA is deployed.

  • has no inter nodes traffic.

The pods network has to communicate with the service network. These communications are handled by iptables that redirects the 10.96.0.0/12 IPs to the right 10.233.0.0/16 IPs.

They are used for internal communication between the ARTESCA components and should not be used by any other element. Conflicts with your current network configuration will cause system malfunctions.

You can change the ranges of the IP addresses by setting the --pods-cidr and --services-cidr options when generating the configuration file during the installation process.

Each of these two ranges must be a /20 or larger, that is at least 4096 addresses. A smaller range is rejected during the installation.

If those forbidden CIDRs are problematic for you, contact Scality Support.

  • ARTESCA single node is delivered as a single VM packed in an .ova file to be deployed in a VMware vSphere environment.

  • ARTESCA-demo.ova must not be used for production.

    Both are built and tested on vSphere 8.0, and the VM’s Hardware version is 17 (vmx-17), which is supported by ESXi 7.0 and later versions.

  • The Virtual Appliance provides a single VM ARTESCA system. If you want to deploy a multiple VM ARTESCA cluster, you need to deploy ARTESCA as a Software Appliance on mulitple VMs. For more information, refer to Virtual Machine Node Preparation.

  • The Virtual Appliance for demo (ARTESCA-demo.ova) provides less than 100 GB of usable capacity for ARTESCA.

  • The Hypervisor must have intel CPU Haswell and Later (Ex-xxx v3 +) or AMD CPU Jaguar or later (grep sse4_1 /proc/cpuinfo | grep sse4_2 | grep movbe | grep pclmulqdq).

  • VMware vSphere 7.0 or higher must be deployed.

Virtual Appliance Sizing for Demo

Hardware requirements

minimum

recommended (defaults)

vCPU

8

12

RAM

32 GB

64 GB

Storage

480 GB using Thin Provisioning

Network Considerations

Refer to Network Considerations for more information.

Since the ARTESCA+ Veeam Unified Software Appliance is a nested virtual machine, it requires nested virtualization support.

The OVA provides a pre-configured virtual machine with hardware virtualization extensions enabled, a feature essential for nested virtualization. This setting is located in the virtual machine configuration (CPU/Hardware virtualization checkbox) and is usually called Virtualization Extensions or VT-x/AMD-V.

Since the nested virtual machine uses a bridge network adapter, you must also enable the Promiscuous Mode and Forged transmits options on the network adapter.

There are two ways to enable this on your virtualized network:

  • Virtual Machine Port Group Level (Recommended):

    • For Distributed Port Group (DVPG): Configure directly in the DVPG settings if using a Distributed Virtual Switch.

    • For standard Port Group (vPortGroup): Configure on each ESXi host where the ARTESCA+ Veeam Unified Software Appliance will run.

  • Virtual Switch Level (Not recommended due to security implications):

    • For Distributed Virtual Switch (DVS): Configure directly in the DVS settings.

    • For standard Virtual Switch (vSwitch): Configure on each ESXi host where the ARTESCA+ Veeam Unified Software Appliance will run.

To configure a Virtual Switch or a Port Group, you must edit their respective settings:

  1. Navigate to the Security tab.

  2. Set Promiscuous Mode to Accept.

  3. Set Forged transmits to Accept.